acceptedThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 1 Benchmark Date: 02 Apr 20253.51.10.07<ProfileDescription></ProfileDescription><ProfileDescription></ProfileDescription><ProfileDescription></ProfileDescription><ProfileDescription></ProfileDescription><ProfileDescription></ProfileDescription><ProfileDescription></ProfileDescription><ProfileDescription></ProfileDescription><ProfileDescription></ProfileDescription><ProfileDescription></ProfileDescription><GroupDescription></GroupDescription>ZHCDR000<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target zOS HCD for RACFDISADPMS TargetzOS HCD for RACF4153V-16932SV-30545CCI-001499CCI-002234The ISSO will ensure that update and allocate access to IBM HCD install data sets is limited to system programmers only, and all update and alter 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 alter access and if required that all update and allocate access is logged. The systems programmer will identify if any additional groups have update and/or alter 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 dataset 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) refreshRefer 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. 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 UPDATE and/or ALTER access to systems programming personnel. The RACF data set rules for the data sets specifies that all (i.e., failures and successes) UPDATE and/or ALTER access are logged.<GroupDescription></GroupDescription>ZHCDR002<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target zOS HCD for RACFDISADPMS TargetzOS HCD for RACF4153SV-30598V-21592CCI-001499CCI-002234The ISSO will ensure that update, and alter access to program product user data sets is limited to systems 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 user 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: ad 'sys3.iodf*.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('Vendor DS Profile: IODF for HCD') pe 'sys3.iodf*.**' id(syspaudt tstcaudt) acc(a) pe 'sys3.iodf*.**' id(audtaudt autoaudt operaudt) acc(r)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 RACF data set rules for the data sets does not restrict UPDATE and/or ALTER access to systems programming personnel. The RACF data set rules for the data sets does not restrict READ access to automated operations users and operations personnel. The RACF 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, there is no finding. If any of the above is true, this is a finding.<GroupDescription></GroupDescription>ZHCDR020<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target zOS HCD for RACFDISADPMS TargetzOS HCD for RACF4153SV-30583V-17947CCI-000213CCI-002234The 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) refRefer 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.