SV-35195r1: The syslog daemon must not accept remote messages unless it is a syslog server documented using site-defined procedures. | HP-UX 11.31 Security Technical Implementation Guide

Loading benchmark…

Assessment Title

Rule Text

The syslog daemon must not accept remote messages unless it is a syslog server documented using site-defined procedures.

Description

Discussion Text

Unintentionally running a syslog server accepting remote messages puts the system at increased risk. Malicious syslog messages sent to the server could exploit vulnerabilities in the server software itself, could introduce misleading information in to the system's logs, or could fill the system's storage leading to a Denial of Service.

How this relates to the STIG checklist: STIG vs SCAP benchmark.

IA Controls

NIST SP 800-53

Not mappedCCI-000366

Additional Details

Responsibility

System Administrator

IA Controls

ECSC-1

References

DPMS Target HP-UX 11.31 DISA DPMS Target HP-UX 11.31 2171

SCC Automation Reference

The reconstructed evaluation script behind this rule's OVAL check(s) — every module a compound check combines, with this rule's own concrete values and DISA's SCC tool's real per-module mechanism curated from static teardown of SCC releases.

#!/bin/bash
# Reconstructed from oval:mil.disa.fso.hpux11:def:302
# The syslog daemon must not accept remote messages unless it is a syslog server documented using site-defined procedures.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.

# Conditions are satisfied
# textfilecontent54_object (textfilecontent54_test)
test_1() {
  ! ( grep -Pq '^[ 	]*SYSLOGD_OPTS[ 	

]*=[

]*.*-N.*$' '/etc/rc.config.d/syslogd' &>/dev/null )
}

if test_1; then
  echo "PASS"
else
  echo "FAIL"
fi

Assessment Script Powered by AISandbox-executed

A standalone Shell script to assess this control automatically. Review before running it in your environment.

Syntax-checked and actually executed in an isolated sandbox (not the real system this checks) — confirmed to run without errors.

#!/bin/sh
# oval:mil.disa.fso.hpux11:def:302
if [ -f /etc/rc.config.d/syslogd ]; then if grep -q "^[ \t]*SYSLOGD_OPTS[ \t\n\r]*=[\n\r]*.*-N.*$" /etc/rc.config.d/syslogd ]; then echo "PASS"; exit 0; fi; fi; echo "FAIL"; exit 1

Remediation

Edit the /etc/rc.config.d/syslogd configuration startup script and add the -N option to the syslogd command. Restart the syslogd service via the following command(s):
# /sbin/init.d/syslogd stop
# /sbin/init.d/syslogd start