NIS2 in Mergers and Acquisitions: The 20-Point Due Diligence Checklist to Run Before You Sign
NIS2 never says “merger”. Yet a deal can pull a target into scope on completion day, with no grace period. The 20-point NIS2 M&A due diligence checklist.
NIS2 compliance guides and resources
NIS2 never says “merger”. Yet a deal can pull a target into scope on completion day, with no grace period. The 20-point NIS2 M&A due diligence checklist.
NIS2 CSIRT reporting portals: the EU’s own directory is unlinked, dated July 2025, and silent on contact hours for 12 of 27 states. Where you actually file.
Cross-border NIS2 incident? You file with one CSIRT, not five. Article 23(6) puts multi-country notification on your regulator – here is who files what.
Your NIS2 final-report clock starts when you file the 72-hour notice, not at the incident. Article 23(4)(d)’s four items, three of them unconditional.
A cross-border critical infrastructure attack can escalate to EU-CyCLONe under Article 16 and nobody tells you. The real large-scale threshold, explained.
NIS2’s 72-hour notification: Article 23(4)(b) names three elements, two of them conditional. What to file, and how to draft it mid-investigation.
Article 23(4)(a) names just two facts for the NIS2 24-hour early warning. Here’s what to write when you know neither cause nor scope — and what to omit.
An API breach under NIS2 is not decided by record count. For most CIR digital providers a maliciously caused compromise is significant on its own facts.
Five questions settle significant vs non-significant under NIS2 Article 23(3) in ten minutes – the test asks what an incident could cause, not what it did.
No EU threshold covers your plant. Here’s the real Article 23 significance test for an OT or ICS incident — and why zero downtime can still be reportable.