z/OS CA 1 Tape Management for RACF STIG Version Comparison
z/OS CA 1 Tape Management for RACF Security Technical Implementation Guide
Comparison
There are 3 differences between versions v6 r7 (April 26, 2019) (the "left" version) and v6 r9 (Oct. 27, 2021) (the "right" version).
Check ZCA1R020 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
CA 1 Tape Management command resources will must be properly defined and protected. protected
Check Content
Refer to the following report produced by the Data Set and Resource Data Collection: - Collection: - SENSITVE.RPT(CA@MD) Automated SENSITVE.RPT(CA@MD) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCA10020) Ensure Collection: - PDI(ZCA10020) Ensure that all CA 1 command resources are properly protected according to the requirements specified in CA 1 Command Resources table in the z/OS STIG Addendum. If the following guidance is true, this is not a finding. ___ The finding. ___ The RACF resources and/or generic equivalent as designated in the above table are defined with a default access of NONE. ___ The RACF resource access authorizations restrict access to the appropriate personnel as designated in the above table. ___ The table. ___ The RACF resource logging is specified as designated in the above table. ___ The table. ___ The RACF resource rules for the resources designated in the above table specify UACC(NONE) and NOWARNING. NOWARNING. __ A Deny-By-Default entry of “**” is defined with UACC(NONE) and no Access Granted.
Discussion
CA 1 Tape Management 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 system programmers only in greater than read authority. Resources are also granted to certain non systems personnel with read only authority. On-line applications offer the capabilities to directly access the CA 1 Tape Management Catalog (TMC) for query and update purposes. CA 1 special tape handling privileges offer the ability to process special tape requirements, such as BLP and foreign tapes. Uncontrolled access to these CA 1 features and facilities may threaten the integrity and availability of the CA 1 tape management system, and compromise the confidentiality of customer data.
Fix
Ensure The IAO will work with the systems programmer to verify that the following are properly specified in the ACP. Ensure that the CA 1 Tape Management command resource access is in accordance with those outlined in CA 1 Command Resources table in the zOS STIG Addendum. Use CA 1 Command Resources and CA 1 Command Resources for RACF tables in the zOS STIG Addendum. These tables list the resources, access requirements, and the resource class for CA 1 Command Resources; ensure the following guidelines are followed: The followed: The RACF resources and/or generic equivalent as designated in the above table are defined with a default access of NONE. The RACF resource access authorizations restrict access to the appropriate personnel as designated in the above table. The RACF resource logging is specified as designated in the above table. The RACF resource rules for the resources designated in the above table specify UACC(NONE) and NOWARNING. The NOWARNING. A Deny-By-Default entry of “**” is defined with UACC(NONE) and no Access Granted. The following commands are provided as a sample for implementing resource controls: RDEFINE CA@MD L0DELETE UACC(NONE) OWNER(ADMIN) AUDIT(FAILURE(READ)) PERMIT L0DELETE CLASS(CA@MD) ACCESS(READ) ID(tapeaudt)