Azure Security Benchmark
Logging and Threat Detection

Azure Security Benchmark ASBv3-LT-7: Use approved time synchronization sources

Use approved time synchronisation sources for log timestamps so recorded date, time and time zone are consistent and correlatable across systems.

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

What else in your programme already covers this

This control maps to 21 controls across 13 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-15 Logging and Monitoring - Accountability

NIST SP 800-53 Rev 5 · 2 controls

CIS Controls v8 · 1 control

  • CIS-8.4 Standardize Time Synchronization

CMMC 2.0 · 1 control

ISO 27001:2022 · 1 control

  • 8.17 Clock synchronization 

ISO 27002:2022 · 1 control

  • 8.17 Clock synchronization

ISO 27701:2019 · 1 control

  • 6.9.4 Logging and monitoring
  • NIST-CSF-PR.PS-04 Log records are generated and made available for continuous 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 Logging and Threat Detection

You are reading one control. How much of Azure Security Benchmark have you already done?

Azure Security Benchmark ASBv3-LT-7 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Azure Security Benchmark your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 71 of 85 Azure Security Benchmark 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. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

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