Crontab files must not have extended ACLs.

From MAC OSX 10.6 Workstation Security Technical Implementation Guide

Associated with IA controls: ECLP-1

Associated with: CCI-000225

SV-38110r1_rule Crontab files must not have extended ACLs.

Vulnerability discussion

To protect the integrity of scheduled system jobs and to prevent malicious modification to these jobs, crontab files must be secured. ACLs on crontab files may provide unauthorized access to the files.

Check content

Open a terminal session and enter the following commands to view the extended ACLs of the crontab file. ls -lL /usr/sbin/cron ls -lL /usr/lib/cron ls -lL /usr/bin/crontab ls -lL /private/var/at/cron.deny If the permissions include a '+', the file has an extended ACL, this is a finding.

Fix text

Open a terminal session and enter the following command to remove the extended ACLs. chmod -N

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.