What changed in z/OS BMC CONTROL-M/Restart for ACF2 STIG V7R2V7R2 changes

z/OS BMC CONTROL-M/Restart for ACF2 STIG V7R2 (2025-10-01) replaced V7R1 (2025-04-02): 2 checks updated. It has 2 checks, against 2 in V7R1.

V7R2 checklistV7R1 checklist Compare V7R1 and V7R2 in STIG Compare

  • 0 added
  • 0 removed
  • 2 updated

Updated fields: Check text 2Fix text 2Title 2Discussion 2

Updated in V7R2 (2)

V-224121CAT IIBMC CONTROL-M/Restart installation datasets will be properly protected.Title, Check text, Fix text, Discussion

Title

BMC CONTROL-M/Restart installation data sets will be properly protected.

Check text

Refer to the following report produced by the Datadataset Set and Resource Data Collection: - SENSITVE.RPT(CTRRPT). Automated Analysis Refer to the following report produced by the Datadataset Set and Resource Data Collection: - PDI(ZCTR0000). Verify that the accesses to the BMC CONTROL-M/Restart installation datadatasets sets are properly restricted. If the following guidance is true, this is not a finding. The ACF2 datadataset set access authorizations restrict READ access to auditors, BMC users, and BMC STCs and/or batch users. The ACF2 datadataset set access authorizations restrict WRITE and/or greater access to systems programming personnel. The ACF2 datadataset set access authorizations specify that all (i.e., failures and successes) WRITE and/or greater access areis logged.

Fix text

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-M/Restart installation datadatasets setsis 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 datadatasets, sets and categorize them according to who will have updateWRITE and/or altergreater access, and if required, ensure that all updateWRITE and/or allocategreater access is logged. The installing systems programmer will identify if any additional groups have updateWRITE and/or altergreater access for specific data setsdatasets, 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 datadatasets sets and/or datadataset set prefixes identified below are examples of a possible installation. The actual datadatasets 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.) DataDatasets sets to be protected will be: SYS2.IOA.*.CTRO. The following commands are provided as a sample for implementing datadataset set controls: $KEY(SYS2) IOA.-.CTRO.- UID(&ltsyspaudt>) R(A) W(L) A(L) E(A) IOA.-.CTRO.- UID(&ltaudtaudt>) R(A) E(A) IOA.-.CTRO.- UID(&ltbmcuser>) R(A) E(A) IOA.-.CTRO.- UID(CONTROLR) R(A) E(A)

Discussion

BMC CONTROL-M/Restart installation datadatasets sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datadatasets sets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.

V-224121 in V7R2

V-224122CAT IIBMC CONTROL-M/Restart Archived Sysout datasets must be properly protected.Title, Check text, Fix text, Discussion

Title

BMC CONTROL-M/Restart Archived Sysout data sets must be properly protected.

Check text

Refer to the following report produced by the Datadataset Set and Resource Data Collection: - SENSITVE.RPT(CTRUSER). Automated Analysis Refer to the following report produced by the Datadataset Set and Resource Data Collection: - PDI(ZCTR0002). Verify that the accesses to the BMC CONTROL-M/Restart Archived Sysout datadatasets sets are properly restricted. If the following guidance is true, this is not a finding. The ACF2 datadataset set access authorizations restrict READ access to auditors and BMC Users. The ACF2 datadataset set access authorizations restrict WRITE and/or greater access to Productionproduction Controlcontrol Schedulingand scheduling personnel, scheduled batch user(s), systems programming personnel, and the BMC STCs and/or batch users.

Fix text

Ensure that WRITE and/or greater access to BMC CONTROL-M/Restart Archived Sysout datadatasets setsis 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 datadatasets, sets and categorize them according to who will have updateWRITE and/or altergreater access, and if required, ensure that all updateWRITE and/or allocategreater access is logged. The installing systems programmer will identify if any additional groups have updateWRITE and/or altergreater access for specific data setsdatasets, 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 datadatasets sets and/or datadataset set prefixes identified below are examples of a possible installation. The actual datadatasets 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.) DataDatasets sets to be protected will be: CTRSYS. The following commands are provided as a sample for implementing datadataset set controls: $KEY(CTRSYS) - UID(&ltsyspaudt>) 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(&ltaudtaudt>) R(A) E(A) - UID(&ltbmcuser>) R(A) E(A) - UID(&ltautoaudt>) R(A) W(A) A(A) E(A) - UID(&ltpcspaudt>) R(A) W(A) A(A) E(A)

Discussion

BMC CONTROL-M/Restart Archived Sysout datadatasets sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datadatasets sets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.

V-224122 in V7R2

How these changes are found

Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V7R2 no longer has.

Comparing other releases, or this one against an older release? Pick any two in STIG Compare.