STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to z/OS CA Common Services for TSS Security Technical Implementation Guide

V-224622

CAT II (Medium)

CA Common Services Started Task name will be properly identified and/or defined to the system ACP.

Rule ID

SV-224622r1145835_rule

STIG

z/OS CA Common Services for TSS Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000764

Discussion

CA Common Services 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 CA Common Services STC/Batch ACID(s). If the following attributes are defined, this is not a finding.

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

Fix Text

The ISSO working with the systems programmer will ensure the CA Common Services 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 a 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(CAS9) TYPE(USER) -
	NAME('STC, CAS9') DEPT(xxxx) -
	FAC(STC,BATCH) PASS(xxxxxxxx,0) -
	SOURCE(INTRDR) -
	NOSUSPEND