Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is NTP Security?

Accurate time underpins certificate validation, Kerberos, logging, and multi-factor codes. NTP security is about keeping that time correct and keeping your servers out of attacks.

Illustration for the cybersecurity term NTP Security
Home / Blog / Cybersecurity Terms / What Is NTP Security?
17 November 2026

What Is NTP Security?

What Is NTP Security?

Time is a silent dependency of nearly every security control. A certificate is valid between two timestamps. Kerberos rejects a ticket whose timestamp differs from the server’s by more than five minutes by default. Time-based one-time passcodes derive from the current interval. Log correlation across systems assumes a shared clock, and digital evidence loses weight when the timeline cannot be trusted. An attacker who can move a machine’s clock can make an expired certificate valid again, break authentication, or desynchronise the record of their own activity.

How NTP Works, Briefly

Network Time Protocol, version 4 specified in RFC 5905, arranges sources into strata. Stratum 0 is a reference clock — an atomic clock, a GPS receiver, or a radio signal such as the MSF transmission from Anthorn in Cumbria. Stratum 1 servers are directly attached to one. Stratum 2 servers synchronise from stratum 1, and so on. A client exchanges timestamps with several servers, measures the round-trip delay, and adjusts its clock gradually rather than stepping it, which matters because a sudden jump backwards breaks databases and log ordering.

The Attacks

Amplification. This is the one most organisations have been caught by. The monlist command in older ntpd implementations returned the last 600 clients that had contacted the server, turning a small request into a response up to several hundred times larger. Attackers used it to build the reflection floods of early 2014, and it was serious enough to receive its own identifier, CVE-2013-5211. Modern builds disable it, but internet-facing NTP servers with legacy configuration are still found and still abused.

Time shifting. An on-path attacker who can modify or forge NTP responses can move a client’s clock. Jumping forward past a certificate’s expiry, or backwards to before a revocation, has obvious consequences. Khronos and similar watchdog mechanisms exist to detect implausible adjustments.

Denial of synchronisation. Simply blocking NTP causes clocks to drift until Kerberos authentication fails across a domain, which looks like a catastrophic identity outage rather than a network attack.

GNSS spoofing. Where stratum 1 servers take time from GPS, a spoofed satellite signal feeds false time into the top of the hierarchy. This is a genuine concern in finance and in OT environments, and incidents of GNSS interference have been reported widely in European airspace.

Authentication: Network Time Security

NTP’s older symmetric key authentication required a pre-shared key per server pair and was effectively unmanageable at scale. Autokey, its public key successor, was broken and is deprecated. Network Time Security, published as RFC 8915 in September 2020, replaces both: a TLS key establishment phase on port 4460 produces cookies, and those cookies authenticate subsequent NTP packets on port 123 without the per-packet cost of TLS. Cloudflare, Netnod, and an increasing number of national providers run public NTS servers, and chrony and ntpsec support it on the client side.

A Sensible Design

Time integrity also matters evidentially. If an incident ends in court or in a regulatory submission, a defensible timeline depends on synchronised, documented clock sources. Our Digital Forensic and Incident Response Services rely on exactly that record.

FAQ – Frequently Asked Questions

Why Does Clock Accuracy Matter for Security?

Certificates are valid only between two timestamps, Kerberos rejects tickets more than about five minutes out of step, time-based one-time passcodes depend on the current interval, and log correlation across systems assumes a common clock. A shifted clock can therefore revive an expired certificate, break authentication across a domain, or make an incident timeline impossible to reconstruct.

Is My NTP Server Being Used for Amplification Attacks?

Check whether it responds to monlist or other control queries from outside your network, and whether it is reachable from the internet at all. Older ntpd configurations return large responses to small requests, which attackers use for reflection floods. Apply restrict directives, disable control queries, update to a current build, and do not expose internal time servers publicly.

What Is Network Time Security?

NTS, defined in RFC 8915, adds authentication to NTP without the per-packet cost of TLS. A TLS handshake on port 4460 establishes cookies, which then authenticate ordinary NTP packets on port 123. It prevents an on-path attacker forging time responses. Public NTS servers are available, and chrony and ntpsec support it on the client.

How Many Time Sources Should I Configure?

At least four external sources from different operators for your internal stratum 2 servers, so that a single incorrect or compromised source is outvoted by the selection algorithm. Internal clients should point only at your own servers, not at the internet. In cloud environments, the provider’s link-local time service is a reliable source that needs no outbound connectivity.

Related Terms

You May Be Interested In These

What Is Multi-Cloud Security?

Cybersecurity Terms

17 November 2026

What Is Multi-Cloud Security?

Read More
What Is OPC UA Security?

Cybersecurity Terms

17 November 2026

What Is OPC UA Security?

Read More
What Is Hashcat?

Cybersecurity Terms

17 November 2026

What Is Hashcat?

Read More