ISO 31000 and COSO ERM do the same job from different starting points. ISO 31000:2018 is short international guidance for managing any risk through principles, a framework and a process. COSO ERM (2017) ties risk to strategy and performance in five components. No organisation can hold an accredited certification against either.
Check which COSO you are being asked about. COSO publishes two frameworks. When an audit committee asks about controls, it may mean the 2013 internal control framework, which is not an enterprise risk framework at all. For UK listed companies preparing a Provision 29 declaration, the distinction matters most.
Three questions settle the choice. Who will test the framework? What must it connect to? What does your sector already reference? Answer them, write the decision down, map the other framework to it and move on.
Sooner or later, every risk lead is asked the ISO 31000 vs COSO question: which one is our framework built on? It might come from a new audit committee chair at her first meeting, or from internal audit asking for the framework reference during a refresh. You know both names. Your policy cites one of them in passing. What you are less sure of is whether your answer survives the follow-up question.
The choice is smaller than the search results make it look, and it takes one meeting. The expensive mistakes sit elsewhere: answering about the wrong COSO framework, and reopening the decision every time a new board member or adviser prefers the other one.
Three questions settle it, and a one-paragraph decision record keeps it settled.
What is the difference between ISO 31000 and COSO?
The difference between ISO 31000 and COSO is starting point, not purpose: ISO 31000 starts from the risk management process, while COSO Enterprise Risk Management (2017) starts from governance and strategy. ISO 31000:2018 guides the management of any risk, and COSO ERM ties risk to strategy and performance through five components and 20 principles. No organisation can hold an accredited certification against either. COSO also publishes a separate internal control framework (2013), which may be what a controls review is really asking about.
So the first job is to establish which COSO framework is meant. The second is to decide which document leads.
ISO 31000 vs COSO at a glance
Most comparisons set ISO 31000:2018 against COSO Enterprise Risk Management (2017) and stop there. A third document belongs in the room, so the table below has three columns.
| Feature | ISO 31000:2018 | COSO ERM (2017) | COSO internal control (2013) |
|---|---|---|---|
| Published by | ISO, through committee ISO/TC 262 and national standards bodies | COSO, a joint initiative of five US professional bodies | COSO |
| What it is for | Managing any type of risk in any organisation | Linking risk to strategy, performance and value | Designing and assessing internal control over operations, reporting and compliance |
| How it is built | Principles, a framework and a process | Five components and 20 principles | Five components and 17 principles |
| How it treats appetite | Through risk criteria the organisation sets | Risk appetite at the centre of strategy setting | Not its focus |
| Accredited certification for organisations? | No | No | No |
| Status as at October 2026 | 2018 edition current. Third edition approved for registration as a draft international standard; no publication date set. | 2017 edition current. Practical guidance paper published May 2026. | 2013 edition current. Sustainability reporting guidance added 2023. |
Read across the first two columns and the overlap is plain. Both put risk inside decision-making, both are principles-based, and neither tells you who owns the risk in front of you. Read down the third column and you are looking at a different instrument. COSO’s internal control framework (2013) asks whether controls work, not how risk shapes strategy. That is why COSO vs ISO 31000 is never quite the right comparison until someone says which COSO framework they mean.
A standard gives you a vocabulary. The framework is what people do on an ordinary Tuesday.
Which COSO? COSO ERM vs COSO internal control
COSO publishes two frameworks, and they answer different questions. COSO’s Internal Control: Integrated Framework came first, in 1992, and was refreshed in 2013. COSO Enterprise Risk Management followed in 2004 and was rewritten in 2017 as Enterprise Risk Management: Integrating with Strategy and Performance.
In US-listed groups, the internal control framework is the usual reference when management assesses internal control over financial reporting, and the external auditor’s opinion on those controls uses it as the criteria. That is an audit opinion on controls, not a certification of anyone’s framework.
In the UK, the controls conversation now runs through Provision 29 of the UK Corporate Governance Code 2024. It applies to companies in the commercial companies listing category for financial years beginning on or after 1 January 2026, and asks boards to declare whether their material controls were effective. The FRC sets no framework for that declaration and does not define material controls. Many boards will still reference COSO’s internal control framework, and that is a choice, not a requirement. See what the Provision 29 declaration asks of boards.
So when an audit committee says “COSO”, ask which one.
Enterprise risk versus internal control
COSO ERM asks how risk shapes strategy and performance. COSO’s internal control framework asks whether controls over operations, reporting and compliance work. A controls declaration draws on the second kind of question, whichever framework a board cites.
Where ISO 31000 and COSO ERM genuinely differ
Set the caricatures aside. Strip the ISO 31000 vs COSO ERM comparison back to ISO 31000:2018 and COSO Enterprise Risk Management (2017), and four genuine differences remain.
- Starting point. ISO 31000 starts from the risk management process and its integration into the organisation, while COSO ERM starts from governance, culture and strategy. Here is what ISO 31000 looks like applied with intent.
- Appetite. COSO ERM develops risk appetite in depth, while ISO 31000 covers the same ground through the risk criteria an organisation sets for itself. If the terms blur, see how risk appetite differs from risk tolerance.
- How each was made. ISO 31000 is consensus guidance agreed through national standards bodies, and it grew from the Australian and New Zealand standard AS/NZS 4360. COSO ERM was developed under COSO, a joint initiative of five US professional bodies.
- Form. ISO 31000 is a 16-page guideline, while COSO ERM is a longer framework with a separate compendium of examples.
Similarities between ISO 31000 and COSO ERM
Both are principles-based. Both put risk inside strategy and decision-making rather than beside it. Both treat risk management as a continuous cycle with built-in review. Neither offers accredited certification to organisations, and neither tells you who owns the risk in front of you.
ISO 31000 vs COSO: three questions that settle the choice
You do not need to rank ISO 31000:2018 against COSO Enterprise Risk Management (2017) or COSO’s internal control framework (2013). You need three answers.
1. Who will test the framework?
These are the people who will ask you to defend it: the audit committee, internal audit or a parent group. If any of them already work in COSO’s terms, that pulls you towards COSO’s frameworks. If none of them does, nothing pulls you away from ISO 31000. It helps to know what directors need to see in a risk report.
2. What must it connect to?
If you run ISO 9001, ISO 14001 or ISO 45001, ISO 31000 fits with little translation. Those are requirements standards an organisation can be certified against, and ISO 31000 is guidance that shares their vocabulary. If the framework must support a controls declaration, that points towards COSO’s internal control framework. If the board wants risk tied explicitly to strategy and performance, that points towards COSO ERM.
3. What does your sector already reference?
Look at what you must be consistent with: regulator guidance, government policy, funding conditions and client contracts. In parts of Australia’s public sector this is settled for you: Victorian Government agencies must have a framework consistent with AS ISO 31000:2018. UK central government bodies work to HM Treasury’s Orange Book. Groups with US listings or US parents may find COSO’s internal control framework is already the reference. If nothing names a standard, this question is neutral.
If nothing points to COSO. Choose ISO 31000:2018. If no one who tests your framework works in COSO’s terms, and you have no controls declaration to support, ISO 31000 is the simpler foundation. You can map COSO’s terms in later if an answer changes.
If your answers split. One defensible arrangement, not the only one: ISO 31000:2018 for principles, structure and process; COSO ERM’s appetite language in board reporting; and COSO’s internal control framework for material controls where a controls declaration applies. Keep ISO 31000 as the master vocabulary and map COSO’s terms into it at those two points. That is one vocabulary with two translations, not two vocabularies side by side.
Then write the decision down.
Example decision record
Our risk management framework follows ISO 31000:2018 for its principles, structure and process. Board reporting on risk appetite uses the terms of COSO Enterprise Risk Management (2017). Where we assess material controls, we refer to COSO’s internal control framework (2013). We chose this because our safety management system already uses ISO’s vocabulary and our audit committee reviews controls in COSO’s terms. We will revisit the choice only if the answer to one of the three questions changes, such as a new listing, a new parent group or a new regulator.
Put that paragraph in the framework document and stop debating.
Choose once, write down why, and map the other one to it.
ISO 31000 principles and COSO ERM components
Both documents set out their core ideas as short, labelled lists. The mapping table in the next section draws on both.
What are the 8 principles of ISO 31000?
ISO 31000:2018 names eight principles. Together they describe what effective risk management looks like, rather than how to run it.
- Integrated. Risk management is part of every activity and decision, not a separate exercise.
- Structured and comprehensive. A consistent approach produces results you can compare.
- Customised. The framework and process fit the organisation’s own context and objectives.
- Inclusive. The right stakeholders are involved early enough to shape decisions.
- Dynamic. Risk management anticipates change and responds to it.
- Best available information. Decisions draw on past, present and forward-looking information, with its limits made clear.
- Human and cultural factors. Behaviour and culture shape every stage of managing risk.
- Continual improvement. The framework gets better with each cycle of learning.
What are the 5 components of COSO ERM?
COSO Enterprise Risk Management (2017) groups its 20 principles into five components.
- Governance and culture. The board oversees risk, and the organisation sets its operating structures, culture and core values.
- Strategy and objective-setting. Risk appetite is set alongside the business context, the strategy and its objectives.
- Performance. Risks to objectives are identified, assessed, prioritised and responded to, then viewed as a portfolio.
- Review and revision. The organisation checks how its risk management performs as circumstances change, and improves it.
- Information, communication and reporting. Risk information reaches the people who make decisions, inside and outside the organisation.
How to use ISO 31000 and COSO together
Using ISO 31000 and COSO together is a mapping exercise, not a second framework. Any working framework rests on the six decisions behind a working framework: purpose and scope; governance and ownership; risk appetite and thresholds; assessment, controls and treatment; reporting and management rhythm; and assurance, review and improvement. Each one maps onto ISO 31000:2018 and COSO Enterprise Risk Management (2017).
| Decision | ISO 31000:2018 | COSO ERM (2017) |
|---|---|---|
| Purpose and scope | Context in framework design (5.4.1); scope, context and criteria (6.3) | Strategy and objective-setting: business context (principle 6) |
| Governance and ownership | Leadership and commitment (5.2); roles and accountabilities (5.4.3) | Governance and culture: board oversight and operating structures (principles 1 and 2) |
| Risk appetite and thresholds | Defining risk criteria (6.3.4) | Defines risk appetite (principle 7) |
| Assessment, controls and treatment | Risk assessment (6.4) and risk treatment (6.5) | Performance: identify, assess, prioritise and respond (principles 10 to 14) |
| Reporting and management rhythm | Communication and consultation (6.2); recording and reporting (6.7) | Information, communication and reporting (principles 18 to 20) |
| Assurance, review and improvement | Monitoring and review (6.6); evaluation and improvement (5.6 and 5.7) | Review and revision (principles 15 to 17) |
Keep one register, one control library and one set of evidence, and let the mapping do the translating. Running two vocabularies in separate spreadsheets is how a mapping drifts. Purpose-built risk management software keeps the register, the controls and the evidence in one connected place rather than in parallel files.
Aligned versus certified
You can align your own framework with ISO 31000, COSO ERM or both. No accredited body certifies an organisation against either, so treat any offer to do so with care.
What changes for ISO 31000 and COSO in 2026
As at October 2026, ISO 31000:2018 remains the current edition. Three dated facts matter for anyone weighing ISO 31000 and COSO.
- ISO 31000’s third edition was approved for registration as a draft international standard on 26 October 2026, and no publication date is set. At the next stage, ISO circulates the draft to national standards bodies for comment and vote.
- COSO published From Guidance to Action, practical guidance on applying COSO Enterprise Risk Management (2017), in May 2026 without changing the framework itself.
- Provision 29 declarations apply to listed companies in scope for financial years beginning on or after 1 January 2026.
The practical meaning is simple. Build on the 2018 edition now. Do not delay a framework for a revision whose final text is not agreed.
Common mistakes when choosing between ISO 31000 and COSO
Five mistakes cost more than any real difference between ISO 31000:2018 and COSO’s two frameworks.
- Answering “COSO” without saying which COSO framework is meant.
- Buying, or claiming, a certification that no accredited body offers to organisations for either standard.
- Adopting both standards in full and running two vocabularies side by side.
- Treating the choice of standard as the implementation of the framework, when the real work is the six decisions behind it.
- Reopening the choice whenever a new board member or adviser prefers the other one.
Frequently asked questions
Which is better, ISO 31000 or COSO?
Neither is better in general. Three questions settle the ISO 31000 vs COSO question. Who will test the framework? What must it connect to? What does your sector already reference? If nothing points towards COSO’s frameworks, choose ISO 31000:2018. If the answers split, keep ISO 31000 as the master vocabulary, and map in COSO Enterprise Risk Management (2017) for risk appetite and COSO’s internal control framework (2013) for material controls.
Is ISO 31000 certifiable?
No. ISO 31000:2018 is guidance, not a requirements standard, so there is no accredited certification for organisations against it, and none against either COSO framework. Individuals can complete training certificates, including COSO’s own programmes. ISO management system standards such as ISO 9001 and ISO 45001 are different, because organisations can be certified against those.
Does Provision 29 require the COSO framework?
No. The FRC’s guidance on the UK Corporate Governance Code 2024 sets no framework that companies must follow for the Provision 29 declaration, and it does not define material controls. Many boards will still reference COSO’s internal control framework (2013) when assessing controls. That is a choice each board makes, not a requirement of the Code.
Is COSO only for financial reporting?
No. COSO’s internal control framework (2013) covers operations, reporting and compliance objectives, not only financial reporting. COSO Enterprise Risk Management (2017) goes further, linking risk to strategy and performance across the whole organisation. In any COSO vs ISO 31000 comparison, it is the ERM framework that sits alongside ISO 31000.
Is there a new version of ISO 31000?
Not yet. ISO 31000:2018 is the current edition. A third edition was approved for registration as a draft international standard in October 2026, and no publication date is set. Its final text is not agreed, so build on the 2018 edition now and review your framework against the new edition once it is published.
Settle it, then do the real work. Answer the three questions this week and put the one-paragraph decision record into your framework document. Then the ISO 31000 vs COSO debate is closed. After that, the board asks the same four questions of every material risk, whichever framework you chose. Which objective does it threaten? Which control manages it? What evidence says the control works? What happened when it did not? Clew calls that chain the Golden Thread: the deliberate link from strategic objectives, through material risks and the critical controls that manage them, to the assurance evidence that validates those controls and the actions taken when weaknesses are found. Clew keeps the register, the controls, the assurance evidence and the actions in one connected platform, so the framework works the same way whichever standard your policy cites. See how Clew connects risks, controls and assurance evidence. Your next step: read the practical guide to building a framework people use. It takes you through the six decisions that make any framework work, whichever standard it cites.
Sources
Primary sources relied on in this article. Last reviewed: 16 Nov 2026.
- ISO, ISO 31000:2018, Risk management: Guidelines.
- ISO, ISO/CD 31000, third edition project page.
- COSO, Enterprise Risk Management guidance.
- COSO, Internal Control guidance.
- COSO, From Guidance to Action announcement, May 2026.
- FRC, guidance for the UK Corporate Governance Code 2024.
- FRC, Provision 29 Mythbuster.
- HM Treasury, The Orange Book: Management of Risk, Principles and Concepts.
- Victorian Department of Treasury and Finance, Victorian Government Risk Management Framework, September 2025.
- Standards Australia, catalogue entry for AS/NZS ISO 31000:2009.
Related resources
- See what the 2024 UK Corporate Governance Code asks of boards on risk, control and assurance.
- Turn your framework into a working plan with our step-by-step guide to writing a risk management plan.
- Go deeper with our white paper on tracing objectives through to assurance evidence.
- Prepare for the boardroom with our white paper on reporting risk to the board.
- Compare platforms with a structured buyer’s guide for risk management software.
- Benchmark your organisation with the free risk maturity assessment.

