Vanguard Security Solutions (VSS) Install data sets are not properly protected.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-224543	SRG-OS-000080	ZVSSR000	SV-224543r1145006_rule	2025-09-27	7

Description
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.

ℹ️ Check
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.

ℹ️ Check

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

✔️ 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)