-
Story
-
Resolution: Done-Errata
-
Undefined
-
rhel-9.5
-
None
-
scap-security-guide-0.1.75-1.el9
-
rhel-sst-security-compliance
-
ssg_security
-
1
-
False
-
-
No
-
None
-
-
Pass
-
None
-
None
Goal
- The DISA STIG for RHEL 9 specifies that there must be an explicit setting for DNS handling by NetworkManager; either dns=none or dns=default must be set in /etc/NetworkManager/NetworkManager.conf [1]. The STIG profile in RHEL 9.4 is setting "dns=none" in generated remediation code, which prevents NM from updating resolv.conf with DNS information from DHCP. "dns=default" is a valid value for the STIG but allows NM to update resolv.conf with DNS settings from DHCP. This is a more pragmatic default.
[1] https://www.stigviewer.com/stig/red_hat_enterprise_linux_9/2023-12-01/finding/V-257949
Acceptance Criteria
- When running 'oscap xccdf generate fix ...' for the STIG profiles, the resulting code should set dns=default.
- links to
-
RHBA-2024:142992 scap-security-guide bug fix and enhancement update