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

V7 · Released 2024-12-16

You are viewing V7. This is not the latest release. View latest release (V7R2) → · Version history

Overview

Version	Date	Finding Count (8)
V7	2024-12-16	CAT I (High): 0	CAT II (Medium): 8	CAT III (Low): 0

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.

Findings — All

Finding ID	Title	Description
V-224388	BMC CONTROL-D configuration/parameter values are not specified properly.	BMC CONTROL-D configuration/parameters control the security and operational characteristics of products. If these parameter values are improperly spec...
V-224389	BMC CONTROL-D security exits are not installed or configured properly.	The BMC CONTROL-D security exits enable access authorization checking to BMC CONTROL-D commands, features, and online functionality. If these exit(s) ...
V-224390	BMC CONTROL-D installation data sets will be properly protected.	BMC CONTROL-D installation data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict a...
V-224391	BMC CONTROL-D STC data sets must be properly protected.	BMC CONTROL-D STC data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to ...
V-224392	BMC CONTROL-D user data sets must be properly protected.	BMC CONTROL-D User data sets, CDAM and Repository, have the ability to use privileged functions and/or have access to sensitive data. Failure to prope...
V-224393	BMC CONTROL-D resources must be properly defined and protected.	BMC CONTROL-D can run with sensitive system privileges, and potentially can circumvent system controls. Failure to properly control access to product ...
V-224394	BMC CONTROL-D Started Task name is not properly identified / defined to the system ACP.	Products that require a started task will require that the started task be restricted to certain resources, datasets and other system functions. By de...
V-224395	BMC CONTROL-D 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 ...