What changed in z/OS SRRAUDIT for TSS STIG V7R1V7R1 changes

z/OS SRRAUDIT for TSS STIG V7R1 (2025-04-02) replaced V6R5 (2022-11-23): 2 checks updated. It has 2 checks, against 2 in V6R5.

  • 0 added
  • 0 removed
  • 2 updated

Updated fields: Check text 2Fix text 2CCIs 1Discussion 1

Updated in V7R1 (2)

V-225606CAT IISRRAUDIT installation data sets must be properly protected.Check text, Fix text, Discussion, CCIs

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(SRRPROD). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZSRR0000). Verify that the accesses to the SRRAUDIT installation data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The TSS data set access authorizations restrictsrestrict READ access to systems programming personnel, domain level production control and scheduling personnel, security personnel, and auditors. ___ The TSS data set access authorizations restrictsrestrict WRITE and/or greater access to systems programming personnel. ___ The TSS data set access authorizations specify that all (i.e., failures and successes) WRITE and/or greater accesses are logged.

Fix text

The ISSO will ensure WRITE and/or greater access to SRRAUDIT installation data sets is limited to systems programmers only, and all WRITE and/or greater access is logged. All failures and successful WRITE and/or greater accesses are logged. The installing systems programmer will identify and document the product data sets and categorize them according to who will have WRITE and/or greater access and, if required, 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 data sets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program (ACP) active on the system. (Note: The data sets and/or data set prefixes identified below are examples of a possible installation. The actual data sets and/or prefixes are determined when the product is actually installed on a system through the product's installation guide and can be site specific.) Data sets to be protected will be: SYS2.SRRAUDIT. The following commands are provided as a sample for implementing data set controls: TSS PERMIT(syspaudt) DSN(SYS2.SRRAUDIT.) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS2.SRRAUDIT.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(tstcaudt) DSN(SYS2.SRRAUDIT.) ACCESS(R) TSS PERMIT(tstcaudt) DSN(SYS2.SRRAUDIT.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(audtaudt) DSN(SYS2.SRRAUDIT.) ACCESS(R) TSS PERMIT(pcspaudt) DSN(SYS2.SRRAUDIT.) ACCESS(R) TSS PERMIT(secaaudt) DSN(SYS2.SRRAUDIT.) ACCESS(R)

Discussion

SRRAUDIT installation data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.

CCIs

CCI-000213499,CCI-002234

V-225607CAT IISRRAUDIT User data sets are not properly protected.Check text, Fix text

Check text

a) Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(SRRUSER) . Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZSRR0002). b) Verify that access to the SRRAUDIT User data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The TSS data set rules for the data sets does not restrict READ, UPDATE, and/or ALTERgreater access to systems programming personnel, security personnel, and auditors. ___ The TSS data set rules for the data sets do not specify that all (i.e., failures and successes) UPDATEWRITE and/or ALTERgreater access will be logged. b) If all of the above are untrue, there is NO FINDING. c) If any of the above is true, this is a FINDING.

Fix text

The IAOISSO will ensure that readREAD, updateUPDATE, and allocateALL access to program product user data sets is limited to Systemsystems Programmersprogrammers, Securitysecurity Personnelpersonnel, and Auditorsauditors and all updateWRITE and/or allocategreater access is logged. The installing Systemsystems Programmerprogrammer will identify and document the product user data sets and categorize them according to who will have updateWRITE and/or allocategreater access and if required that all updateWRITE and/or allocategreater access is logged. HeThe installing systems programmer will identify if any additional groups have updateUPDATE access for specific data sets, and once documented he will work with the IAOISSO to seeensure that they are properly restricted to the ACP (Access Control Program ) active on the system. Data set prefix to be protected will be: SYS3.SRRAUDIT. If doing a full SRR review using the z/OS STIG Instruction, the following data set prefix to be protected will be: SYS3.FSO. The following commands are provided as a sample for implementing datasetdata set controls: TSS ADD(SYS3) DSN(SYS3) TSS PER(syspaudt) DSN(SYS3.SRRAUDIT.) ACC(R) TSS PER(secaaudt) DSN(SYS3.SRRAUDIT.) ACC(R) TSS PER(audtaudt) DSN(SYS3.SRRAUDIT.) ACC(R) TSS PER(syspaudt) DSN(SYS3.SRRAUDIT.) ACC(A) ACTION(AUDIT) TSS PER(secaaudt) DSN(SYS3.SRRAUDIT.) ACC(A) ACTION(AUDIT) TSS PER(audtaudt) DSN(SYS3.SRRAUDIT.) ACC(A) ACTION(AUDIT) TSS PER(syspaudt) DSN(SYS3.FSO.) ACC(R) TSS PER(secaaudt) DSN(SYS3.FSO.) ACC(R) TSS PER(audtaudt) DSN(SYS3.FSO.) ACC(R) TSS PER(syspaudt) DSN(SYS3.FSO.) ACC(A) ACTION(AUDIT) TSS PER(secaaudt) DSN(SYS3.FSO.) ACC(A) ACTION(AUDIT) TSS PER(audtaudt) DSN(SYS3.FSO.) ACC(A) ACTION(AUDIT)

How these changes are found

Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V7R1 no longer has.

Comparing other releases, or this one against an older release? Pick any two in STIG Compare.