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

z/OS BMC CONTROL-D 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-D configuration/parameter values are not specified properly.
CM-7 - Medium - CCI-000381 - V-224106 - SV-224106r1141432_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
ZCTD0040
Vuln IDs
  • V-224106
  • V-18014
Rule IDs
  • SV-224106r1141432_rule
  • SV-32211
BMC CONTROL-D 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-25779r1141431_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(ZCTD0040). The following keywords will have the specified values in the BMC CONTROL-D security parameter member. This is not a finding. Keyword Value DEFMCHKD $$CTDEDM SECTOLD NO DFMD01 EXTEND DFMD04 EXTEND DFMD08 EXTEND DFMD19 EXTEND DFMD23 EXTEND DFMD24 EXTEND DFMD26 EXTEND DFMD27 EXTEND

Fix: F-25767r1041230_fix

The BMC CONTROL-D 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-D security parameters for the specific ACP environment along with additional IOA security parameters with standard values as documented below. Keyword Value DEFMCHKD $$CTDEDM SECTOLD NO DFMD01 EXTEND DFMD04 EXTEND DFMD08 EXTEND DFMD19 EXTEND DFMD23 EXTEND DFMD24 EXTEND DFMD26 EXTEND DFMD27 EXTEND

b
BMC CONTROL-D security exits are not installed or configured properly.
CM-3 - Medium - CCI-001744 - V-224107 - SV-224107r1041234_rule
RMF Control
CM-3
Severity
Medium
CCI
CCI-001744
Version
ZCTD0060
Vuln IDs
  • V-224107
  • V-17985
Rule IDs
  • SV-224107r1041234_rule
  • SV-32015
The BMC CONTROL-D security exits enable access authorization checking to BMC CONTROL-D commands, features, and online functionality. If these exit(s) is (are) not in place, activities by unauthorized users may result. BMC CONTROL-D 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-25780r1041232_chk

Interview the systems programmer responsible for the BMC CONTROL-D. Determine if the site has modified the following security exit(s): CTDSE01 CTDSE04 CTDSE08 CTDSE19 CTDSE24 CTDSE28 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-25768r1041233_fix

The systems programmer responsible for the BMC CONTROL-D will review the BMC CONTROL-D operating environment. Ensure that the following security exit(s) is (are) installed properly. Determine if the site has modified the following security exit(s): CTDSE01 CTDSE04 CTDSE08 CTDSE19 CTDSE24 CTDSE28 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-D installation datasets will be properly protected.
CM-5 - Medium - CCI-001499 - V-224108 - SV-224108r1141435_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZCTDA000
Vuln IDs
  • V-224108
  • V-16932
Rule IDs
  • SV-224108r1141435_rule
  • SV-31827
BMC CONTROL-D 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-25781r1141433_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(CTDRPT). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZCTD0000). Verify that the accesses to the BMC CONTROL-D 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, BMC users, security 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-25769r1141434_fix

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-D installation datasets is limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to auditors, BMC users, security 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.*.CTDI The following commands are provided as a sample for implementing dataset controls: $KEY(SYS2) IOA.-.CTDI.- UID(<syspaudt>) R(A) W(L) A(L) E(A) IOA.-.CTDI.- UID(<audtaudt>) R(A) E(A) IOA.-.CTDI.- UID(<bmcuser>) R(A) E(A) IOA.-.CTDI.- UID(<secaaudt>) R(A) E(A) IOA.-.CTDI.- UID(<secdaudt>) R(A) E(A) IOA.-.CTDI.- UID(CONTROLD) R(A) E(A)

b
BMC CONTROL-D STC datasets must be properly protected.
CM-5 - Medium - CCI-001499 - V-224109 - SV-224109r1141438_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZCTDA001
Vuln IDs
  • V-224109
  • V-17067
Rule IDs
  • SV-224109r1141438_rule
  • SV-32165
BMC CONTROL-D 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-25782r1141436_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(CTDSTC). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZCTD0001). Verify that the accesses to the BMC CONTROL-D 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 CONTROL-D end users. 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 BMC STCs and/or batch users. The ACF2 dataset access authorizations restrict UPDATE access to centralized and decentralized security personnel.

Fix: F-25770r1141437_fix

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-D STC datasets is limited to systems programmers and BMC STCs and/or batch users. UPDATE access can be given to centralized and decentralized security personnel. READ access can be given to auditors and 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.*.CTDO The following commands are provided as a sample for implementing dataset controls: $KEY(SYS3) IOA.-.CTDO.- UID(syspaudt) R(A) W(A) A(A) E(A) IOA.-.CTDO.- UID(tstcaudt) R(A) W(A) A(A) E(A) IOA.-.CTDO.- UID(BMC STCs) R(A) W(A) A(A) E(A) IOA.-.CTDO.- UID(secaaudt) R(A) W(A) E(A) IOA.-.CTDO.- UID(secdaudt) R(A) W(A) E(A) IOA.-.CTDO.- UID(audtaudt) R(A) E(A) IOA.-.CTDO.- UID(bmcuser) R(A) E(A)

