What changed in z/OS VSS for RACF STIG V7R2V7R2 changes

Check text

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 UPDATEWRITE and/or ALTERgreater 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) UPDATEWRITE and/or ALTERgreater access will be logged. If all of the above are untrue, this is not a finding. If any of the above is true, this is a finding.

Fix text

The ISSO will ensure that updateWRITE and/or altergreater access to program product install data sets is limited to system programmers, and readREAD access is limited to security personnel and auditors, and all updateWRITE and/or allocategreater access is logged. The installing systems programmer will identify and document the product data sets and categorize them according to who will have updateWRITE and/or altergreater access and if required that all updateWRITE and/or allocategreater access is logged. The installing systems programmer will identify if any additional groups have updateUPDATE 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 datasetdata 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)

V-224543 in V7R2

Check text

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, UPDATE, and/or ALTERgreater 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) UPDATEWRITE and/or ALTERgreater access will be logged. If all of the above are untrue, this is not a finding. If any of the above is true, this is a finding.

Fix text

The ISSO will ensure that readREAD, updateUPDATE, and alterALTER access to program product user data sets is limited to system programmers, security personnel, and auditors and all updateWRITE and/or altergreater access is logged. The installing systems programmer will identify and document the product data sets and categorize them according to who will have updateWRITE and/or altergreater access and if required that all updateWRITE and/or altergreater access is logged. The installing systems programmer will identify if any additional groups have updateUPDATE 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 datasetdata 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)

V-224544 in V7R2

Check text

Refer to the following report produced by the Access Control Program (ACP) Data Collection and 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.

V-224545 in V7R2