RHEL 10 must disable the ability of systemd to spawn an interactive boot process.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-281300 | RHEL-10-700980 | SV-281300r1167050_rule | CCI-000381 | medium |
| Description | ||||
| Using interactive or recovery boot, the console user could disable auditing, firewalls, or other services, weakening system security. | ||||
| STIG | Date | |||
| Red Hat Enterprise Linux 10 Security Technical Implementation Guide | 2026-03-11 | |||
Related Frameworks
3 paths across 3 frameworks
Related Frameworks
NIST 800-531 mapping
CM-7
1.00
- DISA · V1R1 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1711 mapping
3.4.6
1.00
- DISA · V1R1 · 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-000381
1.00
- DISA · V1R1 · disa_xccdf · related
Details
Check Text (C-281300r1167050_chk)
Verify RHEL 10 is configured so that the current GRUB 2 configuration disables the ability of systemd to spawn an interactive boot process with the following command:
$ sudo grubby --info=ALL | grep args | grep 'systemd.confirm_spawn'
If any output is returned, this is a finding.
Fix Text (F-85766r1167049_fix)
Configure RHEL 10 so that the current GRUB 2 configuration disables the ability of systemd to spawn an interactive boot process with the following command:
$ sudo grubby --update-kernel=ALL --remove-args="systemd.confirm_spawn"