Launch control scripts 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-38096r1_rule Launch control scripts must not have extended ACLs.

Vulnerability discussion

If the launch control scripts are writable by other users, they could modify to insert malicious commands into the startup files.

Check content

Open a terminal session and enter the following command to verify the launch control scripts have no extended ACLs. ls -lL /System/Library/LaunchDaemons /System/Library/LaunchAgents /Library/LaunchDaemons /Library/LaunchAgents 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

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.