File: rule.yml

package info (click to toggle)
scap-security-guide 0.1.78-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 114,600 kB
  • sloc: xml: 245,305; sh: 84,381; python: 33,093; makefile: 27
file content (37 lines) | stat: -rw-r--r-- 1,151 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
documentation_complete: true

title: 'Disable systemd-journal-remote Socket'

description: |-
    Journald 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 Systemd unit files;
        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.

severity: medium

identifiers:
    cce@rhel8: CCE-87605-2
    cce@rhel9: CCE-87606-0
    cce@rhel10: CCE-87754-8

ocil_clause: 'the systemd-journal-remote socket is not masked'

ocil: |-
    {{{ socket_disabled_check_with_systemd("systemd-journal-remote.socket") }}}

fixtext: |-
    {{{ fixtext_socket_disabled("systemd-journal-remote.socket") }}}

template:
    name: socket_disabled
    vars:
        socketname: systemd-journal-remote