Ir al contenido
Implementación
11 min de lectura

ISO 27001 RACI Matrix: Roles, Template and Audit Tips

support@ismscalculator.com|

Colleagues reviewing an ISO 27001 responsibility matrix

An ISO 27001 RACI matrix is a simple table that maps every ISMS activity to the people who are Responsible, Accountable, Consulted and Informed. The standard does not demand one by name. It does require that security roles, responsibilities and authorities are assigned and communicated, and a RACI matrix is the cleanest way to prove you did that. Below you will find what to put in it, a worked example, how to size it for a 15-person startup versus a 250-person company, and the evidence auditors ask for.

Ismscalculator
Estimate Your ISO 27001 Effort
Explore tailored implementation estimates and model reference comparisons to help connect ISMS responsibilities with the resources your plan may require.
Visit

TL;DR

  • ISO 27001 does not mandate a RACI matrix, but Clause 5.3 and Annex A 5.2 require assigned and communicated roles. A matrix is the standard audit-ready way to show it.
  • Give every row exactly one Accountable role. Shared accountability means nobody can make the final call.
  • Assign roles to job titles, not names, so the matrix survives staff changes.
  • Cover both the implementation project and ongoing operations, such as access reviews, incidents, internal audit and management review.
  • Keep proof that people know their roles: approvals, communications, acknowledgments and review records.

Table of Contents

What RACI means in an ISMS

RACI is a responsibility-assignment format. For each task, you mark who plays which part:

  • Responsible ®: does the work.
  • Accountable (A): answers for the result, owns the decision and can delegate the work.
  • Consulted ©: gives input before a decision, in a two-way exchange.
  • Informed (I): receives updates after the fact, one way.

The point is not the letters. It is that when something goes wrong, or an auditor asks who approves access to production, the answer is already written down and agreed.

Is a RACI matrix required by ISO 27001?

No. The standard never uses the word. What it does require is in Clause 5.3: top management must ensure that responsibilities and authorities for information security roles are assigned and communicated, including who ensures the ISMS conforms to the standard and who reports its performance to top management. The text of Clause 5.3 is short, which is why teams reach for a matrix to make it concrete.

Annex A control 5.2 goes one level down: information security roles and responsibilities must be defined and allocated. Together, the clause and the control say what the outcome must be. They leave the format to you. A RACI matrix wins because auditors read it fast, and it exposes gaps that a paragraph of prose hides.

If you want a fuller view of how roles show up in audit findings, see our guide to ISO 27001 roles for implementers.

Is a RACI matrix required by ISO 27001?

Which roles belong in the matrix

The column headers should be positions, not people. A short list that fits most organizations:

  • Top management (CEO, managing director, or the executive team)
  • Information Security Manager or CISO
  • Risk owner (the business leader accountable for a given risk)
  • Asset owner (owns a system, dataset or process)
  • IT or security operations lead
  • HR lead
  • Internal auditor (independent of the work being audited)
  • Department heads or process owners

Some ISMS roles show up in nearly every organization regardless of size: top management, the security manager, risk owners and asset owners, plus someone who owns each security measure. Add a data protection officer, security architect or audit manager when your size and sector call for it.

Sizing the matrix to your company

Small teams combine roles. In a 15-person company, one person can easily fill three columns. In a 250-person company, each column is usually a different person or team. Both are fine, as long as the combination does not break independence. Nobody should audit their own work, and nobody should approve their own privileged access.

When you must combine roles, add a compensating control. Mandatory peer review of changes is the common one. Write it next to the row, so the auditor sees you considered the conflict rather than missed it.

Sizing the matrix to your company

Competence matters too. Whoever is marked Responsible needs the training and skills to do the task. If a role is assigned to someone who has never run a risk assessment, schedule training and record it.

How to build the matrix in six steps

  1. List the activities. Start from the ISMS lifecycle, then add operational tasks. Be specific: “approve the risk treatment plan” beats “risk management.”
  2. List the roles. Use titles. If one person holds two titles today, keep two columns anyway and note the holder in a separate roster.
  3. Assign one A per row. Start here, before R, C and I. If you cannot name a single owner, the decision has no owner.
  4. Assign R. The doer is often not the A. A risk owner is accountable for a risk decision, while the security manager does the analysis.
  5. Add C and I sparingly. If everyone is Consulted on everything, nothing moves. Consult only people whose input changes the outcome.
  6. Get top management approval and communicate it. An unapproved matrix is a draft, not evidence for Clause 5.3.

A worked example for the implementation phase

Here is a trimmed matrix you can adapt. Top management is typically Accountable at the start and end of a project, and process owners can be made Accountable for control implementation so the results matter to them as much as to the project team.

Activity Top mgmt Security manager Risk owner IT lead HR lead Internal auditor
Define ISMS scope and policy A R C C C I
Approve risk assessment method A R C C I I
Perform risk assessment I R A C C I
Approve risk treatment plan A R R C I I
Implement technical controls I C I A/R I I
Run security awareness training I A I C R I
Operate access reviews I C I A/R I I
Investigate incidents I A C R C I
Conduct internal audit I C I I I A/R
Hold management review A R C C C C
Address nonconformities I A C R C I

Note the “A/R” cells. One role is both accountable and doing the work, which is common in small teams. There is still exactly one A per row. Your own sizing will change the details, so treat this as a starting point.

What the matrix should cover

Two layers belong in the same document.

