.Warning added to `rsyslog_remote_loghost`
The SCAP rule `xccdf_org.ssgproject.content_rule_rsyslog_remote_loghost` ensures that the Rsyslog daemon is configured to send log messages to a remote log host. However, the rule does not configure TCP queues. As a consequence, the system hangs if TCP queues are not configured, and the remote log host becomes unavailable. This update adds a warning message that explains how to configure TCP queues. If you encounter system hangs while using this rule, read the warning and configure the system properly.
Description of problem:
Scans for ssg-rhel8-ds.xml using the xccdf_org.ssgproject.content_profile_stig_gui suggest configuring tcp forwarding for rsyslog, but do not indicate that a queue must also be used as queue-less tcp forwarding is not supported.
Version-Release number of selected component (if applicable):
openscap-scanner-1.3.5-6.el8.x86_64
openscap-1.3.5-6.el8.x86_64
scap-security-guide-0.1.57-5.el8.noarch
How reproducible:
Every time
Steps to Reproduce:
1. Install a new RHEL 8 system
2. Scan using /usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml and --profile xccdf_org.ssgproject.content_profile_stig_gui
3. The scan results indicate that forwarding should be configured, but not that a queue is needed. If you allow the scan to remediate, the following line is added to /etc/rsyslog.conf:
*.* @@logcollector
Actual results:
------------------------------
xccdf_org.ssgproject.content_rule_rsyslog_remote_loghost
...
To configure rsyslog to send logs to a remote log server, open /etc/rsyslog.conf and read and understand the last section of the file, which describes the multiple directives necessary to activate remote logging. Along with these other directives, the system can be configured to forward its logs to a particular log server by adding or correcting one of the following lines, substituting logcollector appropriately. The choice of protocol depends on the environment of the system; although TCP and RELP provide more reliable message delivery, they may not be supported in all environments.
To use UDP for log message delivery:
*.* @logcollector
To use TCP for log message delivery:
*.* @@logcollector
To use RELP for log message delivery:
*.* :omrelp:logcollector
------------------------------
Expected results:
The scan/remediation should include a queue setup for tcp forwarding
Additional info:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (scap-security-guide bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:7563
Description of problem: Scans for ssg-rhel8-ds.xml using the xccdf_org.ssgproject.content_profile_stig_gui suggest configuring tcp forwarding for rsyslog, but do not indicate that a queue must also be used as queue-less tcp forwarding is not supported. Version-Release number of selected component (if applicable): openscap-scanner-1.3.5-6.el8.x86_64 openscap-1.3.5-6.el8.x86_64 scap-security-guide-0.1.57-5.el8.noarch How reproducible: Every time Steps to Reproduce: 1. Install a new RHEL 8 system 2. Scan using /usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml and --profile xccdf_org.ssgproject.content_profile_stig_gui 3. The scan results indicate that forwarding should be configured, but not that a queue is needed. If you allow the scan to remediate, the following line is added to /etc/rsyslog.conf: *.* @@logcollector Actual results: ------------------------------ xccdf_org.ssgproject.content_rule_rsyslog_remote_loghost ... To configure rsyslog to send logs to a remote log server, open /etc/rsyslog.conf and read and understand the last section of the file, which describes the multiple directives necessary to activate remote logging. Along with these other directives, the system can be configured to forward its logs to a particular log server by adding or correcting one of the following lines, substituting logcollector appropriately. The choice of protocol depends on the environment of the system; although TCP and RELP provide more reliable message delivery, they may not be supported in all environments. To use UDP for log message delivery: *.* @logcollector To use TCP for log message delivery: *.* @@logcollector To use RELP for log message delivery: *.* :omrelp:logcollector ------------------------------ Expected results: The scan/remediation should include a queue setup for tcp forwarding Additional info: