Policy Register

Information security policy

The top-level statement of intent and direction that every topic-specific document below it derives its authority from.

How the register reads it

Also calledISMS policy, security policy, cyber security policy, IS policy
FamilyGovernance and the management system
Document typePolicy. The regimes ask for the content, not the label; a line pasted as a standard, procedure, plan or schedule is placed here with the label noted.
Expected ownerTop management (the board or the CEO), with the information security lead drafting.
Review cadenceAnnual (the register's default: the clauses say planned intervals and on significant change, and do not fix a period).
On the gap list whenISO 27001 or DORA or NIS2 is ticked and no line resolves to it (ISO 27701 requires it too, inside a parent document, so it does not list it separately).
TemplateInformation security policy.

Which standards require it, and what each expects it to contain

6 requiring clauses, 4 regimes

Shown on a register for the regimes you tick; with none ticked, ISO 27001 is applied. Requirement text is our own statement of each clause, read from the published text and cited so you can check it against the official text; it is not the instrument verbatim. A clause marked named is one of ISO/IEC 27001:2022's management clauses (4 to 10), named with its title and not quoted here.

ISO/IEC 27001:2022

Named, not quoted: 5.2named Policy.

ISO 27001 5.1 Policies for information security

Write, approve and publish a top-level security policy plus topic-specific policies, and review them on a set cadence and after major change.

What the ISO 27002 guidance expects the document to say: Requires an information security policy together with supporting topic specific policies. These must be defined, approved by management, published, communicated to and acknowledged by relevant personnel and relevant interested parties, and reviewed on a planned cycle and whenever significant change occurs.

Evidence an auditor accepts: The approved information security policy, showing the approving authority and the date of approval; the set of topic specific policies beneath it, such as access control, cryptography, backup, acceptable use and supplier security, each with an owner; evidence of publication and of communication to personnel and to relevant interested parties, such as intranet publication records or distribution lists
Common gap: Policies not formally approved by senior management
Source: ISO/IEC 27001:2022; guidance ISO/IEC 27002:2022

ISO/IEC 27701:2025

ISO 27701 5.2 Privacy policy

Top management shall establish a privacy policy that is appropriate to the purpose of the organization, provides a framework for setting privacy objectives, includes a commitment to satisfy applicable requirements related to the processing of PII, and includes a commitment to continual improvement of the privacy information management system. The policy shall be available as documented information, be communicated within the organization, and be available to interested parties as appropriate. The transition documents record that a written privacy policy is now a mandatory standalone requirement rather than an augmentation of the information security policy.

Evidence an auditor accepts: Approved privacy policy carrying each required element; communication records within the organization; evidence the policy is available to interested parties, for example published or provided to customers
Common gap: A privacy notice to individuals presented as the management system policy
Source: ISO/IEC 27701:2025

DORA (Regulation (EU) 2022/2554)

DORA Art. 5 Governance and organisation

The management body defines, approves and oversees the ICT risk management framework and carries final accountability for ICT risk: it sets ICT roles and governance, approves the digital operational resilience strategy and ICT risk tolerance, approves and reviews the continuity and response plans, the ICT internal audit plans and the ICT third-party policy, allocates budget for resilience, awareness and skills, and receives reporting on third-party arrangements and major incidents. Its members keep their own ICT risk knowledge current through regular training. Entities other than microenterprises must also set up a role to monitor ICT third-party arrangements, or name a senior manager accountable for that exposure (Art. 5(3)). Applied in proportion to size, risk profile and complexity under Article 4(1). Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.

Evidence an auditor accepts: Management body minutes approving the ICT risk management framework, the digital operational resilience strategy and the ICT risk tolerance; board-approved ICT third-party policy, ICT internal audit plan and ICT budget, each with its review date; training records for each management body member on ICT risk
Common gap: Board approves the framework once and never revisits plans, audit plans or the third-party policy
Source: DORA (Regulation (EU) 2022/2554)
DORA Art. 9 Protection and prevention

Financial entities keep the security and operation of ICT systems and tools under continuous monitoring and control and limit ICT risk with security policies, procedures, protocols and tooling designed to keep ICT systems (above all those supporting critical or important functions) resilient and available, and protect data at rest, in use and in transit. The chosen solutions must be appropriate under Article 4 and cover secure data transfer, data loss and corruption, unauthorised access and data management risk. Within the ICT risk management framework they keep an information security policy (covering customer data where applicable), a risk-based network and infrastructure management structure that can cut or segment connections at once, least-privilege access controls, strong authentication and cryptographic key protection, a risk-based ICT change management process approved by management, and documented patch and update policies. Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.

Evidence an auditor accepts: Information security policy, including its scope for customer data where the entity holds such data; network architecture and segmentation records showing connections can be severed or isolated quickly; access rights reviews, authentication standards and cryptographic key management procedures
Common gap: Network cannot be segmented quickly to contain an attack
Source: DORA (Regulation (EU) 2022/2554)

The NIS2 Directive

NIS2 Art. 21(2)(a) Policies on risk analysis and on information system security

The first of the ten minimum measure categories requires both a method for analysing risk and the security policy set that the analysis feeds. Risk analysis has to be an actual repeatable method with criteria for assessing and accepting risk, applied to the network and information systems the entity relies on for its operations and for delivering its services, with results that are recorded and revisited. The information system security policies are the codified decisions that follow: what is protected, to what level, who owns each decision, and what happens when the policy cannot be met. Both limbs are needed. A risk register with no policy leaves nothing binding on the organisation, and a policy library with no risk analysis behind it cannot show why it says what it says.

Evidence an auditor accepts: The documented risk analysis method, including risk criteria and acceptance thresholds; the current risk assessment output covering the in-scope network and information systems; the approved information system security policy set, with owners and review dates
Common gap: Risk register maintained as a list of findings with no method or acceptance criteria behind it
Source: NIS2 Directive

Also governs

ISO 27001 controls this document is expected to set the rules for, beside the ones that require it: ISO 27001 5.36.

Customizable template

13 sections, 6 cited to requiring clauses

With every regime ticked. Each clause section carries our statement of the clause, guidance beside it and starter wording to adapt; enter your organisation once, edit any section, export to Word, print or text. Every template is a draft to adapt and approve.

  1. Purpose
  2. Scope
  3. Roles and responsibilities
  4. Policies for information security ISO 27001 A.5.1
  5. Policy ISO 27001 clause 5.2 (named)
  6. Privacy policy ISO 27701 5.2
  7. Governance and organisation DORA Art. 5
  8. Protection and prevention DORA Art. 9
  9. Policies on risk analysis and on information system security NIS2 Art. 21(2)(a)
  10. Compliance with policies, rules and standards for information security ISO 27001 A.5.36
  11. Exceptions
  12. Related documents
  13. Review and approval

Customise this template The template document on the compliance platform

Do this for every document on your list

Paste the list and get this reading for every document at once, with the owner and cadence against each, the clauses quoted, and the documents the regimes expect that the list does not carry. Eight documents free, no account.

Build a register

Document control procedure · Information security roles and responsibilities