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

Check text

Interview the systems programmer responsible for the BMC CONTROL-M. Determine if the site has modified the following security exit(s): CTMSE01 CTMSE02 CTMSE08 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.

V-224396 in V7R2

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CTMRPT). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTM0000). Verify that the accesses to the BMC CONTROL-M installation data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The RACF data 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 RACF data set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The RACF data set access authorizations specify that all (i.e., failures and successes) WRITE and/or greater access are logged. ___ The RACF data set access authorizations specify UACC(NONE) and NOWARNING.

Fix text

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-M installation data sets 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 data sets and categorize them according to who will have updateWRITE and/or altergreater access and if required 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 sets, 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 data sets and/or data set prefixes identified below are examples of a possible installation. The actual data 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.) Data sets to be protected will be: SYS2.IOA.*.CTMI. The following commands are provided as a sample for implementing data set controls: ad 'SYS2.IOA.*.CTMI.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('BMC CONTROL-M Install DS') pe 'SYS2.IOA.*.CTMI.**' id(&ltsyspaudt>) acc(a) pe 'SYS2.IOA.*.CTMI.**' id(&ltaudtaudt>) acc(r) pe 'SYS2.IOA.*.CTMI.**' id(&ltautoaudt>) acc(r) pe 'SYS2.IOA.*.CTMI.**' id(&ltbmcuser>) acc(r) pe 'SYS2.IOA.*.CTMI.**' id(&ltdpcsaudt>) acc(r) pe 'SYS2.IOA.*.CTMI.**' id(&ltoperaudt>) acc(r) pe 'SYS2.IOA.*.CTMI.**' id(&ltpcspaudt>) acc(r) pe 'SYS2.IOA.*.CTMI.**' id(CONTROLM) acc(r) setr generic(dataset)

V-224397 in V7R2

Check text

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

Fix text

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-M STC data sets 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 data sets and categorize them according to who will have updateWRITE and/or altergreater access and if required 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 sets, 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 data sets and/or data set prefixes identified below are examples of a possible installation. The actual data 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.) Data sets to be protected will be: SYS3.IOA.*.CTMO. The following commands are provided as a sample for implementing data set controls: ad 'SYS3.IOA.*.CTMO.**' uacc(none) owner(sys3) - audit(failures(read)) - data('BMC ControlM Started Task DS') pe 'SYS3.IOA.*.CTMO.**' id(&ltsyspaudt> &lttstcaudt>) acc(a) pe 'SYS3.IOA.*.CTMO.**' id(CONTROLM CONTDAY &ltautoaudt> &ltoperaudt> &ltpcspaudt>) acc(u) pe 'SYS3.IOA.*.CTMO.**' id(&ltaudtaudt> &ltbmcuser>) acc(r) setr generic(dataset) refresh

V-224398 in V7R2

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CTMUSER). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTM0002). Verify that the accesses to the BMC CONTROL-M User data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The RACF data set access authorizations restrict READ access to auditors. ___ The RACF data set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The RACF data set access authorizations restrict WRITE and/or greater access to the BMC STCs and/or batch users. ___ The RACF data set access authorizations restrict UPDATE access to the BMC Users, operations, and production control and scheduling personnel (both domain level and Application level). ___ The RACF data set rules for the data sets specify UACC(NONE) and NOWARNING.

Fix text

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-M User data sets 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 Application level). READ access can be given to auditors. The installing systems programmer will identify and document the product data sets and categorize them according to who will have updateWRITE and/or altergreater access and if required 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 sets, 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 data sets and/or data set prefixes identified below are examples of a possible installation. The actual data 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.) Data sets to be protected will be: SYS3.IOA.*.CTMC. The following commands are provided as a sample for implementing data set controls: ad 'SYS3.IOA.*.CTMC.**' uacc(none) owner(sys3) - audit(failures(read)) - data('ControlM Repository Dataset') pe 'SYS3.IOA.*.CTMC.**' id(&ltsyspaudt>) acc(a) pe 'SYS3.IOA.*.CTMC.**' id(BMC STCs) acc(a) pe 'SYS3.IOA.*.CTMC.**' id(&ltbmcuser> &ltoperaudt> &ltpcspaudt> &ltdpcsaudt>) acc(u) pe 'SYS3.IOA.*.CTMC.**' id(&ltaudtaudt>) acc(r) setr generic(dataset) refresh

