Sweden

Sweden MCFFS 2026:12 Security Audit and Security Scanning Regulations

23 controls. 5 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

23 controls 5 frameworks share controls with it Sweden verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
1:1-2Scope: the security audits and security scans foreseen in 3 kap. 5 to 7 §§ of the Cybersecurity Act (2025:1506); chapter 2 applies only where a supervisory authority engages an ind0
1:3-4Definitions: expressions follow the Cybersecurity Act; digital environment, sector-critical system, system, security audit, security scanning and important societal function are de0
2:1A security audit must assess the operator's level of cybersecurity and whether its security measures meet the requirements of the Cybersecurity Act and its subordinate regulation1
2:10If a previously unpublished vulnerability is found in the operator's digital environment during an audit, the supervisory authority must ensure the independent body informs the ope1
2:11After the audit the supervisory authority must ensure the independent body compiles the results in a written report and hands the report and other relevant documentation to the aut1
2:2The independent body engaged for a security audit must be a legal person or sole trader whose staff have knowledge sufficient for the design of the assignment and, where needed, of1
2:3The supervisory authority must ensure the independent body audits impartially, independently and objectively, is bound by no confidentiality agreement with the operator that limits2
2:4When a security audit starts, the supervisory authority must inform the operator of the assignment's scope, of its right to report shortcomings in the independent body's conduct of1
2:5The supervisory authority must ensure the independent body documents every deviation from compliance with the Cybersecurity Act and its subordinate regulation1
2:6A security audit checks both the design and the application of security measures and must be designed so it causes the operator no more cost or inconvenience than necessary1
2:7A security audit includes at least document review, interviews with relevant staff, technical checks of systems and segments and, where needed, inspection of premises, with the las1
2:8The audit follows a documented methodology that allows a systematic, risk-based examination of organisational, technical, operational and physical security measures, and the superv1
2:9Before a security audit begins the supervisory authority must have approved its scope and approach1
3:1Through security scanning the supervisory authority assesses the effectiveness of the security measures implemented in the operator's digital environment1
3:2A security scan is performed by a supervisory authority, which may engage an external actor, and by personnel with knowledge sufficient for the assignment1
3:3The supervisory authority must ensure a security scan goes no further than supervision requires and covers only systems the operator controls within its own activities1
3:4The supervisory authority must ensure a security scan is carried out so that negative impact on system functionality and other adverse consequences for the operator are minimised1
3:5When an external actor performs a security scan, the supervisory authority must ensure it is bound by no confidentiality agreement with the operator that limits the authority's acc1
3:6In choosing a scanning method the supervisory authority must consider the systems' importance to the operator's activities, and where a significant risk of adverse consequences is 1
3:7Before deciding to scan, the supervisory authority must ensure the operator and the systems were selected by a risk-based method and that the methods to be used suit the identified1
3:8Before a security scan, unless special reasons weigh against it, the supervisory authority together with the operator must assess the risk of operational impact, plan the scan to m1
3:9The supervisory authority must ensure the operator is informed without delay and in an appropriate manner of shortcomings and vulnerabilities found in a security scan so that it ca1
statusLegal basis in 38 § point 7 of the Cybersecurity Ordinance (2025:1507), the non-binding status of the general advice, decision on 15 June 2026 and entry into force on 1 October 2020

Tell me when Sweden MCFFS 2026:12 Security Audit and Security Scanning Regulations files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for Sweden MCFFS 2026:12 Security Audit and Security Scanning Regulations, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition