Rule ID
SV-224460r1145211_rule
Version
V7R2
Catalog Solutions can run with sensitive system privileges, and potentially can circumvent system controls. Failure to properly control access to product resources could result in the compromise of the operating system environment, and compromise the confidentiality of customer data. Many utilities assign resource controls that can be granted to systems programmers only in greater than read authority. Resources are also granted to certain non-systems personnel with read only authority.
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ZCSL0020). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCSL0020). Verify that all Catalogued Solutions resources and/or generic equivalents are properly protected according to the requirements specified in Catalogued Solutions Resources table in the z/OS STIG Addendum. If the following guidance is true, this is not a finding. The RACF resource access authorizations restrict access to the appropriate personnel. The RACF resource logging is correctly specified. The RACF resource access authorizations are defined with UACC(NONE) and NOWARNING.
The ISSO will work with the systems programmer to verify that the following are properly specified in the ACP. (Note: The resource class, resources, and/or resource prefixes identified below are examples of a possible installation. The actual resource class, resources, and/or resource prefixes are determined when the product is actually installed on a system through the product's installation guide and can be site specific.) Ensure that all Catalogued Solutions resources and/or generic equivalents are properly protected according to the requirements specified in Catalogued Solutions Resources table in the z/OS STIG Addendum. Use Catalog Solutions Resources table in the z/OS STIG Addendum. This table lists the resources, access requirements, and logging requirements for Catalogued Solutions. Ensure the following guidelines are followed: The RACF resource access authorizations restrict access to the appropriate personnel. The RACF resource logging is correctly specified. The RACF resource access authorizations specify UACC(NONE) and NOWARNING. The following commands are provided as a sample for implementing resource controls: RDEF FACILITY hlq1.** UACC(NONE) OWNER(syspaudt) AUDIT(ALL(READ)) RDEF FACILITY hlq1.hlq2.GLOBAL.DATASET.** UACC(NONE) OWNER(syspaudt) AUDIT(ALL(READ)) PERMIT hlq1.hlq2.GLOBAL.DATASET CLASS(FACILITY) ACCESS(READ) ID(dasdaudt) PERMIT hlq1.hlq2.GLOBAL.DATASET CLASS(FACILITY) ACCESS(READ) ID(dasbaudt) PERMIT hlq1.hlq2.GLOBAL.DATASET CLASS(FACILITY) ACCESS(READ) ID(syspaudt)