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

Overview

Version	Date	Finding Count (9)			Downloads
7	2024-12-16	CAT I (High): 0	CAT II (Medium): 9	CAT III (Low): 0	Excel ↓JSON ↓XML ↓

STIG Description

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.

Classified	Public	Sensitive
I - Mission Critical Classified	I - Mission Critical Public	I - Mission Critical Sensitive
II - Mission Support Classified	II - Mission Support Public	II - Mission Support Sensitive
III - Administrative Classified	III - Administrative Public	III - Administrative Sensitive

Findings - MAC I - Mission Critical Public

Finding ID	Title	Description
V-224396	BMC CONTROL-M security exits are not installed or configured properly.	The BMC CONTROL-M security exits enable access authorization checking to BMC CONTROL-M commands, features, and online functionality. If these exit(s) ...
V-224397	BMC CONTROL-M installation data sets will be properly protected.	BMC CONTROL-M installation data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict a...
V-224398	BMC CONTROL-M STC data sets will be properly protected.	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 ...
V-224399	BMC CONTROL-M User data sets will be properly protected.	BMC CONTROL-M User data sets, Repository, have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restr...
V-224400	BMC CONTROL-M User/Application JCL data sets must be properly protected.	BMC CONTROL-M User/Application JCL data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly re...
V-224401	BMC C0NTROL-M resources must be properly defined and protected.	BMC CONTROL-M can run with sensitive system privileges, and potentially can circumvent system controls. Failure to properly control access to product ...
V-224402	BMC CONTROL-M Started Task name is not properly identified / defined to the system ACP.	BMC CONTROL-M requires a started task that will be restricted to certain resources, datasets and other system functions. By defining the started task ...
V-224403	BMC CONTROL-M Started task(s) must be properly defined to the STARTED resource class for RACF.	Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to ...
V-224404	BMC CONTROL-M configuration/parameter values must be specified properly.	BMC CONTROL-M configuration/parameters control the security and operational characteristics of products. If these parameter values are improperly spec...