# Ensure Core Dump Backtraces Are Disabled to Prevent Sensitive Data Exposure

- Source: https://support.icompaas.com/support/solutions/articles/62000235122-ensure-core-dump-backtraces-are-disabled-to-prevent-sensitive-data-exposure
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [CIS Amazon Linux 2 Benchmark v3.0.0](https://support.icompaas.com/support/solutions/62000112696) › [CIS Amazon Linux 2 Benchmarks](https://support.icompaas.com/support/solutions/folders/62000169265)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Profile Applicability:** • Level 1

**Description:**  
Core dumps capture the memory state of a process when it crashes, including backtraces. Backtraces in core dumps can reveal sensitive information such as memory addresses and program flow, which attackers could exploit.

**Rationale:** Disabling backtraces in core dumps helps prevent leakage of sensitive runtime information, reducing the risk of information disclosure vulnerabilities.

**Impact:  
 Pros:**

-   Protects sensitive memory and debugging information from exposure.  
    
-   Reduces attack surface related to core dump analysis.  
    

Cons:

-   May limit debugging capabilities during crash investigations.  
    

**Default Value:** By default, core dumps with backtraces may be enabled depending on system configuration.

**Pre-requisites:**

-   Root or sudo privileges to configure system core dump settings.  
    

**Remediation:**

### **Test Plan:**

**Using Linux command line:**

1.  Check the current core dump backtrace setting (example for systemd-coredump):  
    
    coredumpctl info | grep Backtrace
    
2.  Verify that backtraces are disabled in core dumps.  
    

### **Implementation Plan:**

**Using Linux command line:**

1\. Configure system to disable core dump backtraces. For systems using systemd-coredump, edit 

/etc/systemd/coredump.conf:
\[Coredump\]

Backtrace=no

2\. Restart systemd-coredump service or reboot:  

systemctl restart systemd-coredump

3\. Confirm configuration is active.  

### Backout Plan:

Using Linux command line:

1.  Re-enable backtraces by setting:  
    
    Backtrace=yes
    
      
    
2.  Restart systemd-coredump service.  
    
3.  Verify backtrace inclusion in core dumps.  
    

**References:**

-   CIS Amazon Linux 2 Benchmark v3.0.0  
    
-   systemd-coredump Documentation

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
