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

z/OS BMC CONTROL-M/Restart for RACF STIG

V6R2 · · · Released 26 Oct 2012 · 2 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

Sort by
b
BMC CONTROL-M/Restart installation data sets will be not properly protected.
Medium - V-16932 - SV-31832r2_rule
RMF Control
Severity
M
CCI
Version
ZCTRR000
Vuln IDs
  • V-16932
Rule IDs
  • SV-31832r2_rule
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.Information Assurance OfficerSystems ProgrammerDCSL-1, ECAR-1, ECAR-2, ECCD-1, ECCD-2
Checks: C-6186r2_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-3268r5_fix

The IAO will ensure that WRITE and/or greater access to BMC CONTROL-M/Restart installation data sets are limited to System 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. He will identify if any additional groups have update and/or alter access for specific data sets, and once documented he will work with the IAO to see that they are properly restricted to the ACP (Access Control Program) 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 will be properly protected.
Medium - V-21592 - SV-32219r2_rule
RMF Control
Severity
M
CCI
Version
ZCTRR002
Vuln IDs
  • V-21592
Rule IDs
  • SV-32219r2_rule
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.Information Assurance OfficerSystems ProgrammerDCSL-1, ECAR-1, ECAR-2, ECCD-1, ECCD-2
Checks: C-3334r3_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, Production Control Scheduling personnel, and scheduled batch user(s). ___ The RACF data set access authorizations restrict WRITE and/or greater access to systems programming personnel and the BMC STCs and/or batch users. ___ The RACF data set access authorizations specify UACC(NONE) and NOWARNING.

Fix: F-3243r4_fix

The IAO will ensure that WRITE and/or greater access to BMC CONTROL-M/Restart Archived Sysout data sets are limited to System Programmers and the BMC STCs and/or batch users only. READ access can be given to auditors, production control scheduling personnel, and scheduled batch 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. He will identify if any additional groups have update and/or alter access for specific data sets, and once documented he will work with the IAO to see that they are properly restricted to the ACP (Access Control Program) 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>) acc(a) pe 'CTRSYS.**' id(<audtaudt> <autoaudt> <pcspaudt>) acc(r) setr generic(dataset) refresh