All library 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-001499

SV-38075r1_rule All library files must not have extended ACLs.

Vulnerability discussion

Unauthorized access could destroy the integrity of the library files.

Check content

Open a terminal session and enter the following command to view the library file ACLs. ls -lLR /System/Library/Frameworks /Library/Frameworks /usr/lib /usr/local/lib 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 -RN /System/Library/Frameworks /Library/Frameworks /usr/lib /usr/local/lib

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.