NIST 800-171 Controls · Audit & Accountability
AU.2.007 — Provide System Clock Capability for Audit Timestamps
Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records.
What AU.2.007 means in plain English
If your computer clock is 20 minutes off, your audit logs become useless for investigations because you cannot line up events across different systems. Windows Time (W32tm) can automatically sync your computers to NIST time servers or Microsoft time servers for free. This is a 5-minute configuration change, but many small shops never do it deliberately—their computers drift. This control simply requires you to configure NTP time sync on every system and document that it is working.
The assessment question
“Are all systems that generate audit records configured to synchronize their clocks to an authoritative NTP time source (e.g., time.nist.gov or time.windows.com), and is there evidence this synchronization is active?”
How to implement AU.2.007
- On every Windows workstation and server, verify NTP sync: open Command Prompt as Administrator and run "w32tm /query /status". The output should show a time source (e.g., time.windows.com or time.nist.gov) and a Last Successful Sync Time.
- If NTP is not configured or syncing to a reliable source, set it: run "w32tm /config /manualpeerlist:time.nist.gov /syncfromflags:manual /reliable:YES /update" followed by "net stop w32tm && net start w32tm && w32tm /resync".
- In a domain environment (Active Directory), configure the PDC Emulator domain controller to sync with an external NTP source; all domain members will automatically sync from it. Use Group Policy: Computer Configuration > Administrative Templates > System > Windows Time Service.
- Verify network devices (firewall/router) are also NTP-synchronized. Most consumer-grade routers support NTP in their admin panel—set the NTP server to time.nist.gov.
- Document the NTP configuration with a screenshot of "w32tm /query /status" output from each system showing it is actively synced, and store in your CMMC evidence folder under "AU — Time Synchronization."
Evidence your assessor will ask for
- Output of "w32tm /query /status" from each system showing active NTP sync and time source
- Group Policy or local policy configuration showing NTP server settings
- Screenshot of network device (router/firewall) NTP configuration
- Written procedure for checking NTP sync as part of regular maintenance
Does AI prompt monitoring help with this control? Honestly, no.
AU.2.007 is met through the remediation steps above, not through AI traffic controls — an AI prompt firewall neither satisfies nor substitutes for it. We map AI monitoring only to the controls it genuinely evidences (flow control, boundary protection, audit, and incident support); for the full picture of where it does help, see the mapping guide linked below.
Full mapping: which 800-171 controls AI prompt monitoring evidences →
More Audit & Accountability controls
Create and Retain System Audit Logs
AU.2.002Ensure User Accountability Through Unique Identifiers
AU.2.003Review and Update Logged Events
AU.2.004Alert on Audit Logging Process Failure
AU.2.005Correlate Audit Review, Analysis, and Reporting
AU.2.006Provide Audit Record Reduction and Report Generation
Score yourself against all 110 controls
The free ShieldReady assessment walks every NIST 800-171 requirement, computes your SPRS score, and shows exactly which gaps cost the most points.