Implementation activities run once or per cycle: identifying interested parties and requirements, defining the ISMS framework, setting the risk methodology, performing the risk assessment, implementing controls, training, monitoring, internal audit, management review and corrective action.

Ongoing operations repeat all year: access management, change management, incident detection through lessons learned, supplier review and awareness refreshers.

For Annex A, avoid creating 93 separate rows unless you need them. Group by theme (organizational, people, physical, technological) and then break out the controls where ownership differs. Link each row to a real workflow or procedure, so what the matrix says matches what happens. For a deeper look at how responsibility splits when you rely on cloud and service providers, read our piece on ISO 27001 shared responsibility.

Keeping the matrix alive

A matrix that was right at certification and wrong a year later is a classic finding. Common failure modes are roles that exist only in someone’s head and a matrix naming people who have left. Prevent both:

  • Use titles. Keep a separate roster of who holds each role, with a deputy and a start date.
  • Publish it where staff look. An internal wiki or onboarding document works better than a PDF buried in a policy folder.
  • Review on triggers. Re-check after reorganizations, new tools, acquisitions, and at least in each management review.
  • Test it with scenarios. Pick a recent incident or access request and trace who actually did what. If reality differs from the matrix, fix one of them.
  • Version it. Track changes and approvals so you can show how the matrix evolved. The same logic applies to any system where you must show who changed a role or permission, as in audit logging for SaaS role changes.

Management review is the natural place to confirm the matrix. Record actual discussion and decisions, not a generic summary. Our management review agenda maps Clause 9.3 inputs to the evidence you will want.

Evidence that roles are assigned and understood

Auditors check more than whether the document exists. They want to see that people know their duties. Typical requests, drawn from A.5.2 audit guidance:

  • The roles and responsibilities matrix or RACI chart
  • Job descriptions that include security responsibilities
  • An organization chart showing security governance
  • Terms of reference for the security steering committee
  • Records that role holders were told about and accepted their responsibilities

Signed role acknowledgments, onboarding checklists and awareness training records are the easiest proof of communication. Keep the approved matrix under version control, with dated approvals. If an auditor samples three role holders and asks what they are accountable for, each should be able to answer in a sentence.

For a wider view of what counts as proof, see types of evidence for ISO 27001 audits and the auditor questions to prepare for. Document control rules for the matrix itself are covered in Clause 7.5 document control.

Common mistakes to avoid

  • Two A’s on one row. It feels collaborative and works like abdication.
  • Everyone is R. If five people are Responsible, find the one who is Accountable for coordinating them.
  • Names instead of titles. The matrix is out of date the first time someone leaves.
  • Vague rows. “Security” is not an activity. “Approve firewall rule changes” is.
  • No link to the plan. A matrix that is not tied to the implementation timeline gets ignored. Put the A and R roles against each phase of your project plan.
  • Auditing your own work. Keep internal audit independent of the activities audited.

Perspective: assign roles before you budget the effort

Most teams treat the RACI matrix as paperwork they will tidy up before the audit. We see it the other way round. Roles decide effort. Once you know who is Accountable for risk treatment, who runs access reviews and how many hours the security manager can truly give, the cost and timeline of an ISO 27001 project stop being guesses.

That is why our calculator asks about company size, industry and security maturity, and why our readiness check looks across the four Annex A control themes. A 15-person startup with one person in three columns needs a different plan than a 250-person finance firm with separate teams. Our estimates keep their assumptions editable and the methodology traceable, so you can challenge any figure and put the roles you actually have into the plan.

Our advice: draft the matrix early, even rough, and use it to find the empty rows. Every empty row is a task someone will have to absorb, and it belongs in your budget and your Gantt chart.

Martin

Turn your matrix into a plan and a budget

A finished RACI matrix tells you who does what. The next question is how long it takes and what it costs. With the ISO 27001 cost calculator, you can enter your company size, industry and maturity and get a real-time estimate with editable assumptions. You can save several scenarios and compare them, for example one with a dedicated security manager and one where the IT lead covers the role.

Ismscalculator

Not sure where you stand? Start with the free 2-minute check, then use the readiness assessment for a domain-by-domain view. The methodology page shows how the figures are built.

FAQ

What is RACI in cybersecurity?

RACI is a way to assign responsibility for each security task: Responsible does it, Accountable owns the outcome, Consulted gives input, Informed is updated. In an ISMS it documents who handles risk assessment, access, incidents, audits and reviews. It turns vague ownership into a table that auditors and staff can read.

Do I need one RACI matrix or several?

One master matrix is enough for most small and mid-sized organizations. Larger ones often add detailed sub-matrices, such as incident response or change management, that roll up to the master. Whichever you choose, each row must have exactly one Accountable role, and the documents must not contradict each other.

Who should be Accountable for the ISMS overall?

Top management. Clause 5.3 puts the assignment of roles and authorities on top management, including who ensures the ISMS conforms and who reports on its performance. Day-to-day work usually sits with the information security manager or CISO, but top management stays accountable for the system.

How often should I update the matrix?

Review it whenever the organization changes, such as new teams, tools, suppliers or leadership, and at least in each management review. Because the matrix uses job titles, most staff changes only need a roster update. Keep dated versions so an auditor can see the history.

Sources

¿Listo para estimar los costos de su ISO 27001?

Use nuestro calculador gratuito para obtener una estimación personalizada de costos, esfuerzo y plazos basada en su perfil empresarial.

Calcule su estimación — gratis
Volver a todos los artículos