From z/OS CL/SuperSession for RACF STIG
Part of ZB000001
Associated with: CCI-001499
CL/SuperSession STC data sets provide the capability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(KLSSTC) Automated Analysis: Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCLS0001) Verify that the accesses to the CL/SuperSession STC data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The RACF data set access authorizations restrict READ access to auditors and authorized users. ___ The RACF data set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The RACF data set rules for the data sets does not restrict WRITE and/or greater access to the product STC(s) and/or batch job(s). ___ The RACF data set access authorizations for the data sets specify UACC(NONE) and NOWARNING.
Ensure that WRITE and/or greater access to CL/SuperSession STC data sets are limited to system programmers and CL/SuperSession STC only. Read access can be given to auditors and authorized users. 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 access is logged. He will identify if any additional groups have WRITE and/or greater access for specific data sets, and once documented he will work with the ISSO to 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 installation guide and can be site specific. The following are an example of data sets to be protected: SYS3.OMEGAMON.RLSNAF SYS3.OMEGAMON.RLSNAM SYS3.OMEGAMON.RLSTDB SYS3.OMEGAMON.RLSVLOG The following commands are provided as an example for implementing dataset controls: ad 'sys3.omegamon.rlsnaf.** uacc(none) owner(sys3) - audit(failures(read)) - data('Site Customized CL/Supersession VSAM') pe 'sys3.omegamon.rlsnaf.**' id(syspaudt) acc(a) pe 'sys3.omegamon.rlsnaf.**' id(kls) acc(a) pe 'sys3.omegamon.rlsnaf.**' id(audtaudt) acc(r) pe 'sys3.omegamon.rlsnaf.**' id(*) acc(r) ad 'sys3.omegamon.rlsnam.** uacc(none) owner(sys3) - audit(failures(read)) - data('Site Customized CL/Supersession VSAM') pe 'sys3.omegamon.rlsnam.**' id(syspaudt) acc(a) pe 'sys3.omegamon.rlsnam.**' id(kls) acc(a) pe 'sys3.omegamon.rlsnam.**' id(audtaudt) acc(r) pe 'sys3.omegamon.rlsnam.**' id(*) acc(r) ad 'sys3.omegamon.rlstdb.** uacc(none) owner(sys3) - audit(failures(read)) - data('Site Customized CL/Supersession VSAM') pe 'sys3.omegamon.rlstdb.**' id(syspaudt) acc(a) pe 'sys3.omegamon.rlstdb.**' id(kls) acc(a) pe 'sys3.omegamon.rlstdb.**' id(audtaudt) acc(r) pe 'sys3.omegamon.rlstdb.**' id(*) acc(r) ad 'sys3.omegamon.rlsvlog.** uacc(none) owner(sys3) - audit(failures(read)) - data('Site Customized CL/Supersession VSAM') pe 'sys3.omegamon.rlsvlog.**' id(syspaudt) acc(a) pe 'sys3.omegamon.rlsvlog.**' id(kls) acc(a) pe 'sys3.omegamon.rlsvlog.**' id(audtaudt) acc(r) pe 'sys3.omegamon.rlsvlog.**' id(*) acc(r)
Lavender hyperlinks in small type off to the right (of CSS
class id, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle or
Accept: application/rdf+xml.
Powered by sagemincer