None Computing title z/OS ROSCOE for RACF Security Technical Implementation Guide version 7 releaseinfo Release: 2 Vuln_Num V-224528 Rule_ID SV-224528r1145273_rule Severity medium Rule_Title ROSCOE Install data sets are not properly protected. Vuln_Discuss 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. Check_Content 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 set are properly restricted. If the following guidance is true, this is not a finding. The RACF data set rules for the data sets restrict WRITE and/or greater access to systems programming personnel. The RACF data set rules for the data sets 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 data sets is limited to system programmers, security personnel and auditors only, and all WRITE and/or greater access is logged. The installing systems programmer will identify and document the product data sets and categorize them according to who will have WRITE and/or greater access and if required that all WRITE and/or greater 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.ROSCOE. SYS2A.ROSCOE. SYS3.ROSCOE. SYS3A.ROSCOE. The following commands are provided as a sample for implementing data set controls: ad 'sys2.roscoe.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('Vendor DS Profile: ROSCOE') pe 'sys2.roscoe.**' id(syspaudt) acc(a) pe 'sys2.roscoe.**' id(*) acc(r) ad 'sys2a.roscoe.**' uacc(none) owner(sys2a) - audit(success(update) failures(read)) - data('Roscoe Vendor Datasets') pe 'sys2a.roscoe.**' id(<syspaudt>) acc(a) pe 'sys2a.roscoe.**' id(*) acc(r) ad 'sys3.roscoe.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('Roscoe Vendor Datasets') pe 'sys3.roscoe.**' id(<syspaudt>) acc(a) pe 'sys3.roscoe.**' id(*) acc(r) ad 'sys3a.roscoe.**' uacc(none) owner(sys3a) - audit(success(update) failures(read)) - data('Roscoe Vendor Datasets') pe 'sys3a.roscoe.**' id(<syspaudt>) acc(a) pe 'sys3a.roscoe.**' id(*) acc(r) setr generic(dataset) refresh Not_Reviewed Vuln_Num V-224529 Rule_ID SV-224529r1145275_rule Severity medium Rule_Title ROSCOE STC data sets are not properly protected. Vuln_Discuss 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. Check_Content 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). Verify that access to the ROSCOE STC data sets is 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. If the following guidance is true, this is not a finding. The RACF data set rules for the data sets restrict WRITE and/or greater access to systems programming personnel. The RACF data set rules for the data sets 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 data sets is limited to system 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 data sets are properly restricted and all required accesses are properly logged. Data sets to be protected will be: SYS3.ROSCOE.sys*.** SYS3.ROSCOE.ros*.** The following commands are provided as a sample for implementing data set controls: ad 'sys3.roscoe.ros*.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('Site Customized Profile: ROSCOE') pe 'sys3.roscoe.ros*.**' id(syspaudt) acc(a) pe 'sys3.roscoe.ros*.**' id(roscoe) acc(a) ad 'sys3.roscoe.sys*.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('Site Customized profile: ROSCOE') pe 'sys3.roscoe.sys*.**' id(syspaudt) acc(a) pe 'sys3.roscoe.sys*.**' id(roscoe) acc(a) setr generic(dataset) refresh Not_Reviewed Vuln_Num V-224530 Rule_ID SV-224530r1144969_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 Data Set and Resource Data Collection: - SENSITVE.RPT(ZROS0020). Automated Analysis Refer to the following report produced by the Data Set 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 (SSP) to determine access and/or user group. If the following guidance is true, this is not a finding. The RACF resource access authorizations restrict access to the appropriate personnel. The RACF resource logging is correctly specified. The RACF resource access authorizations are defined with UACC(NONE) and NOWARNING. 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 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.) 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 RACF resource access authorizations restrict access to the appropriate personnel. The RACF resource logging is correctly specified. The RACF resource access authorizations specify UACC(NONE) and NOWARNING. The following commands are provided as a sample for implementing resource controls: RDEFINE RO@RES rosid.** UACC(NONE) OWNER(ADMIN) AUDIT(FAILURE(READ)) RDEFINE RO@RES rosid.ROSCMD.** UACC(NONE) OWNER(ADMIN) AUDIT(FAILURE(READ)) RDEFINE RO@RES rosid.ROSCMD.MONITOR.** UACC(NONE) OWNER(ADMIN) AUDIT(FAILURE(READ)) RDEFINE RO@RES rosid.ROSCMD.ETSO UACC(NONE) OWNER(ADMIN) AUDIT(FAILURE(READ)) RDEFINE RO@RES rosid.ROSCMD.MONITOR.AMS UACC(NONE) OWNER(ADMIN) AUDIT(FAILURE(READ)) PE rosid.ROSCMD.ETSO CLASS(RO@RES) ID(*) ACCESS(READ) PE rosid.ROSCMD.MONITOR.- CLASS(RO@RES) ID(syspaudt) ACCESS(ALTER) PE rosid.ROSCMD.MONITOR.AMS CLASS(RO@RES) ID(syspaudt) ACCESS(ALTER) PE rosid.ROSCMD.MONITOR.AMS CLASS(RO@RES) ID(*) ACCESS(READ) PE rosid.ROSCMD.- CLASS(RO@RES) ID(syspaudt) ACCESS(ALTER) Not_Reviewed Vuln_Num V-224531 Rule_ID SV-224531r1144972_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, data sets, 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 RACF Data Collection: - RACFCMDS.RPT(LISTUSER). Verify that the userid(s) for the ROSCOE started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. PROTECTED Fix_Text The ROSCOE system programmer and the ISSO 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. A sample is provided here: au roscoe name('stc, roscoe') owner(stc) dfltgrp(stc) nopass Not_Reviewed Vuln_Num V-224532 Rule_ID SV-224532r1144975_rule Severity medium Rule_Title ROSCOE Started task(s) must be properly defined to the STARTED resource class for RACF. Vuln_Discuss Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could potentially compromise the operating system, ACP, and customer data. Check_Content Refer to the following report produced by the RACF Data Collection: - DSMON.RPT(RACSPT). Automated Analysis Refer to the following report produced by the RACF Data Collection: - PDI(ZROS0032). Verify that the ROSCOE started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding. Fix_Text The ROSCOE system programmer and the ISSO will ensure that a product's started task(s) is (are) properly identified and/or defined to the System ACP. A unique userid must be assigned for the ROSCOE started task(s) thru a corresponding STARTED class entry. The following sample set of commands is shown here as a guideline: rdef started ROSCOE.** uacc(none) owner(admin) audit(all(read)) stdata(user(ROSCOE) group(stc)) setr racl(started) ref Not_Reviewed Vuln_Num V-224533 Rule_ID SV-224533r1144978_rule Severity medium Rule_Title The Roscoe Resource Class will be 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 RACF Data Collection: - RACFCMDS.RPT(SETROPTS). - DSMON.RPT(RACCDT) - Alternate list of active resource classes. Automated Analysis Refer to the following report produced by the RACF Data Collection: - PDI(ZROS0038). If the ROSCOE resource class(es) is (are) active, this is not a finding. Fix_Text The ISSO will ensure that the Product Resource Class(es) is (are) active. Issue the following commands: SETR CLASSACT(RO@RES) SETR GENERIC(RO@RES) Not_Reviewed Vuln_Num V-224534 Rule_ID SV-224534r1144980_rule Severity medium Rule_Title Product 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 products 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). If the following keywords specify the values in the ROSCOE configuration/parameter control member, this is not a finding. Keyword Value EXTSEC RACF ACFEXT YES CLLEXT YES JOBEXT YES LIBEXT YES MONEXT YES PRVEXT YES RPFEXT YES UPSEXT YES Fix_Text The product systems programmer will verify that any configuration/parameters required to control the security of the product are properly configured and syntactically correct. See the required parameters below: Example Keyword Value EXTSEC RACF ACFEXT YES CLLEXT YES JOBEXT YES LIBEXT YES MONEXT YES PRVEXT YES RPFEXT YES UPSEXT YES Not_Reviewed