IBM Hardware Configuration Definition (HCD) User data sets are not properly protected.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-224300	SRG-OS-000259	ZHCDA002	SV-224300r1081041_rule	2025-02-25	7

Description
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.

ℹ️ Check
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.

ℹ️ Check

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
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)

✔️ 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)