Cis Ubuntu2004 V300 6 2 2 1 4

6.2.2.1.4 Ensure systemd-journal-remote service is not in use (Automated)

Profile

• Level 1 - Server
• Level 1 - Workstation

Description

Journald systemd-journal-remote supports the ability to receive messages from remote hosts, thus acting as a log server. Clients should not receive data from other hosts.

Note:

• The same package, systemd-journal-remote, is used for both sending logs to remote hosts and receiving incoming logs.
• With regards to receiving logs, there are two services; systemd-journal-remote.socket and systemd-journal-remote.service.

Rationale

If a client is configured to also receive data, thus turning it into a server, the client system is acting outside it's operational boundary.

Note: This recommendation only applies if journald is the chosen method for client side logging. Do not apply this recommendation if rsyslog is used.

Audit Procedure

Command Line

Run the following command to verify systemd-journal-remote.socket and systemd-journal-remote.service are not enabled:

# systemctl is-enabled systemd-journal-remote.socket systemd-journal-remote.service | grep -P -- '^enabled'

Nothing should be returned.

Run the following command to verify systemd-journal-remote.socket and systemd-journal-remote.service are not active:

# systemctl is-active systemd-journal-remote.socket systemd-journal-remote.service | grep -P -- '^active'

Expected Result

Nothing should be returned for either command.

Remediation

Command Line

Run the following commands to stop and mask systemd-journal-remote.socket and systemd-journal-remote.service:

# systemctl stop systemd-journal-remote.socket systemd-journal-remote.service
# systemctl mask systemd-journal-remote.socket systemd-journal-remote.service

Default Value

Not enabled or active by default.

References

1. NIST SP 800-53 Rev. 5: AU-2, AU-7 AU-12

CIS Controls

MITRE ATT&CK Mappings