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

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

  • Version/Release: V7R2
  • Published: 2025-09-23
  • 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/Restart installation datasets will be properly protected.
CM-5 - Medium - CCI-001499 - V-224121 - SV-224121r1141491_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZCTRA000
Vuln IDs
  • V-224121
  • V-16932
Rule IDs
  • SV-224121r1141491_rule
  • SV-31831
BMC CONTROL-M/Restart 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-25794r1141489_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(CTRRPT). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZCTR0000). Verify that the accesses to the BMC CONTROL-M/Restart 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, 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-25782r1141490_fix

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-M/Restart 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, 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 Access Control Program (ACP) 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.*.CTRO The following commands are provided as a sample for implementing dataset controls: $KEY(SYS2) IOA.-.CTRO.- UID(<syspaudt>) R(A) W(L) A(L) E(A) IOA.-.CTRO.- UID(<audtaudt>) R(A) E(A) IOA.-.CTRO.- UID(<bmcuser>) R(A) E(A) IOA.-.CTRO.- UID(CONTROLR) R(A) E(A)

b
BMC CONTROL-M/Restart Archived Sysout datasets must be properly protected.
CM-5 - Medium - CCI-001499 - V-224122 - SV-224122r1141494_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZCTRA002
Vuln IDs
  • V-224122
  • V-21592
Rule IDs
  • SV-224122r1141494_rule
  • SV-32218
BMC CONTROL-M/Restart Archived Sysout 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-25795r1141492_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(CTRUSER). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZCTR0002). Verify that the accesses to the BMC CONTROL-M/Restart Archived Sysout 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 production control and scheduling personnel, scheduled batch user(s), systems programming personnel, and the BMC STCs and/or batch users.

Fix: F-25783r1141493_fix

Ensure that WRITE and/or greater access to BMC CONTROL-M/Restart Archived Sysout datasets is limited to production control scheduling personnel, scheduled batch users, systems programmers, and the BMC STCs and/or batch users only. 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 Access Control Program (ACP) 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: CTRSYS The following commands are provided as a sample for implementing dataset controls: $KEY(CTRSYS) - UID(<syspaudt>) R(A) W(A) A(A) E(A) - UID(CONTROLM) R(A) W(A) A(A) E(A) - UID(CONTDAY) R(A) W(A) A(A) E(A) - UID(<audtaudt>) R(A) E(A) - UID(<bmcuser>) R(A) E(A) - UID(<autoaudt>) R(A) W(A) A(A) E(A) - UID(<pcspaudt>) R(A) W(A) A(A) E(A)