A.8.17 Technological
Clock synchronization
Structured attributes from ISO/IEC 27002:2022 — control type · CIA properties · cybersecurity concept · operational capability · security domain. What do these mean?
Mapped NIST 800-53 r5 controls (10)
Our reading (mostly llm_verified) of how this ISO control and each NIST 800-53 control relate. Not an ISO or NIST product.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- AU-8fullcovers — Both controls establish a single authoritative time source and enforce synchronization across systems so that audit and event records carry consistent, reliable timestamps.
- SC-45mostlycovers — A.8.17's purpose-built requirement for clock synchronization to enable event correlation and incident analysis accounts for the bulk of SC-45's functional mandate; a residual of SC-45's intra- and inter-component technical synchronization details (e.g., protocols, tolerance values) sits outside the ISO control's explicit scope.
Aligned NIST CSF 2.0 outcomes (15)
NIST CSF 2.0 outcomes this ISO control aligns with — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- DE.AE-02impliedimplements — A.8.17 directly operationalizes accurate timestamping required for event correlation and analysis that DE.AE-02 names; the link is within the shared detection/analysis domain but the outcome does not cite clock sync explicitly.
- DE.AE-03domain mandateimplements — A.8.17 directly operationalizes synchronized clocks so that events from multiple sources can be reliably correlated, which is the exact outcome DE.AE-03 names; the link is within the detection-analysis domain but not by explicit citation of correlation mechanics.
- PR.PS-04domain mandateimplements — A.8.17 directly operationalizes synchronized clocks so that the generated log records required by PR.PS-04 can be reliably correlated and analyzed in continuous monitoring
Related OWASP ASVS 5.0 requirements (3)
Application-security verification requirements (OWASP ASVS 5.0) this ISO control aligns with; links open the ASVS chapter. Our analysis (mostly llm_verified) — many ISO controls have no ASVS counterpart.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Related weaknesses / CWE (17)
Weakness classes this ISO control helps prevent or mitigate — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Mitigated MITRE ATT&CK techniques (3168)
Adversary techniques (MITRE ATT&CK Enterprise) this ISO control helps mitigate; links open attack.mitre.org. Our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Control IDs, short titles and the structured attribute table (control type, CIA properties, cybersecurity-concept, operational capability, security domain) are facts from ISO/IEC 27001:2022 Annex A / ISO/IEC 27002:2022. The full implementation guidance prose lives in ISO/IEC 27002:2022 — not reproduced here. Cross-walks to NIST 800-53, NIST CSF 2.0, OWASP ASVS, CWE, MITRE ATT&CK and OWASP Web Top 10 are our own analysis (mostly llm_verified), not an ISO, NIST, MITRE or OWASP product — how ours compare.