Validation build: the evidence log is live; the pricing example is simulated and places no cover. What that means

RiskRouter

For providers of public electronic communications networks and services

After an incident, show which network change came first, exactly as it was made.

When a network goes down or is breached, the first questions are what changed, when, and whether the record of it is the one from the day. The change log usually lives on the very systems that were changed.

Try it in two minutes Talk about a pilot
When it is tested
A significant-incident notification and its final report; a supervisory inspection; a dispute with a supplier over a change; your own post-incident review.
What you will be asked for
NIS2 applies, whatever their size, to providers of public electronic communications networks or of publicly available electronic communications services (Directive (EU) 2022/2555, Article 2(2)(a)(i)); those that qualify as medium-sized enterprises are essential entities (Article 3(1)(c)). Their measures must include incident handling, security in the maintenance of network and information systems, and access control policies (Article 21(2)(b), (e) and (i)), and significant incidents must be notified (Article 23).
What goes wrong today
Configuration archives and change logs sit on management systems that an administrator, or anyone holding their access, can edit; an export is a file anyone can change; and a change log is still the network’s own word.
What changes
Each configuration change, as committed, and each segment of the routers’ and management systems’ logs is sealed as it is written, with logseal and the nis2 pack. Only a salted fingerprint leaves your network; the configurations and log lines stay in your own archive. Numbered in a chain, the changes to one device can be shown complete: one sealed and later removed shows as a gap.

Sealing shows that a record existed unchanged from a given moment; whether your records are enough is yours to judge. A seal is evidence of what was written and when, never detection: it cannot say a change was authorised, identify an attacker, or protect what is written after a machine is taken over. Sealed security logs

Try it in two minutes

  1. Choose a real file of your own: a router configuration export. It is read in your browser and never uploaded.
  2. Seal it on Seal a file. A free sandbox key is issued on the page; only a salted fingerprint reaches the log.
  3. Make a copy, change one character in it, and check both against the receipt at Check. The copy fails; the original passes.

From your own systems it is one API call per record. Integrate · Other industries