acceptedThis 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.07<ProfileDescription></ProfileDescription><ProfileDescription></ProfileDescription><ProfileDescription></ProfileDescription><ProfileDescription></ProfileDescription><ProfileDescription></ProfileDescription><ProfileDescription></ProfileDescription><ProfileDescription></ProfileDescription><ProfileDescription></ProfileDescription><ProfileDescription></ProfileDescription><GroupDescription></GroupDescription>ZROSA000<VulnDiscussion>ROSCOE 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 ROSCOE for ACF2DISADPMS TargetzOS ROSCOE for ACF24128V-16932SV-21879CCI-001499CCI-002234The ISSO will ensure that update and allocate access to program product data sets is limited to system programmers only, and all update and allocate access is logged. Security personnel and auditors should have read access. 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 sets to be protected will be: SYS2.ROSCOE SYS2A.ROSCOE SYS3.ROSCOE SYS3A.ROSCOE The following commands are provided as a sample for implementing dataset controls: $KEY(SYS2) ROSCOE.- UID(syspaudt) R(A) W(L) A(L) E(A) ROSCOE.- UID(secaaudt) R(A) E(A) ROSCOE.- UID(audtaudt) R(A) E(A) $KEY(SYS2A) ROSCOE.- UID(syspaudt) R(A) W(L) A(L) E(A) ROSCOE.- UID(secaaudt) R(A) E(A) ROSCOE.- UID(audtaudt) R(A) E(A) $KEY(SYS3) ROSCOE.- UID(syspaudt) R(A) W(L) A(L) E(A) ROSCOE.- UID(secaaudt) R(A) E(A) ROSCOE.- UID(audtaudt) R(A) E(A) $KEY(SYS3A) ROSCOE.- UID(syspaudt) R(A) W(L) A(L) E(A) ROSCOE.- UID(secaaudt) R(A) E(A) ROSCOE.- UID(audtaudt) R(A) E(A)Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ROSRPT) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZROS0000) Verify that access to the ROSCOE Install data sets are properly restricted. The ACF2 data set rules for the data sets does not restrict UPDATE and/or ALTER access to systems programming personnel. The ACF2 data set rules for the data sets does 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.<GroupDescription></GroupDescription>ZROSA001<VulnDiscussion>ROSCOE STC 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 ROSCOE for ACF2DISADPMS TargetzOS ROSCOE for ACF24128SV-21875V-17067CCI-001499The IAO will ensure that update and allocate access to the ROSCOE started task or batch job data sets is limited to system programmers and the started task only and all update and allocate access is logged. The IAO will ensure that all other accesses to the ROSCOE started task or batch job data sets are properly restricted and all required accesses are properly logged. Data sets to be protected will be SYS3.ROSCOE.SYS** SYS3.ROSCOE.ROSLIB** Example: SET RULE $KEY(SYS3) ROSCOE.SYS- UID(syspudt) R(A) W(L) A(L) E(A) ROSCOE.SYS- UID(stc roscoe) R(A) W(L) A(L) E(A) ROSCOE.ROSLIB- UID(syspudt) R(A) W(L) A(L) E(A) ROSCOE.ROSLIB- UID(stc roscoe) R(A) W(L) A(L) E(A)a) Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ROSSTC) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZROS0001) b) Verify that access to the ROSCOE STC data sets are properly restricted. The data sets in this group are the data sets identified in the ROSACTxx (if used), ROSLIBxx, and SYSAWSx DD statements of the STC or batch JCL. ___ The ACF2 data set rules for the data sets does not restrict UPDATE and/or ALTER access to systems programming personnel. ___ The ACF2 data set rules for the data sets does not restrict UPDATE and/or ALTER access to the product STC(s) and/or batch job(s). c) If all of the above are untrue, there is NO FINDING. d) If any of the above is true, this is a FINDING.<GroupDescription></GroupDescription>ZROSA020<VulnDiscussion>ROSCOE can run with sensitive system privileges, and potentially can circumvent system controls. Failure to properly control access to product resources could result in the compromise of the operating system environment, and compromise the confidentiality and integrity of customer data. Many utilities assign resource controls that can be granted to system 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 ROSCOE for ACF2DISADPMS TargetzOS ROSCOE for ACF24128SV-21876V-17947CCI-000213CCI-002234The ISSO will work with the systems programmer to verify that the following are properly specified in the Access Control Program (ACP). (Note: The resource type, resources, and/or resource prefixes identified below are examples of a possible installation. The actual resource type, 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.) Ensure that all ROSCOE resources and/or generic equivalent are properly protected according to the requirements specified in CA ROSCOE Resources table in the z/OS STIG Addendum. Use CA ROSCOE Resources table in the z/OS STIG Addendum. This table lists the resources, access requirements, and logging requirements for ROSCOE ensure the following guidelines are followed: The ACF2 resources are defined with a default access of PREVENT. The ACF2 resource access authorizations restrict access to the appropriate personnel. The ACF2 resource logging is correctly specified. The following commands are provided as a sample for implementing resource controls: $KEY(rosid) TYPE(ROS) ROSCMD.ETSO UID(*) SEVICE(READ) ROSCMD.MONITOR.- UID(syspaudt) ALLOW ROSCMD.MONITOR.AMS UID(syspaudt) ALLOW ROSCMD.MONITOR.AMS UID(*) SEVICE(READ) ROSCMD.- UID(syspaudt) ALLOW - UID(*) PREVENTRefer to the following report produced by the ACF2 Data Collection and Data Set and Resource Data Collection: - SENSITVE.RPT(ZROS0020) - ACF2CMDS.RPT(RESOURCE) - Alternate report Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZROS0020) Ensure all ROSCOE resources and/or generic equivalent are properly protected according to the requirements specified in the CA ROSCOE Resources table in the z/OS STIG Addendum. Note: Wherever an access or user group is missing, use the Site Security Plan to determine access and/or user group. If the following guidance is true, this is not a finding. The ACF2 resources are defined with a default access of PREVENT. The ACF2 resource access authorizations restrict access to the appropriate personnel. The ACF2 resource logging is correctly specified.<GroupDescription></GroupDescription>ZROSA030<VulnDiscussion>Products that require a started task will require that the started task be restricted to certain resources, datasets and other system functions. By defining the started task as a userid to the system ACP, It allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities, could compromise of the operating system environment, ACP, and customer 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 ROSCOE for ACF2DISADPMS TargetzOS ROSCOE for ACF24128SV-21877V-17452CCI-000764The ROSCOE system programmer and the IAO will ensure that a product's Started Task(s) is properly Identified / defined to the System ACP. If the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes. Most installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified. Example: SET LID CHANGE ROSCOE JOBFROM MUSASS NO-SMCa) Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(LOGONIDS) b) Ensure the following fields are completed for each STC logonid for the product: STC JOBFROM MUSASS NO-SMC c) Ensure the following fields are completed for each Batch logonid for the product: JOB JOBFROM MUSASS NO-SMC d) If the logonids specified in (b) and/or (c) have all the required fields are completed, this is not a FINDING. e) If the logonids specified in (b) and/or (c) do not have all the above fields completed, this is a FINDING.<GroupDescription></GroupDescription>ZROSA038<VulnDiscussion>Failure to use a robust ACP to control a product could potentially compromise the integrity and availability of the MVS operating system and user 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 ROSCOE for ACF2DISADPMS TargetzOS ROSCOE for ACF24128V-18011SV-24845CCI-000336CCI-002358Use SAF security to define and protect the Products resource class(es). Ensure that the following GSO CLASMAP record entry(ies) is (are) defined: CLASMAP.ROSCOE ENTITYLN(nn) RESOURCE(ROSRES) RSRCTYPE(rosid) Note: The site determines the appropriate three letter RSRCTYPE that is unique for each Roscoe system. The ENTITYLN should be appropriate for the site's installation. Example: SET C(GSO) LIST CLASMAP.ROSCOE INSERT CLASMAP.ROSCOE ENTITYLN(39) RESOURCE(ROSRES) RSRCTYPE(ROS) F ACF2,REFRESH(CLASMAP) Ensure that the following GSO CLASMAP record entries are defined: CLASMAPqual RESOURCE(ROSRES) RSRCTYPE(rosid) ENTITYLN(nn) If all of the items in (b) are true, this is not a finding. If any item in (b) is untrue, this is a finding. Note: The site determines the appropriate three letter RSRCTYPE that is unique for each Roscoe system. The ENTITYLN should be appropriate for the site's installation.<GroupDescription></GroupDescription>ZROSA040<VulnDiscussion>Product configuration/parameters control the security and operational characteristics of products. If these parameter values are improperly specified, security and operational controls may be weakened. This exposure may threaten the availability of the product applications, and compromise the confidentiality of customer 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 ROSCOE for ACF2DISADPMS TargetzOS ROSCOE for ACF24128V-18014SV-21878CCI-000015CCI-000381The product systems programmer will verify that any configuration/parameters that are required to control the security of the product are properly configured and syntactically correct. See the required parameters below: Example Keyword Value EXTSEC ACF2 ACFEXT YES CLLEXT YES JOBEXT YES LIBEXT YES MONEXT YES PRVEXT YES RPFEXT YES UPSEXT YESHave the product's system programmer display the configuration/parameters control statements used in the current running product to define or enable security. This information is located in the SYSIN DD statement in the JCL of the STC/Batch job. Automated Analysis Refer to the following report produced by the z/OS Data Collection: - PDI(ZROS0040) Verify the following specifications: Keyword Value EXTSEC ACF2 ACFEXT YES CLLEXT YES JOBEXT YES LIBEXT YES MONEXT YES PRVEXT YES RPFEXT YES UPSEXT YES If the above is true, this is not a finding. If the above is untrue, this is a finding.