STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 4 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to z/OS BMC CONTROL-O for TSS Security Technical Implementation Guide

V-224591

CAT II (Medium)

BMC CONTROL-O security exits are not installed or configured properly.

Rule ID

SV-224591r1145949_rule

STIG

z/OS BMC CONTROL-O for TSS Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-001744

Discussion

The BMC CONTROL-O security exits enable access authorization checking to BMC CONTROL-O commands, features, and online functionality. If these exit(s) is (are) not in place, activities by unauthorized users may result. BMC CONTROL-O security exit(s) interface with the Access Control Program (ACP). If an unauthorized exit was introduced into the operating environment, system security could be weakened or bypassed. These exposures may result in the compromise of the operating system environment, ACP, and customer data.

Check Content

Interview the systems programmer responsible for the BMC CONTROL-O. Determine if the site has modified the following security exit(s):

CTOSE01
CTOSE02
CTOSE03
CTOSE04
CTOSE08
CTOSE10
CTOSE15

Ensure the above security exit(s) has (have) not been modified.

If the above security exit(s) has (have) been modified, ensure that the security exit(s) has (have) been approved by the site systems programmer and the approval is on file for examination.

Fix Text

The systems programmer responsible for the BMC CONTROL-O will review the BMC CONTROL-O operating environment. Ensure that the following security exit(s) is (are) installed properly. Determine if the site has modified the following security exit(s):

CTOSE01
CTOSE02
CTOSE03
CTOSE04
CTOSE08
CTOSE10
CTOSE15

Ensure that the security exit(s) has (have) not been modified.

If the security exit(s) has (have) been modified, ensure the security exit(s) has (have) been checked as to not violate any security integrity within the system and approval documentation is on file.