IBM RACF must define WARN = NO on all profiles.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-223703RACF-ES-000560SV-223703r991591_ruleCCI-000366high
Description
Failure to restrict system access to authenticated users negatively impacts operating system security.
STIGDate
IBM z/OS RACF Security Technical Implementation Guide2025-06-24

Related Frameworks

4 paths across 3 frameworks
NIST 800-531 mapping
CM-6
1.00
  • DISA · 9 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1712 mappings
3.4.1
1.00
  • DISA · 9 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
3.4.2
1.00
  • DISA · 9 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-000366
1.00
  • DISA · 9 · disa_xccdf · related

Details

Check Text (C-223703r991591_chk)

Review all Dataset and resource profiles in the RACF database. If any are not defined with WARN = NO, this is a finding.

Fix Text (F-25364r514798_fix)

Define each dataset and resource profile with WARN = NO