A.8 Technological controls

A.8.17 Clock synchronization

Not mandatory by default – decided in your SoA

What it means in plain language

Synchronise system clocks to an approved time source so logs can be correlated.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Clock synchronization matters because log correlation, incident timelines, and forensic reconstruction become unreliable when systems drift or use inconsistent time zones. Teams should keep a common time source across infrastructure, cloud services, and security tools, while showing how exceptions are tracked and corrected before they affect investigations or monitoring analysis.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Servers, endpoints, and network devices point to different time sources, so event timelines cannot be reconciled confidently during investigation or monitoring review.
  • Logs show local time on some platforms and UTC on others without a documented conversion standard, causing confusion when analysts compare events across systems.
  • No one checks drift or time service status, so failed synchronization persists until an incident reveals that timestamps are offset or missing altogether.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Specify approved time sources and configuration ownership. Infrastructure or platform teams should manage NTP clients, time zones, and fallback servers, while the security function confirms that logging platforms, EDR, and cloud services are aligned to UTC or a documented standard. Include approval for any exceptional environment that cannot use the normal source.
  • Introduce routine checks for drift and service health. A weekly automated report from monitoring tools, a monthly manual sample on critical assets, or a deployment checklist can confirm synchronization status. Record detected offsets, remediation tickets, and the systems reviewed, especially for domain controllers, log servers, and privileged management hosts.
  • Tie clock synchronization to logging and incident handling. If a device records local time, ensure an explicit conversion note or parser mapping exists. When reviewing an event sequence, analysts should be able to compare source times to a trusted reference and explain any discrepancies in the case record or forensic worksheet.
  • Maintain configuration evidence for cloud and virtual environments. Document provider time sync settings, guest OS settings, and images used for new builds. Where systems are rebuilt from templates, verify that time service settings are inherited correctly and that post-deployment validation occurs before the asset enters production monitoring.

What an auditor will ask to see

  • NTP configuration snippets, time zone standard, and approved time source list.
  • Drift check report showing sampled assets, offsets found, and remediation actions.
  • Build or hardening checklist with time sync validation for new servers or images.
  • Incident timeline or forensic notes referencing UTC conversion and source timestamps.

Baseline documents in the kit

These free kit documents help you document or evidence A.8.17. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.8.15 — Logging and A.5.28 — Collection of evidence. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.