z/OS VSS for RACF STIG Version Comparison

There are 3 differences between versions v6 r7 (July 22, 2016) (the "left" version) and v7 r1 (April 2, 2025) (the "right" version).

Check ZVSSR000 was changed between these two versions. Green, underlined text was added, red, struck-out text was removed.

The regular view of the left check and right check may be easier to read.

Title

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

Check Content

a) Refer 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) b) Verify Collection: - PDI(ZVSS0000) Verify that access to the Vanguard Security Solutions (VSS) Install data sets are properly restricted. ___ The restricted. The RACF data set rules for the product install data sets do not restrict UPDATE and/or ALTER access to systems programming personnel. ___ The 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 auditors. The RACF data set rules for the product install data sets do not specify that all (i.e., failures and successes) UPDATE and/or ALTER access will be logged. c) If logged. If all of the above are untrue, there this is NO FINDING. d) If not a finding. If any of the above is true, this is a FINDING. finding.

Discussion

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 product, which could result in compromising the operating system or sensitive data.

Fix

The IAO ISSO will ensure that update and alter access to program product install data sets is limited to System system Programmers, programmers, and read access is limited to Security security personnel and Auditors, auditors, and all update and allocate access is logged. The installing System systems Programmer programmer will identify and document the product data sets and categorize them according to who will have update and alter access and if required that all update and allocate access is logged. He The installing systems programmer will identify if any additional groups have update access for specific data sets, and once documented documented, he will work with the IAO ISSO to ensure see that they are properly restricted to the ACP (Access 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 dataset 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)