Compare / Center for Internet Security (CIS)
COBIT 7 vs CIS Controls
COBIT 7 and the CIS Critical Security Controls work at different heights. COBIT 7 describes how an enterprise directs, manages and assures all of its information and technology, while the CIS Controls list concrete security actions in priority order. CIS publishes its own mapping between the two, which shows how narrow the shared ground really is.
The short answer
COBIT 7 is ISACA's governance and management framework for all enterprise I&T, with 40 objectives covering strategy, risk, vendors, operations and assurance. The CIS Controls v8.1 are a prescriptive cyber defense checklist: 18 controls and 153 safeguards, each asking for one action. COBIT says what must be governed. CIS says which security tasks to perform first.
The official CIS mapping links 53 of the 153 safeguards to 18 COBIT objectives, and every link is marked "Subset": the COBIT objective is broader than the safeguard. Most links land in DSS05 Managed Security Services. No safeguard maps to the four MEA objectives or to four of the five EDM objectives.
In practice the two fit together as layers. COBIT 7 sets priorities, accountability and target capability levels; the CIS Controls supply the safeguard-level work under the security, asset, data and vendor objectives.
At a glance
| COBIT 7 | CIS Controls v8.1 | |
|---|---|---|
| Owner | ISACA | Center for Internet Security, Inc., a US 501(c)(3) nonprofit |
| Current version | COBIT 7, released 19 November 2026 | v8.1, released June 2024; no later version announced |
| Type of document | Governance and management framework for enterprise I&T | Prescriptive, prioritized set of cyber defense safeguards |
| Scope | All of enterprise I&T, from board direction to operations and assurance | Security of assets, software, data, accounts, networks, people, suppliers and incidents |
| Structure | 40 objectives in 5 domains, 231 practices, 2,507 activities, 7 components | 18 controls, 153 safeguards, each tagged with one asset class and one security function |
| Tailoring | 13 design factors select and prioritize objectives and target capability levels | Implementation groups IG1 (56), IG2 (130) and IG3 (153), chosen by self-assessment |
| Governance content | Core of the framework: the EDM domain plus one accountable role per practice | 25 safeguards tagged Govern since v8.1, all about the security program |
| How performance is assessed | Three tiers: board-level maturity, high-level achievement, detailed capability (1 to 5) | Self-assessment with CIS CSAT; CIS Controls Assessment Specification defines measures |
| Certification of people | COBIT 7 Foundation | None from CIS; GIAC GCCC from SANS covers the Controls |
| Certification of organizations | None | None for user organizations; CIS accredits service providers through CREST |
| Cost and access | Digital platform with free basic access | Free for own use under CC BY-NC-ND 4.0; commercial use needs CIS approval |
| How it treats the other | COBIT 2019 cites CIS Controls v6.1 (2016) as related guidance in 16 practices | Publishes an official mapping of v8.1 safeguards to COBIT 2019 objectives |
How they differ
Governance framework versus control checklist
COBIT 7 covers every part of enterprise I&T, including strategy, portfolio, budget, people, architecture and assurance. Security is one area among many. The CIS Controls cover only cyber defense, and say so: CIS states they are not a replacement for any regulatory, compliance or authorization scheme.
One action per safeguard versus objectives made of components
Each CIS safeguard asks for one thing, such as keeping a software inventory or encrypting data at rest, often with a stated review frequency. A COBIT objective bundles practices, activities, roles, information flows, skills, policies and culture. This is why CIS marks every link in its COBIT mapping as Subset.
Implementation groups are scope, capability levels are performance
CIS implementation groups decide which safeguards apply to an enterprise, based on its risk profile and resources. They do not rate how well a safeguard is done. COBIT capability levels 1 to 5 rate how well the activities of an objective are performed. The two scales answer different questions and should not be converted into each other.
Different basis for the content
CIS builds and prioritizes the Controls from attack data, including the Verizon DBIR and its Community Defense Model based on MITRE ATT&CK. COBIT 7 starts from stakeholder needs and enterprise goals and cascades them to objectives through design factors. One asks what attackers do, the other asks what the enterprise needs from I&T.
Legal recognition and licensing
Several US state safe harbor laws name the CIS Controls, most recently Texas SB 2610 in 2025, which requires IG1 for businesses with 20 to 99 employees seeking protection. COBIT is not in the framework lists seen in our sources. The CIS Controls are free under CC BY-NC-ND 4.0, while COBIT 7 runs on an ISACA platform with free basic access.
Where they overlap
Rows marked as published mapping summarize, control by control, which COBIT objectives the official CIS mapping "Controls v8.1 Mapping to ISACA COBIT 19" (January 2025) points to. The CIS mapping works at objective level, so this table does not reach COBIT practices, and it does not reproduce the individual CIS rows. Because COBIT 7 kept the COBIT 2019 objective identifiers, each objective listed still exists in COBIT 7; CIS has not published anything that names COBIT 7.
| CIS Controls | COBIT 7 objectives | Origin |
|---|---|---|
| 1. Inventory and Control of Enterprise Assets Summarized from the CIS v8.1 mapping to COBIT 2019. 2 of 5 safeguards mapped. | Published mapping | |
| 2. Inventory and Control of Software Assets Summarized from the CIS v8.1 mapping to COBIT 2019. 2 of 7 safeguards mapped. | Published mapping | |
| 3. Data Protection Summarized from the CIS v8.1 mapping to COBIT 2019. 10 of 14 safeguards mapped. | Published mapping | |
| 4. Secure Configuration of Enterprise Assets and Software Summarized from the CIS v8.1 mapping to COBIT 2019. 4 of 12 safeguards mapped. | Published mapping | |
| 5. Account Management The CIS mapping has no entry for this control. Our reading: identity and access management falls under DSS05 and DSS06, which COBIT 2019 related guidance also linked to the older CIS v6.1 account and privilege controls. | Our reading | |
| 6. Access Control Management The CIS mapping has no entry for this control. Our reading: access granting, revoking and privileges belong with DSS05 and DSS06, where COBIT 2019 cited CIS v6.1 access controls. | Our reading | |
| 7. Continuous Vulnerability Management Summarized from the CIS v8.1 mapping to COBIT 2019. 4 of 7 safeguards mapped. | Published mapping | |
| 8. Audit Log Management Summarized from the CIS v8.1 mapping to COBIT 2019. 1 of 12 safeguards mapped. | Published mapping | |
| 9. Email and Web Browser Protections Summarized from the CIS v8.1 mapping to COBIT 2019. 4 of 7 safeguards mapped. | Published mapping | |
| 10. Malware Defenses Summarized from the CIS v8.1 mapping to COBIT 2019. 3 of 7 safeguards mapped. | Published mapping | |
| 11. Data Recovery Summarized from the CIS v8.1 mapping to COBIT 2019. 1 of 5 safeguards mapped. | Published mapping | |
| 12. Network Infrastructure Management Summarized from the CIS v8.1 mapping to COBIT 2019. 3 of 8 safeguards mapped. | Published mapping | |
| 13. Network Monitoring and Defense Summarized from the CIS v8.1 mapping to COBIT 2019. 1 of 11 safeguards mapped. | Published mapping | |
| 14. Security Awareness and Skills Training Summarized from the CIS v8.1 mapping to COBIT 2019. 4 of 9 safeguards mapped. | Published mapping | |
| 15. Service Provider Management Summarized from the CIS v8.1 mapping to COBIT 2019. 5 of 7 safeguards mapped. | Published mapping | |
| 16. Application Software Security Summarized from the CIS v8.1 mapping to COBIT 2019. 6 of 14 safeguards mapped. | Published mapping | |
| 17. Incident Response Management Summarized from the CIS v8.1 mapping to COBIT 2019. 2 of 9 safeguards mapped. | Published mapping | |
| 18. Penetration Testing Summarized from the CIS v8.1 mapping to COBIT 2019. 1 of 5 safeguards mapped. | Published mapping |
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
The common pattern is to let COBIT 7 decide what matters and the CIS Controls decide what to do. COBIT design factors and the goals cascade set priorities and target capability levels for objectives such as APO13 and DSS05. The chosen CIS implementation group then fixes which safeguards are in scope, and CSAT results become evidence when those COBIT objectives are assessed.
The mapping also shows where CIS stops. It leaves 22 COBIT objectives without any safeguard, including all of MEA and four of the five EDM objectives, so performance monitoring, compliance, assurance, benefits and resource governance must come from COBIT. In the other direction, 100 of the 153 safeguards have no COBIT counterpart in the CIS mapping, which reflects how far below COBIT objectives the safeguards sit.
Two cautions apply. CIS maps conservatively on purpose, so a missing link does not mean the topics are unrelated: Controls 5 and 6 on accounts and access have no mapped safeguard even though COBIT clearly manages identity and access. And implementing all 153 safeguards is no basis for claiming COBIT conformity.
Which one do you need?
You need COBIT 7 when
- The board needs to direct and oversee I&T as a whole, not only security
- You must assign accountability and assess capability across all of I&T
- Audit, assurance and compliance monitoring are part of the brief
- Security has to compete with other I&T priorities for budget and resources
You need the CIS Controls when
- You need a concrete, ordered list of security actions to start with
- Your IT and security staff are limited and IG1 gives a defined minimum
- You operate in a US state whose safe harbor law names the CIS Controls
- You want a free control set with a free self-assessment tool
You need both when
- COBIT already governs I&T and the security objectives need technical depth
- A security team working from CIS must report to the board in governance terms
- Auditors assess DSS05 and related objectives and ask for safeguard-level evidence
Questions people ask
What is the current version of the CIS Controls?
- The current version is CIS Controls v8.1, released in June 2024. It keeps the 18 controls and 153 safeguards of v8 from May 2021, and the implementation groups did not change. The update realigned the security functions with NIST CSF 2.0, added the Govern function, revised the asset classes and expanded the glossary. As of November 2026 CIS has announced no later version; it says only that it is working on ideas for version 9.
Is there an official mapping between the CIS Controls and COBIT?
- Yes, published by CIS. "Controls v8.1 Mapping to ISACA COBIT 19" is an Excel workbook last updated in January 2025, also viewable in the CIS Controls Navigator. It maps 53 of the 153 safeguards to 18 of the 40 COBIT 2019 objectives in 66 entries, all with the relationship "Subset". It works at objective level only, so no COBIT practices such as DSS05.04 appear in it. CIS calls COBIT 2019 "COBIT 19".
Does the CIS mapping work for COBIT 7?
- CIS has not published a mapping that names COBIT 7, and its tools still refer to COBIT 2019. Because COBIT 7 kept the COBIT 2019 objective identifiers and names, every objective in the CIS mapping still exists in COBIT 7. The mapping does not reflect any change ISACA made inside those objectives, such as new activities, and CIS has said nothing about its validity for COBIT 7.
Which COBIT objectives do the CIS Controls not cover?
- In the official CIS mapping, 22 of the 40 COBIT objectives receive no safeguard. They include all four MEA objectives, covering performance, internal control, compliance and assurance, and four of the five EDM objectives; only EDM03 Ensured Risk Optimization is mapped. Strategy, portfolio, budget, human resources, quality and organizational change objectives are also unmapped, along with DSS01 Managed Operations and DSS02 Managed Service Requests and Incidents.
Does COBIT refer to the CIS Controls?
- Yes, but to an old version. COBIT 2019 lists The CIS Critical Security Controls for Effective Cyber Defense, version 6.1 from August 2016, among its references, and cites it as related guidance in 16 management practices, mostly in DSS05 and DSS06, with others in APO07, APO14, BAI09, DSS02 and DSS04. Version 6.1 had 20 controls with different numbering. Whether COBIT 7 has updated these references could not be verified.
Are CIS implementation groups the same as COBIT capability levels?
- No. Implementation groups are self-assessed tiers that decide which safeguards apply: IG1 has 56 safeguards, IG2 adds 74 for 130, and IG3 adds 23 for all 153. They reflect an enterprise's size, resources and risk profile. COBIT capability levels 1 to 5 rate how well the activities of an objective are performed. An enterprise in IG1 can still perform those safeguards at a low or high capability.
If we implement all 153 CIS safeguards, do we comply with COBIT?
- No. COBIT has no conformity scheme for organizations, and the CIS mapping gives no basis for such a claim. Every mapped link is a Subset relationship, meaning the COBIT objective is broader than the safeguard. In addition, 100 safeguards have no COBIT counterpart in the mapping and 22 objectives receive nothing, including all of monitoring, evaluation and assessment. Full CIS implementation supports parts of COBIT, not all of it.
Can an organization be certified against COBIT 7 or the CIS Controls?
- Neither offers certification of user organizations. ISACA certifies people through the COBIT 7 Foundation exam. CIS does not certify organizations that adopt the Controls; it runs a CIS Controls Accreditation for service providers that implement, audit or assess the Controls, delivered with CREST. Individuals can take the GIAC Critical Controls Certification from SANS. Organizations can self-assess with the free hosted version of CIS CSAT.
Sources
- Controls v8.1 Mapping to ISACA COBIT 19 · Center for Internet Security
- The 18 CIS Critical Security Controls · Center for Internet Security
- CIS Critical Security Controls v8.1 · Center for Internet Security
- CIS Controls Implementation Groups · Center for Internet Security
- CIS Controls Navigator · Center for Internet Security
- CIS Controls FAQ · Center for Internet Security
- COBIT · ISACA
- CIS Controls Accreditation · Center for Internet Security
- Texas becomes fifth safe harbor state · Center for Internet Security
- How to construct a governance system from the board level to the code level · ISACA Journal
Checked on 22 November 2026. CIS Controls and CIS Critical Security Controls are registered trademarks of the Center for Internet Security, Inc. COBIT is a registered trademark of ISACA. Descriptions are our own wording. For anything you rely on, read the source.