top of page

Time synchronization and NIS2: why reliable time is indispensable

5 hours ago
2 min read

Since August 15, 2026, the Cybersecurity Act (Cbw), the Dutch implementation of the European NIS2 Directive, has been in force in the Netherlands. Essential and important organizations must manage their digital risks and report serious incidents promptly. A subject that is often overlooked in this context is time itself.

Why time matters during an incident

In the event of a cyber incident, you want to quickly reconstruct what happened: when did the attacker gain access, which systems did they affect, and in what order? To do this, you compare log files from firewalls, servers, workstations, and applications. If the clocks of those systems are not synchronized, the sequence of events is incorrect. A timeline with errors of minutes slows down the investigation and weakens the evidence, precisely at the moment when you need to file an initial report within 24 hours.

What do the rules say?

NIS2 does not prescribe a specific time protocol, but logging and monitoring are part of the mandatory measures for incident handling. European Implementing Regulation (EU) 2024/2690, which elaborates on the measures for data centres, cloud and IT service providers, among others, is specific in this regard: organisations must, as far as feasible, ensure that all systems have synchronized time sources so that log files can be correlated between systems.

ISO 27001 (control measure 8.17) and NEN 7510 for healthcare also require that the clocks of information systems be synchronized with approved time sources. Those who already work with these standards are therefore already familiar with this requirement.

Please note: this article is a technical explanation and not legal advice. You can check with your supervisor or legal advisor whether and how the Cbw applies to your organization.

This is how you structure reliable time

  1. Use your own time server. Do not rely solely on public time servers via the internet. A private NTP server on your network, using GNSS (GPS/Galileo) as the source, is independent of the internet and third parties.

  2. Build in redundancy. Two time servers, preferably in different locations, prevent a single failure from affecting all systems.

  3. Ensure a holdover. Satellite signals can be interfered with or distorted. A time server with a stable oscillator will then accurately hold the time until the signal returns.

  4. Secure the protocol. Use NTP authentication or NTS so that systems only accept time from your own trusted server.

  5. Monitor the time. Have the time server send notifications in case of loss of the time source or deviations, and include this in your monitoring.

  6. Document it. Describe in your policy which time source you use and how it is monitored. That helps with audits.

Need advice?

BerdoTime supplies NTP and PTP time servers from Mobatime with GNSS reception, redundant configurations, and secure time distribution. We are happy to help you find a time synchronization solution that suits your network and your obligations. Call 085-4000265 or email info@berdo.nl .

 
 
 

Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.
Network clocks
DTS new photo.jpeg
data network ntp server
bottom of page