z/OS Catalog Solutions for RACF Security Technical Implementation Guide

  • Version/Release: V6R5
  • Published: 2022-10-07
  • Expand All:
  • Severity:
  • Sort:
Compare

Select any two versions of this STIG to compare the individual requirements

View

Select any old version/release of this STIG to view the previous requirements

This 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: [email protected].
b
Catalog Solutions Install data sets are not properly protected.
AC-3 - Medium - CCI-000213 - V-224459 - SV-224459r868339_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZCSLR000
Vuln IDs
  • V-224459
  • V-16932
Rule IDs
  • SV-224459r868339_rule
  • SV-19581
Catalog Solutions is a very powerful tool that can pose risks if not properly controlled. If security is not properly implemented, the users of the product could present data integrity exposures, bypass security for catalog datasets, other VSAM files, and aliases. Catalog Solutions 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.
Checks: C-26136r868337_chk

a) Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CSLPROD) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCSL0000) b) Verify that access to the Catalog Solutions Install data sets are properly restricted. ___ The RACF data set rules for the data sets does not restrict UPDATE and/or ALTER access to only systems programming personnel. ___ The RACF 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. c) If all of the above are untrue, there is no finding. d) If any of the above is true, this is a finding.

Fix: F-26124r868338_fix

The ISSO will ensure that update and allocate access to program product data sets is limited to systems programmers only, unless a letter justifying access is filed with the ISSO, 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 ALTER access is logged. The installing systems programmer will identify if any additional groups have UPDATE access for specific data sets, and once documented work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system. The following commands are provided as a sample for implementing dataset controls: ad 'sys2.csl.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('Catalog Solution Vendor Datasets: Ref SRR PDI ZCSLR000') pe 'sys2.csl.**' id(<syspaudt>) acc(a) ad 'sys3.csl.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('Catalog Solution Customized Datasets: Ref SRR PDI ZCSLR000') pe 'sys3.csl.**' id(<syspaudt>) acc(a) setr generic(dataset) refresh Catalog Solution allows you to monitor your catalog environment to help identify and correct structural catalog problems before they create system outages. Catalog Solution is a valuable tool in planning for or implementing System Managed Storage, as well as ensuring daily system availability. Catalog Solution is a comprehensive facility for the management, maintenance, repair, and recovery of the MVS catalog environment that complements the IDC Access Method Services (IDCAMS) utility. Catalog Solution helps you in the five key areas: Maintenance, Diagnostics, Reporting, Backup and Recovery, and SMF management. Catalog Solution is a very powerful tool that can pose risks if not properly controlled. If security is not properly implemented, the users of the product could present data integrity exposures, bypass security for catalog datasets, other VSAM files, and aliases. As an authorized program, Catalog Solution bypasses many of the normal system security facilities - catalog and dataset passwords in particular. Improper use of Catalog Solution can result in non-synchronized catalog, dataset, or VVDS record groups. Therefore, certain commands should not be made available to the user community. As delivered, Catalog Solution bypasses dataset security checking for VSAM datasets and BCS processing. Clearly there are risks associated and valid requirements exist to ensure full external security controls are properly implemented for the Catalog Solution product. Properly securing the use of various commands and features is crucial. All Catalog Solution functions should be reviewed for potential security exposures and to prevent unauthorized use. Some Catalog Solution functions allow for bypassing of security controls, and as such shall be restricted to systems programmers who perform in the specific role of Storage management.

b
Catalog Solutions resources must be properly defined and protected.
AC-4 - Medium - CCI-000035 - V-224460 - SV-224460r868342_rule
RMF Control
AC-4
Severity
Medium
CCI
CCI-000035
Version
ZCSLR020
Vuln IDs
  • V-224460
  • V-17947
Rule IDs
  • SV-224460r868342_rule
  • SV-19622
Catalog Solutions 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 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 non-systems personnel with read only authority.
Checks: C-26137r868340_chk

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ZCSL0020) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCSL0020) Ensure that all Catalogued Solutions resources and/or generic equivalents are properly protected according to the requirements specified in Catalogued Solutions Resources table in the z/OS STIG Addendum. 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: F-26125r868341_fix

The ISSO will work with the systems programmer to verify that the following are properly specified in the ACP. (Note: The resource class, resources, and/or resource prefixes identified below are examples of a possible installation. The actual resource class, 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 Catalogued Solutions resources and/or generic equivalents are properly protected according to the requirements specified in Catalogued Solutions Resources table in the z/OS STIG Addendum. Use Catalog Solutions Resources table in the z/OS STIG Addendum. This table lists the resources, access requirements, and logging requirements for Catalogued Solutions. 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: RDEF FACILITY hlq1.** UACC(NONE) OWNER(syspaudt) AUDIT(ALL(READ)) RDEF FACILITY hlq1.hlq2.GLOBAL.DATASET.** UACC(NONE) OWNER(syspaudt) AUDIT(ALL(READ)) PERMIT hlq1.hlq2.GLOBAL.DATASET CLASS(FACILITY) ACCESS(READ) ID(dasdaudt) PERMIT hlq1.hlq2.GLOBAL.DATASET CLASS(FACILITY) ACCESS(READ) ID(dasbaudt) PERMIT hlq1.hlq2.GLOBAL.DATASET CLASS(FACILITY) ACCESS(READ) ID(syspaudt)