Information security roles and responsibilities
Who owns information security, privacy, continuity and AI decisions, with the authority each role carries and the committee that hears them.
How the register reads it
| Also called | RACI, security organisation, terms of reference |
|---|---|
| Family | Governance and the management system |
| Document type | Record. 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. |
| Folds into | The regimes accept it folded into the information security policy; when neither is listed, the gap is counted once, under the parent. |
| Expected owner | The information security lead (CISO or ISMS manager). |
| Review cadence | Annual (the register's default: the clauses say planned intervals and on significant change, and do not fix a period). |
| On the gap list when | ISO 27001 or ISO 27701 or ISO 42001 or ISO 22301 or DORA is ticked and no line resolves to it or to its parent. |
| Template | No template yet. The clauses below say what the document is expected to contain. |
Which standards require it, and what each expects it to contain
6 requiring clauses, 5 regimesShown 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.3named Organizational roles, responsibilities and authorities.
ISO 27001 5.2 Information security roles and responsibilitiesName who owns what in security and make the allocation explicit and traceable.
What the ISO 27002 guidance expects the document to say: Requires information security roles and responsibilities to be defined and allocated in line with what the organisation actually needs, so ownership of each security duty is explicit rather than assumed.
Common gap: Roles not updated after staff changes
Source: ISO/IEC 27001:2022; guidance ISO/IEC 27002:2022
ISO/IEC 27701:2025
ISO 27701 5.3 Roles, responsibilities and authoritiesTop management shall ensure that the responsibilities and authorities for roles relevant to the privacy information management system are assigned and communicated within the organization. Top management shall assign the responsibility and authority for ensuring that the PIMS conforms to the requirements of this document, and for reporting on the performance of the PIMS to top management. Roles that jurisdictions can require, such as a data protection officer, and the point of contact for PII principals and for customers are addressed by the controls in Annex A (A.3.4).
Common gap: Responsibilities assigned but never communicated
Source: ISO/IEC 27701:2025
ISO/IEC 42001:2023
ISO 42001 A.3.2 AI roles and responsibilitiesRoles and responsibilities for AI shall be defined and allocated according to the organization's needs.
Common gap: Are AI-specific roles defined or rolled into existing IT roles?
Source: ISO/IEC 42001:2023
ISO 22301:2019
ISO 22301 5.3 Roles, responsibilities and authoritiesTop management must assign and communicate the responsibilities and authorities for the roles the BCMS depends on, and must specifically assign responsibility and authority for ensuring the BCMS conforms to the standard and for reporting BCMS performance back to top management.
Common gap: Roles assigned in a matrix that the holders have never seen
Source: ISO 22301:2019
DORA (Regulation (EU) 2022/2554)
DORA Art. 5 Governance and organisationThe 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.
Common gap: Board approves the framework once and never revisits plans, audit plans or the third-party policy
Source: DORA (Regulation (EU) 2022/2554)
Customizable template
12 sections, 6 cited to requiring clausesWith 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.
- Purpose
- Scope
- Roles and responsibilities
- Information security roles and responsibilities ISO 27001 A.5.2
- Organizational roles, responsibilities and authorities ISO 27001 clause 5.3 (named)
- Roles, responsibilities and authorities ISO 27701 5.3
- AI roles and responsibilities ISO 42001 A.3.2
- Roles, responsibilities and authorities ISO 22301 5.3
- Governance and organisation DORA Art. 5
- Exceptions
- Related documents
- Review and approval
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 registerInformation security policy · Internal audit charter and programme