STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to Red Hat Enterprise Linux 10 Security Technical Implementation Guide

V-281317

CAT II (Medium)

RHEL 10 must disable core dump backtraces.

Rule ID

SV-281317r1167101_rule

STIG

Red Hat Enterprise Linux 10 Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000381

Discussion

A core dump includes a memory image taken at the time the operating system terminates an application. The memory image could contain sensitive data and is generally useful only for developers or system operators trying to debug problems. Enabling core dumps on production systems is not recommended; however, there may be overriding operational requirements to enable advanced debugging. Permitting temporary enablement of core dumps during such situations must be reviewed through local needs and policy.

Check Content

Note: If kernel dumps are disabled in accordance with RHEL-10-701090, this requirement is not applicable.

Verify RHEL 10 disables core dump backtraces by issuing the following command:

$ sudo grep -ir ProcessSizeMax /etc/systemd/ | grep -v '#'
/etc/systemd/coredump.conf:ProcessSizeMax=0

If the "ProcessSizeMax" item is missing or the value is anything other than "0", and the need for core dumps is not documented with the information system security officer as an operational requirement for all domains that have the "core" item assigned, this is a finding.

Fix Text

Configure RHEL 10 to disable core dump backtraces.

Create or edit the setting in a drop-in configuration file:

$ sudo vi /etc/systemd/coredump.conf:

Add the following line:

ProcessSizeMax=0