AU.L2-3.3.1 System auditing
What the standard requires
Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity.
Quoted verbatim from NIST SP 800-171 Rev 2 (NIST CPRT), which is in the public domain.
Maps to 2 controls in 1 other framework
| Framework | Control |
|---|---|
| NIST Cybersecurity Framework (1.1, legacy) | DE.AE-3 Event data collected and correlated |
| PR.PT-1 Audit/log records per policy |
Mappings are CMDash’s own, seeded with the product and shown on both frameworks they connect. In the product they mean evidence you attach here also counts against the controls listed above.
Integrations that carry evidence for this family
These connectors produce data relevant to CMMC Level 2’s Audit & Accountability family, which is the granularity CMDash publishes — there is no pre-built per-control mapping, and claiming one would be inventing it. You decide which evidence answers which control.
In CMDash this control is a row with an owner, a status, uploaded evidence kept with its full history, and an export an assessor can read.