IBM Hardware Configuration Definition (HCD) resources are not properly defined and protected.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-224491	SRG-OS-000018	ZHCDR020	SV-224491r1070137_rule	2025-02-24	7

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

Description

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.

ℹ️ Check
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: 1. The RACF rules for the CBD resource specify a default access of NONE. 2. 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. 3. 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. 4. All RACF rules are defined with UACC(NONE). If any item above is untrue, this is a finding. If all items above are true, this is not a finding.

ℹ️ Check

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: 1. The RACF rules for the CBD resource specify a default access of NONE. 2. 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. 3. 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. 4. All RACF rules are defined with UACC(NONE). If any item above is untrue, this is a finding. If all items above are true, this is not a finding.

✔️ 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 RACF rules for the CBD resource specify a default access of NONE. 2. 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') 3. 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. 4. 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. 5. 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

✔️ 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 RACF rules for the CBD resource specify a default access of NONE. 2. 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') 3. 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. 4. 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. 5. 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