The cron log files must not have extended ACLs.

From SUSE Linux Enterprise Server v11 for System z

Associated with: CCI-000225

SV-45622r1_rule The cron log files must not have extended ACLs.

Vulnerability discussion

Cron logs contain reports of scheduled system activities and must be protected from unauthorized access or manipulation.

Check content

Check the permissions of the file. Procedure: Check the configured cron log file found in the cron entry of the rsyslog configuration (normally /var/log/cron). # grep cron /etc/rsyslog.conf /etc/rsyslog.d/*.conf # ls -lL /var/log/cron 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 /var/log/cron

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.