What changed in z/OS BMC CONTROL-O for ACF2 STIG V7R2V7R2 changes

Check text

Refer to the following applicable reports produced by the z/OS Data Collection: - IOA.RPT(SECPARM). Automated Analysis Refer to the following report produced by the z/OS Data Collection: - PDI(ZCTO0040). The following keywords will have the specified values in the BMC CONTROL-O security parameter member:. This is not a finding. Keyword Value DEFMCHKO $$CTOEDM SECTOLO NO DFMO01 EXTEND DFMO02 EXTEND DFMO03 EXTEND DFMO04 EXTEND DFMO08 EXTEND DFMO10 PROD (new for 6.3.xx) DFMO15 EXTEND

Fix text

The BMC CONTROL-O systems programmer will verify that any configuration/parameters that are required to control the security of the product are properly configured and syntactically correct. Set the standard values for the BMC CONTROL-O security parameters for the specific Access Control Program (ACP) environment along with additional IOA security parameters with standard values as documented below. Keyword Value DEFMCHKO $$CTOEDM SECTOLO NO DFMO01 EXTEND DFMO02 EXTEND DFMO03 EXTEND DFMO04 EXTEND DFMO08 EXTEND DFMO10 PROD (new for 6.3.xx) DFMO15 EXTEND

V-224123 in V7R2

Check text

Refer to the following applicable reports produced by the z/OS Data Collection: - IOA.RPT(CTOPARM). Automated Analysis Refer to the following report produced by the z/OS Data Collection: - PDI(ZCTO0041). The following keywords will have the specified values in the BMC CONTROL-O security parameter member:. This is not a finding. Keyword Value RUNTDFT OWNER RUNTCACH 100 AUTOMLOG V

Fix text

The BMC CONTROL-O systems programmer will verify that any configuration/parameters that are required to control the security of the product are properly configured and syntactically correct. Set the standard values for the BMC CONTROL-O security parameters for the specific Access Control Program (ACP) environment along with additional IOA security parameters with standard values as documented below. Keyword Value RUNTDFT OWNER RUNTCACH 100 AUTOMLOG V

V-224124 in V7R2

Check text

Interview the systems programmer responsible for the BMC CONTROL-O. Determine if the site has modified the following security exit(s): CTOSE01 CTOSE02 CTOSE03 CTOSE04 CTOSE08 CTOSE10 CTOSE15 EnsureVerify the above security exit(s) has (have) not been modified. If the above security exit(s) has (have) been modified, ensureverify that the security exit(s) has (have) been approved by the site systems programmer and the approval is on file for examination.

Fix text

The systemsystems programmer responsible for the BMC CONTROL-O will review the BMC CONTROL-O operating environment. Ensure that the following security exit(s) is (are) installed properly. Determine if the site has modified the following security exit(s): CTOSE01 CTOSE02 CTOSE03 CTOSE04 CTOSE08 CTOSE10 CTOSE15 Ensure that the security exit(s) has (have) not been modified. If the security exit(s) has (have) been modified, ensure the security exit(s) has (have) been checked as to not violate any security integrity within the system and approval documentation is on file.

V-224125 in V7R2

Title

BMC CONTROL-O installation data sets will be properly protected.

Check text

Refer to the following report produced by the Datadataset Set and Resource Data Collection: - SENSITVE.RPT(CTORPT). Automated Analysis Refer to the following report produced by the Datadataset Set and Resource Data Collection: - PDI(ZCTO0000). Verify that the accesses to the BMC CONTROL-O installation datadatasets sets are properly restricted. If the following guidance is true, this is not a finding. The ACF2 datadataset set rules for the datadatasets setsrestrict restricts READ access to auditors, BMC users, and BMC STCs and/or batch users. The ACF2 datadataset set rules for the datadatasets setsrestrict restricts WRITE and/or greater access to systems programming personnel. The ACF2 datadataset set rules for the datadatasets sets specify that all (i.e., failures and successes) WRITE and/or greater access areis logged.

