Compliance guide
IT security policy: what to include and which rules ask for one
An IT security policy, also called an information security policy (in Swedish, informationssäkerhetspolicy), is a short document in which management says how the organisation protects its information and systems, and who is responsible. NIS2 asks covered organisations for "policies on risk analysis and information system security". The GDPR asks for data protection policies where proportionate. This page shows the rules, then a starting outline you can adapt.
On this page
This is a plain-language summary, not legal advice. Where this page and the law differ, the law decides. The outline in section 6 is an original starting point written for this guide. It is not a legal template and is not taken from any standard. Adapt it to your organisation.
1. In short
- A policy states the goals and approach for security and gives people their roles. It is not the place for step-by-step instructions.
- NIS2 Article 21(2)(a) lists "policies on risk analysis and information system security" among the measures covered organisations must have.
- For certain digital providers, Regulation 2024/2690 spells out what that policy must contain, in 11 points, and says management must review it at least once a year.
- In Sweden, the rule book MCFFS 2026:11 (issued by MCF, in force since 1 October 2026, applied by FRA) uses the words "internal rules and ways of working" and requires management to set goals and direction for cybersecurity.
- The GDPR asks for "appropriate data protection policies" where proportionate (Article 24(2)).
2. What the policy is
It is the top document in your security paperwork. It answers: what are we protecting, why, who decides, and who does what. It is short, signed off by management and read by everyone.
Below it sit the documents that say how. Examples are rules for passwords, backups, remote work or supplier checks. Regulation 2024/2690 calls these "topic-specific policies" and asks the main policy to list them. This guide keeps to the main policy.
Rule of thumb: the policy says what must hold. A procedure says how to do it. A record shows that you did it.
3. Which rules ask for one
| Where | What it says |
|---|---|
| NIS2, Article 21(2)(a) | The cybersecurity risk-management measures of essential and important entities "shall include at least" "policies on risk analysis and information system security". They must be "appropriate and proportionate" (Article 21(1)). |
| NIS2, Article 20(1) | Management bodies must "approve the cybersecurity risk-management measures", oversee their implementation and "can be held liable for infringements" of Article 21. |
| Regulation 2024/2690, Annex 1.1 | For DNS providers, TLD registries, cloud, data centre, content delivery, managed service and managed security service providers, online marketplaces, search engines, social networks and trust service providers (Article 1): a "policy on the security of network and information systems" with 11 required elements, reviewed at least annually. See section 5. |
| MCFFS 2026:11, 3 kap. | The Swedish authority's binding rule requires goals and direction for cybersecurity, internal rules and ways of working, and management approval. See section 4. |
| GDPR, Article 24(2) | "Where proportionate in relation to processing activities, the measures referred to in paragraph 1 shall include the implementation of appropriate data protection policies by the controller." A controller is the one who decides why and how personal data is used. |
Which of these apply to you depends on who you are. NIS2 duties fall on essential and important entities, so first check whether NIS2 applies to your company. Regulation 2024/2690 applies only to the provider types listed in its Article 1. The GDPR applies if you process personal data. See GDPR compliance.
Article 2(2) of Regulation 2024/2690 adds one thing for those providers: where the Annex says a requirement applies "where appropriate", "where applicable" or "to the extent feasible", and the entity decides it does not fit, it must document its reasoning "in a comprehensible manner".
4. What the Swedish rule book says
MCFFS 2026:11 is the regulation on security measures and management training for essential and important operators. MCF issued it on 15 June 2026. Since 1 July 2026 FRA holds the rule-making role (ordinance 2025:1507, 38 §, as changed by SFS 2026:623). It does not use the word policy. It uses the Swedish words for goals and direction, and "interna regler och arbetssätt" (internal rules and ways of working). It came into force on 1 October 2026. The paragraphs that matter:
| Paragraph | What it requires |
|---|---|
| 3 kap. 1 § | Run "systematic and risk-based cybersecurity work" from an all-hazards view: identify external requirements, internal needs and risks, design and introduce measures, follow up and improve. It must be fitted into how the organisation is already led and managed. |
| 3 kap. 3 § | Set the internal rules and ways of working needed for suitable and proportionate measures. They must start from the organisation's set goals and direction for cybersecurity, be updated when needed, and be communicated to the staff concerned in the relevant parts. Identify and handle the need to document and keep what is needed for follow-up and for supervision. |
| 3 kap. 4 § | Management must approve and oversee the measures by making sure that: goals and direction are set (point 1), management's own tasks are clear (2), resources exist (3), roles have enough authority and resources (4), and management is informed about how the measures are going when needed, and at least once a year (5). |
| 3 kap. 5 § | Appoint roles for coordinating cybersecurity work, for security of information handled in systems (information owner) and for security of systems (system owner). All information handling needs an information owner and every system a system owner. |
Advice, not binding (3 kap. 3 §). The general advice says internal rules and ways of working should show which measure they cover, which roles are affected, the date they were set and who keeps them up to date, what is to be done, by which role, how and when, which decisions are made and by whom, and how compliance is documented. The regulation states that advice is not binding.
Who it applies to. Operators covered by the security measure rules. An operator whose sector activity is only digital infrastructure, digital providers, ICT service management (business-to-business), postal and courier services or space has only the management training requirement (1 kap. 1 §). The full tick-list is in the NIS2 compliance checklist, and the law itself in Cybersäkerhetslagen.
5. What it should contain
The most detailed legal list comes from Regulation 2024/2690, Annex point 1.1.1. It is binding for the provider types in its Article 1. For other organisations it is a useful checklist of what a regulator considers a complete policy. The policy must:
- set out the entity's approach to managing the security of its network and information systems;
- be appropriate to and complementary with the business strategy and objectives;
- set out network and information security objectives;
- include a commitment to continual improvement;
- include a commitment to provide the resources needed, including staff, finances, processes, tools and technologies;
- be communicated to and acknowledged by relevant employees and relevant external parties;
- lay down roles and responsibilities (point 1.2);
- list the documentation to be kept and for how long;
- list the topic-specific policies;
- lay down indicators and measures to monitor implementation and the current maturity level;
- show the date of formal approval by management.
Point 1.1.2 adds: management reviews and, where appropriate, updates the policy "at least annually and when significant incidents or significant changes to operations or risks occur". The result of the reviews must be documented.
6. A starting outline
One heading, one line. Fill each in with two to five sentences for your own organisation. This outline is written for this guide to cover the points in sections 4 and 5. It is a starting point, not legal advice, and not a copy of any standard.
| Heading | What it says |
|---|---|
| 1. Purpose and scope | Why the policy exists and which people, systems and sites it covers. |
| 2. Goals | The few security goals management has set, tied to the business. |
| 3. Management commitment | Management approves this policy, provides resources and commits to keep improving. |
| 4. Roles and responsibilities | Who owns security overall, who owns each system and each set of information, and who acts in an incident. |
| 5. How we handle risk | How risks are found, rated, owned and accepted or treated, and how often this is repeated. |
| 6. Rules for people | What staff and contractors must do and must not do, and the training they get. |
| 7. Access | Who gets access to what, how it is granted and removed, and how accounts are protected. |
| 8. Systems and updates | How devices, software and cloud services are kept up to date and configured safely. |
| 9. Information handling | How information is classified, stored, backed up, shared and deleted. |
| 10. Suppliers | What is checked before and during use of a supplier, and what contracts must say. |
| 11. Incidents | How events are reported internally, judged, handled and, where the law requires, reported to the authority. |
| 12. Continuity and recovery | What must be back first after an outage, and how recovery is tested. |
| 13. Documents and records | The supporting policies and procedures, and which records are kept and for how long. |
| 14. Measuring and exceptions | The indicators you track, how exceptions are requested and approved, and what happens when the policy is broken. |
| 15. Approval and review | Approval date, who approved it, version history and the next review date. |
Keep it to a few pages. A policy nobody reads protects nothing.
7. Keeping it alive
- Management approves it. NIS2 Article 20(1) puts the approval of the measures on the management body. Regulation 2024/2690 asks for the approval date to appear in the policy.
- People acknowledge it. The same Regulation asks that the policy be "communicated to and acknowledged by" employees and relevant outside parties. Keep a record of who read which version.
- Review at least once a year. That is the binding interval for the digital providers under Regulation 2024/2690. Also review after a significant incident or change. A yearly review is also a sensible rhythm for other organisations.
- Inform management yearly. In Sweden, management must be informed about how the measures are going when needed, and at least once a year (MCFFS 2026:11, 3 kap. 4 § point 5).
- Link it to the management system. A policy is one part of a larger system. See What is an ISMS? The ISO 27001 route is in ISO 27001 certification.
8. How SimpleSecurity helps
SimpleSecurity does not make an organisation compliant by itself. It keeps the records around your policy. You write and own the policy.
| Duty | Service |
|---|---|
| Keep each policy with a lifecycle and review date | Policy Register: policy lifecycle tracking, review SLAs, central document register |
| Show who read which version | People & Awareness: policy acknowledgment tied to the approved version, timestamped per person |
| Draft policy text to review and edit | Aegis Intelligence: writes policies, you review, edit and save |
| Map policies to controls in a framework | Compliance: 22 frameworks, including ISO 27001, GDPR and NIS2/Cybersäkerhetslagen |
| Track the risks the policy refers to | Risk Register |
See every service or see the plans.
Related guides
9. Sources
- Directive (EU) 2022/2555 (NIS2), Articles 20 and 21
- Implementing Regulation (EU) 2024/2690, Articles 1 and 2, Annex points 1.1 and 1.2
- Regulation (EU) 2016/679 (GDPR), Article 24
- MCFFS 2026:11, 1 kap. 1 § and 3 kap. 1–5 §§, in force 1 October 2026