Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

z/OS CA VTAPE for ACF2 Security Technical Implementation Guide

V7R2 · · · Released 01 Oct 2025 · 3 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
Digest of Updates vs. V7R1 · 02 Apr 2025 ✎ 3

Comparison against the immediately-prior release (V7R1). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.

Content changes 3

  • V-224279 Medium descriptioncheckfix CA VTAPE installation datasets are not properly protected.
  • V-224280 Medium descriptioncheckfix CA VTAPE STC datasets will be properly protected.
  • V-224281 Medium descriptioncheckfix CA VTAPE Started Task name is not properly identified/defined to the system ACP.
Sort by
b
CA VTAPE installation datasets are not properly protected.
CM-5 - Medium - CCI-001499 - V-224279 - SV-224279r1141660_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZVTAA000
Vuln IDs
  • V-224279
  • V-16932
Rule IDs
  • SV-224279r1141660_rule
  • SV-33824
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.
Checks: C-25952r1141658_chk

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: F-25940r1141659_fix

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)

b
CA VTAPE STC datasets will be properly protected.
CM-5 - Medium - CCI-001499 - V-224280 - SV-224280r1141663_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZVTAA001
Vuln IDs
  • V-224280
  • V-17067
Rule IDs
  • SV-224280r1141663_rule
  • SV-33827
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.
Checks: C-25953r1141661_chk

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: F-25941r1141662_fix

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)

b
CA VTAPE Started Task name is not properly identified/defined to the system ACP.
IA-2 - Medium - CCI-000764 - V-224281 - SV-224281r1144188_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZVTAA030
Vuln IDs
  • V-224281
  • V-17452
Rule IDs
  • SV-224281r1144188_rule
  • SV-33830
CA VTAPE requires a started task that will be restricted to certain resources, datasets, 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.
Checks: C-25954r1141664_chk

Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(ATTSTC). Verify that the logonid(s) for the CA VTAPE started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. STC NO-SMC

Fix: F-25942r1141665_fix

The CA VTAPE systems 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. Example: SET LID INSERT SVTS STC NO-SMC INSERT SVTSAS STC NO-SMC