Incident timeline, live
Detection, classification, escalation and every decision anchored with owner and time as it happens.
Every incident, proven as it unfolds.
Network and Information Security Directive 2
Essential and important entities across 18 sectors must manage cyber risk, report incidents fast and answer for it at board level. Reltime turns all three into proof that runs in real time.
Who it hits.
Essential and important entities in energy, transport, banking, health, water, digital infrastructure, ICT service management, public administration, space, manufacturing, food, waste, chemicals, postal services and digital providers. And the suppliers they depend on.
What it demands.
- Art. 21Cyber risk management measures, supply chain security included
- Art. 23Early warning, incident notification and final report to the authority
- Art. 20Management bodies approve the measures, oversee them and can be held liable
- 24 h
- Early warning
- 72 h
- Incident notification
- 1 month
- Final report
Transposition deadline 17 Oct 2024 · Applies through national law, for example Sweden's Cybersecurity Act from 15 Jan 2026
Up to EUR 10m or 2% of global turnover for essential entities · EUR 7m or 1.4% for important entities
What Reltime runs. In real time.
Reports drafted from the proof
The 24-hour warning, the 72-hour notification and the final report are built straight from the timeline.
Supplier oversight on proof
Supplier evidence and changes anchored once. You and your supplier see the same receipt.
Board accountability
Management approvals of risk measures tied to identity, date and version.
Access checked first
Every request to critical systems proves who is asking, in which role and under which rule.
RELTIME VERIFICATION RECEIPTExample
- Event
- Incident INC-0417 · significant
- Escalated to
- ciso.on-call · verified
- Rule
- nis2-incident-policy v2.1
- Time
- 2026-10-14 03:12:44.201 CET
- Fingerprint
- 4b1e…92ad · unchanged ✓
One receipt. Every auditor.
Who acted, which rule applied and whether anything changed. Created the second it happened. Verified by any authorised party without access to your systems.
Live in four weeks.
- Week 1
Map your incident process and connect the ticketing system
- Week 2
Configure the rail, roles and alerts
- Week 3
Test with your counsel or auditor
- Week 4
Run in real time and deliver the first evidence pack