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

z/OS VSS for RACF 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-224543 Medium checkfix Vanguard Security Solutions (VSS) Install data sets are not properly protected.
  • V-224544 Medium checkfix Vanguard Security Solutions (VSS) User data sets are not properly protected.
  • V-224545 Medium check Vanguard Security Solutions resources must be properly defined and protected.
Sort by
b
Vanguard Security Solutions (VSS) Install data sets are not properly protected.
CM-5 - Medium - CCI-001499 - V-224543 - SV-224543r1145006_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZVSSR000
Vuln IDs
  • V-224543
  • V-16932
Rule IDs
  • SV-224543r1145006_rule
  • SV-24657
Vanguard Security Solutions (VSS) Install data sets provide the capability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their 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-26226r1145004_chk

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(VSSRPT). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZVSS0000). Verify that access to the Vanguard Security Solutions (VSS) Install data sets are properly restricted. If the following guidance is true, this is not a finding. The RACF data set rules for the product install data sets do not restrict WRITE and/or greater access to systems programming personnel. The RACF data set rules for the product install data sets do not restrict READ access to systems programming personnel, security personnel and auditors. The RACF data set rules for the product install data sets do not specify that all (i.e., failures and successes) WRITE and/or greater access will be logged.

Fix: F-26214r1145005_fix

The ISSO will ensure that WRITE and/or greater access to program product install data sets is limited to system programmers, and READ access is limited to security personnel and auditors, and all WRITE and/or greater access is logged. 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 UPDATE 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 set prefix to be protected will be: SYS2.VSS. SYS2A.VSS. SYS3.VSS.VANOPTS The following commands are provided as a sample for implementing data set controls: ad 'sys2.vss.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('Vendor DS Profile: Vanguard Security Solutions') pe 'sys2.vss.**' id(syspaudt) acc(a) pe 'sys2.vss.**' id(secaaudt secdaudt audtaudt) acc(r) ad 'sys2a.vss.**' uacc(none) owner(sys2a) - audit(success(update) failures(read)) - data('Vendor Loadlib: Vanguard Security Solutions') pe 'sys2a.vss.**' id(syspaudt) acc(a) pe 'sys2a.vss.**' id(secaaudt secdaudt audtaudt) acc(r) ad 'sys3.vss.vanopts.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('Site Customized DS Profile: Vanguard Security Solutions') pe 'sys3.vss.vanopts.**' id(syspaudt) acc(a) pe 'sys3.vss.vanopts.**' id(secaaudt secdaudt audtaudt) acc(r)

b
Vanguard Security Solutions (VSS) User data sets are not properly protected.
CM-5 - Medium - CCI-001499 - V-224544 - SV-224544r1145009_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZVSSR002
Vuln IDs
  • V-224544
  • V-21592
Rule IDs
  • SV-224544r1145009_rule
  • SV-24915
VSS User data sets provide the capability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their 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-26227r1145007_chk

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(VSSUSER). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZVSS0002). Verify that access to the Vanguard Security Solutions (VSS) User data sets are properly restricted. If the following guidance is true, this is not a finding. The RACF data set rules for the product user data sets do not restrict READ and/or greater access to systems programming personnel, security personnel, and auditors. The RACF data set rules for the product user data sets do not specify that all (i.e., failures and successes) WRITE and/or greater access will be logged.

Fix: F-26215r1145008_fix

The ISSO will ensure that READ, UPDATE, and ALTER access to program product user data sets is limited to system programmers, security personnel, and auditors and all WRITE and/or greater access is logged. 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 UPDATE 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 set prefix to be protected will be: SYS3.VSS. The above prefix can specify specific data sets, these would include the VSAM and JCL data sets. The following commands are provided as a sample for implementing data set controls: ad 'sys3.vss.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('Site Customized DS Profile: Vanguard Security Solutions') pe 'sys3.vss.**' id(syspaudt secaaudt audtaudt) acc(a)

b
Vanguard Security Solutions resources must be properly defined and protected.
AC-3 - Medium - CCI-000213 - V-224545 - SV-224545r1145011_rule
RMF Control
AC-3
Severity
M
CCI
CCI-000213
Version
ZVSSR020
Vuln IDs
  • V-224545
  • V-17947
Rule IDs
  • SV-224545r1145011_rule
  • SV-24912
Program products can run with sensitive system privileges, and potentially can circumvent system controls. Failure to properly control access to program product resources could result in the compromise of the operating system environment, and compromise the confidentiality of customer data. Many utilities assign resource controls that can be granted to systems programmers only in greater than read authority. Resources are also granted to certain nonsystems personnel with read only authority.
Checks: C-26228r1145010_chk

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(FACILITY). - RACFCMDS.RPT(FACILITY) - Alternate report. Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZVSS0020) Verify that the accesses to resources and/or generic equivalent are properly restricted according to the requirements specified in Vanguard Security Solutions Resources table in the z/OS STIG Addendum. If the following guidance is true, this is not a finding. The RACF resources are defined with a default access of NONE. The RACF resource access authorizations restrict access to the appropriate personnel. The RACF resource logging requirements are specified. The RACF resource access authorizations are defined with UACC(NONE) and NOWARNING. The RACF resource VSR$.SCOPE allowed READ access when approved and documented by ISSM or equivalent Security Authority.

Fix: F-26216r1070124_fix

Configure ACP resource definitions in accordance with Vanguard Security Solutions Resources and Vanguard Security Solutions Resources Descriptions tables in the z/OS STIG Addendum. These tables list the resources, descriptions, and access and logging requirements. Ensure the guidelines for the resources and/or generic equivalent specified in the z/OS STIG Addendum are followed. (Note: The resources, and/or resource prefixes identified below are examples of a possible installation. The actual resources, and/or resource prefixes are determined when the product is actually installed on a system through the product's installation guide and can be site specific.) The following commands are provided as a sample for implementing resource controls: rdef facility vra$.acstask.** uacc(none) owner(admin) - audit(all(read)) - data('protected per zvssr020') pe vra$.acstask.** cl(facility) id(<audtaudt>) acc(read) pe vra$.acstask.** cl(facility) id(<secaaudt>) acc(read) Sample scope definition: rdef facility vsr$.** uacc(none) owner(admin) audi(a(r)) - data('deny-by-default for Vanguard Advisor Reporter') rdef facility vsr$.scope uacc(none) owner(admin) - audit(a(u)) data('Vanguard Advisor Reporter Auth Scope')