{"stig":{"title":"z/OS IBM Health Checker for RACF  Security Technical Implementation Guide","version":"6","release":"3"},"checks":[{"vulnId":"V-224501","ruleId":"SV-224501r868410_rule","severity":"medium","ruleTitle":"IBM Health Checker STC data sets will be properly protected.","description":"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.","checkContent":"Refer to the following report produced by the Data Set and Resource Data Collection:\n\n- SENSITVE.RPT(HCKSTC)\n\nAutomated Analysis\nRefer to the following report produced by the Data Set and Resource Data Collection:\n\n- PDI(ZHCK0001)\n\nVerify 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.\n\n___ The RACF data set rules for the data sets restricts READ access to auditors.\n\n___ The RACF data set rules for the data sets restricts UPDATE access to domain level security administrators.\n\n___ The RACF data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel.\n\n___ The RACF 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).\n\n___ The RACF data set rules for the data sets specify UACC(NONE) and NOWARNING.","fixText":"The ISSO will ensure that WRITE and/or greater access to IBM Health Checker STC data sets is limited to systems programmers and/or Quest NC-Pass's STC(s) and/or batch user(s) only. READ access can be given to auditors.\n\nThe 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.\n\nData sets to be protected will be:\nSYS3.*.HZSPDATA\n\nThe following commands are provided as a sample for implementing data set controls:\n\nAD 'sys3.mmd.hzspdata.**' UACC(NONE) OWNER(SYS3) AUDIT(FAILURES(READ))\n\nPE ' sys3.mmd.hzspdata.**' ID(syspaudt) ACC(A)\nPE ' sys3.mmd.hzspdata.**' ID(Health Checker STCs) ACC(A)\nPE ' sys3.mmd.hzspdata.**' ID(audtaudt) ACC(R)","ccis":["SV-43172"]},{"vulnId":"V-224502","ruleId":"SV-224502r868415_rule","severity":"medium","ruleTitle":"IBM Health Checker Started Task name will be properly identified and/or defined to the system ACP.","description":"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.","checkContent":"Refer to the following report produced by the RACF Data Collection:\n\n- RACFCMDS.RPT(LISTUSER)\n\nVerify that the userid(s) for the IBM Health Checker started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.\n\nPROTECTED","fixText":"The ISSO working with the systems programmer will ensure the IBM Health Checker Started Task(s) is properly identified and/or defined to the System ACP. \n\nIf the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes.\n\nMost installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified.\n\nThe following commands are provided as a sample for defining Started Task(s):\n\nau HZSPROC name('STC, IBM Health Checker') owner(stc) dfltgrp(stc) nopass -\n\tdata('Health Checker')","ccis":["SV-43182"]},{"vulnId":"V-224503","ruleId":"SV-224503r868419_rule","severity":"medium","ruleTitle":"IBM Health Checker Started task will be properly defined to the STARTED resource class for RACF.","description":"Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could potentially compromise the operating system, ACP, and customer data.","checkContent":"Refer to the following report produced by the RACF Data Collection:\n\n- DSMON.RPT(RACSPT)\n\nAutomated Analysis\nRefer to the following report produced by the RACF Data Collection:\n\n- PDI(ZHCK0032)\n\nIf the IBM Health Checker started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding.","fixText":"The ISSO working with the systems programmer will ensure the IBM Health Checker Started Task(s) is properly identified and/or defined to the System ACP. \n\nA unique userid must be assigned for the IBM Health Checker started task(s) thru a corresponding STARTED class entry.\n\nThe following commands are provided as a sample for defining Started Task(s):\n\nrdef started HZSPROC.** uacc(none) owner(admin) audit(all(read)) -\n\tstdata(user(HXSPROC) group(stc))\nsetr racl(started) ref","ccis":["SV-43187"]}]}