System log files must not have extended ACLs, except as needed to support authorized software.

From Oracle Linux 5 Security Technical Implementation Guide

Part of GEN001270

Associated with: CCI-001314

SV-64493r1_rule System log files must not have extended ACLs, except as needed to support authorized software.

Vulnerability discussion

If the system log files are not protected, unauthorized users could change the logged data, eliminating its forensic value. Authorized software may be given log file access through the use of extended ACLs when needed and configured to provide the least privileges required.

Check content

Verify system log files have no extended ACLs. Procedure: # ls -lL /var/log If the permissions include a '+', the file has an extended ACL. If an extended ACL exists, verify with the SA if the ACL is required to support authorized software and provides the minimum necessary permissions. If an extended ACL exists, providing access beyond the needs of authorized software, this is a finding.

Fix text

Remove the extended ACL from the file. Procedure: # setfacl --remove-all [file with extended ACL]

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.

Powered by sagemincer