← Back to z/OS BMC CONTROL-D for TSS Security Technical Implementation Guide

V-224584

CAT II (Medium)

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

Rule ID

SV-224584r1145909_rule

STIG

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

Version

V7R2

CCIs

CCI-000764

Discussion

BMC CONTROL-D requires a started task that will be restricted to certain resources, data sets, 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 TSS Data Collection:

- TSSCMDS.RPT(@ACIDS).

Review BMC CONTROL-D STC/Batch ACID(s). If the following attributes are defined, this is not a finding.

FACILITY(STC, BATCH)
PASSWORD(xxxxxxxx,0)
SOURCE(INTRDR)
NOSUSPEND
MASTFAC(CONTROLD)

Fix Text

The BMC CONTROL-D 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.

A sample is provided here:

TSS CREATE(CONTROLD) TYPE(USER) -
	NAME('*STC* for CONTROL-D') DEPT(xxxx) - 
 	FAC(STC) -
	MASTFAC(CONTROLD) PASS(xxxxxxxx,0) -
	SOURCE(INTRDR) NOSUSPEND