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

Title

BMC CONTROL-M 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(CTMRPT). Automated Analysis Refer to the following report produced by the Datadataset Set and Resource Data Collection: - PDI(ZCTM0000). Verify that the accesses to the BMC CONTROL-M installation 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, automated operations, BMC users, operations, production control and scheduling personnel (domain level and decentralized), and BMC STCs and/or batch users. ___ The ACF2 datadataset set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The ACF2 datadataset set access authorizations 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-M 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, automated operations, BMC users, operations, production control and scheduling personnel (domain level and decentralized), 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 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: SYS2.IOA.*.CTMI. The following commands are provided as a sample for implementing datadataset set controls: $KEY(SYS2) IOA.-.CTMI.- UID(&ltsyspaudt>) R(A) W(L) A(L) E(A) IOA.-.CTMI.- UID(&ltaudtaudt>) R(A) E(A) IOA.-.CTMI.- UID(&ltautoaudt>) R(A) E(A) IOA.-.CTMI.- UID(&ltbmcuser>) R(A) E(A) IOA.-.CTMI.- UID(&ltdpcsaudt>) R(A) E(A) IOA.-.CTMI.- UID(&ltoperaudt>) R(A) E(A) IOA.-.CTMI.- UID(&ltpcspaudt>) R(A) E(A) IOA.-.CTMI.- UID(CONTROLM) R(A) E(A)

Discussion

BMC CONTROL-M 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-224114 in V7R2

Title

BMC CONTROL-M STC data sets will be properly protected.

Check text

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

Fix text

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-M STC datadatasets setsis are limited to systems programmers only. UPDATE access can be given to scheduled batch jobs, operations, and production control and scheduling personnel, BMC STCs, and/or batch users. READ access can be given to auditors and/or BMC users. 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 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.*.CTMO. The following commands are provided as a sample for implementing datadataset set controls: $KEY(SYS3) IOA.-.CTMO.- UID(&ltsyspaudt>) R(A) W(A) A(A) E(A) IOA.-.CTMO.- UID(&lttstcaudt>) R(A) W(A) A(A) E(A) IOA.-.CTMO.- UID(CONTDAY) R(A) W(A) E(A) IOA.-.CTMO.- UID(CONTROLM) R(A) W(A) E(A) IOA.-.CTMO.- UID(&ltautoaudt>) R(A) W(A) E(A) IOA.-.CTMO.- UID(&ltoperaudt>) R(A) W(A) E(A) IOA.-.CTMO.- UID(&ltpcspaudt>) R(A) W(A) E(A) IOA.-.CTMO.- UID(&ltaudtaudt>) R(A) E(A) IOA.-.CTMO.- UID(&ltbmcuser>) R(A) E(A)

Discussion

BMC CONTROL-M 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-224115 in V7R2

Title

BMC CONTROL-M User data sets will be properly protected.

Check text

Refer to the following report produced by the Datadataset Set and Resource Data Collection: - SENSITVE.RPT(CTMUSER). Automated Analysis Refer to the following report produced by the Datadataset Set and Resource Data Collection: - PDI(ZCTM0002). Verify that the accesses to the BMC CONTROL-M User 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. ___ The ACF2 datadataset set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The ACF2 datadataset set access authorizations restrict WRITE and/or greater access to the BMC STCs and/or batch users. ___ The ACF2 access authorizations restrict UPDATE access to the BMC Users, operations, and production control and scheduling personnel (both domain level and Applicationapplication level).

Fix text

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-M User datadatasets setsis are limited to systems programmers and/or BMC STCs and/or batch users only. UPDATE access can be given to the BMC Users, operations, and production control and scheduling personnel (both domain level and Applicationapplication level). READ access can be given to auditors. 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 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.*.CTMC. The following commands are provided as a sample for implementing datadataset set controls: $KEY(SYS3) IOA.-.CTMC.- UID(&ltsyspaudt>) R(A) W(A) A(A) E(A) IOA.-.CTMC.- UID(BMC STCs) R(A) W(A) A(A) E(A) IOA.-.CTMC.- UID(&ltbmcuser>) R(A) W(A) E(A) IOA.-.CTMC.- UID(&ltoperaudt>) R(A) W(A) E(A) IOA.-.CTMC.- UID(&ltpcspaudt>) R(A) W(A) E(A) IOA.-.CTMC.- UID(&ltdpcsaudt>) R(A) W(A) E(A) IOA.-.CTMC.- UID(&ltaudtaudt>) R(A) E(A)

Discussion

BMC CONTROL-M User data setsdatasets, Repository, 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-224116 in V7R2

Title

BMC CONTROL-M User/Application JCL data sets must be properly protected.

Check text

Refer to the following report produced by the Datadataset Set and Resource Data Collection: - SENSITVE.RPT(CTMJCL). Automated Analysis Refer to the following report produced by the Datadataset Set and Resource Data Collection: - PDI(ZCTM0003). Verify that the accesses to the BMC CONTROL-M User/Application JCL datadatasets sets are limited to only those who require access to perform their job duties. If the following guidance is true, this is not a finding. ___ The ACF2 datadataset set access authorizations restrict READ access to auditors, automated batch user(s), BMC user(s), and operations. ___ The ACF2 datadataset set access authorizations restrict WRITE and/or greater access to BMC CONTROL-M administrators and systems programming personnel. ___ The ACF2 datadataset set access authorizations restrict UPDATE access to the Productionproduction Controlcontrol and Schedulingscheduling personnel (both domain level and Applicationapplication level) and BMC STCs and/or batch users. Accesses must be reviewed and approved by the ISSO based on a documented need to perform job duties. Application (external users) will not have access to internal/site data setsdatasets. Note: Update access of the site's DASD Administrator Batch Processing JCL and Procedures must be limited to only the LPAR level DASD Administrators. Update access of the site's (LPAR Level) IA (Security) administrative batch processing JCL and Procedures must be limited to only the LPAR LEVEL ISSO/ISSM Team. It is recommended that multiple datadatasets sets be created, one of which that contains JCL and Procedures that are considered restricted, and this datadataset set be authorized to those users with justification to maintain and run these restricted JCL and Procedures.

Fix text

Ensure that WRITE and/or greater access to BMC CONTROL-M User/Application JCL datadatasets setsis are limited to systems programmers and/or BMC administrators only. UPDATE access can be given to the production control and scheduling personnel (both domain level and Applicationapplication level) and BMC STCs and/or batch users. READ access can be given to auditors, automated batch user(s), BMC users, and operations. Access will be based on a documented need to know requirement. Application (external users) will not have access to internal/site data setsdatasets. 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 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: IOA. The following commands are provided as a sample for implementing datadataset set controls: $KEY(IOA) - UID(&ltbmcadmin>) R(A) W(A) A(A) E(A) - UID(&ltsyspaudt>) R(A) W(A) A(A) E(A) - UID(&lttstcaudt>) R(A) W(A) A(A) E(A) - UID(CONTDAY) R(A) W(A) E(A) - UID(CONTROLM) R(A) W(A) E(A) - UID(&ltdpcsaudt>) R(A) W(A) E(A) - UID(&ltpcspaudt>) R(A) W(A) E(A) - UID(&ltaudtaudt>) R(A) E(A) - UID(&ltautoaudt>) R(A) E(A) - UID(&ltbmcuser>) R(A) E(A) - UID(&ltoperaudt>) R(A) E(A)

Discussion

BMC CONTROL-M User/Application JCL 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-224117 in V7R2

Check text

Refer to the following report produced by the ACF2 Data Collection and Datadataset Set and Resource Data Collection: - SENSITVE.RPT(ZCTM0020). - ACF2CMDS.RPT(RESOURCE) - Alternate report. Automated Analysis Refer to the following report produced by the Datadataset Set and Resource Data Collection: - PDI(ZCTM0020). Verify that the accesses to resources and/or generic equivalent are properly restricted according to the requirements specified in BMC CONTROL-M 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

Verify that the following are properly specified in the 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-M 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. Note: It is the responsibility of the ISSM to determine and document appropriate personnel for access in accordance with DoD 8500.1 para 18(a),(b),(c). The following commands are provided as a sample for implementing resource controls: $key($$ctmpnl3) type(ioa) - uid(BMC STCs) allow - uid(&ltoperaudt>) allow - uid(&ltpcspaudt>) allow - uid(&ltsyspaudt>) allow - uid(*) prevent

V-224118 in V7R2

Title

BMC CONTROL-M Started Task name is not properly identified / defined to the system ACP.

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-M 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-M 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 CONTROLM STC MUSASS NO-SMC

Discussion

BMC CONTROL-M 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-224119 in V7R2

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(ZCTM0040). The following keywords will have the specified values in the BMC CONTROL-M security parameter member:. This is not a finding. Keyword Value DEFMCHKM $$CTMEDM SECTOLM NO DFMM01 EXTEND DFMM02 EXTEND DFMM08 EXTEND SAFJCARD U MSUBCHK NO

V-224120 in V7R2