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

Protect audit information and audit logging tools from unauthorized access, modification, and…

NIST SP 800-171 Rev 2 · §3.3.8

Protect audit information and audit logging tools from unauthorized access, modification, and deletion.

Assessment objectives

From NIST SP 800-171A · 6 objectives must be met to satisfy this control
3.3.8[a] audit information is protected from unauthorized access.
Examine
[SELECT FROM: Audit and accountability policy; access control policy and procedures; procedures addressing protection of audit information; security plan; system design documentation; system configuration settings and associated documentation, system audit logs and records; audit logging tools; other relevant documents or records].
Interview
[SELECT FROM: Personnel with audit and accountability responsibilities; personnel with information security responsibilities; system or network administrators; system developers].
Test
[SELECT FROM: Mechanisms implementing audit information protection].
3.3.8[b] audit information is protected from unauthorized modification.
Examine
[SELECT FROM: Audit and accountability policy; access control policy and procedures; procedures addressing protection of audit information; security plan; system design documentation; system configuration settings and associated documentation, system audit logs and records; audit logging tools; other relevant documents or records].
Interview
[SELECT FROM: Personnel with audit and accountability responsibilities; personnel with information security responsibilities; system or network administrators; system developers].
Test
[SELECT FROM: Mechanisms implementing audit information protection].
3.3.8[c] audit information is protected from unauthorized deletion.
Examine
[SELECT FROM: Audit and accountability policy; access control policy and procedures; procedures addressing protection of audit information; security plan; system design documentation; system configuration settings and associated documentation, system audit logs and records; audit logging tools; other relevant documents or records].
Interview
[SELECT FROM: Personnel with audit and accountability responsibilities; personnel with information security responsibilities; system or network administrators; system developers].
Test
[SELECT FROM: Mechanisms implementing audit information protection].
3.3.8[d] audit logging tools are protected from unauthorized access.
Examine
[SELECT FROM: Audit and accountability policy; access control policy and procedures; procedures addressing protection of audit information; security plan; system design documentation; system configuration settings and associated documentation, system audit logs and records; audit logging tools; other relevant documents or records].
Interview
[SELECT FROM: Personnel with audit and accountability responsibilities; personnel with information security responsibilities; system or network administrators; system developers].
Test
[SELECT FROM: Mechanisms implementing audit information protection].
3.3.8[e] audit logging tools are protected from unauthorized modification.
Examine
[SELECT FROM: Audit and accountability policy; access control policy and procedures; procedures addressing protection of audit information; security plan; system design documentation; system configuration settings and associated documentation, system audit logs and records; audit logging tools; other relevant documents or records].
Interview
[SELECT FROM: Personnel with audit and accountability responsibilities; personnel with information security responsibilities; system or network administrators; system developers].
Test
[SELECT FROM: Mechanisms implementing audit information protection].
3.3.8[f] audit logging tools are protected from unauthorized deletion.
Examine
[SELECT FROM: Audit and accountability policy; access control policy and procedures; procedures addressing protection of audit information; security plan; system design documentation; system configuration settings and associated documentation, system audit logs and records; audit logging tools; other relevant documents or records].
Interview
[SELECT FROM: Personnel with audit and accountability responsibilities; personnel with information security responsibilities; system or network administrators; system developers].
Test
[SELECT FROM: Mechanisms implementing audit information protection].

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.