Tidal Control incident
Individual security measures are not yet NIS2 compliance
Resolved on February 27, 2026.
Implementing individual security measures like two-factor authentication or an incident response plan does not add up to NIS2 compliance. Without a risk-driven foundation, assigned ownership, and continuous visibility, organisations end up with a checkbox mentality that leaves real gaps undetected. The shift to structural compliance requires linking every measure to a concrete risk, giving each measure a responsible owner, and replacing annual snapshots with ongoing monitoring. An honest inventory of what you already have is the right starting point, not adding more measures.
Update timeline
- resolved Feb 27, 2026, 12:00 AM UTC
Implementing individual security measures like two-factor authentication or an incident response plan does not add up to NIS2 compliance. Without a risk-driven foundation, assigned ownership, and continuous visibility, organisations end up with a checkbox mentality that leaves real gaps undetected. The shift to structural compliance requires linking every measure to a concrete risk, giving each measure a responsible owner, and replacing annual snapshots with ongoing monitoring. An honest inventory of what you already have is the right starting point, not adding more measures.
Your product runs on more than Tidal Control
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services