# Ensure systemd-journal-remote Is Configured

- Source: https://support.icompaas.com/support/solutions/articles/62000235544-ensure-systemd-journal-remote-is-configured
- 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-remote service allows a system to receive and process logs forwarded from remote systems using the systemd journal protocol. Proper configuration enables centralized log collection for enhanced monitoring and forensic analysis.

Rationale:  
 Centralized logging with systemd-journal-remote improves log integrity, availability, and supports comprehensive security monitoring across distributed systems.

Impact:  
 Pros:

-   Facilitates centralized log collection and analysis.  
    
-   Enhances security monitoring and incident response.  
    

Cons:

-   Requires network and service configuration.  
    
-   Potentially increases resource usage on the receiving system.  
    

Default Value:  
 systemd-journal-remote is typically not enabled or configured by default.

Pre-requisites:

-   Root or sudo privileges to install and configure the service.  
    
-   Network access for receiving logs.  
    

Remediation:

### Test Plan:

Using Linux command line:

Verify if systemd-journal-remote service is installed:

systemctl status systemd-journal-remote

1.  Check configuration files (e.g., /etc/systemd/journal-remote.conf) for proper setup.  
    

### Implementation Plan:

Using Linux command line:

1.  Install the package if not present:  
    

On RPM-based systems:

yum install systemd-journal-remote -y

On Debian-based systems:

apt-get install systemd-journal-remote -y

Enable and start the service:

systemctl enable systemd-journal-remote  
systemctl start systemd-journal-remote

2.  Configure /etc/systemd/journal-remote.conf as required, e.g., setting listen address and storage options.
    

Restart the service after configuration changes:

systemctl restart systemd-journal-remote

4.  Verify the service is active and logs are being received.  
    

### Backout Plan:

Using Linux command line:

Disable and stop the service if necessary:

systemctl disable systemd-journal-remote    
systemctl stop systemd-journal-remote

1.  Remove or revert configuration changes.  
    
2.  Confirm service is inactive.  
    

References:

-   CIS Amazon Linux 2 Benchmark v3.0.0  
    
-   systemd-journal-remote Documentation  
    
-   [Systemd Journal Remote GitHub  
      
    ](https://github.com/systemd/systemd/tree/main/journal-remote)

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