AU.L2-3.3.4 Audit Failure Alerting
Raise an alert when the audit logging process itself fails, so a loss of logging is noticed rather than silent.
Source: CMMC 2.0, AU.L2-3.3.4. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CMMC 2.0 in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Alert configuration for logging process failure and log storage exhaustion · SIEM / log platform
- Evidence of alerts reaching a monitored destination · SIEM / log platform
periodic reviewEvidence produced at each review
- Records of response to a logging failure · SIEM / log platform
governing documentDocuments that govern the control
none for this control
First move
Common gaps auditors find
- Failure detection absent so logging stops unnoticed
- Alerts generated but routed to an unmonitored mailbox
- Storage capacity failures not treated as logging failures
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet