NIST SP 800-53 Rev. 5 · AU-12

Audit Record Generation

US National Institute of Standards and Technology (NIST) · cited in 266 of our lessons

Explanation

What it asks for. Systems must be able to generate audit records for the event types defined under AU-2, let designated people choose which events are logged by which components, and produce the records with the content required by AU-3.

In practice. This means enabling logging on operating systems, applications, databases, network devices and cloud services in line with the logging policy, and confirming those logs actually arrive centrally. Auditors expect configuration evidence, a mapping of log sources to required event types, and checks that sources have not gone silent. CIS Control 8 sets similar expectations.

Common gaps. Logging is often enabled on servers but not on applications or SaaS platforms, or the default verbosity misses important events. Sources that stop sending logs are frequently not noticed.

The official text
a. Provide audit record generation capability for the event types the system is capable of auditing as defined in [AU-2a](#au-2_smt.a) on [Assignment: organization-defined system components]; b. Allow [Assignment: organization-defined personnel or roles] to select the event types that are to be logged by specific components of the system; and c. Generate audit records for the event types defined in [AU-2c](#au-2_smt.c) that include the audit record content defined in [AU-3](#au-3). Discussion: Audit records can be generated from many different system components. The event types specified in [AU-2d](#au-2_smt.d) are the event types for which audit logs are to be generated and are a subset of all event types for which the system can generate audit records.

From NIST SP 800-53 Rev. 5, a work of the US government in the public domain.

Lessons that cite it

Real incidents where this item mattered: the latest 12 of 266.