EvidenceSheet
PCI DSS v4.0.1 · Req 10: Logging and Monitoring

10.6.2 Systems configured to correct and consistent time

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.

Source: PCI DSS v4.0.1, 10.6.2. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open PCI DSS v4.0.1 in the compliance library.

Version 4.0.1 is the active version; 4.0 has been retired. Appendix A1 applies only to multi-tenant service providers, A2 only to card-present POS POI terminals that still use SSL or early TLS, and A3 only when a payment brand or acquirer requires it. Which requirements apply to you follows your validation type.

5
artefacts
4
held by a system
0
at each review
easy
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • Time server configuration listing permitted industry-accepted external sources · Cloud console / configuration management
  • Peering configuration between multiple internal time servers · Cloud console / configuration management
  • Client configurations showing internal systems point only to designated time servers · Cloud console / configuration management
  • Firewall rules blocking direct external NTP from non-designated systems · Cloud console / configuration management

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Time architecture diagram showing designated internal time servers and external sources · Policy repository / GRC workspace

First move

Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

10.6.1 System clocks synchronized with time-sync technology · 10.6.3 Time sync configuration and time data protected