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

V-224603

CAT II (Medium)

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

Rule ID

SV-224603r1146017_rule

STIG

z/OS BMC IOA for TSS Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000764

Discussion

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

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):

TSS CREATE(IOAGATE) TYPE(USER) -
	NAME('*STC* for IOA') DEPT(xxxx) - 
 	FAC(STC,BATCH) -
	MASTFAC(IOA) PASS(xxxxxxxx,0) -
	SOURCE(INTRDR) NOSUSPEND