Most security failures that end up in an audit report are not technical. A patch was not applied because the infrastructure team thought the application team owned it. A risk was "accepted" by someone who had no authority to accept it. An incident stalled for two hours while people worked out who could approve taking a system offline. Each is a failure of accountability, and a RACI chart is the simplest tool for preventing it.
What RACI stands for
For each activity or decision, a RACI chart records four kinds of involvement:
- Responsible (R): does the work. There can be several.
- Accountable (A): owns the outcome and has the authority to make the final decision or sign off. There must be exactly one.
- Consulted (C): gives input before the work is done or the decision is made. Two-way communication.
- Informed (I): told about progress or the outcome. One-way communication.
The difference between responsibility and accountability is the heart of the model. Responsibility can be shared and delegated. Accountability cannot: one named role answers for the result, even when others do the work.
The rules that make a RACI chart work
- One A per activity. Two accountable parties means nobody is. If you cannot agree on one, the activity is probably two activities.
- At least one R per activity. An A with no R is a decision without anyone to carry it out.
- The A needs real authority. Making someone accountable for something they cannot fund, approve or stop is a setup for failure.
- One person can be both R and A for small activities; record it as "A/R".
- Keep C small. Every C adds delay. Consult the people whose input changes the decision, and inform the rest.
- Use roles, not names. "Application owner" survives a resignation; "Priya" does not. Keep a separate list of who holds each role.
- Check segregation of duties. Read each row and ask whether the same role both performs and approves something sensitive.
Example 1: incident response
| Activity | Security operations lead | Incident manager | System owner | CISO | Legal and privacy | Communications |
|---|---|---|---|---|---|---|
| Detect and triage the alert | A/R | I | ||||
| Declare a major incident | C | A/R | C | I | ||
| Isolate an affected production system | R | C | A | I | ||
| Decide whether a breach is reportable | C | C | C | R | A | I |
| Notify regulators and affected people | I | C | A/R | C | ||
| Run the post-incident review | R | A | C | I | C |
Two choices here are deliberate. The system owner is accountable for isolating their system, because taking a production service offline is a business decision even when security recommends it. And legal and privacy are accountable for the reporting decision, because deadlines such as India's six-hour CERT-In reporting window and breach notification under data protection law carry legal consequences. See the 72-hour breach reporting playbook for how those timelines interact.
Example 2: user access reviews
| Activity | Identity team | Line manager | Application or data owner | Internal audit |
|---|---|---|---|---|
| Extract access lists | A/R | I | ||
| Review and certify each user's access | I | R | A | |
| Remove access that was not certified | A/R | I | I | |
| Independently test the review | I | I | A/R |
The data owner is accountable because they understand what access the data needs. The identity team runs the process but should not decide who keeps access to someone else's data, and internal audit stays independent by testing rather than doing.
Example 3: vulnerability patching
| Activity | Vulnerability management | Infrastructure team | Application owner | Change advisory board | CISO |
|---|---|---|---|---|---|
| Scan and prioritise findings | A/R | I | I | I | |
| Test the patch with the application | R | A | |||
| Approve the production change | C | C | A | ||
| Deploy the patch | A/R | I | I | ||
| Approve an exception when a patch cannot be applied | C | C | R | A |
The last row matters most. Exceptions are risk acceptance in disguise, so the accountable party must be someone with authority to accept risk, not the team that would rather not patch.
Example 4: risk acceptance
| Activity | Risk practitioner | Risk owner (business) | CISO | Risk committee |
|---|---|---|---|---|
| Assess and document the risk | A/R | C | C | |
| Recommend a response | R | C | A | |
| Decide to accept the risk within appetite | C | A/R | C | I |
| Accept a risk above appetite | C | R | C | A |
| Monitor the accepted risk | R | A | I | I |
This reflects how ISACA's CRISC and CISM frame risk: the business risk owner is accountable for the response, the risk practitioner advises, and risks beyond the organisation's appetite go to a body with the authority to accept them. See risk appetite, tolerance and capacity and writing a risk register entry.
Ownership roles you will meet
RACI charts in security keep returning to a few ownership roles, and exams test them often:
- Data owner: a senior business role accountable for a set of information. Decides classification, who may access it and how long it is kept.
- Data custodian: usually IT. Responsible for day-to-day protection: backups, storage, technical access controls.
- System owner: accountable for a system's operation and for making sure its controls are in place.
- Risk owner: accountable for deciding how a risk is treated and for monitoring it.
- Control owner: accountable for a control operating as designed.
- Senior management and the board: ultimately accountable for information security and risk across the organisation. They can delegate the work, not the accountability.
ISO 27001 reflects the same idea: top management must assign and communicate responsibilities and authorities (clause 5.3), Annex A requires defined security roles, segregation of conflicting duties and management responsibility (controls 5.2 to 5.4), and COBIT publishes RACI-style charts for its governance and management practices.
Variants of RACI
- RASCI or RACIS: adds Supportive, for roles that provide resources or help the responsible party.
- RACI-VS: adds Verifier (checks the work meets criteria) and Signatory (signs off).
- CAIRO: adds Out of the loop, to state explicitly who is not involved.
- DACI: Driver, Approver, Contributors, Informed; common for product and project decisions.
The variant matters less than the discipline: one accountable party, clear doers, and a chart that people actually use.
Common mistakes
- Several As on one row, usually to avoid an argument. Resolve the argument instead.
- The security team is accountable for everything. Security can be responsible for many activities, but business owners are accountable for their data, systems and risks.
- Everyone is consulted. Decisions slow down and people stop reading the requests.
- The chart is too granular. Hundreds of rows nobody maintains are worse than twenty that are current. Chart decisions and hand-offs, not every task.
- No segregation of duties check. If one role can create and approve a payment, or request and grant its own access, the chart has written a control failure into policy.
- It is never updated. Review the chart after reorganisations, after major incidents and at least yearly.
How exams test accountability
- CRISC and CISM: "Who should accept this risk?" The risk owner or senior management, never the risk practitioner or security manager acting alone. "Who is accountable for protecting this data?" The data owner.
- CISSP: the data owner sets classification and approves access; the custodian implements protection. Senior management holds ultimate responsibility for security.
- All three: if an answer gives one person conflicting duties, such as developing and deploying code to production without review, it is usually wrong because it breaks segregation of duties.
Frequently asked questions
What is the difference between responsible and accountable in RACI?
The responsible party does the work. The accountable party owns the outcome and makes the final decision. Responsibility can be shared or delegated; accountability sits with exactly one role.
Can there be more than one accountable person in a RACI matrix?
No. Each activity should have exactly one accountable role. If two roles both claim accountability, split the activity or decide who has the final authority.
Can the same person be responsible and accountable?
Yes. For smaller activities one role often does the work and owns the outcome, recorded as A/R.
Who is accountable for information security in an organisation?
Senior management and the board hold ultimate accountability. They delegate the work to the CISO and security teams, and accountability for specific data, systems and risks to the business owners of each.
What is RASCI?
A variant of RACI that adds Supportive: roles that provide resources or assistance to the responsible party without owning the work.
Test yourself
10 CRISC practice questions from Domain 1, Governance, each with an explanation of the best answer.
Sources and further reading
Written and reviewed by the DigiTrust Asia editorial team. How we research, review and correct articles.
Test yourself on the fundamentals
Free CISSP lessons and practice questions, with an explanation for every answer.
Create a free account