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

Provide a system capability that compares and synchronizes internal system clocks with an…

NIST SP 800-171 Rev 2 · §3.3.7

Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records.

Assessment objectives

From NIST SP 800-171A · 3 objectives must be met to satisfy this control
3.3.7[a] internal system clocks are used to generate time stamps for audit records.
Examine
[SELECT FROM: Audit and accountability policy; procedures addressing time stamp generation; system design documentation; security plan; system configuration settings and associated documentation; system audit logs and records; other relevant documents or records].
Interview
[SELECT FROM: Personnel with information security responsibilities; system or network administrators; system developers].
Test
[SELECT FROM: Mechanisms implementing time stamp generation].
3.3.7[b] an authoritative source with which to compare and synchronize internal system clocks is specified.
Examine
[SELECT FROM: Audit and accountability policy; procedures addressing time stamp generation; system design documentation; security plan; system configuration settings and associated documentation; system audit logs and records; other relevant documents or records].
Interview
[SELECT FROM: Personnel with information security responsibilities; system or network administrators; system developers].
Test
[SELECT FROM: Mechanisms implementing time stamp generation].
3.3.7[c] internal system clocks used to generate time stamps for audit records are compared to and synchronized with the specified authoritative time source.
Examine
[SELECT FROM: Audit and accountability policy; procedures addressing time stamp generation; system design documentation; security plan; system configuration settings and associated documentation; system audit logs and records; other relevant documents or records].
Interview
[SELECT FROM: Personnel with information security responsibilities; system or network administrators; system developers].
Test
[SELECT FROM: Mechanisms implementing time stamp generation].

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.