IBM Hardware Configuration Definition (HCD) install data sets are not properly protected.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
|---|---|---|---|---|---|---|
| medium | V-224489 | SRG-OS-000080 | ZHCDR000 | SV-224489r1145241_rule | 2025-09-27 | 7 |
| Description |
|---|
| 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. |
| ℹ️ Check |
|---|
| 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 |
|---|
| 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 |