{"description": "Journald supports the ability to receive messages from remote hosts,\nthus acting as a log server. Clients should not receive data from\nother hosts.\nNOTE:\n    The same package, systemd-journal-remote , is used for both sending\n    logs to remote hosts and receiving incoming logs.\n    With regards to receiving logs, there are two Systemd unit files;\n    systemd-journal-remote.socket and systemd-journal-remote.service.", "rationale": "If a client is configured to also receive data, thus turning it into\na server, the client system is acting outside it's operational boundary.", "severity": "medium", "references": {"cis": ["6.2.1.2.4"]}, "control_references": {"cis": ["6.2.1.2.4"]}, "components": [], "identifiers": {}, "ocil_clause": "the systemd-journal-remote socket is not masked", "ocil": "\nTo check that the <code>systemd-journal-remote.socket</code> socket is disabled in system boot configuration with systemd, run the following command:\n<pre>$ systemctl is-enabled <code>systemd-journal-remote.socket</code></pre>\nOutput should indicate the <code>systemd-journal-remote.socket</code> socket has either not been installed,\nor has been disabled at all runlevels, as shown in the example below:\n<pre>$ sudo systemctl is-enabled <code>systemd-journal-remote.socket</code><br/>disabled</pre>\n\nRun the following command to verify <code>systemd-journal-remote.socket</code> is not active (i.e. not running) through current runtime configuration:\n<pre>$ sudo systemctl is-active systemd-journal-remote.socket</pre>\n\nIf the socket is not running the command will return the following output:\n<pre>inactive</pre>\n\nThe socket will also be masked, to check that the <code>systemd-journal-remote.socket</code> is masked, run the following command:\n<pre>$ sudo systemctl show <code>systemd-journal-remote.socket</code> | grep \"LoadState\\|UnitFileState\"</pre>\n\nIf the socket is masked the command will return the following outputs:\n\n<pre>LoadState=masked</pre>\n\n<pre>UnitFileState=masked</pre>", "oval_external_content": null, "fixtext": "To disable the systemd-journal-remote.socket socket run the following command:\n\n$ sudo systemctl disable --now systemd-journal-remote.socket\n\n$ sudo systemctl mask --now systemd-journal-remote.socket", "checktext": "", "vuldiscussion": "", "srg_requirement": "", "warnings": [], "conflicts": [], "requires": [], "policy_specific_content": {}, "platform": null, "platforms": [], "sce_metadata": {"check-import": "stdout", "platform": ["multi_platform_all"], "environment": "any", "filename": "socket_systemd-journal-remote_disabled.sh", "relative_path": "ubuntu2204/checks/sce/socket_systemd-journal-remote_disabled.sh"}, "inherited_platforms": ["system_with_kernel"], "cpe_platform_names": [], "inherited_cpe_platform_names": ["system_with_kernel"], "bash_conditional": null, "fixes": {}, "title": "Disable systemd-journal-remote Socket", "definition_location": "/aptdata/openscap/scap-security-guide/linux_os/guide/system/logging/journald/socket_systemd-journal-remote_disabled/rule.yml", "template": {"name": "socket_disabled", "vars": {"socketname": "systemd-journal-remote"}, "backends": {}}}