UCF STIG Viewer Logo

IBM RACF must limit Write or greater access to libraries containing EXIT modules to system programmers only.


Finding ID Version Rule ID IA Controls Severity
V-223679 RACF-ES-000310 SV-223679r853584_rule High
To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. Satisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125
IBM z/OS RACF Security Technical Implementation Guide 2022-09-19


Check Text ( C-25352r514726_chk )
Examine the system for active exit modules. You may need the system administrator help for this. There are third-party software products that can determine standard and dynamic exits loaded in the system.

If all the exits are found within APF, LPA and LINKLIST, this is Not Applicable.

If ESM data set rules for libraries that contain system exit modules restrict WRITE or greater access to only z/OS systems programming personnel, this is not a finding.

If the ESM data set rules for libraries that contain exit modules specify that all WRITE or greater access will be logged, this is not a finding.
Fix Text (F-25340r514727_fix)
Using the ESM, protect the data sets associated with all product exits installed in the z/OS environment. This reduces the potential of a hacker adding a routine to a library and possibly creating an exposure. See that all exits are tracked using a CMP. Develop usermods to include the source/object code used to support the exits. Have Systems programming personnel review all z/OS and other product exits to confirm that the exits are required and are correctly installed.

Configure ESM Dataset rules for all WRITE or greater access to libraries containing z/OS and other system level exits will be logged using the ACP’s facilities. Only systems programming personnel will be authorized to update the libraries containing z/OS and other system level exits.