Information security policy: what to include, a template outline and NIS2
An information security policy is the top-level document in which management states how the company protects its information and systems, who is responsible, and which rules apply to everyone. A good information security policy is short, specific to the company, approved by management and backed by a few topic policies and procedures people actually use. This guide covers what the policy must contain, the topic policies NIS2 names, how risk assessment fits in, a template outline, and how to make the policy part of daily work rather than a document in a folder.
Legal texts were read on 12 November 2026: Directive (EU) 2022/2555 (NIS2) and Regulation (EU) 2016/679 (GDPR). We also refer to the NIST Cybersecurity Framework 2.0, published by NIST on 26 February 2024. This guide is general information, not legal advice.
What the policy is for
A policy does three jobs. It sets direction: what the company wants to protect and how much risk it accepts. It assigns responsibility: who owns security, who approves exceptions, who each employee goes to with a problem. And it gives evidence: to customers, auditors, insurers and supervisory authorities that security is managed, not improvised. The policy itself does not make systems secure. The measures it requires do: access control, backups, updates, training, incident handling.
Policies sit at the top of a short hierarchy. The information security policy states principles. Topic policies set rules for one area, for example access control or backups. Procedures and runbooks explain how to carry out the rules step by step. Keeping the levels separate keeps the top document stable while the details change.
Is it a legal requirement?
NIS2 requires Member States to ensure that essential and important entities take appropriate and proportionate technical, operational and organisational measures to manage risks to their network and information systems (Article 21(1)). The list of minimum measures in Article 21(2) begins with "policies on risk analysis and information system security". Article 20(1) requires the management bodies of those entities to approve the cybersecurity risk-management measures, oversee their implementation, and makes them liable for infringements. Our NIS2 compliance guide explains who is in scope.
The GDPR applies to almost every company. Article 24(2) states that, where proportionate in relation to processing activities, the controller's measures shall include the implementation of appropriate data protection policies, and Article 32 requires security appropriate to the risk. An information security policy that covers personal data is the natural place to meet both.
The topic policies NIS2 lists
Article 21(2) NIS2 lists the minimum measures. Each translates naturally into a section of the main policy or a short topic policy:
| NIS2 Article 21(2) | Topic policy or section |
|---|---|
| (a) Risk analysis and information system security | The information security policy itself, plus the risk assessment method |
| (b) Incident handling | Incident response plan |
| (c) Business continuity, backup management, disaster recovery, crisis management | Business continuity plan and backup strategy |
| (d) Supply chain security | Supplier security policy and contract requirements |
| (e) Security in acquisition, development and maintenance, including vulnerability handling | Secure development and patch management policy |
| (f) Assessing the effectiveness of measures | Internal audit, testing and review plan |
| (g) Basic cyber hygiene and training | Acceptable use policy and training plan |
| (h) Cryptography and encryption | Cryptography policy |
| (i) Human resources security, access control, asset management | Access control policy and asset register |
| (j) Multi-factor authentication, secured communications | Authentication and communication rules |
For digital infrastructure and certain digital service providers, such as cloud, data centre and managed service providers, Article 21(5) required the Commission to adopt implementing acts with technical and methodological requirements for these measures, which go into more detail.
Risk assessment comes first
A policy written without a risk assessment is generic, and generic policies are ignored. Before writing, list the information and systems that matter (customer data, financial systems, production control, the website that sells), what could go wrong with each (theft, ransomware, outage, error, supplier failure), how likely and how harmful each scenario is, and what is already in place. The policy then sets priorities where the risk is highest. The NIST Cybersecurity Framework 2.0 is a useful free reference: it offers a taxonomy of high-level cybersecurity outcomes for organisations of any size and, by design, does not prescribe how the outcomes should be achieved.
An information security policy template outline
- Purpose: why the policy exists and what it protects, in three sentences.
- Scope: which companies, locations, systems, data and people it covers, including contractors and suppliers with access.
- Goals and risk appetite: confidentiality, integrity and availability goals for the most important information, and which risks management accepts.
- Roles and responsibilities: management approval, a named security owner, system owners, every employee's duties, the data protection officer if there is one.
- Risk management: how risks are assessed, how often, who decides on treatment.
- Core rules: short principles per area (access, devices, passwords and multi-factor authentication, email and phishing, data classification, encryption, backups, updates, suppliers, remote work).
- Topic policies: a list of the supporting documents, each with an owner.
- Incidents: how to report one, to whom, and the duty to report even when unsure.
- Legal and contractual requirements: GDPR, NIS2 where applicable, sector rules, customer contracts.
- Training and awareness: what everyone learns at onboarding and each year.
- Exceptions and consequences: how to request an exception, and what happens on breach of the policy.
- Review: owner, approver, version, date, next review date.
A starting point for small companies
A company of ten to fifty people does not need a library of documents. It needs a two to four page policy, an access control policy, a backup and recovery section, an incident reporting rule and an asset list, plus the measures behind them: multi-factor authentication everywhere, devices managed and encrypted, updates automatic, backups with an offline or immutable copy and a tested restore, admin rights limited. Those measures are the foundation everything else builds on. Add documents only when a real need appears, such as a customer audit or NIS2 scope.
Writing it so people follow it
Policies fail when they read like legal text. Write in short sentences, in the language your staff use at work, with the rule first and the reason second: "Use multi-factor login on every work account, because a stolen password alone should never be enough to get in." Give examples for the grey areas people actually meet, such as using a personal phone for work email or sharing a file with a customer. Say who to ask. And keep the policy consistent with what systems enforce: a rule that the tools make impossible to follow will be ignored, and then the whole document loses credibility.
Keeping the policy alive
- Put it where people work: the intranet, onboarding checklists, the ticket system, not a shared drive folder.
- Measure a few things: multi-factor coverage, patch delay, restore test results, training completion, open access reviews.
- Review after incidents: every incident or near miss is a test of the policy; update it with what was learned.
- Review yearly with management, and record the approval.
- Build the rules into systems: roles in the software, enforced multi-factor login, automatic updates, so following the policy is the default.
How we help
We help companies turn a policy into working measures. A security audit checks the current state against the policy and NIS2 and ends in a prioritised fix list. Our managed IT security services run the measures every day: devices, accounts, updates, backups and monitoring. In the software we build, access control, logging, encryption and backups are designed in, hosted in EU regions, and documented in a form your auditors can use.
Questions people ask
What is an information security policy?
An information security policy is a document approved by management that states how the company protects its information and systems: the goals, the scope, who is responsible for what, and the rules everyone must follow. It is usually supported by shorter topic policies, such as access control, backups and acceptable use, and by procedures that explain how each rule is carried out.
Is an information security policy required by law?
For essential and important entities under NIS2, yes: Article 21 requires policies on risk analysis and information system security, and management bodies must approve the measures. Under the GDPR, controllers must implement appropriate data protection policies where proportionate. For other companies it is not a general legal duty, but customers, insurers and auditors routinely ask for one.
How long should an information security policy be?
The top-level policy should be short, often two to five pages, so that people actually read it. Detail belongs in topic policies and procedures that the relevant teams use. A long policy nobody reads protects nothing.
What is the difference between an information security policy and ISO 27001?
ISO/IEC 27001 is an international standard for an information security management system, against which a company can be certified. An information security policy is one document that such a system requires. A company can have a good policy without certification; certification needs much more than the policy.
How often should the policy be reviewed?
At least once a year, and after any significant change: a new system, a new supplier for critical services, a security incident, new legal requirements. The review date and the approver should be written in the document itself.
Sources
- Directive (EU) 2022/2555 (NIS2), Articles 20 and 21 (read 12 November 2026)
- Regulation (EU) 2016/679 (GDPR), Articles 24 and 32 (read 12 November 2026)
- NIST, The NIST Cybersecurity Framework (CSF) 2.0, CSWP 29, published 26 February 2024 (read 12 November 2026)