Cyber Trackr - Free Compliance Library
Cyber Trackr
The Free Compliance Library

z/OS BMC CONTROL-M for ACF2 Security Technical Implementation Guide - V7R2

  • Version/Release: V7R2
  • Published: 2025-09-26
  • Released: 2025-10-01
  • Expand All:
  • Severity:
  • Sort:
Compare

Select any two versions of this STIG to compare the individual requirements

View

Select any old version/release of this STIG to view the previous requirements

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
b
BMC CONTROL-M security exits are not installed or configured properly.
CM-3 - Medium - CCI-001744 - V-224113 - SV-224113r1041243_rule
RMF Control
CM-3
Severity
Medium
CCI
CCI-001744
Version
ZCTM0060
Vuln IDs
  • V-224113
  • V-17985
Rule IDs
  • SV-224113r1041243_rule
  • SV-32017
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.
Checks: C-25786r1041241_chk

Interview the systems programmer responsible for the BMC CONTROL-M. Determine if the site has modified the following security exit(s): CTMSE01 CTMSE02 CTMSE08 Ensure the above security exit(s) has (have) not been modified. If the above security exit(s) has (have) been modified, ensure that the security exit(s) has (have) been approved by the site systems programmer and the approval is on file for examination.

Fix: F-25774r1041242_fix

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.

b
BMC CONTROL-M installation datasets will be properly protected.
CM-5 - Medium - CCI-001499 - V-224114 - SV-224114r1141450_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZCTMA000
Vuln IDs
  • V-224114
  • V-16932
Rule IDs
  • SV-224114r1141450_rule
  • SV-31897
BMC CONTROL-M installation datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datasets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
Checks: C-25787r1141448_chk

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

Fix: F-25775r1141449_fix

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-M installation datasets is 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 datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure 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 datasets, 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 datasets and/or dataset prefixes identified below are examples of a possible installation. The actual datasets and/or prefixes are determined when the product is installed on a system through the product's installation guide and can be site specific.) Datasets to be protected will be: SYS2.IOA.*.CTMI The following commands are provided as a sample for implementing dataset controls: $KEY(SYS2) IOA.-.CTMI.- UID(<syspaudt>) R(A) W(L) A(L) E(A) IOA.-.CTMI.- UID(<audtaudt>) R(A) E(A) IOA.-.CTMI.- UID(<autoaudt>) R(A) E(A) IOA.-.CTMI.- UID(<bmcuser>) R(A) E(A) IOA.-.CTMI.- UID(<dpcsaudt>) R(A) E(A) IOA.-.CTMI.- UID(<operaudt>) R(A) E(A) IOA.-.CTMI.- UID(<pcspaudt>) R(A) E(A) IOA.-.CTMI.- UID(CONTROLM) R(A) E(A)

b
BMC CONTROL-M STC datasets will be properly protected.
CM-5 - Medium - CCI-001499 - V-224115 - SV-224115r1141453_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZCTMA001
Vuln IDs
  • V-224115
  • V-17067
Rule IDs
  • SV-224115r1141453_rule
  • SV-31940
BMC CONTROL-M STC datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datasets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
Checks: C-25788r1141451_chk

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

Fix: F-25776r1141452_fix

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-M STC datasets is limited to systems programmers only. UPDATE access can be given to scheduled batch jobs, operations, 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 datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure 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 datasets, 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 datasets and/or dataset prefixes identified below are examples of a possible installation. The actual datasets and/or prefixes are determined when the product is installed on a system through the product's installation guide and can be site specific.) Datasets to be protected will be: SYS3.IOA.*.CTMO The following commands are provided as a sample for implementing dataset controls: $KEY(SYS3) IOA.-.CTMO.- UID(<syspaudt>) R(A) W(A) A(A) E(A) IOA.-.CTMO.- UID(<tstcaudt>) 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(<autoaudt>) R(A) W(A) E(A) IOA.-.CTMO.- UID(<operaudt>) R(A) W(A) E(A) IOA.-.CTMO.- UID(<pcspaudt>) R(A) W(A) E(A) IOA.-.CTMO.- UID(<audtaudt>) R(A) E(A) IOA.-.CTMO.- UID(<bmcuser>) R(A) E(A)

b
BMC CONTROL-M User datasets will be properly protected.
CM-5 - Medium - CCI-001499 - V-224116 - SV-224116r1141456_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZCTMA002
Vuln IDs
  • V-224116
  • V-21592
Rule IDs
  • SV-224116r1141456_rule
  • SV-32159
BMC CONTROL-M User datasets, Repository, have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datasets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
Checks: C-25789r1141454_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(CTMUSER). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZCTM0002). Verify that the accesses to the BMC CONTROL-M User datasets are properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset access authorizations restrict READ access to auditors. The ACF2 dataset access authorizations restrict WRITE and/or greater access to systems programming personnel. The ACF2 dataset 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 application level).

