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

V-224253

CAT II (Medium)

BMC Mainview for z/OS Started Task name must be properly identified and/or defined to the system ACP.

Rule ID

SV-224253r1144185_rule

STIG

z/OS BMC MAINVIEW for z/OS for ACF2 Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000764

Discussion

BMC Mainview for z/OS 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 Mainview for z/OS started task(s) includes the following. If the following attributes are defined, this is not a finding.

STC
NO-SMC

Fix Text

Ensure that a product's Started Task(s) is 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.

Example:

SET LID
INSERT MV$CAS STC NO-SMC
INSERT MV$PAS STC NO-SMC
INSERT MV$MVS STC NO-SMC