Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(SRRPROD). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZSRR0000). Verify that the accesses to the SRRAUDIT installation datasets are properly restricted. If the following guidance is true, this is not a finding. The 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. The ACF2 dataset rules for the datasets do not restrict WRITE and/or greater access to systems programming personnel. The ACF2 dataset rules for the datasets do not specify that all (i.e., failures and successes) WRITE and/or greater access will be logged.
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. The 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. (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.) Datasets to be protected will be: SYS2.SRRAUDIT The following commands are provided as a sample for implementing dataset controls: $KEY(SYS2) SET RULE $KEY(S2S) $PREFIX(SYS2) SRRAUDIT.- UID(audtaudt) R(A) E(A) DATA(DEFAULT Auditor) SRRAUDIT.- UID(pcspaudt) R(A) E(A) DATA(DEFAULT Production control and Scheduling) SRRAUDIT.- UID(secaaudt) R(A) E(A) DATA(DEFAULT Security) SRRAUDIT.- UID(syspaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT SYSPROG) SRRAUDIT.- UID(tstcaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT Trusted STCs)
Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(SRRUSER). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZSRR0002). Verify that access to the SRRAUDIT User datasets is properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset rules for the datasets restrict READ and/or greater access to systems programming personnel, security personnel, and auditors. The ACF2 dataset rules for the datasets do not specify that all (i.e., failures and successes) WRITE and/or greater access will be logged.
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. The 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. Dataset prefix to be protected will be: SYS3.SRRAUDIT If doing a full SRR review using the z/OS STIG Instruction, the following dataset prefix to be protected will be: SYS3.FSO The following commands are provided as a sample for implementing dataset controls: SET RULE $KEY(S3S) $PREFIX(SYS3) SRRAUDIT.- UID(syspaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT SYSPROG) SRRAUDIT.- UID(secaaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT Security) SRRAUDIT.- UID(audtaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT Auditor) $KEY(S3F) $PREFIX(SYS3) FSO- UID(syspaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT SYSPROG) FSO- UID(secaaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT Security) FSO- UID(audtaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT Auditor)