b
BMC CONTROL-D user datasets must be properly protected.
CM-5 - Medium - CCI-001499 - V-224110 - SV-224110r1141441_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZCTDA002
Vuln IDs
  • V-224110
  • V-21592
Rule IDs
  • SV-224110r1141441_rule
  • SV-32162
BMC CONTROL-D User datasets, CDAM and 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-25783r1141439_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(ZCTD0002). Verify that the accesses to the BMC CONTROL-D 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 dataset access authorizations restrict UPDATE access to centralized and decentralized security personnel and/or CONTROL-D end users.

Fix: F-25771r1141440_fix

The ISSO must ensure that WRITE and/or greater access to BMC CONTROL-D User datasets is limited to systems programmers and BMC STCs and/or batch users. Additionally, UPDATE access can be given to centralized and decentralized security personnel and BMC users. The ISSO can approve ALLOC access in circumstances where it is determined to be necessary and appropriate for systems operations to execute in a normal secure manner. 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 must 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.*.CTDR CTRUSR CTDSRV CTDJB1 The following commands are provided as a sample for implementing dataset controls: $KEY(SYS3) IOA.-.CTDR.- UID(syspaudt) R(A) W(A) A(A) E(A) IOA.-.CTDR.- UID(tstcaudt) R(A) W(A) A(A) E(A) IOA.-.CTDR.- UID(BMC STCs) R(A) W(A) A(A) E(A) IOA.-.CTDR.- UID(bmcuser) R(A) W(A) E(A) IOA.-.CTDR.- UID(secaaudt) R(A) W(A) E(A) IOA.-.CTDR.- UID(secdaudt) R(A) W(A) E(A) IOA.-.CTDR.- UID(audtaudt) R(A) E(A) $KEY(CTRUSR) - UID(syspaudt) R(A) W(A) A(A) E(A) - UID(tstcaudt) R(A) W(A) A(A) E(A) - UID(BMC STCs) R(A) W(A) A(A) E(A) - UID(bmcuser) R(A) W(A) E(A) - UID(secaaudt) R(A) W(A) E(A) - UID(secdaudt) R(A) W(A) E(A) - UID(audtaudt) R(A) E(A) $KEY(CTDSRV) - UID(syspaudt) R(A) W(A) A(A) E(A) - UID(tstcaudt) R(A) W(A) A(A) E(A) - UID(BMC STCs) R(A) W(A) A(A) E(A) - UID(bmcuser) R(A) W(A) E(A) - UID(secaaudt) R(A) W(A) E(A) - UID(secdaudt) R(A) W(A) E(A) - UID(audtaudt) R(A) E(A) $KEY(CTDJB1) - UID(syspaudt) R(A) W(A) A(A) E(A) - UID(tstcaudt) R(A) W(A) A(A) E(A) - UID(BMC STCs) R(A) W(A) A(A) E(A) - UID(bmcuser) R(A) W(A) E(A) - UID(secaaudt) R(A) W(A) E(A) - UID(secdaudt) R(A) W(A) E(A) - UID(audtaudt) R(A) E(A)

b
BMC CONTROL-D resources will be properly defined and protected.
AC-3 - Medium - CCI-000213 - V-224111 - SV-224111r1141444_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZCTDA020
Vuln IDs
  • V-224111
  • V-17947
Rule IDs
  • SV-224111r1141444_rule
  • SV-32055
BMC CONTROL-D 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-25784r1141442_chk

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

The ISSO will work with the systems programmer to 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-D 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. The following commands are provided as a sample for implementing resource controls: $key($$addnot) type(ioa) - uid(<appsaudt>) allow - uid(<operaudt>) allow - uid(<pcspaudt>) allow - uid(<syspaudt>) allow - uid(*) prevent

b
BMC CONTROL-D Started Task name is not properly identified/defined to the system ACP.
IA-2 - Medium - CCI-000764 - V-224112 - SV-224112r1144176_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000764
Version
ZCTDA030
Vuln IDs
  • V-224112
  • V-17452
Rule IDs
  • SV-224112r1144176_rule
  • SV-32067
BMC CONTROL-D 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-25785r1141445_chk

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

Fix: F-25773r1141446_fix

The BMC CONTROL-D 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 CONTROLD STC MUSASS NO-SMC