Audit records must include where the events occurred.

From Solaris 11 X86 Security Technical Implementation Guide

Part of SRG-OS-000039

Associated with: CCI-000132

SV-60675r1_rule Audit records must include where the events occurred.

Vulnerability discussion

Without auditing, individual system accesses cannot be tracked, and malicious activity cannot be detected and traced back to an individual account.Without accurate time stamps, source, user, and activity information, malicious activity cannot be accurately tracked.Without an audit reduction and reporting capability, users find it difficult to identify specific patterns of attack.

Check content

The Audit Configuration profile is required. This check applies to the global zone only. Determine the zone that you are currently securing. # zonename If the command output is "global", this check applies. Check the status of the audit system. It must be auditing. # pfexec auditconfig -getcond If this command does not report: audit condition = auditing this is a finding.

Fix text

The Audit Control profile is required. This action applies to the global zone only. Determine the zone that you are currently securing. # zonename If the command output is "global", this action applies. If auditing has been disabled, it must be enabled with the following command: # pfexec audit -s

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