What changed in z/OS HCD for ACF2 STIG V7R2V7R2 changes

z/OS HCD for ACF2 STIG V7R2 (2025-10-01) replaced V7R1 (2025-04-02): 3 checks updated. It has 3 checks, against 3 in V7R1.

  • 0 added
  • 0 removed
  • 3 updated

Updated fields: Check text 3Fix text 3Discussion 3Title 2

Updated in V7R2 (3)

V-224299CAT IIIBM Hardware Configuration Definition (HCD) install datasets are not properly protected.Title, Check text, Fix text, Discussion

Title

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

Check text

Refer to the following report produced by the Datadataset Set and Resource Data Collection: - SENSITVE.RPT(HCDRPT). Automated Analysis Refer to the following report produced by the Datadataset Set and Resource Data Collection: - PDI(ZHCD0000). Verify that access to the IBM Hardware Configuration Definition (HCD) install datadatasets setsis are properly restricted. If the following guidance is true, this is not a finding. The ACF2 datadataset set rules for the datadatasets setsrestrict restricts READ access to auditors, automated operations, operators, and systems programming personnel. The ACF2 datadataset set rules for the datadatasets setsrestrict restrictsWRITE UPDATE and/or ALTERgreater access to systems programming personnel. The ACF2 datadataset set rules for the datadatasets setsspecify specifies that all (i.e., failures and successes) UPDATEWRITE and/or ALTERgreater access areis logged.

Fix text

The ISSO will ensure that updateWRITE and/or allocategreater access to IBM HCD install datadatasets sets is limited to systemsystems programmers only, and all updateWRITE and/or altergreater access is logged. Auditors, automated operations, and operators should have READ access. The installing systems programmer will identify and document the product datadatasets, sets and categorize them according to who will have updateWRITE and/or altergreater access, and if required, ensure that all updateWRITE and/or allocategreater access is logged. The installing systems programmer will identify if any additional groups have updateWRITE and/or altergreater access for specific data setsdatasets, and once documented, will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system. DataDatasets 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)

Discussion

IBM HCD product has the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their datadatasets sets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.

V-224300CAT IIIBM Hardware Configuration Definition (HCD) User datasets are not properly protected.Title, Check text, Fix text, Discussion

Title

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

Check text

Refer to the following report produced by the Datadataset Set and Resource Data Collection: - SENSITVE.RPT(HCDUSER). Automated Analysis Refer to the following report produced by the Datadataset Set and Resource Data Collection: - PDI(ZHCD0002). Verify that the access to the IBM HCD install datadatasets sets is properly restricted. The datadatasets sets to be protected are the production and working IODF datadatasets sets as well as the activity log for the IODF datadatasets. setsIf the following guidance is true, this is not a finding. Note: Currently on most CSD systems the prefix for these datadatasets sets is SYS3.IODF*.**. The ACF2 datadataset set rules for the datadatasets sets does not restrict UPDATEWRITE and/or ALTERgreater access to systems programming personnel. The ACF2 datadataset set rules for the datadatasets sets does not restrict READ access to automated operations users and operations personnel. The ACF2 datadataset set rules for the datasets doesdo not specify that all (i.e., failures and successes) UPDATEWRITE and/or ALTERgreater 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 text

The ISSO will ensure that update,WRITE and/or allocategreater access to program product user datadatasets sets is limited to systemsystems programmers, and all updateWRITE and/or allocategreater access is logged. Ensure that readREAD access is limited to auditors, operations personnel, and automated operations users. The installing systems programmer will identify and document the product datadatasets, sets and categorize them according to who will have updateWRITE and/or altergreater access, and if required, ensure that all updateWRITE and/or allocategreater access is logged. The installing systems programmer will identify if any additional groups have updateUPDATE access for specific data setsdatasets, and once documented, will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system. DataDatasets sets to be protected will be: The production IODF datadatasets sets. (i.e., hhhhhhhh.IODFnn) The working IODF datadatasets sets. (i.e., hhhhhhhh.IODFnn.) The activity log for the IODF datadatasets sets. (i.e., hhhhhhhh.IODFnn.ACTLOG) Note: Currently on most CSD systems the prefix for these datadatasets 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)

Discussion

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 datadatasets sets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.

V-224301CAT IIIBM Hardware Configuration Definition (HCD) resources are not properly defined and protected.Check text, Fix text, Discussion

Check text

Refer to the following report produced by the ACF2 Data Collection and Datadataset Set and Resource Data Collection: - SENSITVE.RPT(FACILITY). - ACF2CMDS.RPT(RESOURCE) - Alternate report. Automated Analysis Refer to the following report produced by the Datadataset 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. If the following guidance is true, this is not a finding. The ACF2 rules for the CBD resource specify a default access of NONE. 2. No 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 text

The systems programmer will work with the ISSO to verifyensure 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) No 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

Discussion

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 systemsystems programmers only in greater than read authority. Resources are also granted to certain non-systems personnel with read only authority.

How these changes are found

Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V7R2 no longer has.

Comparing other releases, or this one against an older release? Pick any two in STIG Compare.