Integrated
Risk management is integral to all organisational activities, not a parallel discipline that runs alongside.
Enterprise risk management (ERM) is the board-led discipline of identifying, assessing, treating, monitoring, and reporting on every material risk an organisation faces as a single portfolio. It replaces the siloed view (cyber, financial, operational, compliance) with one enterprise picture, governed by a board-approved risk appetite. COSO ERM 2017 and ISO 31000:2018 are the two reference frameworks.
Enterprise risk management is the discipline of identifying, assessing, treating, monitoring, and reporting on all material risks an organisation faces as a single portfolio, governed by the board and tied to a documented risk appetite. The phrase distinguishes it from the older silo model, where cyber risk, financial risk, operational risk, and compliance risk were each owned and assessed separately. ERM rolls those silos up.
The term hardened in the early 2000s with the original COSO ERM framework (2004) and the first edition of ISO 31000 (2009). The 2017 COSO update repositioned ERM as integral to strategy and performance, not a parallel compliance exercise, which is the definition most US boards and audit committees work to today. ISO 31000:2018 sharpened the principles and process for use outside the US and in regulated industries internationally.
One enterprise register that consolidates risks across cyber, financial, operational, compliance, strategic, and physical categories. Dependencies surface explicitly.
The board owns the programme, approves the risk appetite statement, and reviews material risks at least quarterly. The CRO or equivalent runs the framework.
Risk is considered in strategy formulation, not bolted on after. The default question is how much risk to take in pursuit of objectives, not only how to avoid loss.
“Enterprise risk management is the culture, capabilities, and practices, integrated with strategy-setting and performance, that organizations rely on to manage risk in creating, preserving, and realizing value.”
Traditional risk management runs in silos and reports up in separate stacks. ERM is a portfolio view owned by the board. The methodology and the cadence differ accordingly.
| Dimension | Traditional risk management | Enterprise risk management |
|---|---|---|
| Scope | Siloed: cyber risk, financial risk, operational risk, compliance risk each owned and assessed separately, with little consolidation. | Portfolio: a single enterprise view of all material risks, owned by the board, with cross-category dependencies surfaced explicitly. |
| Driver | Loss prevention and regulatory compliance. The default question is 'how do we stop the next bad thing'. | Strategic value creation. The default question is 'how much risk should we take to achieve this objective, and which risks return the most value per dollar of treatment'. |
| Owner | Functional heads (CISO, CFO, Compliance Officer) own their slice. The board sees a stack of separate reports. | Board owns the portfolio. CRO or equivalent runs the framework. Three lines of defense organise oversight. |
| Methodology | Mostly qualitative, mostly retrospective. Heat maps per silo. Quantitative work, if any, is local to one silo. | Qualitative across the register, quantitative on the top tier (FAIR, Monte Carlo). Forward-looking via scenarios and KRIs. |
| Cadence | Annual assessment, sometimes shelved between cycles. Updates triggered by incidents or audits. | Continuous monitoring with quarterly board cycles. Material change triggers immediate reassessment of affected risks. |
| Output | Multiple registers and reports, one per function. Often inconsistent in scoring and language. | Single enterprise register reconciled to a board-approved appetite. One vocabulary across the firm. |
The shift is less a tooling change than a governance change. Most organisations already run risk activity in every silo ERM rolls up. ERM gives those activities a common vocabulary, a board-approved appetite line to compare against, and a single register that survives a board question on a Tuesday morning.
The Committee of Sponsoring Organizations published the integrated framework in 2017 as a replacement for the 2004 cube. The 2017 version positions ERM as integral to strategy and performance, with five components and 20 principles distributed across them.
The board oversees risk. The operating model defines authority and reporting lines. Core values, desired culture, and the talent pipeline get explicit attention. Without governance the rest of the framework is decorative.
Risk is considered in strategy formulation, not bolted on after. Business context is analysed. Risk appetite is defined in board-approved statements. Alternative strategies and business objectives are stress-tested against the appetite line.
Risks are identified, assessed for severity, prioritised, treated, and the portfolio view is developed. This is the analytical core: the register, the heat map, the loss-exceedance curve, the residual-versus-appetite gap.
Substantial change is assessed for its impact on the risk profile. ERM performance itself is reviewed. The framework is improved on a defined cadence so it does not ossify around the first design choices.
Relevant information is gathered. Communication channels are defined for upward, downward, and lateral flow. Risk, culture, and performance are reported to the board and management on a schedule the board can rely on.
The 20 principles are not optional bullets; they are the audit-committee checklist. Internal audit reviews against them, the SEC references them in disclosure rules, and the big four use them as the structure for ERM maturity assessments. A programme that cannot map its activity to all five components is a programme an auditor can pick apart.
The 2018 revision shortened the document, sharpened the principles, and made the framework consciously generic. Eight principles sit at the front; the framework and the process follow. Useable in any sector, at any scale.
Risk management is integral to all organisational activities, not a parallel discipline that runs alongside.
A structured and comprehensive approach contributes to consistent and comparable results across the enterprise.
The framework and process are customized and proportionate to the organisation's external and internal context related to its objectives.
Appropriate and timely involvement of stakeholders enables their knowledge, views, and perceptions to be considered.
Risks emerge, change, and disappear as context changes. Risk management anticipates, detects, acknowledges, and responds to those changes.
Inputs are based on historical and current information and on future expectations, with limitations and assumptions stated.
Human behaviour and culture significantly influence all aspects of risk management at each level and stage.
Risk management is continually improved through learning and experience.
COSO is governance-heavy and well-suited to US public companies and SOX-regulated entities. ISO 31000 is principles-led and easier to localise into international or non-listed organisations. Both describe the same underlying process. Mature programmes borrow the governance scaffolding from COSO and the methodology vocabulary from ISO 31000, then add ISO/IEC 27005 or NIST 800-30 for the cyber sub-portfolio and FAIR for quantitative depth.
COSO ERM 2017 distributes the work across its five components. ISO 31000:2018 lists six process steps. Practitioners usually run an eight-step version that pulls the governance and reporting work into named stages, so every artefact has a home.
Document the organisation's mission, strategy, structure, external regulatory landscape, and internal operating model. Capture the risk culture honestly. The work below depends on this scoping being defensible.
Translate strategy into specific, measurable objectives. The board approves a risk appetite statement that names tolerated exposure by category. Without appetite, the assessment has no decision line.
Interview business owners, review incident history, run scenario workshops, scan external threat intel. Each risk gets a one-sentence statement (threat, vulnerability, consequence) and an accountable owner from the business.
Score each risk on a consistent scale (most teams start with a 5x5 ordinal matrix). For the top 10 to 20 risks, run a quantitative pass in monetary terms using FAIR or a Monte Carlo simulation.
For each risk above appetite, choose to accept, treat, transfer (insurance, contractual shift), or avoid (exit the activity). Treatment plans name the controls, the owner, the deadline, and the target residual score.
Stand up the preventative, detective, and corrective controls the treatment plan calls for. Map each control to the risk it reduces and to the compliance obligations it also satisfies so evidence collected once is credited many times.
Key risk indicators (KRIs) carry the watch between assessments. Control tests run on schedule. Incidents and audit findings feed the register without waiting for the next cycle. The fifth COSO component (review and revision) lives here.
Board pack on a fixed cadence. Audit-committee deep-dive each quarter. Internal communications to risk owners and to the workforce on culture and incidents. Reporting is a feature of the framework, not an afterthought.
Steps seven and eight are where programmes that look good in the binder fail in practice. Continuous monitoring keeps the register honest between cycles; reporting keeps the board engaged. A programme that runs steps one through six well and then drops the last two has produced a snapshot, not a framework.
ERM accountability is not flat. The board owns the portfolio. The CRO runs the framework. The business owns the risks it generates. Internal audit provides assurance. The IIA three lines model gives the structure.
Ultimate accountability for the risk programme. Approves the risk appetite statement and reviews material risks at least quarterly. Signs off on the framework and on changes to it.
Oversees the integrity of risk reporting, the independence of internal audit, and the effectiveness of the framework. Reviews internal-audit findings and follow-through on management actions.
Owns the risks of executing the strategy. Allocates capital to treatment plans. Ensures risk owners across the business have the resources and authority their role requires.
Designs and runs the framework. Owns the methodology, the enterprise register, the aggregation up to portfolio view, and the board reporting cadence. Reports to the CEO or the audit committee, ideally both.
Business heads who own the risks generated by their activity. They identify, assess, treat, and monitor their risks day to day. The first line of defense.
CRO function, compliance officer, BCM, information security, and similar oversight functions. Set policy, methodology, and independent challenge. The second line of defense.
Independent assurance to the board on the effectiveness of lines one and two. Reports functionally to the audit committee. The third line of defense per the IIA model.
The IIA refreshed the model in 2020 as the “Three Lines Model” to emphasise collaboration over rigid separation. Lines do not work in isolation; they coordinate. What survives the refresh is the principle that the third line (internal audit) reports to the audit committee, not into the management chain it audits.
No mature programme picks one framework and lives there forever. ERM in practice is a stack: an enterprise wrapper (COSO or ISO 31000), a cyber methodology (ISO 27005 or NIST 800-30), and sector-specific frameworks (Basel III for banks, Solvency II for insurers, NIST RMF for federal).
The Committee of Sponsoring Organizations framework, integrated with strategy and performance. Five components and 20 principles. Widely referenced by US public companies, SOX internal controls work, and the SEC.
The international standard for risk management principles, framework, and process. Sits above any specific domain. The reference boards and regulators outside the US most often cite.
An ISMS standard, not an enterprise framework, but the methodology in ISO/IEC 27005 plugs into ERM as the cyber risk engine. 93 Annex A controls. Certifiable. Required by many enterprise customers.
Risk Management Framework for federal information systems. Seven steps from prepare to monitor. Pairs with NIST 800-30 for assessment and NIST 800-53 for the control catalogue. Default for federal and defence contractors.
Sector-specific frameworks for banking capital, liquidity, and model risk. ERM at a bank inherits these and adds the rest of the enterprise picture on top.
EU prudential regime for insurers. The Own Risk and Solvency Assessment (ORSA) is the insurer's annual ERM exercise. US equivalents are the NAIC ORSA Guidance Manual and the Insurance Holding Company Act.
A credible first cycle is achievable in a quarter, provided the board mandate is in place and risk activity already runs in silos that can be consolidated. Below is the cadence that holds up at audit-committee level.
Ninety days produces a defensible first cycle, not a mature programme. Maturity comes from the next four quarters: embedding ERM in change management, vendor onboarding, M&A diligence, strategy reviews, and incident learning loops. The RIMS Risk Maturity Model and ISO 31000 self-assessment tools both give a structured way to score progress.
Most ERM programmes fail in predictable ways. None of these failures are framework choices; they are governance and cadence choices that catch up with the programme inside two cycles.
If the register lives in a CRO's spreadsheet and only the CRO references it, the framework has not been adopted. Board cadence, board readability, and board questions back to risk owners are the test.
A risk appetite statement that never causes a 'no' or a 'reduce' decision is decorative. Appetite earns its keep when it constrains real choices about strategy, M&A, vendor onboarding, and product launches.
ERM is not SOX with extra steps. A programme that only counts controls and never weighs strategic risk has missed the value-creation half of the COSO 2017 definition.
Picking COSO or ISO 31000 is the easy bit. Without a documented scoring methodology, calibrated assessors, and a consistent vocabulary, the register reads differently in every business unit.
An ERM cycle that runs once a year produces a museum exhibit, not a live picture of exposure. KRIs, control tests, incidents, and audit findings must update the register continuously.
If the CRO function reports only to the CEO and cannot escalate independently to the audit committee, the second line is structurally weak. The IIA three-lines model exists for a reason.
The frameworks and governance models referenced on this page are published by standards bodies, US federal agencies, and professional institutes. Direct links below.
Twelve questions that come up on the way to a working programme, with practitioner answers.
The enterprise risk register, COSO and ISO 31000 templates, FAIR quantitative engine, KRI library, board reporting workflow, and cross-mapping to 40+ compliance frameworks. 30-day free trial, no credit card.
No credit card required · 30-day free trial · Cancel anytime