# Ensure systemd-journal-remote Is Installed

- Source: https://support.icompaas.com/support/solutions/articles/62000235541-ensure-systemd-journal-remote-is-installed
- 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:  
 systemd-journal-remote is a service that enables a system to receive and process logs forwarded from remote systems using the systemd journal protocol. Installing this service is essential for centralized log collection and enhanced monitoring.

Rationale:  
 Installing systemd-journal-remote supports centralized logging infrastructure, improving log management, security monitoring, and incident response capabilities.

Impact:  
 Pros:

-   Enables receipt and processing of remote journal logs.  
    
-   Supports comprehensive centralized log management.  
    

Cons:

-   Requires additional resources and configuration.  
    

Default Value:  
 The service is typically not installed by default on most systems.

Pre-requisites:

-   Root or sudo privileges to install packages.  
    
-   Network access to fetch packages from repositories.  
    

Remediation:

### Test Plan:

Using Linux command line:

1.  Check if systemd-journal-remote is installed:On RPM-based systems:
    

rpm -q systemd-journal-remote

On Debian-based systems:

dpkg -l | grep systemd-journal-remote

2.  Confirm the package installation status.  
    

### Implementation Plan:

Using Linux command line:

1.  Install systemd-journal-remote if missing:
    

On RPM-based systems:

yum install systemd-journal-remote -y

On Debian-based systems:  

apt-get install systemd-journal-remote -y

Verify installation:

systemctl status systemd-journal-remote

### Backout Plan:

Using Linux command line:

1.  Remove systemd-journal-remote if necessary:
    

On RPM-based systems:

yum remove systemd-journal-remote -y

On Debian-based systems:

apt-get remove systemd-journal-remote -y

2.  Confirm removal.  
    

References:

-   CIS Amazon Linux 2 Benchmark v3.0.0  
    
-   systemd-journal-remote 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.