CMMC readiness · NIST 800-171 alignment · DFARS support Mon–Fri · 0800–1800 ET
Controls / Audit and Accountability / 3.3.3
3.3.3
AU.L2-3.3.3 · Level 2

Review and update logged events.

NIST SP 800-171 Rev 2 · §3.3.3

Review and update logged events.

Assessment objectives

From NIST SP 800-171A · 3 objectives must be met to satisfy this control
3.3.3[a] a process for determining when to review logged events is defined.
Examine
[SELECT FROM: Audit and accountability policy; procedures addressing audit records and event types; security plan; list of organization-defined event types to be logged; reviewed and updated records of logged event types; system audit logs and records; system incident reports; other relevant documents or records].
Interview
[SELECT FROM: Personnel with audit and accountability responsibilities; personnel with information security responsibilities].
Test
[SELECT FROM: Mechanisms supporting review and update of logged event types].
3.3.3[b] event types being logged are reviewed in accordance with the defined review process.
Examine
[SELECT FROM: Audit and accountability policy; procedures addressing audit records and event types; security plan; list of organization-defined event types to be logged; reviewed and updated records of logged event types; system audit logs and records; system incident reports; other relevant documents or records].
Interview
[SELECT FROM: Personnel with audit and accountability responsibilities; personnel with information security responsibilities].
Test
[SELECT FROM: Mechanisms supporting review and update of logged event types].
3.3.3[c] event types being logged are updated based on the review.
Examine
[SELECT FROM: Audit and accountability policy; procedures addressing audit records and event types; security plan; list of organization-defined event types to be logged; reviewed and updated records of logged event types; system audit logs and records; system incident reports; other relevant documents or records].
Interview
[SELECT FROM: Personnel with audit and accountability responsibilities; personnel with information security responsibilities].
Test
[SELECT FROM: Mechanisms supporting review and update of logged event types].

What we look for in practice

The following are placeholder notes that should be refined based on practice experience.

What assessors look for in practice. Documented evidence that this control is implemented across all CUI-handling systems within scope. Specific artifacts vary, but expect requests for written procedures, system configurations, and operational records demonstrating the control is active.

Common failure patterns. Typical issues include incomplete documentation, inconsistent implementation across systems, and missing periodic review records. Refine this section as your practice accumulates direct assessment experience.

Strong evidence looks like. Formal policy referencing this control, technical configurations demonstrating enforcement, periodic review logs with sign-off, and procedures for handling exceptions.

Scoring and POA&M context. 1-point control under the DoD Assessment Methodology. Lower scoring impact, but still required for full compliance. POA&M-eligible — deferral up to 180 days is allowed under conditional certification per 32 CFR 170.21.