NIS2 security measures – 10 areas in the Cybersecurity Act and MCFFS 2026:11
Organizations covered by the Cybersecurity Act must adopt a risk-based approach across ten explicit security areas. As of October 1, 2026, the act is further supplemented by MCFFS 2026:11 regarding security measures and training. The work should therefore be organized as an ongoing management system—not as a one-time checklist prior to an audit.
The basic requirement: appropriate, proportionate, and all-risk-based
According to Chapter 2, Section 3 of the Cybersecurity Act (2025:1506), entities must implement appropriate and proportionate technical, operational, and organizational measures to protect the network and information systems used in their operations or for their services, as well as the physical environment of these systems.
The measures must be based on an all-risk perspective, and the level of security must be proportionate to the risk. This means the work needs to encompass more than traditional IT security. Dependencies on personnel, facilities, suppliers, communications, operations, and the physical environment can be part of the same risk profile.
If you are unsure whether your organization is covered by the regulations, start with which companies are covered by NIS2 and the Cybersecurity Act.
The 10 security areas in Chapter 2, Section 3
| Area | Practical focus |
|---|---|
| 1. Risk analysis and security strategies | Risk methodology, risk register, responsibilities, policies, and decisions on risk treatment. |
| 2. Incident handling | Detection, alerts, classification, response, escalation, and learning. | 3. Continuity and crisis management | Backup, recovery, contingency procedures, BIA, and crisis organization. |
| 4. Supply chain | Critical suppliers, contractual requirements, subcontractors, and follow-up. | 5. Security in acquisition, development, and maintenance | Security requirements in procurement, change, development, vulnerabilities, and patching. |
| 6. Assessing the effectiveness of measures | Measurement, control, auditing, testing, and improvement. |
| 7. Cyber hygiene and training | Basic routines, awareness, and role-adapted training. |
| 8. Cryptography and, where necessary, encryption | Management of cryptographic solutions, keys, and protection needs. |
| 9. Personnel security, access, and assets | Access rights, joiner/mover/leaver, inventory, and asset responsibility. |
| 10. Authentication and secured communication | Multi-factor authentication where necessary, secured voice/text/video, and emergency communication. |
1. Risk analysis that actually guides measures
The risk analysis should not sit in a document archive. Connect identified threats and vulnerabilities to concrete assets, services, owners, and measures. Specify who accepts residual risk and when the risk assessment should be updated.
2. Incident handling
The organization needs to know how a suspected incident moves from initial observation to classification, containment, communication, and recovery. Internal workflows should support statutory reporting deadlines when a significant incident occurs. See NIS2 incident reporting – 24 and 72 hours and the new guide to incident management plans.
3. Continuity and crisis management
Identify which activities must function first, how quickly they need to be restored, and what dependencies they have. A BIA provides the basis for prioritization, and the continuity plan describes the contingency procedures.
4. The supply chain
Classify suppliers by criticality and define proportionate security requirements. This may include incident information, access rights, subcontractors, continuity, verification, and exit strategies. Read NIS2 and supplier contracts.
5. Secure acquisition, development, and maintenance
Security requirements must be introduced as early as when systems are purchased, developed, or modified. Document minimum requirements, vulnerability and patching processes, pre-deployment testing, and how major changes are risk-assessed.
6. Measure whether measures work
A policy shows intent; measurement shows function. For example, follow up on old critical vulnerabilities, recurring access anomalies, completed recovery tests, supplier audits, and how quickly incidents are detected and escalated.
7–10. People, cryptography, access, and communication
Strong technical tools provide limited help if permissions remain after role changes, keys are poorly managed, or personnel do not recognize incidents. Therefore, integrate training, asset inventory, access control, authentication, cryptography, and secured communication channels into the same management model.
How to build a functional risk management workflow
- Inventory. Identify services, processes, systems, data, suppliers, and physical dependencies.
- Assess impact. What happens to availability, accuracy, confidentiality, and operations if something fails?
- Identify threats and vulnerabilities. Use cyber, supplier, personnel, and continuity perspectives.
- Prioritize risk. Determine which risks must be treated first.
- Select measures. Reduce, avoid, transfer, or, in documented cases, accept risk.
- Assign owners and deadlines. Every important measure needs a person responsible.
- Verify effectiveness. Test if the measure works, not just if it is implemented.
- Re-evaluate. Update in the event of incidents, major changes, and according to a set cycle.
Management responsibility and training
The Cybersecurity Act requires members of the entity's management to undergo training on security measures. MCFFS 2026:11 supplements the regulations from October 1, 2026, with provisions and general advice on security measures and training.
Management reporting should therefore provide a clear basis for decision-making: the most significant risks, major incidents, open high-risk actions, critical supplier deficiencies, results from tests/audits, and decisions that need to be made.
Documentation: show how the requirement is applied in practice
A common weakness is having many policy documents but poor traceability between risk and actual control. Create a simple chain instead:
requirement → risk → control → responsible → evidence → follow-up → improvement.
Evidence can be meeting minutes, technical configurations, training logs, log extracts, audit results, test protocols, supplier assessments, incident reports, and recovery tests.
Where should a company start?
- Confirm that the organization is covered and submit the required notification.
- Appoint responsibilities and create management-level governance.
- Inventory critical services and dependencies.
- Conduct a documented risk analysis.
- Perform a gap analysis of the ten areas.
- Prioritize measures where the impact is greatest.
- Establish incident and continuity capabilities.
- Classify critical suppliers.
- Introduce follow-up, KPIs, testing, and auditing.
- Document training and recurring re-evaluations.
Quick checklist
- Is there an up-to-date risk register with risk owners?
- Is the incident management plan tested?
- Are there BIAs and continuity plans for critical activities?
- Are suppliers classified by criticality?
- Is there a process for vulnerabilities, patching, and secure development?
- Do you measure whether security measures are actually working?
- Is training documented, including management training?
- Are cryptography and key management governed where needed?
- Are access rights and assets inventoried?
- Are authentication and emergency communication adapted to risk?

Structure your security work
Mallbutiken's NIS2 Template Package 2026 contains 15 integrated Word/PDF templates for areas including risk management, incidents, continuity, supplier security, and follow-up. Price in store: 199 SEK.
See the NIS2 template packageSources and further reading
- The Swedish Parliament: Cybersecurity Act (2025:1506), especially Chapter 2, Sections 3–4
- FRA/NCSC: new requirements and regulations for cybersecurity
The guide provides general information. Organizational measures need to be adapted to your own operations, risk profile, applicable regulations, and any sector-specific requirements.
Templates in this article
Explore the topic
Business guides – contracts, HR, AI & complianceWhich companies are covered by NIS2 and the Cybersecurity Act?
How Swedish organizations determine if they are covered by the Cybersecurity Act: sector, establishment, size, special cases, essential/important e...
Business guides – contracts, HR, AI & complianceNIS2 incident reporting – 24 hours, 72 hours and final report
This is how incident reporting works under the Cybersecurity Act: notification within 24 hours, incident report within 72 hours, and a final report...
Business guides – contracts, HR, AI & complianceIncident Response Plan – how companies build a practical plan for cyber incidents
Build an incident response plan covering roles, escalation paths, triage, classification, containment, evidence, communication, reporting, recovery...