V-224399 in V7R2

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CTMJCL). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTM0003). Verify that the accesses to the BMC CONTROL-M User/Application JCL data 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 RACF data set access authorizations restrict READ access to auditors, automated batch user(s), BMC user(s), and operations. ___ The RACF data set access authorizations restrict WRITE and/or greater access to BMC CONTROL-M administrators and systems programming personnel. ___ The RACF data set access authorizations restrict UPDATE access to the Production Control and Scheduling personnel (both domain level and Application 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 sets. Note: UpdateWRITE and/or greater access of the site's DASD Administrator Batch Processing JCL and Procedures must be limited to only the LPAR level DASD Administrators. UpdateWRITE and/or greater 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 data sets be created, one of which that contains JCL and Procedures that are considered restricted, and this data set be authorized to those users with justification to maintain and run these restricted JCL and Procedures. ___ The RACF data set access authorizations specify UACC(NONE) and NOWARNING.

Fix text

Ensure that updateWRITE and/or altergreater access to BMC CONTROL-M User/Application JCL data sets are limited to BMC CONTROL-M administrators only. Update access can be given to the Production Control and Scheduling personnel and/or BMC CONTROL-M's STC(s) and/or BMC CONTROL-M's batch user(s). ReadREAD access can be given to auditors and automated batch user(s). The installing systems programmer will identify and document the product data sets and categorize them according to who will have updateWRITE and/or altergreater access and if required 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 sets, and once documented will work with the ISSO to see that they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: IOA.** The following commands are provided as a sample for implementing data set controls: ad 'IOA.**' uacc(none) owner(IOA) - data('ControlM User Datasets') pe 'IOA.**' id(&ltsyspaudt>) acc(a) pe 'IOA.**' id(&ltaudtaudt> &ltautoaudt>) acc(r) pe 'IOA.**' id(&ltbmcuser> &ltbmcbatch> &ltoperaudt> &ltpcspaudt>) acc(r) pe 'IOA.**' id(CONTROLM CONTDAY) acc(r) setr generic(dataset) refresh

V-224400 in V7R2

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ZCTM0020). Automated Analysis Refer to the following report produced by the Data 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 RACF resources are defined with a default access of NONE. ___ The RACF resource access authorizations restrict access to the appropriate personnel. ___ The RACF resource logging requirements are specified. ___ The RACF resource access authorizations are defined with UACC(NONE) and NOWARNING.

V-224401 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 RACF Data Collection: - RACFCMDS.RPT(LISTUSER). TheVerify that the userid(s) for the BMC CONTROL-M started task(s) and/oris batch job userid(sare) isproperly defined. andIf isthe assignedfollowing theattributes RACFare PROTECTEDdefined, attributethis is not a finding. PROTECTED

Fix text

The BMC CONTROL-M system 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. A sample is provided here: au CONTROLM name('stc, BMC CONTROL-M') owner(stc) dfltgrp(stc) nopass

Discussion

BMC CONTROL-M requires a started task that will be restricted to certain resources, datasetsdata sets, 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-224402 in V7R2

Check text

Refer to the following report produced by the RACF Data Collection: - DSMON.RPT(RACSPT). Automated Analysis Refer to the following report produced by the RACF Data Collection: - PDI(ZCTM0032). Verify that the BMC CONTROL-M started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is a finding.

Fix text

The BMC CONTROL-M system programmer and the IAOISSO will ensure that a product's started task(s) is (are) properly identified and/or defined to the System ACP. A unique userid must be assigned for the BMC CONTROL-M started task(s) thru a corresponding STARTED class entry. The following sample set of commands is shown here as a guideline: rdef started CONTROLM.** uacc(none) owner(admin) audit(all(read)) stdata(user(CONTROLM) group(stc)) setr racl(started) ref

Discussion

Access to product resources shouldmust be restricted to only those individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could potentially compromise the operating system, ACP, and customer data.

V-224403 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). TheIf the following keywords willspecify 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 RACJCARD U MSUBCHK NO

V-224404 in V7R2