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

z/OS CA VTAPE for RACF Security Technical Implementation Guide

V7R2 · · · Released 01 Oct 2025 · 4 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 ✎ 4

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 4

  • V-224444 Medium checkfix CA VTAPE installation data sets are not properly protected.
  • V-224445 Medium checkfix CA VTAPE STC data sets will be properly protected.
  • V-224446 Medium descriptioncheckfix CA VTAPE Started Task name is not properly identified/defined to the system ACP.
  • V-224447 Medium checkfix CA VTAPE Started task(s) must be properly defined to the STARTED resource class for RACF.
Sort by
b
CA VTAPE installation data sets are not properly protected.
CM-5 - Medium - CCI-001499 - V-224444 - SV-224444r1145288_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZVTAR000
Vuln IDs
  • V-224444
  • V-16932
Rule IDs
  • SV-224444r1145288_rule
  • SV-33825
CA VTAPE installation data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.
Checks: C-26121r1145012_chk

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(VTARPT). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZVTA0000). Verify that the accesses to the CA VTAPE installation data sets are properly restricted. If the following guidance is true, this is not a finding. The RACF data set rules for the data sets restricts READ access to all authorized users. The RACF data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel. The RACF data set rules for the data sets specify that all (i.e., failures and successes) WRITE and/or greater access are logged.

Fix: F-26109r1145287_fix

The ISSO will ensure that WRITE and/or greater access to CA VTAPE installation data sets is limited to system 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 data sets and categorize them according to who will have WRITE and/or greater access and if required 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 data sets, and once documented, will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system. Data sets to be protected will be: SYS2.VTAPE.** SYS3.VTAPE.** (data sets that are not altered by product STCs, can be more specific) The following commands are provided as a sample for implementing data set controls: ad 'SYS2.VTAPE.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('CA VTAPE Install DS') pe 'SYS2.VTAPE.**' id(<syspaudt> <tstcaudt>) acc(a) pe 'SYS2.VTAPE.**' id(<audtaudt> authorized users) acc(r) pe 'SYS2.VTAPE.**' id(VTAPE STCs) ad 'SYS3.VTAPE.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('CA VTAPE Install DS') pe 'SYS3.VTAPE.**' id(<syspaudt> <tstcaudt>) acc(a) pe 'SYS3.VTAPE.**' id(<audtaudt> authorized users) acc(r) pe 'SYS3.VTAPE.**' id(VTAPE STCs) setr generic(dataset) refresh

b
CA VTAPE STC data sets will be properly protected.
CM-5 - Medium - CCI-001499 - V-224445 - SV-224445r1145290_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZVTAR001
Vuln IDs
  • V-224445
  • V-17067
Rule IDs
  • SV-224445r1145290_rule
  • SV-33828
CA VTAPE STC data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
Checks: C-26122r1145015_chk

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(VTASTC). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZVTA0001). Verify that the accesses to the CA VTAPE STC data sets are properly restricted. If the following guidance is true, this is not a finding. The RACF data set rules for the data sets restricts READ access to auditors and authorized users. The RACF data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel and Tape Management personnel. The RACF data set rules for the data sets restricts WRITE and/or greater access to the CA VTAPE's STC(s) and/or batch user(s). The RACF data set rules for the data sets specify UACC(NONE) and NOWARNING.

Fix: F-26110r1145289_fix

The ISSO will ensure that WRITE and/or greater access to CA VTAPE STC data sets 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 data sets and categorize them according to who will have WRITE and/or greater access and if required 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 data sets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: SYS3.VTAPE (data sets that are altered by the product's STCs, this can be more specific) The following commands are provided as a sample for implementing data set controls: ad 'SYS3.VTAPE.**' uacc(none) owner(sys3) - audit(failures(read)) - data('Vendor DS Profile: CA VTAPE') pe 'SYS3.VTAPE.**' id(<syspaudt> <tstcaudt> VTAPE STCs) acc(a) pe 'SYS3.VTAPE.**' id(<tapeaudt> VTAPE STCs) acc(a) pe 'SYS3.VTAPE.**' id(<audtaudt> authorized users) acc(r) setr generic(dataset) refresh

b
CA VTAPE Started Task name is not properly identified/defined to the system ACP.
IA-2 - Medium - CCI-000764 - V-224446 - SV-224446r1145291_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZVTAR030
Vuln IDs
  • V-224446
  • V-17452
Rule IDs
  • SV-224446r1145291_rule
  • SV-33831
CA VTAPE requires a started task that will be restricted to certain resources, data sets, 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-26123r1145018_chk

Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(LISTUSER). Verify that the userid(s) for the CA VTAPE started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. PROTECTED

Fix: F-26111r1145019_fix

The CA VTAPE system 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. A sample is provided here: au SVTS name('CA VTAPE') owner(stc) dfltgrp(stc) nopass au SVTSAS name('CA VTAPE') owner(stc) dfltgrp(stc) nopass

b
CA VTAPE Started task(s) must be properly defined to the STARTED resource class for RACF.
IA-2 - Medium - CCI-000764 - V-224447 - SV-224447r1145023_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZVTAR032
Vuln IDs
  • V-224447
  • V-17454
Rule IDs
  • SV-224447r1145023_rule
  • SV-33833
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.
Checks: C-26124r1145021_chk

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: F-26112r1145022_fix

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