Cyber Trackr - Free Compliance Library
Cyber Trackr
The Free Compliance Library

z/OS IBM Health Checker for RACF Security Technical Implementation Guide

  • Version/Release: V6R3
  • Published: 2022-10-10
  • Released: 2022-11-23
  • Expand All:
  • Severity:
  • Sort:
Compare

Select any two versions of this STIG to compare the individual requirements

View

Select any old version/release of this STIG to view the previous requirements

This 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.
b
IBM Health Checker STC data sets will be properly protected.
CM-5 - Medium - CCI-001499 - V-224501 - SV-224501r868410_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZHCKR001
Vuln IDs
  • V-224501
  • V-17067
Rule IDs
  • SV-224501r868410_rule
  • SV-43172
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.
Checks: C-26184r868406_chk

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 RACF data set rules for the data sets restricts READ access to auditors. ___ The RACF data set rules for the data sets restricts UPDATE access to domain level security administrators. ___ The RACF data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel. ___ 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). ___ The RACF data set rules for the data sets specify UACC(NONE) and NOWARNING.

Fix: F-26172r868409_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 Quest NC-Pass'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: AD 'sys3.mmd.hzspdata.**' UACC(NONE) OWNER(SYS3) AUDIT(FAILURES(READ)) PE ' sys3.mmd.hzspdata.**' ID(syspaudt) ACC(A) PE ' sys3.mmd.hzspdata.**' ID(Health Checker STCs) ACC(A) PE ' sys3.mmd.hzspdata.**' ID(audtaudt) ACC(R)

b
IBM Health Checker Started Task name will be properly identified and/or defined to the system ACP.
IA-2 - Medium - CCI-000764 - V-224502 - SV-224502r868415_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000764
Version
ZHCKR030
Vuln IDs
  • V-224502
  • V-17452
Rule IDs
  • SV-224502r868415_rule
  • SV-43182
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.
Checks: C-26185r868411_chk

Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(LISTUSER) Verify 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. PROTECTED

Fix: F-26173r868412_fix

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. 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): au HZSPROC name('STC, IBM Health Checker') owner(stc) dfltgrp(stc) nopass - data('Health Checker')

b
IBM Health Checker Started task will be properly defined to the STARTED resource class for RACF.
IA-2 - Medium - CCI-000764 - V-224503 - SV-224503r868419_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000764
Version
ZHCKR032
Vuln IDs
  • V-224503
  • V-17454
Rule IDs
  • SV-224503r868419_rule
  • SV-43187
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.
Checks: C-26186r868417_chk

Refer to the following report produced by the RACF Data Collection: - DSMON.RPT(RACSPT) Automated Analysis Refer to the following report produced by the RACF Data Collection: - PDI(ZHCK0032) If 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.

Fix: F-26174r868418_fix

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. A unique userid must be assigned for the IBM Health Checker started task(s) thru a corresponding STARTED class entry. The following commands are provided as a sample for defining Started Task(s): rdef started HZSPROC.** uacc(none) owner(admin) audit(all(read)) - stdata(user(HXSPROC) group(stc)) setr racl(started) ref