Systems must be set to correct and consistent time as follows: at least one designated time server is in use; no system other than the designated central time server(s) takes time from outside sources; the time taken from outside derives from Coordinated Universal Time (UTC) or International Atomic Time; the designated time server(s) take updates solely from particular external sources the industry accepts; where more than one designated time server exists, they peer with each other to stay accurate; and internal systems obtain their time solely from those central server(s). Applies to all entities. Objective under the customized approach: every system keeps accurate and consistent time.
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.
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.
PCI DSS 4.0 10.6.2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 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. 415 were rejected on the ISO 27001:2022 pair alone.
The graph holds this control, the 21 it maps to, and the evidence behind each claim, over MCP and REST.