Study guide

2.2 Organizational Structures, Roles & RACI Matrix

Certified in Risk and Information Systems Control CRISC

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Risk Foundations

1.1 About the CRISC Exam 1.2 Exam Day Strategy & Question Analysis

2 Chapter 2: Enterprise Governance & Organizational Strategy

2.1 Enterprise Governance of IT & Strategic Alignment 2.2 Organizational Structures, Roles & RACI Matrix 2.3 The Three Lines Model & Assurance Coordination 2.4 Legal, Regulatory & Contractual Compliance

3 Chapter 3: Risk Governance Frameworks & ERM

3.1 Enterprise Risk Management Frameworks 3.2 Risk Appetite, Tolerance & Capacity 3.3 IT Risk Strategy Alignment with Business Objectives

4 Chapter 4: Risk Culture, Ethics & Policy Architecture

4.1 Risk Culture, Tone at the Top & Accountability 4.2 Ethics, Integrity & ISACA Code of Professional Ethics 4.3 Risk Policy, Standards, Guidelines & Procedures Architecture

5 Chapter 5: Asset Management & Business Resilience Governance

5.1 Asset Identification, Valuation & Data Classification 5.2 Data Ownership, Custodianship & Governance Roles 5.3 Business Resilience Governance & Strategic Alignment 5.4 Data Privacy Governance & Global Mandates

6 Chapter 6: IT Risk Identification & Threat Modeling

6.1 Risk Identification Techniques 6.2 Threat Landscape Analysis, Threat Actors & Attack Vectors 6.3 Vulnerability Assessment & Exposure Analysis 6.4 Risk Scenario Development & Threat Modeling

7 Chapter 7: Risk Analysis Methodologies & Evaluation

7.1 Qualitative Risk Analysis & Risk Matrices 7.2 Quantitative Risk Analysis & FAIR Framework 7.3 Semi-Quantitative Analysis & Monte Carlo Simulation 7.4 Risk Evaluation, Ranking & Prioritization Criteria

8 Chapter 8: Risk Register, Aggregation & BIA Integration

8.1 Risk Register Architecture, Maintenance & Lifecycle 8.2 Risk Aggregation, Correlation & Interdependencies 8.3 Business Impact Analysis (BIA) Integration

9 Chapter 9: Risk Treatment Strategies & Cost-Benefit Analysis

9.1 Risk Response Options 9.2 Cost-Benefit Analysis & Return on Security Investment (ROSI) 9.3 Developing & Implementing Risk Action Plans 9.4 Managing Residual Risk & Secondary Risk

10 Chapter 10: Control Design, Selection & Assessment

10.1 Control Types & Categories 10.2 Control Design Principles & Defense-in-Depth 10.3 Testing Control Design & Operating Effectiveness 10.4 Remediation of Control Deficiencies & Exceptions

11 Chapter 11: Third-Party & Supply Chain Risk Management

11.1 Third-Party Risk Management Lifecycle & Due Diligence 11.2 Vendor Contracts, SLAs & Right-to-Audit Clauses 11.3 Supply Chain Risk Management & Software Bill of Materials (SBOM) 11.4 Cloud Service Provider Governance & Shared Responsibility

12 Chapter 12: Risk Monitoring, KRIs & Executive Reporting

12.1 Key Risk Indicators (KRIs), Thresholds & Triggers 12.2 Aligning KRIs with KPIs & Business Performance Metrics 12.3 Stakeholder Risk Reporting & Governance Communication 12.4 Continuous Risk Monitoring & Automated Telemetry

13 Chapter 13: Enterprise IT Architecture & Operations

13.1 Enterprise Architecture & IT Governance Alignment 13.2 Cloud Computing & Virtualization Architecture Risk 13.3 Systems Resilience, High Availability & Infrastructure Redundancy 13.4 Technology Roadmaps, IT Portfolio & Project Risk Governance

14 Chapter 14: Information Security Principles, IAM & SSDLC

14.1 Information Security Principles & The CIA Triad 14.2 Identity & Access Management (IAM), PAM & RBAC 14.3 Cryptography, Encryption & Key Management (KMS) 14.4 Secure Software Development Lifecycle (SSDLC) & DevSecOps

15 Chapter 15: Incident Response, Resilience & Emerging Tech Risk

