The /etc/syslog.conf file must not have an extended ACL.

From Oracle Linux 5 Security Technical Implementation Guide

Associated with: CCI-000225

SV-63471r2_rule The /etc/syslog.conf file must not have an extended ACL.

Vulnerability discussion

Unauthorized users must not be allowed to access or modify the /etc/syslog.conf file.

Check content

Check the permissions of the syslog configuration file. Depending on what system is used for log processing either /etc/syslog.conf or /etc/rsyslog.conf will be the logging configuration file. # ls -lL /etc/syslog.conf Or: # ls -lL /etc/rsyslog.conf If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.

Fix text

Remove the extended ACL from the file. # setfacl --remove-all /etc/syslog.conf Or: # setfacl -- remove-all /etc/rsyslog.conf

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.