STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub·STIGs updated 2 days ago
Powered by Pylon·© 2026 Beacon Cloud Solutions, Inc.
← Back to z/OS CA VTAPE for ACF2 Security Technical Implementation Guide

V-224281

CAT II (Medium)

CA VTAPE Started Task name is not properly identified/defined to the system ACP.

Rule ID

SV-224281r1144188_rule

STIG

z/OS CA VTAPE for ACF2 Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000764

Discussion

CA VTAPE 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 CA VTAPE started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.

STC
NO-SMC

Fix Text

The CA VTAPE 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.

Example:

SET LID
INSERT SVTS STC NO-SMC
INSERT SVTSAS STC NO-SMC