Compare / National Institute of Standards and Technology (NIST)
COBIT 7 vs NIST CSF
COBIT 7 and the NIST Cybersecurity Framework are often named together, and CSF 1.1 even printed COBIT 5 references throughout its core. CSF 2.0 dropped printed references and no COBIT mapping to it has been published. This page compares the two as they stand in November 2026 and shows how far the older ISACA mapping still carries.
The short answer
COBIT 7 is ISACA's framework for governing and managing all enterprise information and technology, with 40 objectives, practices, roles and capability levels. NIST CSF 2.0 is a free taxonomy of cybersecurity outcomes: 6 functions, 22 categories and 106 subcategories. The CSF states which security outcomes to reach. COBIT describes how the enterprise governs and manages I&T, security included.
The CSF deliberately does not prescribe how outcomes are achieved, and it expects to be used with other frameworks. COBIT 7 supplies that layer for governance: accountable roles, practices, activities and capability assessment. Security is one area of COBIT, mainly APO13 Managed Security and DSS05 Managed Security Services, next to strategy, portfolio, vendors, operations and assurance.
The formal link between them is dated. ISACA's COBIT 2019 OLIR maps to CSF 1.1, and NIST lists no COBIT reference for CSF 2.0. Because COBIT 7 kept the COBIT 2019 objective identifiers, that mapping can still be read forward with care.
At a glance
| COBIT 7 | NIST CSF 2.0 | |
|---|---|---|
| Owner | ISACA | NIST, US Department of Commerce |
| Current version | COBIT 7, released 19 November 2026 | CSF 2.0 (NIST CSWP 29), final 26 February 2024; no later version |
| Type of document | Governance and management framework for enterprise I&T | Taxonomy of cybersecurity outcomes; does not prescribe how to achieve them |
| Scope | All enterprise I&T, with security as one area among 40 objectives | Cybersecurity risk across IT, IoT and OT, meant to sit alongside other enterprise risks |
| Structure | 40 objectives in 5 domains, 231 practices, 2,507 activities, 7 components | 6 functions, 22 categories, 106 subcategories; implementation examples online |
| Tailoring | 13 design factors set priorities and target capability levels | Current and Target Organizational Profiles, plus sector Community Profiles |
| How performance is assessed | Three tiers: board-level maturity, high-level achievement, detailed capability (1 to 5) | Four optional tiers that characterize the rigor of risk governance and management practices |
| Legal status | Voluntary | Voluntary for most; mandatory for US federal agencies under Executive Order 13800 |
| Certification | People only (COBIT 7 Foundation); none for organizations | None from NIST, and no conformity assessment program planned |
| Cost and access | Digital platform with free basic access | Free of charge; CSF 2.0 translated into 11 languages |
| Links to other frameworks | Related guidance inside the framework; appendix C cites CSF 2.0 | Online catalog (OLIR) with 26 informative references for CSF 2.0, none for COBIT |
How they differ
All of I&T versus cybersecurity
COBIT 7 covers strategy, architecture, portfolio, budget, people, vendors, operations, compliance and assurance, with security as one part. The CSF covers cybersecurity risk only, although NIST intends it to be used alongside the management of other enterprise risks. The new GOVERN function brings the CSF closer to COBIT territory, but only for cybersecurity.
Outcomes versus practices and activities
A CSF subcategory states a result, such as an asset inventory being maintained, and NIST says the outcomes are not a checklist of actions. COBIT objectives break down into practices and activities, each practice with one accountable role, plus the other governance components. The CSF leaves the how to informative references; COBIT is one of the frameworks that can supply it.
Tiers versus capability levels
CSF 2.0 says its four tiers characterize the rigor of an organization's cybersecurity risk governance and management practices, and their use is optional. CSF 1.1 stated plainly that tiers do not represent maturity levels. COBIT 7 rates activities at capability levels 1 to 5 and offers three assessment tiers, from board-level maturity to detailed capability. The scales answer different questions and do not convert into each other.
Profiles versus design factors
The CSF works through Current and Target Organizational Profiles, a gap analysis and an action plan, with Community Profiles as shared baselines for a sector or threat. COBIT 7 uses 13 design factors to decide which objectives matter most and what capability to aim for. Both are tailoring methods, applied to different content.
Public guidance versus a professional framework
The CSF is a free US government publication, mandatory for federal agencies and often required by customers in supply chains. COBIT 7 is voluntary and delivered by ISACA on a digital platform. Neither certifies organizations: NIST has no conformity assessment program, and ISACA certifies people, not enterprises.
Where they overlap
No official mapping between COBIT 7 or COBIT 2019 and CSF 2.0 exists, so no row here is a published mapping. Most rows chain two official files ourselves: ISACA's COBIT 2019 OLIR, which maps COBIT 2019 practices to CSF 1.1 subcategories, and NIST's CSF 1.1 to 2.0 crosswalk; objectives are listed by how many CSF 2.0 subcategories in the category reach them, up to five. COBIT 7 kept the COBIT 2019 objective identifiers, so the objectives still exist, but the chain stops at objective level and was not reviewed by ISACA or NIST.
| NIST CSF | COBIT 7 objectives | Origin |
|---|---|---|
| GV.OC Organizational Context Derived from ISACA's COBIT 2019 OLIR mapping to CSF 1.1 via NIST's 1.1 to 2.0 crosswalk; not reviewed by ISACA or NIST. | Third-party source | |
| GV.RM Risk Management Strategy Derived from ISACA's COBIT 2019 OLIR mapping to CSF 1.1 via NIST's 1.1 to 2.0 crosswalk; not reviewed by ISACA or NIST. GV.RM-07 on positive risks is new in 2.0 and reaches no COBIT practice by this route. | Third-party source | |
| GV.RR Roles, Responsibilities, and Authorities Derived from ISACA's COBIT 2019 OLIR mapping to CSF 1.1 via NIST's 1.1 to 2.0 crosswalk; not reviewed by ISACA or NIST. GV.RR-01 on leadership accountability is new in 2.0 and has no derived link. | Third-party source | |
| GV.PO Policy Derived from ISACA's COBIT 2019 OLIR mapping to CSF 1.1 via NIST's 1.1 to 2.0 crosswalk; not reviewed by ISACA or NIST. | Third-party source | |
| GV.OV Oversight New category in CSF 2.0 with no derived link. Our reading: reviewing and adjusting the risk strategy from results resembles the evaluate, direct and monitor practices of EDM01 and EDM03, with MEA01 for performance monitoring. | Our reading | |
| GV.SC Cybersecurity Supply Chain Risk Management Derived from ISACA's COBIT 2019 OLIR mapping to CSF 1.1 via NIST's 1.1 to 2.0 crosswalk; not reviewed by ISACA or NIST. APO10 Managed Vendors is reached from 8 of the 10 subcategories. | Third-party source | |
| ID.AM Asset Management Derived from ISACA's COBIT 2019 OLIR mapping to CSF 1.1 via NIST's 1.1 to 2.0 crosswalk; not reviewed by ISACA or NIST. | Third-party source | |
| ID.RA Risk Assessment Derived from ISACA's COBIT 2019 OLIR mapping to CSF 1.1 via NIST's 1.1 to 2.0 crosswalk; not reviewed by ISACA or NIST. | Third-party source | |
| ID.IM Improvement Derived from ISACA's COBIT 2019 OLIR mapping to CSF 1.1 via NIST's 1.1 to 2.0 crosswalk; not reviewed by ISACA or NIST. Most continuity links land here rather than under RECOVER, following their CSF 1.1 lineage. | Third-party source | |
| PR.AA Identity Management, Authentication, and Access Control Derived from ISACA's COBIT 2019 OLIR mapping to CSF 1.1 via NIST's 1.1 to 2.0 crosswalk; not reviewed by ISACA or NIST. | Third-party source | |
| PR.AT Awareness and Training Derived from ISACA's COBIT 2019 OLIR mapping to CSF 1.1 via NIST's 1.1 to 2.0 crosswalk; not reviewed by ISACA or NIST. | Third-party source | |
| PR.DS Data Security Derived from ISACA's COBIT 2019 OLIR mapping to CSF 1.1 via NIST's 1.1 to 2.0 crosswalk; not reviewed by ISACA or NIST. | Third-party source | |
| PR.PS Platform Security Derived from ISACA's COBIT 2019 OLIR mapping to CSF 1.1 via NIST's 1.1 to 2.0 crosswalk; not reviewed by ISACA or NIST. | Third-party source | |
| PR.IR Technology Infrastructure Resilience Derived from ISACA's COBIT 2019 OLIR mapping to CSF 1.1 via NIST's 1.1 to 2.0 crosswalk; not reviewed by ISACA or NIST. | Third-party source | |
| DE.CM Continuous Monitoring Derived from ISACA's COBIT 2019 OLIR mapping to CSF 1.1 via NIST's 1.1 to 2.0 crosswalk; not reviewed by ISACA or NIST. | Third-party source | |
| DE.AE Adverse Event Analysis Derived from ISACA's COBIT 2019 OLIR mapping to CSF 1.1 via NIST's 1.1 to 2.0 crosswalk; not reviewed by ISACA or NIST. | Third-party source | |
| RS.MA Incident Management Derived from ISACA's COBIT 2019 OLIR mapping to CSF 1.1 via NIST's 1.1 to 2.0 crosswalk; not reviewed by ISACA or NIST. | Third-party source | |
| RS.AN Incident Analysis, RS.CO Reporting and Communication, RS.MI Incident Mitigation Derived from ISACA's COBIT 2019 OLIR mapping to CSF 1.1 via NIST's 1.1 to 2.0 crosswalk; not reviewed by ISACA or NIST. RS.CO reaches DSS03 only. | Third-party source | |
| RC.RP Incident Recovery Plan Execution and RC.CO Incident Recovery Communication Derived from ISACA's COBIT 2019 OLIR mapping to CSF 1.1 via NIST's 1.1 to 2.0 crosswalk; not reviewed by ISACA or NIST. DSS01 and EDM03 come from RC.CO, one subcategory each. | Third-party source | |
| RC.RP-03 to RC.RP-06 backup integrity, restoration and end of recovery New in CSF 2.0 with no derived link. Our reading from COBIT practice names: DSS04.07 Manage backup arrangements and DSS04.08 Conduct postresumption review, with APO14 for data. | 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
NIST expects the CSF to be combined with other frameworks, standards and practices, and ISACA has long positioned COBIT as one of them. A workable split is to let COBIT 7 run the governance system, with accountable roles, priorities set through design factors and capability assessment, while the CSF supplies the cybersecurity outcome language and the Current and Target Profiles that security teams already use.
The derived map shows that every CSF 2.0 category except GV.OV has a COBIT home through ISACA's mapping, with APO12, APO13 and DSS05 appearing almost everywhere and APO10 dominating supply chain risk. Seven objectives never appear: EDM04, EDM05, APO04, APO05, APO06, APO09 and BAI11. Resources, stakeholder engagement, innovation, portfolio, budget, service agreements and projects are COBIT ground that the CSF does not address directly.
ISACA's own material is split across versions. Its 2019 book, Implementing the NIST Cybersecurity Framework Using COBIT 2019, and the OLIR mapping target CSF 1.1, while its 2024 Cybersecurity Audit Program covers the six functions of CSF 2.0. No ISACA publication pairing COBIT 7 with CSF 2.0 was found.
Which one do you need?
You need COBIT 7 when
- The board must direct and oversee all of I&T, not only cybersecurity
- You need accountable roles and capability assessment across I&T processes
- Portfolio, budget, vendors, projects and assurance are in scope
- Security has to compete with other I&T priorities for resources
You need NIST CSF 2.0 when
- You are a US federal agency, or customers or partners require the CSF
- You need a common, free vocabulary for cybersecurity outcomes
- You want Current and Target Profiles to plan security improvements
- You want ready sector baselines through Community Profiles
You need both when
- A CSF program must report to the board in governance terms
- You need practices and roles that deliver the outcomes the CSF names
- Auditors assess CSF outcomes and also review I&T governance
Questions people ask
What is the current version of the NIST CSF?
- The current version is CSF 2.0, published as NIST Cybersecurity White Paper 29 on 26 February 2024 after a draft in August 2023. As of November 2026 there is no CSF 2.1 or 3.0. What 2025 and 2026 brought is companion material around the unchanged core: community profiles such as SP 800-61r3 on incident response, quick-start guides, IR 8286 updates aligned with CSF 2.0 and new informative references. Some NIST pages now say super intelligence (SI) where they used to say AI, so search for both terms when looking for AI-related CSF guides.
Is the NIST CSF mandatory?
- For most organizations, no. NIST is not a regulator, and its FAQ says most organizations use the CSF voluntarily. Executive Order 13800 made the framework mandatory for US federal government agencies, and some companies require it from customers or within their supply chain. CSF 2.0 also widened the intended audience from critical infrastructure to organizations of all sizes and sectors, and its taxonomy is not specific to any country.
Can an organization be certified against the NIST CSF or COBIT 7?
- No. NIST does not certify or endorse CSF implementations, products or services and has no plans for a conformity assessment program. ISACA does not certify organizations against COBIT 7 either; it certifies people through the COBIT 7 Foundation exam. Auditors can still assess an organization against the CSF, for example with ISACA's Cybersecurity Audit Program based on CSF 2.0, which includes a worksheet for subcategory implementation status.
Does the NIST CSF reference COBIT?
- CSF 1.1, from April 2018, printed COBIT 5 as an informative reference across its core, for example BAI09.01 and BAI09.02 against asset inventory. CSF 2.0 prints no references at all and moved them online, and neither NIST's CSF 2.0 reference download nor the OLIR catalog includes COBIT for CSF 2.0. The only COBIT entry in OLIR is ISACA's COBIT 2019 OLIR, which maps to CSF 1.1 and was posted on 26 August 2020.
Can ISACA's COBIT 2019 mapping be used with COBIT 7 and CSF 2.0?
- With care. On the COBIT side it still points at the right objectives, because COBIT 7 kept the COBIT 2019 identifiers. On the CSF side it maps to 1.1, but NIST publishes an official 1.1 to 2.0 crosswalk that carries most links forward. Sixteen of the 106 CSF 2.0 subcategories are new and reach no COBIT practice this way, including the whole GV.OV Oversight category. Neither ISACA nor NIST has reviewed such a chained result.
Are CSF tiers the same as COBIT maturity or capability levels?
- No. CSF 2.0 says its four tiers, Partial, Risk Informed, Repeatable and Adaptive, characterize the rigor of an organization's cybersecurity risk governance and management practices. They are optional and applied to Organizational Profiles. CSF 1.1 stated outright that tiers do not represent maturity levels; CSF 2.0 does not repeat that sentence. COBIT 7 rates activities at capability levels 1 to 5 and adds three assessment tiers, including board-level maturity.
What is the difference between the NIST CSF, SP 800-53 and the AI RMF?
- All three come from NIST, which is why people say "NIST" for each. CSF 2.0 is a voluntary taxonomy of cybersecurity outcomes and does not specify actions. SP 800-53 Rev. 5 is a catalog of security and privacy controls for information systems and organizations; its latest release, 5.2.0, dates from 27 August 2025 and is published as an informative reference to CSF 2.0. The AI RMF 1.0 (NIST AI 100-1, January 2023) is a voluntary framework for AI risks, not cybersecurity in general.
Does the NIST CSF tell us which security controls to implement?
- No. NIST states that the CSF gives outcomes to prioritize and address cybersecurity risks but does not specify actions for meeting them. Implementation examples are available online, but NIST says they are neither complete nor a required baseline. Controls come from informative references such as SP 800-53, ISO/IEC 27001 or the CIS Controls, and governance practices from frameworks such as COBIT 7.
Sources
- NIST CSWP 29: The NIST Cybersecurity Framework (CSF) 2.0 · NIST
- The NIST Cybersecurity Framework (CSF) 2.0, full text · NIST
- Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1 · NIST
- Cybersecurity Framework FAQs · NIST
- Cybersecurity Framework updates archive · NIST
- CSF informative references · NIST
- OLIR informative reference catalog · NIST
- COBIT 2019 OLIR, catalog record · NIST
- SP 800-53 Rev. 5, Security and Privacy Controls · NIST
- AI Risk Management Framework · NIST
- New ISACA resources offer step-by-step guidance for NIST Cybersecurity Framework implementation · ISACA
- Audit and assurance guidance for the NIST Cybersecurity Framework 2.0 and artificial intelligence · ISACA
Checked on 22 November 2026. The NIST Cybersecurity Framework is published by the US National Institute of Standards and Technology, Department of Commerce. COBIT is a registered trademark of ISACA. Descriptions are our own wording. For anything you rely on, read the source.