In an audit, someone asks “Who is responsible for this control?” and three people give three different answers. That picture shows the role definitions in the ISMS have stayed on paper. A RACI matrix shows in a single table, for every ISMS activity, who does the work, who is accountable, who is consulted and who is informed. Below we cover, as they look in practice, meeting the role requirements of ISO/IEC 27001:2022 with RACI, a sample matrix, the segregation of duties problem in small teams and how to show outsourced roles.
Role, responsibility and authority requirements
ISO/IEC 27001:2022 clause 5.3 requires top management to assign and communicate within the organization the responsibilities and authorities for roles relevant to information security. The clause specifically names two assignments: ensuring the ISMS conforms to the standard, and reporting ISMS performance to top management. Annex A 5.2 covers defining and allocating roles and responsibilities according to the organization’s needs, 5.3 segregating conflicting duties and areas of responsibility, and 5.4 management requiring personnel to comply with policies.
The auditor usually tests these requirements with three questions: Are the roles written down? Do the people assigned know their roles? Has the authority the role requires actually been granted in the systems? A RACI matrix answers only the first question. For the second and third, the matrix has to be reflected in job descriptions, appointment letters and system permissions. The table alone isn’t evidence.
Rules of the RACI model
RACI consists of four letters. When the letters aren’t read the same way by everyone, the matrix increases confusion instead of reducing it. Put a short explanation at the top of the matrix:
| Letter | Meaning | Rule |
|---|---|---|
| R – Responsible | Does the work | At least one R on every row |
| A – Accountable | Answers for the result, approves | Exactly one A on every row |
| C – Consulted | Whose opinion is sought (two-way) | Keep the number limited |
| I – Informed | Kept informed of the result (one-way) | The notification channel must be defined |
Additional rules that work in practice:
- The single-A rule: A row with two As means nobody answers at the moment of decision. If a joint decision is needed, A is a committee and the committee’s decision record is defined.
- A and R can be the same person; however, for control-type activities such as approval and review, this is assessed separately from a segregation of duties perspective.
- Rows must be activities: Write measurable statements containing a verb, such as “Approve a privileged account request”, not “Access control”.
- Columns must be roles: Use titles or role names, not people’s names; names are kept in a separate assignment list.
- Too many Cs means slow decisions: Don’t seek everyone’s opinion on every activity; make C only the roles whose knowledge is really needed.
Sample ISMS RACI matrix
The matrix below is a starting draft for a mid-sized organization. The rows cover the standard’s clause structure and frequently audited Annex A controls; add and remove rows to fit your own processes. Column abbreviations: TM (top management), ISM (ISMS manager), IT (IT manager), HR, PO (process/asset owner).
| Activity | TM | ISM | IT | HR / PO |
|---|---|---|---|---|
| Approve the information security policy | A | R | C | HR: I, PO: I |
| Carry out the risk assessment | I | A | R | PO: R |
| Accept the risk treatment plan and residual risk | A | R | C | PO: C |
| Approve an access request from a business perspective | – | I | R | PO: A |
| Periodic access review | I | A | R | PO: R |
| Account operations on joining and leaving | – | I | R | HR: A |
| Awareness training program | I | A | C | HR: R |
| Responding to an information security incident | I | A | R | PO: C |
| Internal audit program | A | C | I | Internal auditor: R |
| Management review | A | R | C | PO: C |
Write the reasoning for some choices under the matrix; the auditor will ask. A sitting with the process owner for access approval shows permissions are granted according to business need. IT only implements. A sitting with HR for joining and leaving reflects that the triggering event is the HR record and that IT can’t act without notification. A gap you may come across is exactly here: HR doesn’t report the departure, the account stays active for months, the VPN connection stays open. The ISMS manager being C rather than R for the internal audit is a deliberate choice for the impartiality clause 9.2 requires. Nobody audits a process they built themselves.
Segregation of duties in small organizations
Annex A 5.3 requires conflicting duties to be segregated. In an organization with a one-person IT team, however, the person requesting, granting and reviewing permissions is often the same. The standard doesn’t expect the impossible here; it expects the conflict to be identified and the risk reduced with compensating controls. This assessment is explained in the risk register and, if needed, in the Statement of Applicability.
Common conflicts and ways to compensate:
| Conflict | Compensating control |
|---|---|
| The IT manager both grants and reviews permissions | Process owners sign off the review; the list is pulled directly from the system |
| Administrator accounts are held by the same person who also reviews the logs | Logs are sent to a central environment the person can’t delete from; the summary report is reviewed by top management or an outside party |
| The same person makes and approves a change | A pre-approved list of standard changes; manager approval and after-the-fact checks for the rest |
| The ISMS manager is also the IT manager | Internal audit carried out by an outside provider or another unit |
A compensating control also needs an owner and evidence. The sentence “Top management reviews the logs” isn’t a control on its own. It must state how often the review is done, from which report, and where the signed record is kept. A method that works in practice: a few critical events, such as Domain Admins group membership changes and event log clearing records, come out of the central log environment as a monthly report, which the manager signs and archives. How this kind of separation is designed at enterprise scale is also touched on in the three lines of defense model guide.
Showing outsourced and supplier roles
If there’s a managed service provider, an outsourced information security manager or a cloud service, and the matrix consists only of internal roles, the table doesn’t reflect reality. Add external parties as separate columns and follow this principle: R can be external, A stays inside the organization. The service provider runs backup operations (R); the IT manager is the one who accepts the restore test result (A).
For outsourced columns to be reflected correctly in the matrix:
- For each external role, refer to the relevant contract or service level agreement; the R in the RACI must not contradict the contract scope.
- Explicitly assign to internal roles the activities the external party can’t decide on behalf of the organization (risk acceptance, policy approval).
- For cloud services, reflect the shared responsibility model at row level: the provider applies infrastructure patches, user and access management stays with the organization.
A situation you may come across is the contract saying “backup” while restore testing isn’t assigned to any party. Read the contract and the matrix side by side. Which outputs to take delivery of when working with an outsourced ISMS manager is explained in the article outsourced ISMS consulting deliverables. For how the role can be set up, see the outsourced information security officer (vCISO) page.
Reflecting the matrix in job descriptions and records
A RACI on its own is a draft. Without records showing the assignment happened, its evidential value in an audit is limited. To make the matrix work:
- Assignment list: Keep a separate list showing the current holder and deputy of each role, with name, title and start date.
- Job descriptions: Add the relevant R and A rows to HR job descriptions; prove they were communicated with the employee’s signature or electronic acknowledgment.
- Top management approval: Have top management approve the matrix itself; that’s the evidence of the assignment in clause 5.3.
- Comparison with system permissions: Check that the person who is A in the matrix is actually defined as an approver in the approval workflow. Looking at the approval group in the service desk tool is enough.
- Document control: Manage the matrix with a version number and review date; let organizational changes trigger an update. For the version and approval flow, see the document control guide.
There’s a simple way to measure the matrix’s accuracy. Pick three rows at random and ask the person in the A column for the latest record of that activity. If the record is found within a few minutes, the matrix works. If the person doesn’t know about their role, the problem isn’t the table but the communication. To set up the role distribution together with the policy and procedure set, the information security policy and procedure package offers a starting framework.
Frequently asked questions
Is a RACI matrix mandatory in ISO 27001?
No. The standard requires roles, responsibilities and authorities to be assigned and communicated; it doesn’t set the format. RACI is one of the practical ways of showing this requirement in a single, auditable table.
Can an activity have more than one A?
It shouldn’t. Two accountable parties blur responsibility at the moment of decision. If a joint decision is needed, a committee or board is written as A, and how the decision record is kept is defined.
How is segregation of duties achieved in small companies?
If full separation isn’t possible, the conflict is written into the risk register and compensating controls are defined: independent log retention, access reviews by business unit managers, periodic review by top management, or outsourcing the internal audit, for example.
Can an outsourced service provider be A in the RACI?
The provider carrying out operational work can be R. For activities requiring accountability, such as risk acceptance, policy approval and acceptance of results, A must stay with a role inside the organization.