15.1 Incident Response Lifecycle & Containment Strategies 15.2 Business Continuity & Disaster Recovery Planning and Testing 15.3 Emerging Technologies Risk (AI/LLM, Quantum, IoT/OT) 15.4 Risk Program Maturity Assessment & Continuous Improvement

2.2 Organizational Structures, Roles & RACI Matrix

Key Takeaways Explain This Topic AI

The Board of Directors holds ultimate fiduciary accountability for establishing enterprise risk appetite, approving governance policies, and ensuring active oversight of organizational risk management.

Business Unit Leaders / Business Process Owners are the true 'Risk Owners'—they own the business assets and processes, bear the operational consequences of risk events, and have the sole authority to accept residual risk or fund risk treatment.

The Chief Risk Officer (CRO) and Chief Information Security Officer (CISO) act as strategic advisors, risk facilitators, and program coordinators; neither the CISO nor IT operational staff own business risk.

A RACI matrix establishes clear governance by defining who is Responsible (completes the work), Accountable (has final decision and ownership; exactly one 'A' per activity), Consulted (provides subject matter expertise), and Informed (receives status updates).

The Enterprise Risk Committee provides cross-functional executive coordination, ensuring IT and cyber risks are integrated into broader enterprise risk management (ERM) rather than managed in technical silos.

Last updated: August 2026

2.2 Organizational Structures, Roles & RACI Matrix

Effective IT risk governance depends entirely on well-defined organizational structures, unambiguous authority limits, and clear lines of accountability. When risk roles and responsibilities are ill-defined or blurred, organizations suffer from governance vacuums—where critical vulnerabilities are ignored because operational teams assume security is responsible, while security assumes business units own the remediation budget.

