None Computing title z/OS ROSCOE for ACF2 Security Technical Implementation Guide version 7 releaseinfo Release: 2 Vuln_Num V-224336 Rule_ID SV-224336r1141623_rule Severity medium Rule_Title ROSCOE Install datasets are not properly protected. Vuln_Discuss ROSCOE Install datasets provide the capability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their datasets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data. Check_Content Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(ROSRPT). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZROS0000). Verify that access to the ROSCOE Install datasets is properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to systems programming personnel. The ACF2 dataset rules for the datasets do not specify that all (i.e., failures and successes) WRITE and/or greater access will be logged. Fix_Text The ISSO will ensure that WRITE and/or greater access to program product datasets is limited to systems programmers only, and all WRITE and/or greater access is logged. Security personnel and auditors should have READ access. The installing systems programmer will identify and document the product datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure that all WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have UPDATE access for specific datasets, and once documented, will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system. Datasets 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) Not_Reviewed Vuln_Num V-224337 Rule_ID SV-224337r1141626_rule Severity medium Rule_Title ROSCOE STC datasets are not properly protected. Vuln_Discuss ROSCOE STC datasets provide the capability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their datasets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data. Check_Content Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(ROSSTC). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZROS0001). Verify that access to the ROSCOE STC datasets is properly restricted. The datasets in this group are the datasets identified in the ROSACTxx (if used), ROSLIBxx, and SYSAWSx DD statements of the STC or batch JCL. If the following guidance is true, this is not a finding. The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to systems programming personnel. The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to the product STC(s) and/or batch job(s). Fix_Text The ISSO will ensure that WRITE and/or greater access to the ROSCOE started task or batch job datasets is limited to systems programmers and the started task only, and all WRITE and/or greater access is logged. The ISSO will ensure that all other accesses to the ROSCOE started task or batch job datasets are properly restricted and all required accesses are properly logged. Datasets 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) Not_Reviewed Vuln_Num V-224338 Rule_ID SV-224338r1141629_rule Severity medium Rule_Title ROSCOE resources must be properly defined and protected. Vuln_Discuss 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 systems programmers only in greater than read authority. Resources are also granted to certain nonsystems personnel with read only authority. Check_Content Refer to the following report produced by the ACF2 Data Collection and dataset and Resource Data Collection: - SENSITVE.RPT(ZROS0020). - ACF2CMDS.RPT(RESOURCE) - Alternate report. Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZROS0020). Verify 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. Fix_Text The 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 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(*) PREVENT Not_Reviewed Vuln_Num V-224339 Rule_ID SV-224339r1144193_rule Severity medium Rule_Title ROSCOE Started Task name is not properly identified/defined to the system ACP. Vuln_Discuss Products that require a started task will require that the started task be restricted to certain resources, datasets, and other system functions. Defining the started task as a userid to the system ACP allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities could compromise the operating system environment, ACP, and customer data. Check_Content Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(LOGONIDS). If the logonids specified below have all the required fields completed and if the following attributes are defined, this is not a finding. For Started Tasks logonid: STC JOBFROM MUSASS NO-SMC For Batch logonid: JOB JOBFROM MUSASS NO-SMC Fix_Text The ROSCOE systems programmer and the ISSO will verify 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 STC JOBFROM MUSASS NO-SMC Not_Reviewed Vuln_Num V-224340 Rule_ID SV-224340r1141634_rule Severity medium Rule_Title The ROSCOE's Resource Class is not defined or active in the ACP. Vuln_Discuss 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. Check_Content Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(ACFGSO). If the following GSO CLASMAP record entry(ies) is (are) defined, this is not a finding. CLASMAPqual RESOURCE(ROSRES) RSRCTYPE(rosid) ENTITYLN(nn) 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. Fix_Text Use 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) Not_Reviewed Vuln_Num V-224341 Rule_ID SV-224341r1141636_rule Severity medium Rule_Title ROSCOE configuration/parameter values are not specified properly. Vuln_Discuss 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. Check_Content Have the product's systems 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. This is not a finding. 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. Fix_Text The 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 YES Not_Reviewed