Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

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

V7R1 · · · Released 02 Apr 2025 · 2 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

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.
Digest of Updates vs. V6R6 · 23 Nov 2022 ✎ 2

Comparison against the immediately-prior release (V6R6). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.

Content changes 2

  • V-224405 Medium descriptioncheckfix BMC CONTROL-M/Restart installation data sets will be not properly protected.
  • V-224406 Medium descriptioncheckfix BMC CONTROL-M/Restart Archived Sysout data sets must be properly protected.
Sort by
b
BMC CONTROL-M/Restart installation data sets will be not properly protected.
CM-5 - Medium - CCI-001499 - V-224405 - SV-224405r1070131_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZCTRR000
Vuln IDs
  • V-224405
  • V-16932
Rule IDs
  • SV-224405r1070131_rule
  • SV-31832
BMC CONTROL-M/Restart 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.
Checks: C-26082r1070129_chk

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

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-M/Restart 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, 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 data sets and categorize them according to who will have update and alter access and if required that all update and allocate access is logged. The installing systems programmer will identify if any additional groups have update and/or alter access for specific data sets, 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 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.*.CTRO. The following commands are provided as a sample for implementing data set controls: ad 'SYS2.IOA.*.CTRO.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('Vendor DS Profile: BMC CONTROL-M/Restart') pe 'SYS2.IOA.*.CTRO.**' id(<syspaudt>) acc(a) pe 'SYS2.IOA.*.CTRO.**' id(<audtaudt> <bmcuser>) acc(r) pe 'SYS2.IOA.*.CTRO.**' id(CONTROLR) acc(r) setr generic(dataset) refresh

b
BMC CONTROL-M/Restart Archived Sysout data sets must be properly protected.
CM-5 - Medium - CCI-001499 - V-224406 - SV-224406r1070134_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZCTRR002
Vuln IDs
  • V-224406
  • V-21592
Rule IDs
  • SV-224406r1070134_rule
  • SV-32219
BMC CONTROL-M/Restart Archived Sysout 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.
Checks: C-26083r1070132_chk

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CTRUSER) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTR0002) Verify that the accesses to the BMC CONTROL-M/Restart Archived Sysout 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 and BMC users. The RACF data set access authorizations restrict WRITE and/or greater access to Production Control Scheduling personnel, scheduled batch user(s), systems programming personnel, and the BMC STCs and/or batch users. The RACF data set access authorizations specify UACC(NONE) and NOWARNING.

Fix: F-26071r1070133_fix

Ensure that WRITE and/or greater access to BMC CONTROL-M/Restart Archived Sysout data sets are 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 data sets and categorize them according to who will have update and alter access and if required that all update and allocate access is logged. The installing systems programmer will identify if any additional groups have update and/or alter access for specific data sets, and once documented, will work with the ISSO to see that they are properly restricted to the Access Control Program (ACP) 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: CTRSYS. The following commands are provided as a sample for implementing data set controls: ad 'CTRSYS.**' uacc(none) owner(CTRSYS) - data('BMC CONTROL-M/Restart Archived Sysout') pe 'CTRSYS.**' id(CONTROLM CONTDAY) acc(a) pe 'CTRSYS.**' id(<syspaudt> <autoaudt> <pcspaudt>) acc(a) pe 'CTRSYS.**' id(<audtaudt>) acc(r) pe 'CTRSYS.**' id(<bmcuser>) acc(r) setr generic(dataset) refresh