Getting NIS2 incident handling and reporting right in practice: the response plan, the end-to-end reporting process, reporting one incident under NIS2 and GDPR, and the exercises that prove the process works.
What a NIS2 incident response plan must contain: incident categories, escalation and reporting communication plans, roles, containment and recovery procedures, reporting channels for staff and suppliers, post-incident reviews and links to the reporting deadlines.
The full NIS2 reporting sequence for a significant incident: deciding significance, where to report, the 24-hour early warning, 72-hour notification, intermediate and final or progress reports, telling customers, cross-border incidents and the proposed single-entry point.
When a cyber incident is also a personal data breach: the two authorities and timelines, what each notification contains, processor duties, informing individuals and customers, coordination between authorities and the rule against double fines.
How to test NIS2 incident handling before a real incident: testing response procedures and continuity and crisis plans at planned intervals, rehearsing the 24-hour and 72-hour reports, quarterly recurring incident reviews and documenting lessons learned.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.