Compare / ISO and IEC
COBIT 7 vs ISO/IEC 27001
ISO/IEC 27001 and COBIT 7 both deal with information security, but at different altitudes. ISO/IEC 27001 specifies a management system for information security that an accredited body can certify. COBIT 7 sets out how the whole of enterprise information and technology is governed and managed, with security as one part of it.
The short answer
ISO/IEC 27001 is an international standard with requirements for an information security management system (ISMS), and organizations can be certified against it. COBIT 7 is ISACA's framework for governing and managing all enterprise I&T, from strategy and investment to security and assurance. It has no certification for organizations, only for people.
The current standard is ISO/IEC 27001:2022 with Amendment 1:2024, which added a climate change consideration to clauses 4.1 and 4.2. Its Annex A lists 93 controls in four themes, and ISO/IEC 27002:2022 explains each one. Since 31 October 2025, every valid certificate refers to the 2022 edition.
The two fit together. In COBIT terms, an ISMS is mainly the implementation of APO13 Managed Security and much of DSS05 Managed Security Services, while COBIT adds board direction, enterprise risk, performance measurement and the parts of I&T that ISO/IEC 27001 does not address.
At a glance
| COBIT 7 | ISO/IEC 27001:2022 with Amd 1:2024 | |
|---|---|---|
| Owner | ISACA | ISO and IEC, prepared by the joint committee ISO/IEC JTC 1/SC 27 |
| Current version | COBIT 7, released 19 November 2026 | Third edition, 25 October 2022, plus Amendment 1 of 23 February 2024 |
| Type of document | Governance and management framework for enterprise I&T | Requirements standard for an information security management system |
| Scope | All enterprise I&T, security being one area among many | Information security within a scope the organization defines, such as a unit, service or site |
| Structure | 40 objectives in 5 domains, 231 practices, 2,507 activities, 7 components | Requirement clauses 4 to 10, plus Annex A with 93 controls in 4 themes |
| Companion guidance | Focus area guidance; COBIT 2019 had one for information security (2020) | ISO/IEC 27002:2022, 152 pages of guidance on each Annex A control |
| Tailoring | 13 design factors that shape the governance system | ISMS scope, risk assessment and the statement of applicability |
| Governance layer | Explicit: the EDM domain for the governing body | Not explicit; ISO/IEC 27014 gives separate guidance on governance of information security |
| Certification of organizations | None | Yes, by accredited certification bodies, never by ISO itself |
| Assessment | Three tiers: board-level maturity, high-level achievement, detailed capability | Conformity audit: two-stage initial audit, yearly surveillance, recertification in year 3 |
| Cost and access | Digital platform with free basic access; premium US$300 members, US$550 others | ISO/IEC 27001 CHF 155, ISO/IEC 27002 CHF 227, the amendment is free |
| How it treats the other | COBIT 2019 cites ISO/IEC 27001 and 27002 (2013) as related guidance | No ISO or IEC statement about COBIT was found |
How they differ
Certifiable standard versus framework
ISO/IEC 27001 states requirements, and an organization that excludes any of clauses 4 to 10 cannot claim conformity. An accredited certification body audits against them and issues a certificate on a three-year cycle. COBIT 7 is guidance to be tailored, assessed through capability and maturity ratings, and there is no certificate an organization can hold for it.
Information security versus all of I&T
ISO/IEC 27001 covers information security inside a scope the organization chooses. COBIT 7 covers benefits, strategy, architecture, portfolio, projects, service operations, compliance and assurance as well. Areas such as investment governance (EDM02, APO05) or organizational change (BAI05) appear in ISO/IEC 27001 only where they affect security.
Governance is explicit only in COBIT
COBIT separates the governing body's work, in the EDM domain, from management. ISO/IEC 27001 asks top management for leadership and commitment in clause 5 but does not set up a governance layer; ISO/IEC 27014 addresses that separately. COBIT therefore gives a board a place to set direction and risk appetite for security alongside the rest of I&T.
How controls are chosen
In ISO/IEC 27001 the organization selects controls through risk treatment, compares them with Annex A so nothing needed is missed, and justifies each inclusion or exclusion in the statement of applicability. COBIT sets target capability levels per objective through design factors and the goals cascade. COBIT 2019 also names the statement of applicability as an activity in APO13.
Pass or fail versus capability
A certification audit ends in a decision, with nonconformities to correct. COBIT 2019 itself notes that formal certification methods tend to use binary ratings, while capability assessment uses a wider scale. COBIT 7 offers three tiers, from board-level maturity down to detailed capability per practice.
Editions and mappings
The only ISACA mapping with public content, the related guidance in COBIT 2019, points to the 2013 editions at clause level, not control by control. The 2022 Annex A was restructured from 114 controls to 93, with 11 new, 24 merged and 58 updated. COBIT 7 includes mappings on its platform, but their content is not public.
Where they overlap
Rows marked as a published mapping come from the related guidance tables of COBIT 2019, which cite ISO/IEC 27001:2013 and 27002:2013 clauses against COBIT practices. COBIT 7 keeps the same objective identifiers, so the pairs still point at the same objectives; where a 2022 Annex A number is shown, the translation from the 2013 clause is ours. Third-party rows come through the NIST CSF 1.1 informative references, and the rest is our reading.
| ISO/IEC 27001 | COBIT 7 objectives | Origin |
|---|---|---|
| The management system as a whole (clauses 4 to 10) ISACA, COBIT 2019 Framework: Governance and Management Objectives (2018), related guidance, written against ISO/IEC 27001:2013 and 27002:2013. ISO/IEC 27001 is cited in full at the practice for designing the management system for enterprise I&T. | Published mapping | |
| The ISMS seen as one security objective APO13 practices use ISMS terms (scope, risk treatment plan, statement of applicability, audits, management review), yet COBIT 2019 prints no ISO/IEC 27001 reference for them. | Our reading | |
| Clause 5.1 Leadership and commitment No published reference. None of the five EDM objectives cites ISO/IEC 27001 in COBIT 2019. | Our reading | |
| Clauses 5.2 Policy and 7.3 Awareness ISACA, COBIT 2019 Framework: Governance and Management Objectives (2018), related guidance, written against ISO/IEC 27001:2013 and 27002:2013. Cited for the policy and the culture components of APO13. | Published mapping | |
| Clause 5.3 Roles, responsibilities and authorities ISACA, COBIT 2019 Framework: Governance and Management Objectives (2018), related guidance, written against ISO/IEC 27001:2013 and 27002:2013. Cited for the organizational structures component. | Published mapping | |
| Clauses 6.1 and 8.2 Risk assessment and treatment ISACA, COBIT 2019 Framework: Governance and Management Objectives (2018), related guidance, written against ISO/IEC 27001:2013 and 27002:2013. Cited at the practices Analyze risk and Respond to risk. | Published mapping | |
| Clause 7.2 Competence ISACA, COBIT 2019 Framework: Governance and Management Objectives (2018), related guidance, written against ISO/IEC 27001:2013 and 27002:2013. Cited at the practice on skills and competencies of personnel. | Published mapping | |
| Clauses 9.1 Monitoring and 9.3 Management review ISACA, COBIT 2019 Framework: Governance and Management Objectives (2018), related guidance, written against ISO/IEC 27001:2013 and 27002:2013. 9.1 at Establish a monitoring approach, 9.3 at Perform control self-assessments. | Published mapping | |
| Clause 9.2 Internal audit ISACA, COBIT 2019 Framework: Governance and Management Objectives (2018), related guidance, written against ISO/IEC 27001:2013 and 27002:2013. Cited at the two practices that execute the assurance initiative. | Published mapping | |
| Annex A 5.9 to 5.11 Assets ISACA, COBIT 2019 Framework: Governance and Management Objectives (2018), related guidance, written against ISO/IEC 27001:2013 and 27002:2013. The 2022 control numbers are our translation of the 2013 clause cited. | Published mapping | |
| Annex A 5.15 to 5.18 and 8.2 to 8.5 Access control ISACA, COBIT 2019 Framework: Governance and Management Objectives (2018), related guidance, written against ISO/IEC 27001:2013 and 27002:2013. The 2022 control numbers are our translation of the 2013 clause cited. | Published mapping | |
| Annex A 5.19 to 5.22 Suppliers and ICT supply chain ISACA, COBIT 2019 Framework: Governance and Management Objectives (2018), related guidance, written against ISO/IEC 27001:2013 and 27002:2013. The 2022 control numbers are our translation of the 2013 clause cited. | Published mapping | |
| Annex A 5.24 to 5.28 and 6.8 Incident management ISACA, COBIT 2019 Framework: Governance and Management Objectives (2018), related guidance, written against ISO/IEC 27001:2013 and 27002:2013. The 2022 control numbers are our translation of the 2013 clause cited. | Published mapping | |
| Annex A 5.29, 8.13 and 8.14 Continuity, backup, redundancy ISACA, COBIT 2019 Framework: Governance and Management Objectives (2018), related guidance, written against ISO/IEC 27001:2013 and 27002:2013. The 2022 control numbers are our translation of the 2013 clause cited. | Published mapping | |
| Annex A 5.31 to 5.36 Legal requirements and compliance ISACA, COBIT 2019 Framework: Governance and Management Objectives (2018), related guidance, written against ISO/IEC 27001:2013 and 27002:2013. The 2022 control numbers are our translation of the 2013 clause cited. | Published mapping | |
| Annex A 6.1 to 6.5 People controls ISACA, COBIT 2019 Framework: Governance and Management Objectives (2018), related guidance, written against ISO/IEC 27001:2013 and 27002:2013. The 2022 control numbers are our translation of the 2013 clause cited. | Published mapping | |
| Annex A 7.1 to 7.14 Physical controls and 8.20 to 8.22 Network security ISACA, COBIT 2019 Framework: Governance and Management Objectives (2018), related guidance, written against ISO/IEC 27001:2013 and 27002:2013. The 2022 control numbers are our translation of the 2013 clause cited. | Published mapping | |
| Annex A 8.25 to 8.33 Secure development and testing ISACA, COBIT 2019 Framework: Governance and Management Objectives (2018), related guidance, written against ISO/IEC 27001:2013 and 27002:2013. The 2022 control numbers are our translation of the 2013 clause cited. | Published mapping | |
| Annex A 8.8 Vulnerabilities, 8.9 Configuration, 8.15 Logging NIST Cybersecurity Framework 1.1 (2018) lists COBIT 5 and ISO/IEC 27001:2013 Annex A as informative references on the same subcategory. Shared relevance, not equivalence; shown here at COBIT 7 objective level. | Third-party source | |
| Annex A 5.7 Threat intelligence and 8.16 Monitoring (new in 2022) No 2013 ancestor, so no COBIT 2019 reference exists. | 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
A common arrangement is to govern I&T as a whole with COBIT and to run information security through an ISMS built to ISO/IEC 27001. COBIT supplies board direction, risk appetite, enterprise risk management and performance measurement (EDM, APO12, MEA). The ISMS then becomes the working implementation of APO13 and much of DSS05.
The ISACA Germany Chapter guide on ISO/IEC 27001:2022 takes this view: objectives for the ISMS are derived from corporate objectives with COBIT or COSO, and detailed security domains can come from ISO/IEC 27002. ISACA Journal authors describe the same layering, with COBIT at the strategic level and ISO/IEC 27001 and 27002 at the operational level.
In our reading, evidence prepared for a certification audit, such as the risk assessment, statement of applicability, internal audit reports and management review records, can also feed a COBIT capability assessment of APO13, APO12 and the MEA objectives. The reverse holds too: an organization with COBIT practices in place starts an ISMS project with policies, risk assessments and controls already defined.
Which one do you need?
You need COBIT when
- The board wants oversight of all I&T, not only security
- Investment, value and resource decisions need a governance structure
- You need clear accountability across 40 objectives
- Auditors ask for a capability baseline of IT processes
You need ISO/IEC 27001 when
- A customer, tender or regulator asks for a certificate
- You want an auditable security management system with a defined scope
- Security controls must be selected by risk and justified
- You need external, internationally recognized assurance
You need both when
- Security must be certified and also governed with the rest of I&T
- The CISO reports into an enterprise risk and governance structure
- You want one set of evidence to serve certification and capability assessment
Questions people ask
Is COBIT an alternative to ISO/IEC 27001?
- No. They answer different questions. ISO/IEC 27001 specifies how to establish, run and improve a management system for information security, and it can be certified. COBIT 7 is a framework for the governance and management of all enterprise information and technology, including strategy, investment, projects, operations, compliance and assurance. Information security is one area within COBIT, covered mainly by APO13 Managed Security and DSS05 Managed Security Services. Many organizations use COBIT for overall I&T governance and run their security program as an ISO/IEC 27001 ISMS.
Can an organization be certified against COBIT 7 or ISO/IEC 27001?
- Only against ISO/IEC 27001. An accredited certification body, not ISO, audits the ISMS in a two-stage initial audit, then runs surveillance audits in the first and second years and a recertification audit in the third. Certification is voluntary, although contracts or sector rules can require it. COBIT 7 has no certification scheme for organizations. ISACA certifies people, starting with COBIT 7 Foundation, and organizations can have their capability assessed against COBIT, but that does not produce a conformity certificate.
What is the current version of ISO/IEC 27001?
- ISO/IEC 27001:2022, the third edition, published on 25 October 2022, together with Amendment 1:2024 of 23 February 2024. The amendment adds one sentence and one note on climate change to clauses 4.1 and 4.2, and is free. No 2026 edition exists; the standard published in 2026 is ISO/IEC 27000:2026, the overview and vocabulary document. The transition from the 2013 edition ended on 31 October 2025, and certificates based on the 2013 edition expired or were withdrawn at that date.
How many controls does ISO/IEC 27001 Annex A have, and must all be implemented?
- Annex A of ISO/IEC 27001:2022 lists 93 controls in four themes: 37 organizational, 8 people, 14 physical and 34 technological. The 2013 edition had 114 controls in 14 clauses; in 2022, 11 controls were new, 24 were merged from existing ones and 58 were updated. Annex A is a reference list, not a checklist. The organization selects controls through its risk treatment, compares them with Annex A, and records each inclusion or exclusion with its reason in the statement of applicability.
What is the difference between ISO/IEC 27001 and ISO/IEC 27002?
- ISO/IEC 27001 contains the requirements for an ISMS and is the document organizations are certified against. ISO/IEC 27002:2022 is guidance: for each of the 93 controls it gives a purpose, implementation guidance and attributes such as control type, security property and cybersecurity concept. Annex A of 27001 phrases controls with "shall", while 27002 uses "should". Organizations may also draw controls from other sources. In COBIT 2019, most security references at practice level point to ISO/IEC 27002 clauses rather than to 27001.
Does COBIT map to ISO/IEC 27001?
- Partly, and against older editions. COBIT 2019 lists ISO/IEC 27001:2013 and 27002:2013 clauses as related guidance for practices in 18 of its 40 objectives, none of them in the EDM domain. These are pointers to related guidance at clause level, not statements of equivalence. Oddly, the three process practices of APO13 Managed Security carry no ISO/IEC 27001 reference, although they use ISMS terms throughout. COBIT 7 delivers mappings inside its digital platform, but their content is not public.
Which COBIT objectives correspond to an ISMS?
- APO13 Managed Security covers the management system itself and DSS05 Managed Security Services covers most operational controls. Around them, APO12 handles risk assessment and treatment, MEA01, MEA02 and MEA04 cover monitoring, management review and internal audit, DSS02 incidents, DSS04 continuity and backup, BAI02 and BAI03 secure development, APO10 suppliers and BAI09 assets. Most of these links come from COBIT 2019 related guidance; the APO13 link is our reading, since ISACA prints no ISO/IEC 27001 reference for its practices.
Which is better for SOX compliance, COBIT or ISO/IEC 27001?
- Neither is the reference framework for SOX section 404. The SEC requires management to use a suitable, recognized control framework and stated that COSO meets its criteria. COBIT has been used beneath COSO for IT control detail: ISACA's IT Governance Institute published guidance that used COBIT as the basis for IT controls in SOX work. ISO/IEC 27001 certifies a security management system, not internal control over financial reporting. In our reading, a certificate does not replace testing of IT general controls.
How much do COBIT 7 and ISO/IEC 27001 cost?
- ISO/IEC 27001:2022 costs CHF 155 and ISO/IEC 27002:2022 costs CHF 227 in the IEC webstore; Amendment 1:2024 is free. National standards bodies sell adopted versions at their own prices. COBIT 7 is delivered on an ISACA digital platform with free basic access for members and non-members, and premium access costs US$300 for ISACA members and US$550 for non-members. Certification audits, training and assessments are separate costs for both, and are not covered here.
Sources
- ISO/IEC 27001:2022 Information security management systems, Requirements · IEC webstore (ISO and IEC)
- ISO/IEC 27001:2022/Amd 1:2024 Climate action changes · IEC webstore (ISO and IEC)
- ISO/IEC 27002:2022 Information security controls · IEC webstore (ISO and IEC)
- COBIT · ISACA
- ISACA launches updated COBIT 7 with enhanced assessment model and modern digital platform · ISACA, 19 November 2026
- IAF MD 26:2023 Transition requirements for ISO/IEC 27001:2022 · International Accreditation Forum
- SC 27 Journal, 2026 issue 1 · ISO/IEC JTC 1/SC 27
- Release 33-8238, management's report on internal control over financial reporting · US Securities and Exchange Commission
- Framework for Improving Critical Infrastructure Cybersecurity, version 1.1 · NIST
- Navigating the ISO/IEC 27001:2022 transition: a 90-day challenge · ISACA Journal, 2024 volume 3
- Implementation guide ISO/IEC 27001:2022 · ISACA Germany Chapter
- ISO certification statistics (ISO Survey 2025) · Glocal Insight
Checked on 22 November 2026. ISO/IEC 27001 and ISO/IEC 27002 are published jointly by ISO and IEC. COBIT is a registered trademark of ISACA. Descriptions are our own wording. For anything you rely on, read the source.