Fix text

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-O installation datadatasets setsis are limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to auditors, BMC users, and BMC STCs and/or batch users. All failures and successful WRITE and/or greater accesses are logged. The installing systems programmer will identify and document the product datadatasets, sets and categorize them according to who will have updateWRITE and/or altergreater access, and if required, ensure that all updateWRITE and/or allocategreater access is logged. The installing systems programmer will identify if any additional groups have updateWRITE and/or altergreater access for specific data setsdatasets, and once documented, will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system. (Note: The datadatasets sets and/or datadataset set prefixes identified below are examples of a possible installation. The actual datadatasets 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.) DataDatasets sets to be protected will be: SYS2.IOA.*.CTOI. The following commands are provided as a sample for implementing datadataset set controls: $KEY(SYS2) IOA.-.CTOI.- UID(&ltsyspaudt>) R(A) W(L) A(L) E(A) IOA.-.CTOI.- UID(&ltaudtaudt>) R(A) E(A) IOA.-.CTOI.- UID(&ltbmcuser>) R(A) E(A) IOA.-.CTOI.- UID(CONTROLO) R(A) E(A)

Discussion

BMC CONTROL-O installation datadatasets sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datadatasets sets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.

V-224126 in V7R2

Title

BMC CONTROL-O STC data sets must be properly protected.

Check text

Refer to the following report produced by the Datadataset Set and Resource Data Collection: - SENSITVE.RPT(CTOSTC). Automated Analysis Refer to the following report produced by the Datadataset Set and Resource Data Collection: - PDI(ZCTO0001). Verify that the accesses to the BMC CONTROL-O STC datadatasets sets are properly restricted. If the following guidance is true, this is not a finding. ___ The ACF2 datadataset set access authorizations restrict READ access to auditors, operators, and domain level production control and scheduling personnel. ___ The ACF2 datadataset set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The ACF2 datadataset set access authorizations restrict UPDATE access to the BMC users and BMC STCs and/or batch users.

Fix text

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-O STC datadatasets sets are limited to systems programmers only. UPDATE access can be given to BMC users and the BMC STCs and/or batch users. READ access can be given to auditors, operators, and domain level production control and scheduling personnel. The installing systems programmer will identify and document the product datadatasets sets and categorize them according to who will have what type of access and if required which type of access is logged. The installing systems programmer will identify any additional groups requiring access to specific data setsdatasets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system. (Note: The datadatasets sets and/or datadataset set prefixes identified below are examples of a possible installation. The actual datadatasets 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.) DataDatasets sets to be protected will be: SYS3.IOA.*.CTOO. The following commands are provided as a sample for implementing datadataset set controls: $KEY(SYS3) IOA.-.CTOO.- UID(&ltsyspaudt>) R(A) W(A) A(A) E(A) IOA.-.CTOO.- UID(CONTROLO) R(A) W(A) E(A) IOA.-.CTOO.- UID(&ltbmcuser>) R(A) W(A) E(A) IOA.-.CTOO.- UID(&ltaudtaudt>) R(A) E(A) IOA.-.CTOO.- UID(&ltoperaudt>) R(A) E(A) IOA.-.CTOO.- UID(&ltpcspaudt>) R(A) E(A)

Discussion

BMC CONTROL-O STC datadatasets sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datadatasets sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.

V-224127 in V7R2

Check text

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

Fix text

The ISSO will work with the systems programmer to verify that the following are properly specified in the Access Control Program (ACP). Note: To determine what resource class is used review the IOACLASS setting in 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 installation guide and can be site specific.) Use BMC CONTROL-O Resources and BMC INCONTROL Resources Descriptions tables in the z/OS 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: $key($$ctoaop) type(ioa) - uid(&ltoperaudt>) log - uid(&ltpcspaudt>) log - uid(&ltprodaudt>) log - uid(&ltsyspaudt>) log - uid(*) prevent

Discussion

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

V-224128 in V7R2

Check text

Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(ATTSTC). InsureEnsure that the logonids(s) for the BMC CONTROL-O started task(s) includes the following:. If the following attributes are defined, this is not a finding. STC MUSASS NO-SMC

Fix text

The BMC CONTROL-O systemsystems programmer and the IAOISSO will ensure that a product's Started Task(s) is properly Identified / defined to the System ACP. If the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes. Most installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified. Example: SET LID CHANGE CONTROLO STC MUSASS NO-SMC

Discussion

BMC CONTROL-O requires a started task that will be restricted to certain resources, datasets, and other system functions. ByDefining defining the started task as a userid to the system ACP, It allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities, could compromise of the operating system environment, ACP, and customer data.

V-224129 in V7R2