Title

The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. (Cat II impact)

Discussion

Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00216

Check Content

Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding. Check which audits occur: $ cat /etc/security/audit_class $ cat /etc/security/audit_event These two files document the types of audit events available. $ cat /etc/security/audit_control $ cat /etc/security/audit_user These two document what is actually audited by default (audit_control) and per-user (audit_user). If "ad" events are not audited, this is a finding. The FreeBSD "audit_*" (5) manpages document each file's format. For example, see "man 5 audit_user" and "man 5 audit_control" for details on the user and control auditing files.

Fix Text

Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur.

Additional Identifiers

Rule ID:

Vulnerability ID: V-330

Group Title:

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.