Policy Register

Risk management policy

How risks to information, systems, personal data and AI systems are identified, scored, treated and accepted, and by whom.

How the register reads it

Also calledrisk methodology, ICT risk management framework, ERM 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 ownerThe information security lead (CISO or ISMS manager).
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 ISO 27701 or DORA or NIS2 is ticked and no line resolves to it (ISO 22301 requires it too, inside a parent document, so it does not list it separately).
TemplateRisk management policy.

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

7 requiring clauses, 5 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: 6.1.2named Information security risk assessment; 6.1.3named Information security risk treatment.

ISO/IEC 27701:2025

ISO 27701 6.1.2 Privacy risk assessment

The organization shall define and apply a privacy risk assessment process that establishes and maintains privacy risk criteria, including risk acceptance criteria and criteria for performing assessments; ensures that repeated assessments produce consistent, valid and comparable results; identifies the privacy risks associated with the processing of PII within the scope of the PIMS, both risks to the organization and risks to PII principals, and identifies the risk owners; analyses the risks by assessing the potential consequences and the realistic likelihood of their occurrence and determining the levels of risk; and evaluates the risks by comparing the results against the criteria and prioritising them for treatment. Where the organization also runs an information security risk assessment, the relationship between information security and the protection of PII shall be managed throughout. The organization shall retain documented information about the process. The first edition's dual assessment, information security risk plus privacy risk inside an ISMS, becomes a privacy risk assessment in its own right; the transition documents note the guidance draws on ISO/IEC 27557.

Evidence an auditor accepts: Privacy risk assessment methodology with criteria, acceptance levels and assessment triggers; risk register identifying risks to PII principals separately from risks to the organization, with owners; analysis showing consequence, likelihood and level per risk
Common gap: Risk register that holds security risks only, with no risk to individuals recorded
Source: ISO/IEC 27701:2025
ISO 27701 6.1.3 Privacy risk treatment

The organization shall define and apply a privacy risk treatment process that selects appropriate treatment options taking account of the assessment results; determines all controls necessary to implement the options; compares the determined controls with those in Annex A to verify that no necessary controls have been omitted, Annex A being a reference list of possible controls that the organization can add to; identifies and documents the information security programme that protects PII, which the transition documents record as required to address a stated set of areas and which may but need not follow ISO/IEC 27002; produces a Statement of Applicability that contains the necessary controls, the justification for their inclusion, whether they are implemented and the justification for excluding any Annex A control; formulates a privacy risk treatment plan; and obtains the risk owners' approval of the plan and their acceptance of the residual privacy risks. Documented information about the process shall be retained. In the first edition the comparison ran against ISO/IEC 27001:2013 Annex A and the two PIMS annexes; in this edition it runs against Annex A of this document alone.

Evidence an auditor accepts: Risk treatment plan with options, controls, owners and dates; statement of Applicability listing every Annex A control with inclusion or exclusion justification and implementation status; documented information security programme covering the areas the standard names
Common gap: Statement of Applicability copied from an ISO/IEC 27001 SoA with the 2019 annexes bolted on
Source: ISO/IEC 27701:2025

ISO 22301:2019

ISO 22301 8.2.3 Risk assessment

Implement and maintain a risk assessment process that identifies the risks of disruption to the organization's prioritized activities and the resources they require, analyses and evaluates those risks, and determines which of them require treatment.

Evidence an auditor accepts: Documented risk assessment process; risk register scoped to prioritized activities and their required resources; analysis and evaluation records with the criteria applied
Common gap: Risk register covering the enterprise generally rather than the prioritized activities specifically
Source: ISO 22301:2019

DORA (Regulation (EU) 2022/2554)

DORA Art. 6 ICT risk management framework

Financial entities keep a sound, comprehensive and documented ICT risk management framework within their overall risk management system, covering the strategies, policies, procedures, protocols and tools that protect information and ICT assets and physical infrastructure, and including a digital operational resilience strategy (risk tolerance, security objectives, reference architecture, detection, testing and incident communication). The framework is reviewed yearly as a minimum (a microenterprise may instead set its own periodic cycle), and also after major ICT-related incidents and after supervisory instructions or test and audit conclusions, with a review report available to the competent authority on request (Art. 6(5)). Entities other than microenterprises assign ICT risk to an independent control function (Art. 6(4)) and subject the framework to regular internal audit by auditors with ICT expertise and independence, followed by a formal process to remediate critical findings (Art. 6(6) and (7)); microenterprises are outside the internal-audit duty. 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: Current ICT risk management framework document with version history showing the yearly review (or the periodic review cycle a microenterprise has set); review records triggered by major ICT-related incidents, supervisory instructions or test and audit conclusions, and any review report sent to the authority on request; mandate of the independent ICT risk control function (entities other than microenterprises)
Common gap: Framework reviewed only on the calendar cycle, not after a major ICT-related incident
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

Customizable template

13 sections, 7 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. Information security risk assessment ISO 27001 clause 6.1.2 (named)
  5. Information security risk treatment ISO 27001 clause 6.1.3 (named)
  6. Privacy risk assessment ISO 27701 6.1.2
  7. Privacy risk treatment ISO 27701 6.1.3
  8. Risk assessment ISO 22301 8.2.3
  9. ICT risk management framework DORA Art. 6
  10. Policies on risk analysis and on information system security NIS2 Art. 21(2)(a)
  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

Nonconformity and corrective action procedure · Acceptable use policy