Fix: F-25777r1141455_fix

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-M User datasets is 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 datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure 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 datasets, 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 datasets and/or dataset prefixes identified below are examples of a possible installation. The actual datasets and/or prefixes are determined when the product is installed on a system through the product's installation guide and can be site specific.) Datasets to be protected will be: SYS3.IOA.*.CTMC The following commands are provided as a sample for implementing dataset controls: $KEY(SYS3) IOA.-.CTMC.- UID(<syspaudt>) R(A) W(A) A(A) E(A) IOA.-.CTMC.- UID(BMC STCs) R(A) W(A) A(A) E(A) IOA.-.CTMC.- UID(<bmcuser>) R(A) W(A) E(A) IOA.-.CTMC.- UID(<operaudt>) R(A) W(A) E(A) IOA.-.CTMC.- UID(<pcspaudt>) R(A) W(A) E(A) IOA.-.CTMC.- UID(<dpcsaudt>) R(A) W(A) E(A) IOA.-.CTMC.- UID(<audtaudt>) R(A) E(A)

b
BMC CONTROL-M User/Application JCL datasets must be properly protected.
CM-5 - Medium - CCI-001499 - V-224117 - SV-224117r1141459_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZCTMA003
Vuln IDs
  • V-224117
  • V-17072
Rule IDs
  • SV-224117r1141459_rule
  • SV-32215
BMC CONTROL-M User/Application JCL datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datasets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
Checks: C-25790r1141457_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(CTMJCL). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZCTM0003). Verify that the accesses to the BMC CONTROL-M User/Application JCL datasets 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 dataset access authorizations restrict READ access to auditors, automated batch user(s), BMC user(s), and operations. The ACF2 dataset access authorizations restrict WRITE and/or greater access to BMC CONTROL-M administrators and systems programming personnel. The ACF2 dataset 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 datasets. 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 datasets be created, one of which contains JCL and Procedures that are considered restricted, and this dataset be authorized to users with justification to maintain and run these restricted JCL and Procedures.

Fix: F-25778r1141458_fix

Ensure that WRITE and/or greater access to BMC CONTROL-M User/Application JCL datasets is 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 application 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 datasets. The installing systems programmer will identify and document the product datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure 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 datasets, 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 datasets and/or dataset prefixes identified below are examples of a possible installation. The actual datasets and/or prefixes are determined when the product is installed on a system through the product's installation guide and can be site specific.) Datasets to be protected will be: IOA The following commands are provided as a sample for implementing dataset controls: $KEY(IOA) - UID(<bmcadmin>) R(A) W(A) A(A) E(A) - UID(<syspaudt>) R(A) W(A) A(A) E(A) - UID(<tstcaudt>) 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(<dpcsaudt>) R(A) W(A) E(A) - UID(<pcspaudt>) R(A) W(A) E(A) - UID(<audtaudt>) R(A) E(A) - UID(<autoaudt>) R(A) E(A) - UID(<bmcuser>) R(A) E(A) - UID(<operaudt>) R(A) E(A)

b
BMC C0NTROL-M resources must be properly defined and protected.
AC-3 - Medium - CCI-000213 - V-224118 - SV-224118r1141462_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZCTMA020
Vuln IDs
  • V-224118
  • V-17947
Rule IDs
  • SV-224118r1141462_rule
  • SV-32058
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.
Checks: C-25791r1141460_chk

Refer to the following report produced by the ACF2 Data Collection and dataset and Resource Data Collection: - SENSITVE.RPT(ZCTM0020). - ACF2CMDS.RPT(RESOURCE) - Alternate report. Automated Analysis Refer to the following report produced by the dataset 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: F-25779r1141461_fix

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 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(<operaudt>) allow - uid(<pcspaudt>) allow - uid(<syspaudt>) allow - uid(*) prevent

b
BMC CONTROL-M Started Task name is not properly identified/defined to the system ACP.
IA-2 - Medium - CCI-000764 - V-224119 - SV-224119r1144178_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000764
Version
ZCTMA030
Vuln IDs
  • V-224119
  • V-17452
Rule IDs
  • SV-224119r1144178_rule
  • SV-32070
BMC CONTROL-M requires a started task that will be restricted to certain resources, datasets, 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.
Checks: C-25792r1144178_chk

Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(ATTSTC). Ensure 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: F-25780r1141464_fix

The BMC CONTROL-M systems 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. Example: SET LID CHANGE CONTROLM STC MUSASS NO-SMC

b
BMC CONTROL-M configuration/parameter values must be specified properly.
CM-7 - Medium - CCI-000381 - V-224120 - SV-224120r1141467_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
ZCTMA040
Vuln IDs
  • V-224120
  • V-18014
Rule IDs
  • SV-224120r1141467_rule
  • SV-31975
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.
Checks: C-25793r1141466_chk

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

Fix: F-25781r518738_fix

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 SAFJCARD U MSUBCHK NO