← Back to z/OS BMC CONTROL-M for ACF2 Security Technical Implementation Guide

V-224119

CAT II (Medium)

BMC CONTROL-M Started Task name is not properly identified/defined to the system ACP.

Rule ID

SV-224119r1144178_rule

STIG

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

Version

V7R2

CCIs

CCI-000764

Discussion

BMC CONTROL-M requires a started task that will be restricted to certain resources, datasets, and other system functions. Defining the started task as a userid to the system ACP allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities could compromise the operating system environment, ACP, and customer data.

Check Content

Refer to the following report produced by the ACF2 Data Collection:

- ACF2CMDS.RPT(ATTSTC).

Ensure that the logonids(s) for the BMC CONTROL-M started task(s) includes the following. If the following attributes are defined, this is not a finding.

STC
MUSASS
NO-SMC

Fix Text

The BMC CONTROL-M systems programmer and the ISSO will ensure that a product's Started Task(s) is properly Identified / defined to the System ACP. 

If the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes.

Most installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified.

Example:

SET LID
CHANGE CONTROLM STC MUSASS NO-SMC