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

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

  • Version/Release: V7R2
  • Published: 2025-09-23
  • 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 datasets are not properly protected.
CM-5 - Medium - CCI-001499 - V-224299 - SV-224299r1141517_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZHCDA000
Vuln IDs
  • V-224299
  • V-16932
Rule IDs
  • SV-224299r1141517_rule
  • SV-30544
IBM HCD product has the ability 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.
Checks: C-25976r1141515_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(HCDRPT). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZHCD0000). Verify that access to the IBM Hardware Configuration Definition (HCD) install datasets is properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset rules for the datasets restrict READ access to auditors, automated operations, operators, and systems programming personnel. The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to systems programming personnel. The ACF2 dataset rules for the datasets specify that all (i.e., failures and successes) WRITE and/or greater access is logged.

Fix: F-25964r1141516_fix

The ISSO will ensure that WRITE and/or greater access to IBM HCD install datasets is limited to systems 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 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 WRITE and/or greater 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: SYS1.SCBD* The following commands are provided as a sample for implementing dataset controls: $KEY(SYS1) SCBD- UID(syspaudt) R(A) W(L) A(L) E(A) SCBD- UID(tstcaudt) R(A) W(L) A(L) E(A) SCBD- UID(audtaudt) R(A) E(A) SCBD- UID(autoaudt) R(A) E(A) SCBD- UID(operaudt) R(A) E(A)

b
IBM Hardware Configuration Definition (HCD) User datasets are not properly protected.
CM-5 - Medium - CCI-001499 - V-224300 - SV-224300r1141520_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZHCDA002
Vuln IDs
  • V-224300
  • V-21592
Rule IDs
  • SV-224300r1141520_rule
  • SV-30577
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 datasets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.
Checks: C-25977r1141518_chk

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

The ISSO will ensure that WRITE and/or greater access to program product user datasets 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 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: The production IODF datasets (i.e., hhhhhhhh.IODFnn) The working IODF datasets (i.e., hhhhhhhh.IODFnn) The activity log for the IODF datasets (i.e., hhhhhhhh.IODFnn.ACTLOG) Note: Currently on most CSD systems the prefix for these datasets is SYS3.IODF*.**. The following commands are provided as a sample for implementing dataset controls: SET RULE $KEY(S3I) $PREFIX(SYS3) IODF-.- UID(syspaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT SYSPROG) IODF-.- UID(tstcaudt) R(A) W(L) A(L) E(A) IODF-.- UID(audtaudt) R(A) E(A) DATA(DEFAULT Auditor) IODF-.- UID(autoaudt) R(A) E(A) IODF-.- UID(operaudt) R(A) E(A)

b
IBM Hardware Configuration Definition (HCD) resources are not properly defined and protected.
AC-3 - Medium - CCI-000213 - V-224301 - SV-224301r1141523_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZHCDA020
Vuln IDs
  • V-224301
  • V-17947
Rule IDs
  • SV-224301r1141523_rule
  • SV-30582
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 non-systems personnel with read only authority.
Checks: C-25978r1141521_chk

Refer to the following report produced by the ACF2 Data Collection and dataset and Resource Data Collection: - SENSITVE.RPT(FACILITY). - ACF2CMDS.RPT(RESOURCE) - Alternate report. Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZHCD0020). Review the following items for the IBM Hardware Configuration Definition (HCD) resources in the FACILITY resource class, TYPE(FAC). If the following guidance is true, this is not a finding. The ACF2 rules for the CBD resource specify a default access of NONE. No ACF2 rules allow access to the CBD resource. The ACF2 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 ACF2 rules for the CBD.CPC.IOCDS and CBD.CPC.IPLPARM resources are restricted access to systems programming with access of UPDATE and logged.

Fix: F-25966r1141522_fix

The systems programmer will work with the ISSO to ensure that the following are properly specified in the Access Control Program (ACP). The ACF2 rules for the CBD resource specify a default access of NONE. No ACF2 rules allow access to the CBD resource. Example: SET R(FAC) $KEY(CBD) TYPE(FAC) - UID(*) PREVENT DATA(SRR FINDING FOR HCD) The ACF2 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 ACF2 rules for the CBD.CPC.IOCDS and CBD.CPC.IPLPARM resources are restricted access to systems programming with access of UPDATE and logged. Example: SET R(FAC) $KEY(CBD) TYPE(FAC) CPC.IOCDS.- UID(syspaudt) SERVICE(READ,UPDATE) LOG CPC.IOCDS.- UID(operaudt) SERVICE(READ) ALLOW CPC.IOCDS.- UID(autoaudt) SERVICE(READ) ALLOW CPC.IPLPARM.- UID(syspaudt) SERVICE(READ,UPDATE) LOG CPC.IPLPARM.- UID(operaudt) SERVICE(READ) ALLOW CPC.IPLPARM.- UID(autoaudt) SERVICE(READ) ALLOW