z/OS IBM Health Checker for ACF2 STIG
z/OS IBM Health Checker for ACF2 Security Technical Implementation Guide. Version v6 r3, released Nov. 23, 2022.
ZHCKA001: IBM Health Checker STC data sets will be properly protected.
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(HCKSTC) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZHCK0001) Verify that the accesses to the IBM Health Checker STC data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The ACF2 data set rules for the data sets restricts READ access to auditors. ___ The ACF2 data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel. ___ The ACF2 data set rules for the data sets restricts WRITE and/or greater access to the IBM Health Checker's STC(s) and/or batch user(s).
Discussion
IBM Health Checker STC data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
Fix
The ISSO will ensure that WRITE and/or greater access to IBM Health Checker STC data sets is limited to systems programmers and/or IBM Health Checker's STC(s) and/or batch user(s) only. READ access can be given to auditors. 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 installing 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 ACP (Access Control Program) active on the system. The dataset to be protected can be found in the HZSPROC STC member in HZSPDATA DD statement. Data sets to be protected will be: SYS3.*.HZSPDATA The following commands are provided as a sample for implementing data set controls: $KEY(S3A) $PREFIX(SYS3) MVA.HZSPDATA UID(syspaudt) R(A) W(A) A(A) E(A) MVA.HZSPDATA UID(Health Checker STCs) R(A) W(A) A(A) E(A) MVA.HZSPDATA UID(audtaudt) R(A) E(A)
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
ZHCKA030: IBM Health Checker Started Task name will be properly identified and/or defined to the system ACP.
Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(ATTSTC) Verify that the logonid(s) for the IBM Health Checker started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. STC
Discussion
IBM Health Checker requires a started task that will be restricted to certain resources, datasets and other system functions. By defining the started task as a userid to the system ACP, It allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities, could compromise of the operating system environment, ACP, and customer data.
Fix
The IAO working with the systems programmer will ensure the IBM Health Checker Started Task(s) is properly identified and/or defined to the System ACP. If the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes. Most installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified. The following commands are provided as a sample for defining Started Task(s): SET LID insert HZSPROC stc name('STC, IBM Health Checker')
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None