ISACA emphasizes that risk management is an enterprise-wide responsibility that spans from the boardroom to frontline systems administrators. Understanding the specific duties of each role and applying responsibility assignment models (such as the RACI matrix) is vital for passing the CRISC exam and establishing resilient enterprise governance. +-----------------------------------------------------------------------------+

  • | ENTERPRISE RISK GOVERNANCE ORGANIZATIONAL HIERARCHY |
  • | |
  • | +---------------------------------+ |
  • | | BOARD OF DIRECTORS | (Ultimate Oversight)|
  • | | (Audit / Risk Committee) | |
  • | +----------------+----------------+ |
  • | | |
  • | v |
  • | +---------------------------------+ |
  • | | CHIEF EXECUTIVE OFFICER | (Executive Direction|
  • | | & EXECUTIVE SUITE | |
  • | +----------------+----------------+ |
  • | | |
  • | +------------------------------+------------------------------+ |
  • | | | | |
  • | v v v |
  • | +-------------+ +---------------+ +-------------+ |
  • | | ENTERPRISE | <----------> | CHIEF RISK | <----------> | CHIEF INFO | |
  • | | RISK COMM. | | OFFICER (CRO) | | SEC. OFF. | |
  • | |(Exec Leads) | | (Independent) | | (CISO) | |
  • | +------+------+ +---------------+ +------+------+ |
  • | | | |
  • | v v |
  • | +------------------------------------+ +------------------------------+ |
  • | | BUSINESS UNIT LEADERS | | IT OPERATIONS / ENG. | |
  • | | (THE RISK OWNERS) | | (CONTROL CUSTODIANS) | |
  • | | - Own business processes & assets | | - Configure, deploy, & run | |
  • | | - Authorize risk acceptance/budget | | technical controls | |
  • | +------------------------------------+ +------------------------------+ |
  • +-----------------------------------------------------------------------------+
  • 1. Key Governance & Risk Roles Breakdown

To correctly answer CRISC scenario questions, candidates must recognize the exact legal, fiduciary, and operational boundaries of each organizational stakeholder:

A. The Board of Directors (Governing Body)

Fiduciary Obligation: Holds ultimate legal and fiduciary accountability to shareholders, regulators, and stakeholders for the enterprise's long-term viability and risk posture.

Key Responsibilities:

Defines and approves the enterprise Risk Appetite and risk governance philosophy.

Sets the Tone at the Top , establishing ethical expectations and compliance culture.

Ensures adequate capital, executive staffing, and resources are allocated to risk management.

Oversees risk exposure via quarterly briefings from the Chief Risk Officer, CISO, and Board Audit/Risk Committees.

What the Board Does NOT Do: The Board never manages operational incidents, reviews individual technical log files, or chooses specific firewall vendors.

B. Executive Management (CEO, CFO, COO, CIO)

Operationalizing Governance: Translates Board-approved risk appetite into operational policies, capital allocations, and organizational performance objectives.

Chief Executive Officer (CEO): Ultimately accountable for day-to-day organizational execution and operational risk management.

Chief Financial Officer (CFO): Ensures financial risk controls, capital allocation for risk mitigation, and compliance with statutory financial reporting (e.g., SOX).

Chief Information Officer (CIO): Accountable for IT strategy, enterprise systems availability, digital transformation, and ensuring IT operations meet agreed-upon service levels.

C. The Enterprise Risk Committee (ERC / Risk Steering Committee)

Composition: Cross-functional executive body comprising Business Unit Heads, CRO, CISO, CIO, CFO, Chief Legal Counsel, and Chief Compliance Officer (Internal Audit attends as an independent observer).

Key Functions:

Meets regularly (typically monthly or quarterly) to evaluate the aggregated enterprise risk register.

Prioritizes capital investment for risk mitigation across competing business unit demands.

Reviews systemic Key Risk Indicators (KRIs) and escalates risk appetite breaches to the Board.

Ensures IT and cybersecurity risks are evaluated alongside market, credit, and operational risks rather than treated as isolated IT problems.

D. Chief Risk Officer (CRO) vs. Chief Information Security Officer (CISO)

Chief Risk Officer (CRO): Leads the independent enterprise risk management (ERM) function. Establishes enterprise-wide risk assessment methodologies, aggregates risk across all domains (credit, market, operational, cyber), and reports directly to executive leadership and the Board.

Chief Information Security Officer (CISO): Establishes information security architecture, cybersecurity operations, incident response plans, and security policies. The CISO acts as a risk advisor and facilitator to business leaders regarding cyber threats.

Important

CRISC Golden Rule — The CISO Never Owns Business Risk: One of the most frequently tested concepts on the CRISC exam is that the CISO and IT teams do not own business risk . The CISO discovers, measures, and reports risk, and recommends control strategies. However, the business leader who relies on the system to generate revenue is the Risk Owner and makes the final decision on whether to accept, mitigate, transfer, or avoid that risk.

E. Business Unit Leaders (The True "Risk Owners")

Definition: The business executive who possesses budgetary authority over a business process, operational system, or data asset.

Key Authority:

Accountable for business assets and the impact of potential risk events.

Sole authority to accept residual risk that falls within authorized organizational risk tolerance thresholds.

Approves and funds risk treatment plans (e.g., purchasing insurance, hiring staff, buying controls).

F. Control Custodians / IT Administrators

Definition: The technical custodians who deploy, configure, maintain, and operate controls on behalf of the Risk Owner.

Responsibilities: Implementing access controls, configuring firewalls, backing up data, executing patch cycles, and monitoring technical alerts in accordance with policy.

2. Accountability vs. Responsibility: The Non-Delegation Principle

A critical distinction tested on the CRISC exam is the difference between Accountability and Responsibility : +-----------------------------------------------------------------------------+

  • | ACCOUNTABILITY vs. RESPONSIBILITY |
  • | |
  • | ACCOUNTABILITY (Non-Delegable) RESPONSIBILITY (Delegable) |
  • | -------------------------- -------------------------- |
  • | - Cannot be shared or delegated. - Can be shared and delegated. |
  • | - Belongs to exactly ONE individual. - Can involve multiple actors. |
  • | - Holds ultimate decision & veto power. - Executes the operational work. |
  • | - Answers to Board and Regulators. - Answers to the Accountable Lead|
  • | - Examples: Risk Owner, Board, CEO. - Examples: Engineers, Vendors. |
  • +-----------------------------------------------------------------------------+
  • The Outsourcing Paradox

When an enterprise contracts a third-party Cloud Service Provider (CSP) or Managed Security Service Provider (MSSP):

The enterprise can delegate responsibility for operating firewalls, patching hypervisors, and managing physical data centers to the vendor.

The enterprise can NEVER delegate accountability . If customer data is compromised or regulatory non-compliance occurs, the enterprise governing body and business risk owner remain 100% accountable to regulators, courts, and customers.

3. The RACI Assignment Matrix Mechanics

The RACI Matrix (Responsible, Accountable, Consulted, Informed) is the standard governance tool used to clarify roles and eliminate operational ambiguity across complex risk and security workflows. +-----------------------------------------------------------------------------+

  • | THE RACI MATRIX MECHANICS |
  • | |
  • | [R] RESPONSIBLE The "Doer" - The individual or team that performs |
  • | the activity to achieve the deliverable. |
  • | |
  • | [A] ACCOUNTABLE The "Owner" - The single individual with final |
  • | decision-making power, ownership, and veto authority. |
  • | *MANDATORY RULE: Exactly ONE 'A' per activity!* |
  • | |
  • | [C] CONSULTED The "Advisor" - Subject matter experts who provide |
  • | two-way input, analysis, or guidance before actions. |
  • | |
  • | [I] INFORMED The "Stakeholder" - Individuals kept updated with |
  • | one-way notifications regarding progress or results. |
  • +-----------------------------------------------------------------------------+

Core Rules for Building an Effective RACI Matrix:

Exactly One 'A' Per Activity: If zero individuals are Accountable, no one takes ownership and tasks fail. If multiple individuals are assigned 'A', decision gridlock occurs and accountability is diluted.

Minimize Excessive 'C's (Consulted): Consulting too many stakeholders creates bureaucratic paralysis, slows incident response, and increases meeting overhead.

Clarity in 'R' (Responsible): Ensure those assigned 'R' possess the necessary authority, tools, skills, and budget from the Accountable leader to execute the task.

Illustrative Enterprise Risk & Security RACI Matrix

Governance / Operational Activity Board of Directors Executive Comm. (CEO/CFO) Business Risk Owner CISO / CRO IT Operations Custodian Internal Audit

  • Establish Enterprise Risk Appetite A R C C I I
  • Approve Business System Residual Risk I I A C I I
  • Design Information Security Policy I I C A / R C C
  • Deploy Operating System Security Patches I I I C A / R I
  • Conduct Independent Risk & Control Audit I I I I I A / R
  • Perform Third-Party Vendor Risk Assessment I I C A / R C I

Note

Reading the Table: In row 2 ( Approve Business System Residual Risk ), the Business Risk Owner is Accountable (A) . The CISO is Consulted (C) to provide threat analysis and control recommendations, while IT Operations and Executive Management are Informed (I) .

4. Organizational Governance Anti-Patterns & Exam Traps +-----------------------------------------------------------------------------+

  • | FOUR CLASSIC GOVERNANCE ANTI-PATTERNS |
  • | |
  • | 1. THE "IT OWNS THE RISK" ANTI-PATTERN |
  • | Symptom: Business executives disclaim responsibility for cyber risk, |
  • | claiming "IT is in charge of computers." |
  • | Result: Security controls lack business context; risk is ignored. |
  • | |
  • | 2. THE "MULTIPLE ACCOUNTABLES" ANTI-PATTERN |
  • | Symptom: Assigning both the CIO and CISO as 'A' in the RACI matrix. |
  • | Result: Finger-pointing during major breaches; zero clear ownership.|
  • | |
  • | 3. THE "SILOED RISK COMMITTEE" ANTI-PATTERN |
  • | Symptom: IT Risk meets separately from Enterprise Financial Risk. |
  • | Result: Inability to evaluate aggregated operational risk exposure. |
  • | |
  • | 4. THE "AUDITOR AS DECISION MAKER" ANTI-PATTERN |
  • | Symptom: Allowing Internal Audit to approve system architecture. |
  • | Result: Destroys audit independence (Third Line assurance failure). |
  • +-----------------------------------------------------------------------------+
  • Real-World Vignette: The Orphaned Database

An online retail conglomerate suffered a breach compromising 2.4 million payment records from an unpatched legacy analytics database.

The Investigation: The database was created five years earlier for a marketing campaign. When the marketing vice president left the company, no successor was assigned as the Risk Owner .

The RACI Void: The IT infrastructure team kept the server running (operational responsibility) but refused to upgrade the underlying OS because they had no budget or business approval to test application compatibility. The CISO had flagged the vulnerability, but had no authority to decommission the revenue-generating database.

Lesson for CRISC: Without clear assignment of a single Accountable Business Risk Owner for every enterprise asset, technical controls will inevitably fail.