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

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

V7R2 checklistV7R1 checklist Compare V7R1 and V7R2 in STIG Compare

  • 0 added
  • 0 removed
  • 3 updated

Updated fields: Check text 3Fix text 3

Updated in V7R2 (3)

V-224726CAT IIIBM Hardware Configuration Definition (HCD) install data sets are not properly protected.Check text, Fix text

Check text

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. If the following guidance is true, this is not a finding. The TSS data set rules for the data sets restricts READ access to auditors, automated operations, operators, and systems programming personnel. The TSS data set rules for the data sets restricts UPDATEWRITE and/or ALLgreater access to systems programming personnel. The TSS data set rules for the data sets specifies that all (i.e., failures and successes) UPDATEWRITE and/or ALLgreater access are logged.

Fix text

The ISSO will ensure that update and ALL access to IBM HCD install data sets is limited to systemsystems programmers only, and all update and ALL 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 ALL access and if required that all update and ALL access is logged. The installing systems programmer will identify if any additional groups have update and/or ALL 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 datasetdata set controls: TSS PERMIT(audtaudt) DSN(SYS1.SCBD) ACCESS(R) TSS PERMIT(autoaudt) DSN(SYS1.SCBD) ACCESS(R) TSS PERMIT(operaudt) DSN(SYS1.SCBD) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS1.SCBD) ACCESS(R) TSS PERMIT(tstcaudt) DSN(SYS1.SCBD) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS1.SCBD) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(tstcpaudt) DSN(SYS1.SCBD) ACCESS(ALL) ACTION(AUDIT)

V-224726 in V7R2

V-224727CAT IIIBM Hardware Configuration Definition (HCD) User data sets are not properly protected.Check text, Fix text

Check text

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 Hardware Configuration Definition (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. If the following guidance is true, this is not a finding. Note: Currently on most CSD systems the prefix for these data sets is SYS3.IODF*.**. The TSS data set rules for the data sets does not restrict UPDATEWRITE and/or ALLgreater access to systems programming personnel. The TSS data set rules for the data sets does not restrict READ access to automated operations users and operations personnel. The TSS data set rules for the data sets do not specify that all (i.e., failures and successes) UPDATEWRITE and/or ALLgreater 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 data 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 data sets and categorize them according to who will have updateWRITE and/or altergreater access and if required 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 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 datasetdata set controls: TSS ADD(SYS3) DSN(SYS3) TSS PER(syspaudt) DSN(SYS3.IODF) ACC(R) TSS PER(tstcaudt) DSN(SYS3.IODF) ACC(R) TSS PER(audtaudt) DSN(SYS3.IODF) ACC(R) TSS PER(autoaudt) DSN(SYS3.IODF) ACC(R) TSS PER(operaudt) DSN(SYS3.IODF) ACC(R) TSS PER(syspaudt) DSN(SYS3.IODF) ACC(A) ACTION(AUDIT) TSS PER(tstcaudt) DSN(SYS3.IODF) ACC(A) ACTION(AUDIT)

V-224727 in V7R2

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

Check text

Refer to the following reports produced by the TSS Data Collection and Data Set and Resource Data Collection: - TSSCMDS.RPT(WHOOIBMF). - SENSITVE.RPT(WHOHIBMF). 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 IBMFAC resource class: 1. If the following guidance is true, this is not a finding. The TSS owner is defined for the CBD resource and/or IBMFAC RDT entry has DEFPROT specified. 2. There areis no TSS rules that allow access to the CBD resource. 3. The TSS 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 TSS 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 item above is 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 verify that the following are properly specified in the Access Control Program (ACP). 1. The TSS owner is defined for the CBD resources and/or IBMFAC RDT entry has DEFPROT specified. For example: TSS ADD(dept-acid)IBMFAC(CBD.) TSS REP(RDT)RESCLASS(IBMFAC)ATTR(DEFPROT) 2. There are no TSS rules that allow access to the CBD resource. 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. Example: TSS PERMIT(syspaudt)IBMFAC(CBD.CPC.IOCDS)ACCESS(READ) TSS PERMIT(operaudt)IBMFAC(CBD.CPC.IOCDS)ACCESS(READ) TSS PERMIT(autoaudt)IBMFAC(CBD.CPC.IOCDS)ACCESS(READ) TSS PERMIT(syspaudt)IBMFAC(CBD.CPC.IOCDS) - ACCESS(UPDATE)ACTION(AUDIT) TSS PERMIT(syspaudt)IBMFAC(CBD.CPC.IPLPARM)ACCESS(READ) TSS PERMIT(operaudt)IBMFAC(CBD.CPC.IPLPARM)ACCESS(READ) TSS PERMIT(autoaudt)IBMFAC(CBD.CPC.IPLPARM)ACCESS(READ) TSS PERMIT(syspaudt)IBMFAC(CBD.CPC.IPLPARM) - ACCESS(UPDATE)ACTION(AUDIT)

V-224728 in V7R2

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.