← Back to z/OS CA VTAPE for RACF Security Technical Implementation Guide

V-224447

CAT II (Medium)

CA VTAPE Started task(s) must be properly defined to the STARTED resource class for RACF.

Rule ID

SV-224447r1145023_rule

STIG

z/OS CA VTAPE for RACF Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000764

Discussion

Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could potentially compromise the operating system, ACP, and customer data.

Check Content

Refer to the following report produced by the RACF Data Collection:

- DSMON.RPT(RACSPT).

Automated Analysis
Refer to the following report produced by the RACF Data Collection:

- PDI(ZVTA0032).

Verify that the CA VTAPE started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding.

Fix Text

The CA VTAPE system programmer and the ISSO will ensure that a product's started task(s) is (are) properly identified and/or defined to the System ACP. 

A unique userid must be assigned for the CA VTAPE started task(s) thru a corresponding STARTED class entry.

The following sample set of commands is shown here as a guideline:

rdef started SVTS.** uacc(none) owner(admin) audit(all(read)) stdata(user(SVTS) group(stc))
rdef started SVTSAS.** uacc(none) owner(admin) audit(all(read)) stdata(user(SVTSAS) group(stc))

setr racl(started) ref