← Back to z/OS BMC IOA for ACF2 Security Technical Implementation Guide

V-224248

CAT II (Medium)

BMC IOA Started Task name must be properly identified and defined to the system ACP.

Rule ID

SV-224248r1144183_rule

STIG

z/OS BMC IOA for ACF2 Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000764

Discussion

BMC IOA 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).

Verify that the logonid(s) for the BMC IOA started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.

STC
MUSASS
NO-SMC

Fix Text

The ISSO working with the systems programmer will ensure the BMC IOA Started Task(s) is (are) properly identified and/or 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.

The following commands are provided as a sample for defining Started Task(s):

SET LID
CHANGE IOAGATE STC MUSASS NO-SMC