Compare / COSO (Committee of Sponsoring Organizations of the Treadway Commission)
COBIT 7 vs COSO
COSO and COBIT meet wherever internal control depends on technology, which today means almost everywhere. COSO sets the criteria for judging internal control across the whole entity. COBIT 7 describes how information and technology should be governed and managed, including the IT controls that financial reporting relies on.
The short answer
COSO Internal Control: Integrated Framework (2013) defines what an effective system of internal control looks like for the whole entity, across operations, reporting and compliance, and is the usual basis for SOX assessments. COBIT 7 defines how to govern and manage enterprise information and technology. COSO sets the control criteria, COBIT supplies the IT detail beneath them.
COSO has two frameworks in force: the 2013 internal control framework, with 5 components and 17 principles, and the 2017 enterprise risk management framework, with 5 components and 20 principles. Neither has been revised since. What COSO published from 2023 to 2026, on sustainability reporting, robotic process automation, generative AI and board oversight, is supplemental guidance.
ISACA describes the two as complementary. Its official mappings are historical: a 2003 Sarbanes-Oxley guide that related COBIT processes to COSO components, and a 2014 white paper that related the 2013 COSO framework to COBIT 5. No official mapping between COSO and COBIT 2019 or COBIT 7 was found.
At a glance
| COBIT 7 | COSO Internal Control (2013) | |
|---|---|---|
| Owner | ISACA, a professional association | COSO, formed in 1985 by five US bodies: AAA, AICPA, FEI, IIA and IMA |
| Current version | COBIT 7, released 19 November 2026 | Released in 2013; the 1992 edition was superseded on 15 December 2014 |
| Recent publications | Replaces COBIT 2019, with objective identifiers and names unchanged | Supplemental guidance only (2023 to 2026): sustainability reporting, RPA, generative AI, board oversight |
| Enterprise risk | I&T risk covered by EDM03 Ensured Risk Optimization and APO12 Managed Risk | Separate ERM framework (2017): 5 components, 20 principles, linking risk to strategy and performance |
| Type and scope | Governance and management framework for enterprise I&T | Principles-based framework for entity-wide internal control over operations, reporting and compliance |
| Structure | 40 objectives in 5 domains, 231 practices, 2,507 activities, 7 components, 13 design factors | 5 components, 17 principles, each supported by points of focus that serve as guidance |
| Who it is for | Boards, executives, IT management, risk, IT audit and assurance | Boards, management, controllers, internal and external auditors |
| Assessment | Three tiers: board-level maturity, high-level achievement, detailed capability | Components and relevant principles present and functioning, and the five components operating together |
| Regulatory role | Not required for SOX; used for IT control detail and IT general controls | Recognized by the SEC as meeting its criteria for SOX 404 assessments, though no framework is mandated |
| Certification | People only: COBIT 7 Foundation. No certification of organizations | Individual certificates of completion after an online exam. No certification of organizations |
| Cost and access | Digital platform with free basic access | Framework sold by COSO, with multi-user licensing; executive summary and FAQs listed separately |
| How it treats the other | Official ISACA mapping last done in 2014, against COBIT 5 | No COSO statement naming COBIT was found |
How they differ
Whole entity versus I&T
COSO covers internal control over every activity of the entity, grouped into operations, reporting and compliance objectives. COBIT 7 covers the governance and management of information and technology. Where COSO asks whether internal control is effective, COBIT 7 asks how I&T should be directed, run and monitored, including the IT controls that support COSO.
Principles versus objectives and practices
COSO is deliberately principles-based: 17 principles under 5 components, with points of focus that guide judgment but are not required criteria and are not meant as a checklist. COBIT 7 goes much further down, from 40 objectives to 231 practices and 2,507 activities, with one accountable role per practice. That depth is why IT audit teams use COBIT to build control detail under COSO.
Regulatory weight under SOX
The SEC requires management to assess internal control over financial reporting against a suitable, recognized framework and to name it in the report. In 2003 it stated that COSO meets its criteria, while making clear that no particular framework is mandated. Under PCAOB AS 2201 the auditor uses the same framework as management. No regulator names COBIT as the SOX framework.
How effectiveness is judged
Under COSO, internal control is effective when each component and relevant principle is present and functioning and the five components operate together; a major deficiency rules out that conclusion. For SOX, the SEC and PCAOB terms significant deficiency and material weakness apply instead. COBIT 7 assesses through three tiers, from board-level maturity to detailed capability of practices at levels 1 to 5.
Depth on technology
COSO deals with technology mainly in principle 11, on general control activities over technology, whose points of focus cover infrastructure, security management, and acquisition, development and maintenance. It also touches information quality and segregation of duties. COBIT 7 spreads the same territory across many objectives, from change and configuration to operations, security and data.
Stable frameworks, new guidance
COSO has not revised either framework since 2013 and 2017. Its recent output applies the existing frameworks: sustainability reporting controls (2023), robotic process automation (2024), generative AI (February 2026) and 12 guiding principles for board oversight (March 2026), issued after a 2025 governance framework draft was withdrawn. COBIT 7, by contrast, is a new version released in November 2026.
Where they overlap
This table is our own reading. ISACA has published no mapping between COSO and COBIT 2019 or COBIT 7; its official work relates COBIT processes to COSO components (2003) and the 2013 COSO framework to COBIT 5 (2014), and those references are cited in the notes where they support a row. Each row shows COBIT 7 objectives that cover similar territory to a COSO principle, which is not equivalence and does not mean that applying COBIT satisfies COSO or SOX.
| COSO | COBIT 7 objectives | Origin |
|---|---|---|
| Principle 1: commitment to integrity and ethical values Governance principles, culture and policies. COBIT addresses I&T, not the ethics of the whole entity. | Our reading | |
| Principle 2: board independence and oversight of internal control | Our reading | |
| Principle 3: structures, reporting lines and authorities APO01 practices 04 (organizational structures) and 05 (roles and responsibilities). | Our reading | |
| Principle 4: attracting, developing and retaining competent people APO01 practice 08 defines target skills and competencies. | Our reading | |
| Principle 5: accountability for internal control responsibilities | Our reading | |
| Principle 6: objectives specified clearly enough to assess risk COBIT covers I&T objectives only, not entity financial reporting objectives. | Our reading | |
| Principle 7: identifying and analyzing risk The ISACA 2003 Sarbanes-Oxley guide listed risk assessment among the COBIT processes to consider for COSO. | Our reading | |
| Principle 8: considering the potential for fraud Weak overlap: COBIT has no dedicated fraud objective. | Our reading | |
| Principle 9: identifying and assessing significant change Partial: BAI06 covers IT changes only. | Our reading | |
| Principle 10: selecting and developing control activities | Our reading | |
| Principle 11: program development and program changes IT general control area named in SEC Release 33-8810 (2007) and in the points of focus of principle 11. | Our reading | |
| Principle 11: computer operations and technology infrastructure IT general control area named in SEC Release 33-8810 (2007) and in the points of focus of principle 11. | Our reading | |
| Principle 11: access to programs and data, security management IT general control area named in SEC Release 33-8810 (2007) and in the points of focus of principle 11. | Our reading | |
| Principle 12: control activities deployed through policies and procedures APO01 practice 09 defines and communicates policies and procedures. | Our reading | |
| Principle 13: obtaining and using quality information | Our reading | |
| Principles 14 and 15: internal and external communication on internal control | Our reading | |
| Principle 16: ongoing and separate evaluations The ISACA 2003 Sarbanes-Oxley guide listed process monitoring, internal control adequacy and independent assurance for the COSO monitoring component. The link to COBIT 7 objectives is ours. | Our reading | |
| Principle 17: evaluating and communicating deficiencies | Our reading | |
| Compliance objectives category The ISACA 2003 Sarbanes-Oxley guide listed compliance with external requirements among the COBIT processes to consider. | Our reading | |
| COSO ERM (2017), risk integrated with strategy and performance Covers I&T risk only; ERM addresses risk for the whole entity. | Our reading |
Published mapping: taken from a mapping published by the framework owner or by ISACA. Third-party source: taken from a named publication. Our reading: our own comparison at objective level, not an official mapping. Select an objective to open its practices.
Using them together
For a US SEC registrant the usual pattern is COSO at the top and COBIT underneath. Management assesses internal control over financial reporting against the 2013 COSO framework, and the external auditor uses the same framework. COBIT 7 then helps design, run and test the IT general controls that support the financial reporting controls, mainly under principle 11.
Scope stays tied to financial reporting risk. SEC interpretive guidance from 2007 says management needs to evaluate only the IT general controls that other financial reporting controls depend on, not those that mainly serve operational efficiency. COBIT 7 covers much more than that, so an organization using it for SOX selects the objectives and practices that matter for that scope.
Beyond SOX, COSO ERM and COBIT 7 fit the same way: ERM frames risk for the whole entity and its strategy, while EDM03 and APO12 handle I&T risk within that frame. MEA02 Managed System of Internal Control and MEA04 Managed Assurance give the IT function a way to report into the entity-wide monitoring that COSO expects.
Which one do you need?
You need COBIT 7 when
- You must govern and manage I&T across the enterprise, not only its controls
- You need practice-level detail for IT general controls and their owners
- You want to assess I&T capability or maturity in a structured way
- Your IT audit team needs a common reference for control objectives
You need COSO when
- Management must assess internal control over financial reporting under SOX
- You need entity-wide criteria for internal control, beyond IT
- The board wants an enterprise risk framework linked to strategy (COSO ERM)
- Your external auditor attests to internal control against a recognized framework
You need both when
- Financial reporting relies on systems whose general controls must be tested
- Internal audit covers both business process controls and IT
- You want IT control evidence to feed the entity-wide COSO assessment
Questions people ask
Is COBIT required for SOX compliance?
- No. The SEC rules that implement section 404 require management to use a suitable, recognized control framework and to name it in its report, but they do not mandate any particular framework. COSO is the framework the SEC recognized as meeting its criteria. COBIT is widely used to define and test IT general controls under that framework, yet nothing in the SEC or PCAOB material requires it.
Is the COSO framework legally required for SOX?
- Not legally. In its 2003 release the SEC stated that COSO satisfies its criteria for a suitable framework but also that its rules do not mandate one. Its 2007 interpretive guidance mentioned other frameworks as well and encouraged companies to choose one that fits their circumstances. In practice the 2013 COSO internal control framework is the usual choice for US registrants.
Does COBIT 7 replace COSO?
- No. They work at different levels. COSO sets criteria for internal control across the whole entity, while COBIT 7 covers the governance and management of information and technology. ISACA has described the two frameworks as complementary and compatible for assessing and improving internal control. Organizations that use COBIT 7 for IT still need an entity-wide framework such as COSO for a SOX assessment.
Which COSO principle covers IT general controls?
- Principle 11 of the 2013 framework, under the control activities component, deals with general control activities over technology. Its points of focus cover the dependency between business processes and technology general controls, infrastructure, security management, and acquisition, development and maintenance. Other principles touch technology too, notably principle 13 on information quality and principle 10 on segregation of duties.
Must the external auditor use the same framework as management?
- Yes. PCAOB AS 2201 says the auditor should use the same suitable, recognized control framework for the audit of internal control over financial reporting that management uses for its annual evaluation. The standard also treats IT as an integral part of the top-down approach rather than a separate evaluation, so IT general controls are assessed where they support financial reporting controls.
Has COSO released a new framework in 2026?
- No. The 2013 internal control framework and the 2017 enterprise risk management framework are still the COSO frameworks in force. In 2026 COSO published guidance on internal control over generative AI (February), 12 guiding principles for board oversight developed with PwC (March) and a practical ERM paper (May). These apply or supplement the existing frameworks rather than replace them.
Is there an official mapping between COBIT 7 and COSO?
- None was found. ISACA published a white paper relating the 2013 COSO internal control framework to COBIT 5, and earlier IT Control Objectives for Sarbanes-Oxley guides related COBIT processes to COSO components. Because COBIT 7 keeps the COBIT 2019 objective identifiers and names, older references to those objectives still apply, but objectives new since COBIT 5 had no counterpart in those papers.
Can an organization be certified against COSO or COBIT 7?
- No. Neither framework offers certification of organizations. COSO is used as the criteria for management assessments and auditor attestation, for example under SOX section 404. For individuals, COSO offers certificates of completion with an online exam and digital badge, delivered through its sponsoring bodies, and ISACA offers the COBIT 7 Foundation certificate.
What is the difference between COSO internal control and COSO ERM?
- They are two separate COSO frameworks with different purposes that are designed to complement each other. The 2013 internal control framework has 5 components and 17 principles and sets criteria for effective internal control. The 2017 framework, Enterprise Risk Management: Integrating with Strategy and Performance, has 5 components and 20 principles and links risk to strategy setting and performance.
Sources
- Guidance on internal control · COSO
- Enterprise risk management · COSO
- Corporate Governance: Guiding Principles for Board Oversight · COSO
- COSO releases guidance on internal control over generative AI · COSO via PR Newswire
- Internal Control Certificate Program · COSO
- Release 33-8238, management reports on internal control over financial reporting · US Securities and Exchange Commission
- Release 33-8810, interpretive guidance for management · US Securities and Exchange Commission
- AS 2201, audit of internal control over financial reporting · PCAOB
- Relating the COSO Internal Control: Integrated Framework and COBIT · ISACA
- ISACA and IT Governance Institute comment to PCAOB Docket 008 (2003) · PCAOB
- COBIT · ISACA
Checked on 22 November 2026. The COSO frameworks are published by the Committee of Sponsoring Organizations of the Treadway Commission. COBIT is a registered trademark of ISACA. Descriptions are our own wording. For anything you rely on, read the source.