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

V-224446

CAT II (Medium)

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

Rule ID

SV-224446r1145291_rule

STIG

z/OS CA VTAPE for RACF Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000764

Discussion

CA VTAPE 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 RACF Data Collection:

- RACFCMDS.RPT(LISTUSER).

Verify that the userid(s) for the CA VTAPE started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.

PROTECTED

Fix Text

The CA VTAPE system 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:

au SVTS name('CA VTAPE') owner(stc) dfltgrp(stc) nopass
au SVTSAS name('CA VTAPE') owner(stc) dfltgrp(stc) nopass