ISO 27001:2022
Technological controls – ISO 27001:2022

ISO 27001:2022 8.17: Clock synchronization 

The clocks of the organization's information processing systems are to be kept in step with approved time sources. Purpose (stated in ISO/IEC 27002:2022): enables correlation and analysis of security events and recorded data and supports incident investigations. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 8.17.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 24 controls across 15 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

FedRAMP High · 3 controls

  • AU-8 Time Stamps
  • SC-45 System Time Synchronization (SC-45)
  • SC-45(1) System Time Synchronization | Synchronization with Authoritative Time Source (SC-45(1))

FedRAMP Moderate · 3 controls

  • AU-8 Time Stamps
  • SC-45 System Time Synchronization (SC-45)
  • SC-45(1) System Time Synchronization | Synchronization with Authoritative Time Source (SC-45(1))

PCI DSS 4.0 · 3 controls

  • 10.6.1 10.6.1 System clocks synchronized with time-sync technology
  • 10.6.2 10.6.2 Systems configured to correct and consistent time
  • 10.6.3 10.6.3 Time sync configuration and time data protected

C5 (Germany) · 2 controls

  • C5-OPS-11 Logging and Monitoring - Metadata Management Concept
  • C5-OPS-16 Logging and Monitoring - Configuration

NIST SP 800-53 Rev 5 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies
  • ASBv3-LT-7 Use approved time synchronization sources

CIS Controls v8 · 1 control

  • CIS-8.4 Standardize Time Synchronization

CMMC 2.0 · 1 control

EU AI Act · 1 control

ISO 27001:2013 · 1 control

ISO 27002:2022 · 1 control

  • 8.17 Clock synchronization

ISO 27701:2019 · 1 control

  • 6.9.4 Logging and monitoring

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Technological controls – ISO 27001:2022

You are reading one control. How much of ISO 27001:2022 have you already done?

ISO 27001:2022 8.17 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27001:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27001:2022 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 170 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 24 it maps to, and the evidence behind each claim, over MCP and REST.