STIGQter: STIG Summary: z/OS CA VTAPE for RACF STIG Version: 6 Release: 4 Benchmark Date: 20 Jan 2015:

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

DISA Rule

SV-33833r1_rule

Vulnerability Number

V-17454

Group Title

ZB000032

Rule Version

ZVTAR032

Severity

CAT II

CCI(s)

• CCI-000764 - The information system uniquely identifies and authenticates organizational users (or processes acting on behalf of organizational users).

Weight

10

Fix Recommendation

The CA VTAPE system programmer and the IAO 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

Check Contents

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.

Vulnerability Number

V-17454

Documentable

False

Rule Version

ZVTAR032

Severity Override Guidance

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.

Check Content Reference

M

Responsibility

Information Assurance Manager

Target Key

2092

Comments