NIS2 is no longer something on the horizon. It is here. The Swedish Cybersecurity Act has been adopted. MCF has shifted from information sessions to active supervision. And yet we see the same four failures in nearly every organisation we meet, whether it is a listed company, a municipality or a government agency. It is not the technology that fails. It is governance. The good news is that all four can be fixed in a matter of weeks once you know where to start.
It is not the technology that fails. It is governance.
Background
NIS2 Article 21 requires processes for detection, handling and reporting. Article 23 requires early warning to MCF within 24 hours, an interim report within 72 hours and a final report within a month. Article 20 places accountability on management, personally.
GDPR Article 33 gives 72 hours to notify the Swedish DPA (IMY) of a personal data breach. The Protective Security Act and the Public Access to Information and Secrecy Act add layers for public bodies. The Swedish Cybersecurity Act, in force since January 2026, raises the bar further. MCF has already started asking for evidence of capability, not just documentation.
agencies met all requirements in the latest Cybersecurity Audit. Our view of the private sector is that the picture is similar. Documents exist. Capability does not.
Here are the four failures we see most often.
The incident plan lives where the incident strikes
The most common, and most ironic, mistake: the incident plan lives in Microsoft 365. Which happens to be the very environment ransomware attacks first.
When access disappears, so does the plan. Right when it is needed most.
In the private sector, this leads to the crisis being documented in mobile notes, WhatsApp threads and Post-it notes. In the public sector, OSL, the Archives Act and protective security collapse within minutes.
Print the plan, store an encrypted copy on a USB drive and a second copy with an external partner. Update them quarterly.
It is one of the cheapest and most effective steps you can take. It is also the one I most often have to remind leadership teams about twice.
Classification is missing or unclear
An incident plan without a classification model is just a collection of routines. When the alert comes in, the person receiving it must be able to decide within five minutes whether the incident is L1, L2, L3 or L4.
Classification governs everything:
- escalation
- communication
- reporting obligations
- documentation requirements
- leadership activation
In the private sector, thresholds for when the CEO and board should be informed are usually missing. In the public sector, the distinction between IT incident, security incident and sensitive security incident under need-to-know is usually missing.
The result is the same: the wrong people find out at the wrong time, or not at all.
Build a four-level model with clear criteria and binding time limits. Once it is rehearsed, triage time drops from hours to minutes.
Reporting chains are not synchronised
NIS2 requires MCF reporting at 24 and 72 hours. GDPR requires DPA notification within 72 hours. Customer contracts often require notification within 24 to 48 hours. The Protective Security Act requires reporting to the supervisory authority and sometimes to SÄPO. CERT-SE often needs to be informed in parallel.
Each of these has its own template, lead time and approval flow. In most organisations they are handled by different people, in different documents, without a shared timeline.
The result is that the same incident is told differently in different reports. That is one of the most common reasons a supervisory inquiry deepens.
For private companies, this is a commercial risk. A customer who finds out last loses trust, even if the response was technically sound.
For public bodies, this is a supervisory risk. From our experience, MCF looks at the whole picture, not at individual details. When reports do not align, that signals weak governance regardless of what the incident itself was about.
Build a common reporting chain with a central incident log from which all reports are written. That way you tell the same story to everyone, every time.
Leadership has never rehearsed
A tabletop exercise with leadership in the room is the single investment that pays back the most. Not the IT department's technical run-through, but a realistic simulation where the CEO, head of administration or municipal director has to make the decisions that come up in a real crisis:
- do we go public
- do we report today or tomorrow
- do we pause deliveries
- do we send staff home
- do we file a police report, and when
A police report is not a checkbox in a process
A police report is a strategic decision with consequences for:
- communication
- the relationship with the attacker
- insurance terms
- the chain of evidence
- supervisory authorities
- the media
It is a decision that cannot be delegated.
In the private sector, it is commercial and reputational. A poorly timed police report can affect ongoing negotiations with the attacker, customer relationships and, in the worst case, the share price.
In the public sector, it is legal and political. A missing or late police report can become a supervisory matter, or a front-page story.
What a tabletop actually reveals
A tabletop with leadership reveals more than technical gaps. It exposes governance gaps:
- who dares to make the decision
- who waits for someone else
- who assumes someone else owns the issue
- who understands the consequences of filing a police report, and of not filing one
One day a year is enough to expose almost everything. Two hours afterwards is enough to fix the most important gaps.
I have never seen a leadership team regret their first real tabletop. I have seen several regret waiting so long to do it.
What this means for you
If you recognise yourself in three or four of these points, you are where the Swedish average is right now. That is nothing to be ashamed of. It is also not sustainable.
Supervision is active. Customer expectations are tightening. Incidents are increasing.
Those who build capability now stand firm at the next audit and at the next breach. Those who wait will explain.
The question to take to your next leadership meeting
If your organisation suffers a serious security incident tonight, do you know who decides on isolation, who notifies the DPA and MCF within 24 hours, who speaks to the media, who opens a channel to CERT-SE, and who decides on the police report? Are the decisions documented in advance, or are you hoping the right people are awake?
Want to see what it looks like in your organisation?
We start with a NovuLens gap analysis that gives leadership a clear picture in two weeks. Then the actual work is delivered through NovuPro Incident Management & Reporting, at a fixed price and within four to six weeks. The result is a complete process that ties NIS2, NIST CSF 2.0 and ISO 27035 together, ready to be implemented and, above all, rehearsed.
Contact BjörnBook a tabletop with leadership, at least once a year. Two hours is enough to expose the governance gaps and produce an action plan. The first one is always the most valuable. Don't wait for a crisis to force it.