{"stig":{"title":"z/OS SRRAUDIT for ACF2 Security Technical Implementation Guide","version":"7","release":"2"},"checks":[{"vulnId":"V-224342","ruleId":"SV-224342r1141639_rule","severity":"medium","ruleTitle":"SRRAUDIT installation datasets must be properly protected.","description":"SRRAUDIT installation datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datasets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.","checkContent":"Refer to the following report produced by the dataset and Resource Data Collection:\n\n- SENSITVE.RPT(SRRPROD).\n\nAutomated Analysis\nRefer to the following report produced by the dataset and Resource Data Collection:\n\n- PDI(ZSRR0000).\n\nVerify that the accesses to the SRRAUDIT installation datasets are properly restricted. If the following guidance is true, this is not a finding.\n \nThe ACF2 dataset rules for the datasets do not restrict READ access to systems programming personnel, domain level production control and scheduling personnel, security personnel, and auditors.\n\nThe ACF2 dataset rules for the datasets do not restrict WRITE and/or greater access to systems programming personnel.\n\nThe ACF2 dataset rules for the datasets do not specify that all (i.e., failures and successes) WRITE and/or greater access will be logged.","fixText":"The ISSO will ensure WRITE and/or greater access to SRRAUDIT installation datasets is limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to security personnel, production control and scheduling personnel, and auditors. All failures and successful WRITE and/or greater accesses are logged.\n\nThe installing systems programmer will identify and document the product datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure that all WRITE and/or greater accesses are logged. The installing systems programmer will identify if any additional groups have WRITE and/or greater access for specific datasets, and once documented, will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system.\n\n(Note: The datasets and/or dataset prefixes identified below are examples of a possible installation. The actual datasets and/or prefixes are determined when the product is installed on a system through the product's installation guide and can be site specific.)\n\nDatasets to be protected will be: \nSYS2.SRRAUDIT\n\nThe following commands are provided as a sample for implementing dataset controls: \n\n$KEY(SYS2)\nSET RULE\n$KEY(S2S)\n$PREFIX(SYS2)\nSRRAUDIT.- UID(audtaudt) R(A) E(A) DATA(DEFAULT Auditor)\nSRRAUDIT.- UID(pcspaudt) R(A) E(A) DATA(DEFAULT Production control and Scheduling)\nSRRAUDIT.- UID(secaaudt) R(A) E(A) DATA(DEFAULT Security)\nSRRAUDIT.- UID(syspaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT SYSPROG)\nSRRAUDIT.- UID(tstcaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT Trusted STCs)","ccis":["CCI-001499","CCI-002234"]},{"vulnId":"V-224343","ruleId":"SV-224343r1144089_rule","severity":"medium","ruleTitle":"SRRAUDIT User datasets are not properly protected.","description":"SRRAUDIT User datasets provide the capability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their datasets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.","checkContent":"Refer to the following report produced by the dataset and Resource Data Collection:\n\n- SENSITVE.RPT(SRRUSER).\n\nAutomated Analysis\nRefer to the following report produced by the dataset and Resource Data Collection:\n\n- PDI(ZSRR0002).\n\nVerify that access to the SRRAUDIT User datasets is properly restricted. If the following guidance is true, this is not a finding.\n\nThe ACF2 dataset rules for the datasets restrict READ and/or greater access to systems programming personnel, security personnel, and auditors.\n\nThe ACF2 dataset rules for the datasets do not specify that all (i.e., failures and successes) WRITE and/or greater access will be logged.","fixText":"The ISSO will ensure that READ, UPDATE, and ALTER access to program product user datasets is limited to systems programmers, security personnel, and auditors, and all WRITE and/or greater access is logged.\n\nThe installing systems programmer will identify and document the product user datasets and categorize them according to who will have WRITE and/or greater access and, if required, that all WRITE and/or greater access is logged. The systems programmer will identify if any additional groups have UPDATE access for specific datasets, and once documented will work with the ISSO to ensure that they are properly restricted to the ACP (Access Control Program) active on the system.\n\nDataset prefix to be protected will be:\nSYS3.SRRAUDIT\n\nIf doing a full SRR review using the z/OS STIG Instruction, the following dataset prefix to be protected will be:\nSYS3.FSO\n\nThe following commands are provided as a sample for implementing dataset controls:\n\nSET RULE\n$KEY(S3S)\n$PREFIX(SYS3)\nSRRAUDIT.- UID(syspaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT SYSPROG)\nSRRAUDIT.- UID(secaaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT Security)\nSRRAUDIT.- UID(audtaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT Auditor)\n\n$KEY(S3F)\n$PREFIX(SYS3)\nFSO- UID(syspaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT SYSPROG)\nFSO- UID(secaaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT Security)\nFSO- UID(audtaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT Auditor)","ccis":["CCI-001499"]}]}