# Ensure journald Is Not Configured to Forward Logs to rsyslog

- Source: https://support.icompaas.com/support/solutions/articles/62000235508-ensure-journald-is-not-configured-to-forward-logs-to-rsyslog
- 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: The systemd journal (journald) can forward log messages to the traditional syslog daemon (rsyslog). Disabling this forwarding prevents duplicate logging, reduces system overhead, and minimizes potential security risks from unnecessary log transmission.

Rationale: Preventing journald from forwarding logs to rsyslog reduces redundancy and limits the exposure of sensitive log data, improving overall system security and performance.

**Impact:** **Pros:**

-   Reduces log duplication and storage usage.  
    
-   Decreases inter-process communication overhead.  
    
-   Minimizes risk of unintended log exposure.  
    

**Cons:**

-   Systems relying on rsyslog for centralized logging may lose log data if forwarding is disabled.  
    

Default Value: Forwarding logs to rsyslog is often enabled by default.

Pre-requisites:

-   Root or sudo privileges to modify systemd journal configuration.  
    

Remediation:

### Test Plan:

Using Linux command line:

1.  Check the forwarding setting in /etc/systemd/journald.conf:
    
    grep ForwardToSyslog /etc/systemd/journald.conf
    
2.  Verify that ForwardToSyslog is set to no.  
    

### Implementation Plan:

Using Linux command line:

1.  Edit the journald configuration file:
    
    vi /etc/systemd/journald.conf
    
2.  Set the parameter to disable forwarding:
    
    ForwardToSyslog=no
    
3.  Save the file and restart the journald service:
    
    systemctl restart systemd-journald
    
4.  Confirm the change:
    
    grep ForwardToSyslog /etc/systemd/journald.conf
    
      
    

### Backout Plan:

Using Linux command line:

1.  Re-enable forwarding if necessary by setting:
    
    ForwardToSyslog=yes
    
2.  Restart journald service:
    
    systemctl restart systemd-journald
    
3.  Verify forwarding is active.  
    

References:

-   CIS Amazon Linux 2 Benchmark v3.0.0  
    
-   systemd-journald Documentation  
    
-   [NIST SP 800-53 Revision 5 - AU-6  
      
    ](https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final#au-6)

## 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.
