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-224280

CAT II (Medium)

CA VTAPE STC datasets will be properly protected.

Rule ID

SV-224280r1141663_rule

STIG

z/OS CA VTAPE for ACF2 Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-001499

Discussion

CA VTAPE STC datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datasets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.

Check Content

Refer to the following report produced by the dataset and Resource Data Collection:

- SENSITVE.RPT(VTASTC).

Automated Analysis
Refer to the following report produced by the dataset and Resource Data Collection:

- PDI(ZVTA0001).

Verify that the accesses to the CA VTAPE STC datasets are properly restricted. If the following guidance is true, this is not a finding.
 
The ACF2 dataset rules for the datasets restrict READ access to auditors and authorized users.

The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to systems programming personnel and Tape Management personnel.

The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to the CA VTAPE's STC(s) and/or batch user(s).

Fix Text

The ISSO will ensure that WRITE and/or greater access to CA VTAPE STC datasets is limited to systems programmers, tape management personnel, and/or CA VTAPE's STC(s) and/or batch user(s) only. READ access can be given to auditors and authorized users.

The installing systems programmer will identify and document the product datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure that all WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have WRITE and/or greater access for specific datasets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system.

Datasets to be protected will be: 
SYS3.VTAPE (Datasets that are altered by the product's STCs can be more specific.)

The following commands are provided as a sample for implementing dataset controls: 

$KEY(SYS3)
VTAPE.- UID(<syspaudt>) R(A) W(A) A(A) E(A)
VTAPE.- UID(<tapeaudt>) R(A) W(A) A(A) E(A)
VTAPE.- UID(<tstcaudt>) R(A) W(A) A(A) E(A)
VTAPE.- UID(VTAPE STCs) R(A) W(A) A(A) E(A)
VTAPE.- UID(<audtaudt>) R(A) E(A)
VTAPE.- UID(authorize users) R(A) E(A)