acceptedz/OS VSS for RACF Security Technical Implementation GuideThis 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.DISASTIG.DOD.MILRelease: 1 Benchmark Date: 02 Apr 20253.51.10.07I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>SRG-OS-000080<GroupDescription></GroupDescription>ZVSSR000Vanguard Security Solutions (VSS) Install data sets are not properly protected.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target zOS VSS for RACFDISADPMS TargetzOS VSS for RACF4165V-16932SV-24657CCI-001499CCI-002234The ISSO will ensure that update and alter access to program product install data sets is limited to system programmers, and read access is limited to security personnel and auditors, and all update and allocate access is logged.
The installing systems 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. 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 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)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.
The RACF data set rules for the product install data sets do not restrict UPDATE and/or ALTER 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) UPDATE and/or ALTER 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.SRG-OS-000080<GroupDescription></GroupDescription>ZVSSR002Vanguard Security Solutions (VSS) User data sets are not properly protected.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target zOS VSS for RACFDISADPMS TargetzOS VSS for RACF4165SV-24915V-21592CCI-001499The 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 update and alter access is logged.
The installing systems 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 alter 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 dataset 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)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.
The RACF data set rules for the product user data sets do not restrict READ, UPDATE, and/or ALTER 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) UPDATE and/or ALTER 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.SRG-OS-000018<GroupDescription></GroupDescription>ZVSSR020Vanguard Security Solutions resources must be properly defined and protected.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target zOS VSS for RACFDISADPMS TargetzOS VSS for RACF4165SV-24912V-17947CCI-000213CCI-002234Configure 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')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.