2020
DOI: 10.17487/rfc8915
|View full text |Cite
|
Sign up to set email alerts
|

Network Time Security for the Network Time Protocol

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
20
0

Year Published

2020
2020
2024
2024

Publication Types

Select...
5
2
2

Relationship

0
9

Authors

Journals

citations
Cited by 30 publications
(26 citation statements)
references
References 0 publications
0
20
0
Order By: Relevance
“…NTP Security. Different recommendations for securing NTP were proposed, such as TLS for NTP (NTS) [41], or Roughtime [42] with proof of misbehaviour (wrong time) to report bad servers. However, none is deployed or used, mostly due to the significant changes to the NTP ecosystem that they require, or assumptions which cannot be fulfilled in practice.…”
Section: Countermeasures and Mitigationsmentioning
confidence: 99%
“…NTP Security. Different recommendations for securing NTP were proposed, such as TLS for NTP (NTS) [41], or Roughtime [42] with proof of misbehaviour (wrong time) to report bad servers. However, none is deployed or used, mostly due to the significant changes to the NTP ecosystem that they require, or assumptions which cannot be fulfilled in practice.…”
Section: Countermeasures and Mitigationsmentioning
confidence: 99%
“…Finally, in October 2020 the IETF introduced the Network Time Security mechanism in RFC8915 [6] using Transport Layer Security (TLS) [25] and Authenticated Encryption with Associated Data (AEAD) [17] to provide cryptographic security for the client-server mode of the Network Time Protocol (NTP). NTS is based on two loosely coupled sub-protocols, the NTS Key Establishment (NTS-KE) which handles initial authentication and key establishment over TLS and the NTS Extension Fields for NTPv4 (NTS-EF) which handles encryption and authentication during NTP time synchronization via extension fields in the NTPv4 packets.…”
Section: Network Time Securitymentioning
confidence: 99%
“…With security measures being too insecure [23], too complex or too inconvenient [19], today the default is still to use NTP and PTP without any countermeasures against manipulations [23]. This circumstance is potentially about to change as in October 2020 the IETF proposed a novel mechanism for cryptographic secured transmission of timestamps without major deficits in accuracy: RFC8915 standardizes the Network Time Security (NTS) mechanism, for using Transport Layer Security (TLS) and Authenticated Encryption with Associated Data (AEAD) in extension to NTPv4 to provide integrity and authenticity for timestamp transmission [6]. In February 2022, the German Federal Office for Information Security (BSI) even issued the official advisory to use NTS in favor of NTP where possible 1 .…”
Section: Introductionmentioning
confidence: 99%
“…NTP is not encrypted nor cryptographically signed (past approaches like the Autokey-protocol [12] are broken [35], the newer Network Time Security (NTS) [10] was introduced recently in 2020 and has no practical relevance yet).…”
Section: Ntpmentioning
confidence: 99%