The Body That Registers You Is Not the Body That Audits You
On 1 October 2026 the Swedish regulations on security measures, MCFFS 2026:11, began to apply. Transportstyrelsen has scheduled reviews of those measures at its registered essential entities to begin in November 2026. Any organisation under Cybersäkerhetslagen that buys managed detection and response now faces the practical side of NIS2 audit evidence in Sweden. Detection logs count only when they answer the sections your own sector supervisor chooses to examine.
The reason is a split that many compliance plans still miss. Early in 2026 the visible authority was MCF (formerly MSB), which wrote the registration rules and hosted CERT-SE. Since 1 July 2026 registration and incident reports go instead to the National Cybersecurity Centre (NCSC) at FRA. Neither body audits you.
Supervision sits with 13 sector authorities named in the Cybersecurity Ordinance. Since October they have section-level requirements on logging, monitoring and incident handling to check you against. Your MDR provider produces much of the material they will want to see.
Key Takeaways
- Since 1 July 2026 you register and report incidents to NCSC at FRA, but one of 13 sector authorities audits you.
- MCFFS 2026:11 has applied since 1 October 2026 and sets out what monitoring, security logging and incident handling must cover.
- Essential entities can face regular security audits. Important entities are supervised only when there is reason to suspect a breach.
- Transportstyrelsen plans reviews of essential entities from November 2026 and asks for documents before interviews and a site visit.
- Fines reach the higher of 2% of global turnover or the krona equivalent of EUR 10 million for essential entities.
What is NIS2 Audit Evidence?
NIS2 audit evidence is the dated record showing that a required security measure exists, is applied and is followed up. In Sweden it means the documents, logs and decisions that let a supervisory authority verify compliance with Cybersäkerhetslagen and MCFFS 2026:11, which give effect to the risk-management measures in Article 21 of the NIS2 Directive.
Two of the ten Article 21 measures sit closest to an MDR service. Article 21(2)(b) covers incident handling. Article 21(2)(f) covers policies and procedures to assess whether the measures are effective. Swedish law carries both into chapter 2 section 3 of Cybersäkerhetslagen as points 2 and 6.
MCFFS 2026:11 turns them into checkable duties. Chapter 3 section 17 requires incident handling that can identify, report, analyse and contain incidents. Section 19 requires yearly follow-up of security measures for sector-critical systems. Chapter 4 sections 20 to 22 cover monitoring, security logging and log analysis. Section 29 makes intrusion detection and prevention mandatory for IT segments in production.
The regulation also tells you to work out what you must document and keep for supervisory purposes. Its general advice lists decisions, analyses, assessments, plans and follow-up results. That list is the closest thing Swedish law offers to an official evidence pack.
The Dates That Matter
| 15 January 2026 | Cybersäkerhetslagen (SFS 2025:1506) and the Cybersecurity Ordinance (SFS 2025:1507) enter into force. |
| 1 July 2026 | FRA becomes single point of contact and CSIRT. Registration and incident reporting move to NCSC. MCFFS 2026:8 on incident reporting applies. |
| 1 October 2026 | MCFFS 2026:11 on security measures and MCFFS 2026:12 on security audits and scans apply. |
| November 2026 | Transportstyrelsen plans to begin reviewing security measures at registered essential entities. |
Who Audits You and How Often
Section 7 of the Cybersecurity Ordinance (SFS 2025:1507) assigns supervision by sector. Seven national authorities and six county administrative boards share the work. If two of them supervise the same organisation they must agree how the supervision is carried out.
How often you hear from them depends on your classification. Supervisors may run regular security audits of essential entities, themselves or through an independent body. For important entities they may request documents, enter premises, audit or scan only when there is reason to assume a breach. This mirrors Articles 32 and 33 of the NIS2 Directive, under which essential entities face proactive and reactive supervision while important entities face reactive supervision only.
Once a review starts the toolkit is the same. A supervisor can demand information and documents, enter premises, run targeted security audits where there are special reasons and carry out security scans in cooperation with you. It can also order you to take part under threat of a fine. Article 32 adds requests for evidence that policies are implemented, including audit results and their underlying evidence.
One exception changes the rulebook. Organisations operating only in PTS sectors such as digital infrastructure or managed ICT services take just the management training duty from MCFFS 2026:11. Cloud, data centre and managed security service providers follow Commission Implementing Regulation (EU) 2024/2690 instead, whose annex covers monitoring and logging in point 3.2.
Who Audits Which Sector
- Energimyndigheten : Energy
- Transportstyrelsen : Transport and vehicle manufacturing
- Finansinspektionen : Banking and financial market infrastructure, with DORA entities exempt from the security and reporting duties
- IVO and Läkemedelsverket : Health, with IVO covering care providers
- Livsmedelsverket : Drinking water, waste water and food production and distribution
- PTS : Digital infrastructure, digital providers, managed ICT services, postal and courier services and space
- Six länsstyrelser : Public administration, waste, research, chemicals and several manufacturing sectors, split by region
What a Supervisory Review Asks For
Transportstyrelsen has published its method and it shows what a NIS2 auditor asks for in practice.
Transportstyrelsen’s Published Review Process
Transportstyrelsen’s supervision page, last updated on 20 October 2026, describes nine steps for reviewing security measures at registered essential entities. It starts with a notice proposing dates. The authority then requests documents proving compliance with the specific sections it has selected, before any meeting takes place.
After a start-up meeting the authority drafts an agenda, which a second digital meeting confirms. The site visit follows, with interviews of the people responsible for each selected area and a review of documentation. A draft report goes to you for a fact check before the final assessment. Any shortcomings may require a remediation plan.
The control that makes this manageable is an evidence index organised by MCFFS 2026:11 section and ready before the notice arrives.
Before the Notice Arrives
Confirm which authority supervises each of your sectors and whether you are essential or important. Check your MDR provider’s standard reports against the sections in the list below and fill gaps now. Evidence produced after the request looks produced for the request.
During and After the Review
Send documents mapped to the sections the authority named rather than a full platform export. Put the owners of incident handling and log review in the interviews. Check the draft report carefully, since it is your chance to correct facts. If a remediation plan is required, give each action an owner and a date.
MDR Output and the Section It Proves
- Log source inventory : Chapter 4 section 21 on what production systems must log
- Alert-to-action records : Chapter 4 section 20 on alarms and the action taken
- Log review cadence : Chapter 4 section 22 on analysing logs per system at a risk-based interval
- Incident tickets : Chapter 3 section 17 on identifying, analysing, containing and recovering
- Reporting timestamps : Chapter 2 sections 5 to 8 of the law on the 24 hour, 72 hour and one month reports
- Detection test results : Chapter 3 section 19 on yearly follow-up of security measures
Where MDR Evidence Falls Short
The logging duties exist so that intrusions can be investigated afterwards. A review tests whether your records allow that. Five gaps recur in MDR arrangements.
Coverage That Stops at the Endpoint
MCFFS 2026:11 requires logging of unauthorised and attempted access across the digital environment. In production it adds access to systems, use of administrator rights, configuration changes in security functions and sector-critical systems, permission changes and access to sensitive information. An MDR service fed only by endpoint agents may miss several of these sources.
Alerts Without a Decision Trail
Section 20 asks you to assess the need for alarms and for action when they fire. An alert queue with no record of who triaged each alert, what they decided and when proves monitoring but not response.
Clocks That Disagree
Section 23 requires robust and accurate time traceable to UTC(SP), the Swedish realisation of coordinated universal time, in production. Logs from systems on different clocks are hard to correlate and harder to defend.
Supplier Reports Outside the Contract
When you outsource, chapter 4 section 1 makes you responsible for the supplier meeting the regulation’s requirements. The general advice says contracts should state when and how the supplier informs you about incidents.
Evidence That Overstates
Giving false or grossly inaccurate information about security measures is a serious infringement under chapter 4 section 3 of Cybersäkerhetslagen. Claiming log coverage you cannot demonstrate is a risk in its own right.
Penalties for Non-Compliance
A supervisor that finds a breach must intervene, by remark, injunction with a conditional fine or administrative fine. At a private essential entity it can also ask a court to ban a manager from a management role for one to three years.
When choosing the intervention the authority must consider what you did to prevent or limit harm. Records of fast detection and response support that case.
The Fine Bands in Swedish Law
Fines start at SEK 5,000. The ceiling is the higher of 2% of global annual turnover or the krona equivalent of EUR 10 million for essential private entities and 1.4% or EUR 7 million for important ones. Public sector bodies face up to SEK 10 million.
How to Keep MDR Output Audit-Ready
Treat MDR NIS2 compliance as a reporting task as much as a detection task.
Map every recurring MDR report to the MCFFS 2026:11 section it supports and keep that map with the reports.
Record a log source inventory per sector-critical system and review it whenever the environment changes.
Protect logs and keep them as long as investigations need, with the reasoning written down.
Test detection and response at least once a year for sector-critical systems and after each completed root cause analysis, then file the results as effectiveness evidence for Article 21(2)(f).
Brief management on the state of security measures at least once a year as chapter 3 section 4 requires. Keep the briefing material.
Rehearse a document request internally before the first real one.
The First Request Will Name Sections, Not Tools
Swedish supervisors now check NIS2 compliance against MCFFS 2026:11, one sector at a time. Find out which authority holds your file and map your MDR output to the sections on incident handling, monitoring and logging. Then close the gaps before the notice arrives.
How eBuilder Helps
eBuilder Security’s MDR & SOC service delivers managed detection and response for organisations that want monitoring, alert handling and incident response run as a service. It suits teams that need to show a supervisor how detection and incident handling work in practice.
Frequently Asked Questions
Who audits NIS2 compliance in Sweden?
Your sector authority does. The Cybersecurity Ordinance names 13 supervisors, including Energimyndigheten, Transportstyrelsen, PTS, Finansinspektionen and six county administrative boards. NCSC at FRA receives registrations and incident reports but does not supervise. MCF (formerly MSB) is not a supervisory authority under the law.
What does a NIS2 auditor ask for?
Documents that prove compliance with the specific sections selected for review, sent before any meeting. Transportstyrelsen’s published process then adds interviews with responsible staff and a documentation review on site. MCFFS 2026:11 points to decisions, analyses, assessments, plans and follow-up results as the records to keep for supervision.
Can MDR reports count as NIS2 evidence?
Yes, if they show what the regulations require. Reports should prove which systems are logged, how alerts were handled and when, how incidents were contained and that detection is tested. Your contract with the provider should define these reports, because you stay responsible for the supplier meeting the requirements.
How long should security logs be kept under NIS2 in Sweden?
MCFFS 2026:11 sets no fixed period. It requires security logs to be protected against unauthorised access and kept as long as needed to investigate security shortcomings. Base the period on your risk analysis and incident history. Document the reasoning so a supervisor can see how you decided.
This post is also available in: