z/OS HCD for ACF2 Security Technical Implementation Guide

  • Version/Release: V7R1
  • Published: 2025-02-25
  • Released: 2025-04-02
  • 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-224299 - SV-224299r1081019_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZHCDA000
Vuln IDs
  • V-224299
  • V-16932
Rule IDs
  • SV-224299r1081019_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 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-25976r1070042_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 Hardware Configuration Definition (HCD) install data sets are properly restricted. The ACF2 data set rules for the data sets restricts READ access to auditors, automated operations, operators, and systems programming personnel. The ACF2 data set rules for the data sets restricts UPDATE and/or ALTER access to systems programming personnel. The ACF2 data set rules for the data sets specifies that all (i.e., failures and successes) UPDATE and/or ALTER access are logged.

Fix: F-25964r1081018_fix

The ISSO will ensure that update and allocate access to IBM HCD install data sets is limited to system programmers only, and all update and alter 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 update and alter access and if required that all update and allocate access is logged. The installing systems programmer will identify if any additional groups have update and/or alter 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 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 data sets are not properly protected.
CM-5 - Medium - CCI-001499 - V-224300 - SV-224300r1081041_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZHCDA002
Vuln IDs
  • V-224300
  • V-21592
Rule IDs
  • SV-224300r1081041_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 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-25977r1070045_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. Note: Currently on most CSD systems the prefix for these data sets is SYS3.IODF*.**. The ACF2 data set rules for the data sets does not restrict UPDATE and/or ALTER access to systems programming personnel. The ACF2 data set rules for the data sets does not restrict READ access to automated operations users and operations personnel. The ACF2 data set rules for the datasets does not specify that all (i.e., failures and successes) UPDATE and/or ALTER access will be logged. If all of the above are untrue, this is not a finding. If any of the above is true, this is a finding.

Fix: F-25965r1081040_fix

The ISSO will ensure that update, and allocate access to program product user data sets is limited to system programmers and all update and allocate 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 data sets and categorize them according to who will have update and alter access and if required that all update and allocate 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 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-224301r1069981_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZHCDA020
Vuln IDs
  • V-224301
  • V-17947
Rule IDs
  • SV-224301r1069981_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 system programmers only in greater than read authority. Resources are also granted to certain non-systems personnel with read only authority.
Checks: C-25978r1069979_chk

Refer to the following report produced by the ACF2 Data Collection and Data Set and Resource Data Collection: - SENSITVE.RPT(FACILITY) - ACF2CMDS.RPT(RESOURCE) - Alternate report 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 Hardware Configuration Definition (HCD) resources in the FACILITY resource class, TYPE(FAC): 1. The ACF2 rules for the CBD resource specify a default access of NONE. 2. There are no ACF2 rules that allow access to the CBD resource. 3. 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. 4. 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. If any of the above are untrue, this is a finding. If all items above are true, this is not a finding.

Fix: F-25966r1069980_fix

The systems programmer will work with the ISSO to verify that the following are properly specified in the Access Control Program (ACP). 1) The ACF2 rules for the CBD resource specify a default access of NONE. 2) There are no ACF2 rules that allow access to the CBD resource. Example: SET R(FAC) $KEY(CBD) TYPE(FAC) - UID(*) PREVENT DATA(SRR FINDING FOR HCD) 3) 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. 4) 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