None Computing title z/OS BMC CONTROL-M for RACF Security Technical Implementation Guide version 7 releaseinfo Release: 2 Vuln_Num V-224396 Rule_ID SV-224396r1144770_rule Severity medium Rule_Title BMC CONTROL-M security exits are not installed or configured properly. Vuln_Discuss The BMC CONTROL-M security exits enable access authorization checking to BMC CONTROL-M commands, features, and online functionality. If these exit(s) is (are) not in place, activities by unauthorized users may result. BMC CONTROL-M security exit(s) interface with the ACP. If an unauthorized exit was introduced into the operating environment, system security could be weakened or bypassed. These exposures may result in the compromise of the operating system environment, ACP, and customer data. Check_Content Interview the systems programmer responsible for the BMC CONTROL-M. Determine if the site has modified the following security exit(s): CTMSE01 CTMSE02 CTMSE08 Verify the above security exit(s) has (have) not been modified. If the above security exit(s) has (have) been modified, verify 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 systems programmer responsible for the BMC CONTROL-M will review the BMC CONTROL-M operating environment. Ensure that the following security exit(s) is (are) installed properly. Determine if the site has modified the following security exit(s): CTMSE01 CTMSE02 CTMSE08 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. Not_Reviewed Vuln_Num V-224397 Rule_ID SV-224397r1145219_rule Severity medium Rule_Title BMC CONTROL-M installation data sets will be properly protected. Vuln_Discuss BMC CONTROL-M installation data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data. Check_Content 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 WRITE and/or greater access and if required that all WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have WRITE and/or greater 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(<syspaudt>) acc(a) pe 'SYS2.IOA.*.CTMI.**' id(<audtaudt>) acc(r) pe 'SYS2.IOA.*.CTMI.**' id(<autoaudt>) acc(r) pe 'SYS2.IOA.*.CTMI.**' id(<bmcuser>) acc(r) pe 'SYS2.IOA.*.CTMI.**' id(<dpcsaudt>) acc(r) pe 'SYS2.IOA.*.CTMI.**' id(<operaudt>) acc(r) pe 'SYS2.IOA.*.CTMI.**' id(<pcspaudt>) acc(r) pe 'SYS2.IOA.*.CTMI.**' id(CONTROLM) acc(r) setr generic(dataset) Not_Reviewed Vuln_Num V-224398 Rule_ID SV-224398r1145221_rule Severity medium Rule_Title BMC CONTROL-M STC data sets will be properly protected. Vuln_Discuss BMC CONTROL-M STC data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data. Check_Content 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 WRITE and/or greater access and if required that all WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have WRITE and/or greater 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(<syspaudt> <tstcaudt>) acc(a) pe 'SYS3.IOA.*.CTMO.**' id(CONTROLM CONTDAY <autoaudt> <operaudt> <pcspaudt>) acc(u) pe 'SYS3.IOA.*.CTMO.**' id(<audtaudt> <bmcuser>) acc(r) setr generic(dataset) refresh Not_Reviewed Vuln_Num V-224399 Rule_ID SV-224399r1145223_rule Severity medium Rule_Title BMC CONTROL-M User data sets will be properly protected. Vuln_Discuss BMC CONTROL-M User data sets, Repository, have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data. Check_Content 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 WRITE and/or greater access and if required that all WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have WRITE and/or greater 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(<syspaudt>) acc(a) pe 'SYS3.IOA.*.CTMC.**' id(BMC STCs) acc(a) pe 'SYS3.IOA.*.CTMC.**' id(<bmcuser> <operaudt> <pcspaudt> <dpcsaudt>) acc(u) pe 'SYS3.IOA.*.CTMC.**' id(<audtaudt>) acc(r) setr generic(dataset) refresh Not_Reviewed Vuln_Num V-224400 Rule_ID SV-224400r1145225_rule Severity medium Rule_Title BMC CONTROL-M User/Application JCL data sets must be properly protected. Vuln_Discuss BMC CONTROL-M User/Application JCL data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data. Check_Content 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: WRITE 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. WRITE 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 contains JCL and Procedures that are considered restricted, and this data set be authorized to 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 WRITE and/or greater 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). READ 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 WRITE and/or greater access and if required that all WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have WRITE and/or greater 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(<syspaudt>) acc(a) pe 'IOA.**' id(<audtaudt> <autoaudt>) acc(r) pe 'IOA.**' id(<bmcuser> <bmcbatch> <operaudt> <pcspaudt>) acc(r) pe 'IOA.**' id(CONTROLM CONTDAY) acc(r) setr generic(dataset) refresh Not_Reviewed Vuln_Num V-224401 Rule_ID SV-224401r1144784_rule Severity medium Rule_Title BMC C0NTROL-M resources must be properly defined and protected. Vuln_Discuss BMC CONTROL-M 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 systems programmers only in greater than read authority. Resources are also granted to certain non-systems personnel with read only authority. Check_Content 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. 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: rdef $ioa $$ctmpnl3.** uacc(none) owner(admin) - audit(failure(read)) - data('protected per zctmr020') pe $$ctmpnl3.** cl($ioa) id(BMC STCs) acc(alter) pe $$ctmpnl3.** cl($ioa) id(<operaudt>) acc(alter) pe $$ctmpnl3.** cl($ioa) id(<pcspaudt>) acc(alter) pe $$ctmpnl3.** cl($ioa) id(<syspaudt>) acc(alter) Not_Reviewed Vuln_Num V-224402 Rule_ID SV-224402r1144787_rule Severity medium Rule_Title BMC CONTROL-M Started Task name is not properly identified/defined to the system ACP. Vuln_Discuss BMC CONTROL-M requires a started task that will be restricted to certain resources, data sets, and other system functions. Defining the started task as a userid to the system ACP allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities could compromise the operating system environment, ACP, and customer data. Check_Content Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(LISTUSER). Verify that the userid(s) for the BMC CONTROL-M started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. PROTECTED Fix_Text The BMC CONTROL-M system programmer and the ISSO 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 Not_Reviewed Vuln_Num V-224403 Rule_ID SV-224403r1144790_rule Severity medium Rule_Title BMC CONTROL-M Started task(s) must be properly defined to the STARTED resource class for RACF. Vuln_Discuss Access to product resources must be restricted to only individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could compromise the operating system, ACP, and customer data. Check_Content 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 ISSO 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 Not_Reviewed Vuln_Num V-224404 Rule_ID SV-224404r1144792_rule Severity medium Rule_Title BMC CONTROL-M configuration/parameter values must be specified properly. Vuln_Discuss BMC CONTROL-M configuration/parameters control the security and operational characteristics of products. If these parameter values are improperly specified, security and operational controls may be weakened. This exposure may threaten the availability of the product applications, and compromise the confidentiality of customer data. Check_Content 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). If the following keywords specify the 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 Fix_Text Configure the standard values for the BMC CONTROL-M security parameters for the specific ACP environment along with additional IOA security parameters with standard values as documented below. Keyword Value DEFMCHKM $$CTMEDM SECTOLM NO DFMM01 EXTEND DFMM02 EXTEND DFMM08 EXTEND RACJCARD U MSUBCHK NO Not_Reviewed