OpenControls Logo

STIG Viewer

STIGViewer Support

BMC CONTROL-M STC data sets will be properly protected.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-224398ZCTMR001SV-224398r1145221_ruleCCI-001499medium
Description
BMC CONTROL-M STC 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.
STIGDate
z/OS BMC CONTROL-M for RACF Security Technical Implementation Guide2025-09-27

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CHG-04.5Library Privileges
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (56) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-17(1)Monitoring and Control
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(10)Shared and Group Account Credential Change
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-3(7)Role-based Access Control
1.00
AC-4Information Flow Enforcement
1.00
AC-6(10)Prohibit Non-privileged Users from Executing Privileged Functions
1.00

+46 more (top 10 by confidence shown)

CCI1 mapping
CCI-001499
1.00

Details

Check Text (C-224398r1145221_chk)

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CTMSTC). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTM0001). Verify that the accesses to the BMC CONTROL-M STC data sets are properly restricted. If the following guidance is true, this is not a finding. The RACF data set access authorizations restricts READ access to auditors and BMC users. The RACF data set access authorizations restricts WRITE and/or greater access to systems programming personnel. The RACF data set access authorizations restricts UPDATE access to the BMC STCs and/or batch users. The RACF data set access authorizations restricts UPDATE access to scheduled batch jobs, operations, and production control and scheduling personnel. The RACF data set rules for the data sets specify UACC(NONE) and NOWARNING.

Fix Text (F-26063r1145220_fix)

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-M STC data sets are limited to systems programmers only. UPDATE access can be given to scheduled batch jobs, operations, and production control and scheduling personnel, BMC STCs and/or batch users. READ access can be given to auditors and/or BMC users. The installing systems programmer will identify and document the product data sets and categorize them according to who will have WRITE and/or greater access and if required 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 data sets, 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 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: SYS3.IOA.*.CTMO. The following commands are provided as a sample for implementing data set controls: ad 'SYS3.IOA.*.CTMO.**' uacc(none) owner(sys3) - audit(failures(read)) - data('BMC ControlM Started Task DS') pe 'SYS3.IOA.*.CTMO.**' id(<syspaudt> <tstcaudt>) acc(a) pe 'SYS3.IOA.*.CTMO.**' id(CONTROLM CONTDAY <autoaudt> <operaudt> <pcspaudt>) acc(u) pe 'SYS3.IOA.*.CTMO.**' id(<audtaudt> <bmcuser>) acc(r) setr generic(dataset) refresh