z/OS SRRAUDIT for TSS STIG Version Comparison
z/OS SRRAUDIT for TSS Security Technical Implementation Guide
Comparison
There are 1 differences between versions v6 r4 (Jan. 20, 2015) (the "left" version) and v6 r5 (Nov. 23, 2022) (the "right" version).
Check ZSRRT000 was changed between these two versions. Green, underlined text was added, red, struck-out text was removed.
The regular view of the left check and right check may be easier to read.
Text Differences
Title
SRRAUDIT installation data sets must be properly protected.
Check Content
Refer to the following report produced by the Data Set and Resource Data Collection: - Collection: - SENSITVE.RPT(SRRPROD) Automated SENSITVE.RPT(SRRPROD) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZSRR0000) Verify 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 finding. ___ The TSS data set access authorizations restricts READ access to systems programming personnel, domain level production control and scheduling personnel, security personnel, and auditors. ___ The auditors. ___ The TSS data set access authorizations restricts WRITE and/or greater access to systems programming personnel. ___ The personnel. ___ The TSS data set access authorizations specify that all (i.e., failures and successes) WRITE and/or greater accesses are logged.
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.
Fix
The IAO ISSO will ensure WRITE and/or greater access to SRRAUDIT installation data sets is limited to System systems Programmers 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 systems Programmer 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. He The installing systems programmer will identify if any additional groups have WRITE and/or greater access for specific data sets, and once documented he will work with the IAO ISSO to ensure see that they are properly restricted to the ACP (Access Control Program) 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 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)