Level 2 · Audit and Accountability

AU.L2-3.3.4

Audit Failure Alerting

Logging failure must be detectable even when the failure itself stops normal event delivery.

Score: 1 POA&M: Eligible
GAVII Cybersecurity assessment reference

Official reference

The requirement

Alert in the event of an audit logging process failure.

DoD CMMC Assessment Guide, Level 2, version 2.13. AU.L2-3.3.4; requirement and objectives, printed page 79 ↗

Assessment objectives

What must be established

Determine if each applicable objective is satisfied. The labels below follow the cited DoD assessment guide.

  1. [a]

    personnel or roles to be alerted in the event of an audit logging process failure are identified;

  2. [b]

    types of audit logging process failures for which alert will be generated are defined; and

  3. [c]

    identified personnel or roles are alerted in the event of an audit logging process failure.

MET requires evidence that all applicable objectives are satisfied. Final, approved evidence is needed. A NOT APPLICABLE determination needs a scope-based basis and is equivalent to MET for scoring. Enduring exceptions and temporary deficiencies have specific conditions under 32 CFR 170.24; they are not a general permission to defer implementation.

GAVII Cybersecurity assessment approach

Connect the objective to the evidence

Identify which failures matter, how an alert is generated, and who receives it. Include loss of forwarding, full storage, and other relevant failure modes in the assessment discussion.

Assessment focus: objectives [a], [b], [c]. Use the methods together; a single example does not establish every objective.

Examine

Inspect failure-alert settings, recipient configuration, service-health monitoring, and recorded alerts or test results.

Interview

Who notices if a critical source stops sending logs, and how is the problem escalated?

Demonstrate or test

Safely simulate or replay a logging failure in a test context and trace the alert to its recipient.

Evidence gaps to look for

  • The only failure record is stored in the failed logging system.
  • Notifications go to an unmonitored mailbox.

GAVII Cybersecurity’s examples illustrate ways to examine, interview, and test. They are not a mandatory artifact list or a guarantee of an assessment result. Combine methods and address every applicable objective in the actual scope.

Assessment constraints

Scoring and POA&M eligibility

Score: 1

If this requirement is NOT MET, deduct 1 point from the Level 2 maximum of 110. The deduction applies to the requirement, not separately to each objective.

Scoring rule ↗

POA&M: Eligible

Potentially eligible only if all Conditional Level 2 criteria are satisfied, including a score of at least 88 out of 110 and timely closeout. Eligibility is not a finding that this requirement is MET.

POA&M rule ↗

Conditional Level 2 requires a score of at least 88 out of 110 and satisfaction of every eligibility condition. A 1-point requirement is not automatically eligible. The permitted POA&M must be closed through the appropriate closeout assessment within 180 days of the Conditional CMMC Status Date. An operational remediation plan does not confer Conditional Status.

Assessment planning

Location and observation

Not specifically listed in CAP P.11

This requirement is not specifically listed in CAP P.11. That does not establish that remote assessment is sufficient: the Lead CCA and C3PAO determine an adequate approach for the actual scope and evidence.

CAP §P.11, pages 10–11 ↗

Check the source

References and related requirements

Program timing and contract applicability can change independently of these requirements. Check current DoD program notices and your solicitation or contract before making a compliance decision. Open the official DoD resource hub.

Get your free consultation.