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

CAT II (Medium)

CA VTAPE installation datasets are not properly protected.

Rule ID

SV-224279r1141660_rule

STIG

z/OS CA VTAPE for ACF2 Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-001499CCI-002234

Discussion

CA VTAPE installation 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(VTARPT).

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

- PDI(ZVTA0000).

Verify that the accesses to the CA VTAPE installation 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 all authorized users.

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

The ACF2 dataset rules for the datasets specify that all (i.e., failures and successes) WRITE and/or greater access is logged.

Fix Text

The ISSO will ensure that WRITE and/or greater access to CA VTAPE installation datasets is limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to all 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 Access Control Program (ACP) active on the system.

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

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

$KEY(SYS2)
VTAPE.- UID(<syspaudt>) R(A) W(L) A(L) E(A)
VTAPE.- UID(<tstcaudt>) R(A) W(L) A(L) E(A)
VTAPE.- UID(<audtaudt>) R(A) E(A)
VTAPE.- UID(authorized users) R(A) E(A)
VTAPE.- UID(<audtaudt>) R(A) E(A)
VTAPE.- UID(VTAPE STCs) R(A) E(A)

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