Cyber Trackr - Free Compliance Library
Cyber Trackr
The Free Compliance Library

z/OS HCD for RACF Security Technical Implementation Guide - V7R2

  • Version/Release: V7R2
  • Published: 2025-09-27
  • Released: 2025-10-01
  • 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: disa.stig_spt@mail.mil.
b
IBM Hardware Configuration Definition (HCD) install data sets are not properly protected.
CM-5 - Medium - CCI-001499 - V-224489 - SV-224489r1145241_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZHCDR000
Vuln IDs
  • V-224489
  • V-16932
Rule IDs
  • SV-224489r1145241_rule
  • SV-30545
IBM HCD product has the ability 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-26172r1144843_chk

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(HCDRPT). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZHCD0000). Verify that access to the IBM HCD install data sets are properly restricted. If the following guidance is true, this is not a finding. The RACF data set rules for the data sets restricts READ access to auditors, automated operations, operators, and systems programming personnel. The RACF data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel. The RACF data set rules for the data sets specifies that all (i.e., failures and successes) WRITE and/or greater access are logged. The RACF data set access authorizations specify UACC(NONE) and NOWARNING.

Fix: F-26160r1145240_fix

The ISSO will ensure that WRITE and/or greater access to IBM HCD install data sets is limited to system programmers only, and all WRITE and/or greater access is logged. Auditors, automated operations, and operators should have READ access. 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 systems programmer will identify if any additional groups have WRITE and/or greater 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: SYS1.SCBD* The following commands are provided as a sample for implementing data set controls: ad 'SYS1.SCBD*.**' uacc(none) owner(sys1) - audit(success(update) failures(read)) - data('Vendor DS Profile: hcd') pe 'SYS1.SCBD*.**' id(syspaudt tstcaudt) acc(a) pe 'SYS1.SCBD*.**' id(audtaudt autoaudt operaudt) acc(r) setr generic(dataset) refresh

b
IBM Hardware Configuration Definition (HCD) User data sets are not properly protected.
CM-5 - Medium - CCI-001499 - V-224490 - SV-224490r1145243_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZHCDR002
Vuln IDs
  • V-224490
  • V-21592
Rule IDs
  • SV-224490r1145243_rule
  • SV-30598
IBM HCD product has the capability to use privileged functions and/or to 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-26173r1145242_chk

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(HCDUSER). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZHCD0002). Verify that the access to the IBM HCD install data sets is properly restricted. The data sets to be protected are the production and working IODF data sets as well as the activity log for the IODF data sets. If the following guidance is true, this is not a finding. Note: Currently on most CSD systems the prefix for these data sets is SYS3.IODF*.**. 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 READ access to automated operations users and operations 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. The RACF data set access authorizations specify UACC(NONE) and NOWARNING.

Fix: F-26161r1144847_fix

The ISSO will ensure that WRITE and/or greater access to program product user data sets is limited to systems programmers and all WRITE and/or greater access is logged. Ensure that READ access is limited to auditors, Operations personnel, and Automated Operations users. The installing systems programmer will identify and document the product user 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 sets to be protected will be: The production IODF data sets. (i.e., hhhhhhhh.IODFnn) The working IODF data sets. (i.e., hhhhhhhh.IODFnn.) The activity log for the IODF data sets. (i.e., hhhhhhhh.IODFnn.ACTLOG) Note: Currently on most CSD systems the prefix for these data sets is SYS3.IODF*.**. The following commands are provided as a sample for implementing data set controls: ad 'sys3.iodf*.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('Vendor DS Profile: IODF for HCD') pe 'sys3.iodf*.**' id(syspaudt tstcaudt) acc(a) pe 'sys3.iodf*.**' id(audtaudt autoaudt operaudt) acc(r)

b
IBM Hardware Configuration Definition (HCD) resources are not properly defined and protected.
AC-3 - Medium - CCI-000213 - V-224491 - SV-224491r1145245_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZHCDR020
Vuln IDs
  • V-224491
  • V-17947
Rule IDs
  • SV-224491r1145245_rule
  • SV-30583
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.
Checks: C-26174r1145244_chk

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(FACILITY). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZHCD0020). Review the following items for the IBM HCD resources in the FACILITY resource class. If the following guidance is true, this is not a finding. The RACF rules for the CBD resource specify a default access of NONE. The RACF rules for the CBD.CPC.IOCDS and CBD.CPC.IPLPARM resources restrict access to systems programming and operations personnel as well as possibly any automated operations batch users with access of READ. The RACF rules for the CBD.CPC.IOCDS and CBD.CPC.IPLPARM resources are restricted access to systems programming with access of UPDATE and logged. All RACF rules are defined with UACC(NONE).

Fix: F-26162r1144850_fix

The systems programmer will work with the ISSO to verify that the following are properly specified in the Access Control Program (ACP). The RACF rules for the CBD resource specify a default access of NONE. There are no RACF rules that allow access to the CBD resource. Example: rdef facility cbd.** uacc(none) owner(admin) audit(failure(read)) - data('added per PDI ZHCD0020') The RACF rules for the CBD.CPC.IOCDS and CBD.CPC.IPLPARM resources are restricted access to systems programming and operations personnel as well as possibly any automated operations batch users with access of READ. The RACF rules for the CBD.CPC.IOCDS and CBD.CPC.IPLPARM resources are restricted access to systems programming with access of UPDATE and logged. All RACF rules are defined with UACC(NONE). Example: rdef facility cbd.cpc.iocds.** uacc(none) owner(admin) - audit(success(update) failures(read)) - data('added per PDI ZHCD0020') rdef facility cbd.cpc.iplparm.** uacc(none) owner(admin) - audit(success(update) failures(read)) - data('added per PDI ZHCD0020') pe cbd.cpc.iocds.** cl(facility) id(syspaudt) acc(u) pe cbd.cpc.iocds.** cl(facility) id(operaudt) acc(r) pe cbd.cpc.iocds.** cl(facility) id(autoaudt) acc(r) pe cbd.cpc.iplparm.** cl(facility) id(syspaudt) acc(u) pe cbd.cpc.iplparm.** cl(facility) id(operaudt) acc(r) pe cbd.cpc.iplparm.** cl(facility) id(autoaudt) acc(r) setr racl(facility) ref