z/OS BMC CONTROL-D for RACF STIG Version Comparison

There are 1 differences between versions v6 r6 (Jan. 20, 2015) (the "left" version) and v6 r8 (Nov. 23, 2022) (the "right" version).

Check ZCTDR020 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.

Title

BMC CONTROL-D resources will must be properly defined and protected.

Check Content

Refer to the following report produced by the Data Set and Resource Data Collection: - Collection: - SENSITVE.RPT(ZCTD0020) Automated SENSITVE.RPT(ZCTD0020) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTD0020) Verify Collection: - PDI(ZCTD0020) Verify that the accesses to resources and/or generic equivalent are properly restricted according to the requirements specified in BMC CONTROL-D Resources table in the z/OS STIG Addendum. If the following guidance is true, this is not a finding. Note: To finding. Note: To determine what resource class is used review the IOACLASS setting in SECPARM. ___ The SECPARM. The "Trigger" resources i.e., $$SECxxx (xxx is unique to the product) are defined in the FACILITY resource class ___ The RACF resources are defined with a default access of NONE. ___ The NONE. ___ The RACF resource access authorizations restrict access to the appropriate personnel. ___ The personnel. ___ The RACF resource logging requirements are specified. ___ The specified. ___ The RACF resource access authorizations are defined with UACC(NONE) and NOWARNING.

Discussion

BMC CONTROL-D 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 systems programmers only in greater than read authority. Resources are also granted to certain non systems personnel with read only authority.

Fix

The IAO ISSO will work with the systems programmer to verify that the following are properly specified in the ACP. Note: To ACP. Note: To determine what resource class is used review the IOACLASS setting in SECPARM. (Note: SECPARM. The "Trigger" resources i.e., $$SECxxx (xxx is unique to the product) are defined in the FACILITY resource class (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 product's installation guide and can be site specific.) Use BMC CONTROL-D Resources and BMC INCONTROL Resources Descriptions tables in the zOS STIG Addendum. These tables list the resources, descriptions, and access and logging requirements. Ensure the guidelines for the resources and/or generic equivalent specified in the z/OS STIG Addendum are followed. The following commands are provided as a sample for implementing resource controls: rdef $ioa $$addnot.** uacc(none) owner(admin) - – audit(failure(read)) audit(failure(read)) - - data('protected data('protected per zctdr020') pe $$addnot.** cl($ioa) id(<appsaudt>) acc(alter) pe $$addnot.** cl($ioa) id(<operaudt>) acc(alter) pe $$addnot.** cl($ioa) id(<pcspaudt>) acc(alter) pe $$addnot.** cl($ioa) id(<syspaudt>) acc(alter)