IT governance framework built on NIST CSF 2.0
For MSPs and in-house IT teams: the six NIST CSF 2.0 Govern categories turned into six short artifacts, a co-managed decision rights table and a 90-day rollout, plus where COBIT 2019, ITIL, ISO/IEC 38500, ISO/IEC 27001, COSO and FAIR fit.
Updated: November 2026
An IT governance framework settles who decides what about technology and how anyone can check those decisions were followed, whether an in-house IT team or an MSP runs the systems. This guide picks the governance layer first, the Govern function in NIST CSF 2.0, then fits the operational frameworks underneath it. It also covers what changed from CSF 1.1 to 2.0 and the NIST updates published since launch, dated so you can tell what's current.
TL;DR
| Question | Short answer |
|---|---|
| What is an IT governance framework? | A documented structure that assigns decision rights, policy ownership, and oversight for technology, kept separate from the day to day management of it. |
| Which one should you start with? | The Govern function in NIST CSF 2.0. Six categories, plain language, and the vocabulary auditors and underwriters already use. |
| What do COBIT and ITIL do then? | They sit underneath. COBIT supplies auditable process detail, ITIL runs service delivery, ISO/IEC 38500 handles board level direction. |
| What changed in CSF 2.0? | A sixth function (Govern), a scope covering every organization, and 22 categories and 106 subcategories, down from 23 and 108 in version 1.1. |
| Is there a newer NIST CSF? | No. As of November 2026, CSF 2.0 is current, and NIST adds guides and profiles around it instead of revising it. |
| What's the first artifact? | A one page decision rights table naming who approves risk acceptance, policy exceptions, and vendor onboarding. |
| Why does this matter commercially? | Cyber insurance applications and buyer security questionnaires can ask about governance controls, so keep the evidence ready. |
| How long to something usable? | 90 days to a defensible v1 if you write artifacts instead of strategy documents. |
What an IT governance framework is
An IT governance framework answers one question in writing: who gets to decide what about technology, and how does anyone know the decisions are being followed. It's a structure of decision rights, policies, and oversight loops. It is not a project plan, a control checklist, or a tool.
The cleanest statement of the split comes from ISO/IEC 38500, the international standard for board level governance of information technology, last revised as ISO/IEC 38500:2024. Governance evaluates, directs, and monitors. Management plans, builds, runs, and reports. A CIO deciding to migrate to Intune is management. The written rule that says migrations above a certain spend need executive sign off, and the quarterly review that checks whether that rule was followed, is governance.
That distinction is where governance work tends to fall apart in smaller organizations. A 40 seat accounting firm has no board, no CIO, and no governance committee. Its IT decisions get made in a hallway by whoever noticed the problem first. In a company that size, the framework's job is to write down the three or four decisions that carry consequence and name a person for each one, without building a committee nobody has time to staff.
For anyone running IT on behalf of clients, the framework does a second job. It draws the line between what the provider decides and what the client decides. Ambiguity there causes a familiar failure in co-managed arrangements: alerts go unacknowledged because both sides assumed the other owned them. In-house IT teams face the same split with business unit leaders and outside vendors.
Why NIST CSF 2.0 changed the starting point
NIST published Cybersecurity Framework 2.0 on February 26, 2024. The headline change was structural. Where version 1.1 had five functions, 2.0 has six: Govern, Identify, Protect, Detect, Respond, Recover, spread across 22 categories and 106 subcategories. Govern is the new one, and it doesn't sit alongside the other five. It sits underneath them and feeds them.
The scope also widened. Version 1.1 was written for critical infrastructure. Version 2.0 is written for everyone, which is why it reads more plainly than COBIT and costs nothing to obtain.
NIST's release announcement described a new focus on governance, meaning how organizations make and carry out informed decisions on cybersecurity strategy, and framed cybersecurity as a major source of enterprise risk for senior leaders to weigh alongside finance and reputation. Kevin Stine, chief of NIST's Applied Cybersecurity Division, described the 2.0 update as an effort to make the framework relevant to a much wider set of users in the United States and abroad.
Cybersecurity Dive's coverage put the practical consequence bluntly: NIST made governance a formal, first class part of cybersecurity rather than an assumed prerequisite. That matters for procurement. Once governance has its own function identifier, a questionnaire can ask for it by name.
The reason to start here rather than with COBIT is availability and vocabulary. CSF 2.0 is free, it's roughly 30 pages of readable outcomes rather than several hundred pages of process reference, and the six function names are already the shared language on insurance applications and vendor security questionnaires. Building governance in a vocabulary your counterparties don't recognize means translating it later.
NIST CSF 2.0 and the Govern function
The governance build in this guide rests on one document, so it helps to know what the NIST CSF 2.0 framework contains, what NIST says Govern is for, what changed from version 1.1, and what NIST has published since.
The NIST CSF 2.0 framework at a glance
CSF 2.0 is published as NIST CSWP 29, a 32 page document with a core of six functions, 22 categories and 106 subcategories. It lists outcomes and leaves the methods to you: in NIST's words, the CSF "does not prescribe how outcomes should be achieved."
| Function | NIST's outcome statement | Where it meets governance |
|---|---|---|
| Govern (GV) | Risk management strategy, expectations, and policy are established, communicated, and monitored | The decision layer this guide builds |
| Identify (ID) | Current cybersecurity risks are understood | Asset, supplier and risk inventories that Govern prioritizes |
| Protect (PR) | Safeguards to manage cybersecurity risks are used | Identity, training, data and platform controls that policy calls for |
| Detect (DE) | Possible attacks and compromises are found and analyzed | Monitoring data that feeds GV.OV metrics |
| Respond (RS) | Actions regarding a detected incident are taken | Incident decisions owned through GV.RR |
| Recover (RC) | Assets and operations affected by an incident are restored | Restore priorities set by GV.OC and GV.RM |
NIST says the functions should be addressed concurrently rather than in sequence. Around the core sit Organizational Profiles (a Current Profile and a Target Profile), Community Profiles for shared use cases, and four Tiers (Partial, Risk Informed, Repeatable, Adaptive) that describe how rigorous an organization's risk governance and management are.
When a small MSP asked r/msp how NIST CSF certification works, the top reply was that there isn't one: CSF is a voluntary framework, and aligning processes, technology and training with it is an iterative process. That's why the evidence you keep carries more weight than any badge.
The Govern function, in NIST's words
The official definition reads: the organization's cybersecurity risk management strategy, expectations, and policy are established, communicated, and monitored. NIST adds that Govern informs how an organization achieves and prioritizes the outcomes of the other five functions, and that governance activities are how cybersecurity gets folded into enterprise risk management (ERM).
Govern holds six categories and 31 subcategories, numbered from GV.OC-01 to GV.SC-10. Those numbered IDs are what an assessor, a questionnaire or a client contract will cite, so use them as the labels in your own evidence folders. NIST also publishes online Implementation Examples for each subcategory, which show what a finished outcome can look like.
What changed from NIST CSF 1.1 to 2.0
| Area | CSF 1.1 (April 2018) | CSF 2.0 (February 2024) |
|---|---|---|
| Title and audience | Framework for Improving Critical Infrastructure Cybersecurity | The NIST Cybersecurity Framework 2.0, for any organization regardless of size, sector or maturity |
| Functions | Five: Identify, Protect, Detect, Respond, Recover | Six, with Govern added |
| Categories and subcategories | 23 and 108 | 22 and 106 |
| Governance outcomes | Spread across Identify (Business Environment, Governance, Risk Management Strategy, Supply Chain Risk Management) | Gathered into Govern, with supply chain risk as GV.SC |
| Profiles | Current and Target Profiles | Organizational Profiles plus Community Profiles and templates |
| Tiers | Four Implementation Tiers | Same four Tiers, described in terms of risk governance and risk management |
| Supporting material | Informative references printed in the core | Online Implementation Examples, Quick-Start Guides, the CSF 2.0 Reference Tool and a searchable catalog mapping to more than 50 documents |
For a governance build, two changes matter most. Decision rights and oversight now have their own outcomes to cite, and the Quick-Start Guides give smaller organizations a short path in, including one written for small businesses.
NIST CSF 2.0 news and updates (as of November 2026)
No new version has been released. CSF 2.0 is still current, and NIST has kept its core stable while publishing guides, profiles and mappings around it, logged on its CSF updates page. The entries most relevant to governance work:
- December 18, 2025. NIST updated IR 8286r1, 8286Ar1 and 8286Cr1 to align with CSF 2.0. The series connects cybersecurity risk to enterprise risk management, the territory of GV.RM.
- January 14, 2026. NIST's National Cybersecurity Center of Excellence held a workshop on the preliminary draft Cyber AI Profile, the NIST Cybersecurity Framework Profile for Artificial Intelligence, and ran working sessions on it through spring 2026. Our guide to AI governance covers the policy side for teams using AI tools today.
- Spring 2026. SP 1308, the CSF 2.0 Quick-Start Guide on cybersecurity, enterprise risk management and workforce management, was published as final.
- 2026. NIST finalized IR 8374 Revision 1, the ransomware Community Profile built on CSF 2.0, and the CSF 2.0 Informative References Quick-Start Guide (SP 1347), which explains how to find and apply mappings between CSF outcomes and other standards.
- October 15, 2026. Comments closed on the draft Quick-Start Guide for using AI for CSF analysis and reporting (SP 1353).
- Open until December 7, 2026. Comments on the initial public draft of SP 800-221 Revision 1, on governing and managing ICT risk programs within an enterprise risk portfolio, aligned with CSF 2.0.
NIST adds to that page throughout the year, so check it before citing a draft as final.
The six Govern categories, translated
Govern breaks into six categories. Each one maps to a question a client executive can answer and an artifact you can produce.
| Category | The question it answers | First artifact to produce |
|---|---|---|
| GV.OC, Organizational Context | What does this business do, who depends on it, and which laws and contracts bind it? | A one page context statement listing regulated data types, contractual security obligations, and critical services. |
| GV.RM, Risk Management Strategy | How much risk is acceptable, and who says so? | A written risk appetite statement with named thresholds for downtime, data loss, and unpatched exposure. |
| GV.RR, Roles, Responsibilities, Authorities | Who owns each cybersecurity outcome, from the top down? | A decision rights table naming an accountable person per outcome, not a department. |
| GV.PO, Policy | Which policies exist, who approves them, and when are they reviewed? | A policy register with owner, approval date, and next review date per policy. |
| GV.OV, Oversight | Is the program producing the outcomes it promised, and how do we know? | A quarterly review agenda with three to five metrics tied to the risk appetite statement. |
| GV.SC, Supply Chain Risk Management | Which third parties can hurt us, and what do we require of them? | A tiered vendor inventory with security requirements attached per tier. |
Read down the artifact column and you have the deliverable list for a first governance build. Six documents, none longer than two pages. That's a very different scope from what "roll out an IT governance framework" usually implies.
GV.SC deserves extra attention because it holds ten of Govern's 31 subcategories and reaches outside the organization to every supplier. A tiered vendor inventory is the entry point, and the mechanics of building one are covered in more depth in our guide to vendor risk management for MSPs.
How the major frameworks fit together
Framework selection often gets presented as a competition, but these frameworks stack, and the useful question is which layer each one occupies.
| Framework | What it governs | Where it plugs into Govern | Effort to adopt |
|---|---|---|---|
| NIST CSF 2.0 | Cyber risk outcomes across six functions | Is the governance layer. Start here. | Low. Free, ~30 pages, no certification body. |
| ISO/IEC 38500 | Board level direction of IT, via evaluate, direct, monitor | Sharpens GV.OV and GV.RR for organizations that have a board | Low, but abstract. Principles, no controls. |
| COBIT 2019 | End to end enterprise IT, governance and management objectives | Supplies auditable process detail under every GV category | High. Large reference model, training oriented. |
| ITIL 4 / ITIL (Version 5) | Service delivery, incident, change, problem | Operationalizes policy set in GV.PO | Medium. Well known to service desk teams. |
| ISO/IEC 27001 | Information security management system | Provides certifiable evidence for GV.PO and GV.OV | High. Audit, surveillance, real cost. |
| COSO | Enterprise risk and internal control, finance led | Aligns GV.RM with the language finance and audit committees use | Medium. Familiar to CFOs, less so to IT. |
| FAIR | Quantified cyber risk in financial terms | Turns GV.RM's risk appetite into dollar figures | Medium to high. Needs data and a trained analyst. |
The pattern: CSF 2.0 sets direction, ITIL and COBIT do the work, ISO 27001 supplies the certificate when a contract demands one, and FAIR converts the whole thing into numbers a CFO will argue with. Picking all of them at once is how governance projects die. Picking CSF 2.0 and one operational partner is how they ship.
AI adds one more layer to the same stack. Our AI governance framework template maps 16 AI controls to NIST AI RMF and ISO/IEC 42001, and it plugs into Govern the same way.
On ITIL versions: PeopleCert launched ITIL (Version 5) in early 2026 and still sells ITIL 4 modules alongside it, so either edition fills the same service delivery layer here. Our ITSM certifications guide compares the two for anyone planning team training.
For a wider survey of the frameworks in this table, including the compliance regimes that sit next to them, see our cybersecurity frameworks list. That post catalogs the landscape. This one is about the decision layer, so treat them as companions rather than substitutes.
Who decides what in a co-managed setup
Governance in a provider relationship breaks down where ownership is ambiguous. Both parties usually have opinions about security. Neither has written down who signs.
A decision rights table fixes that in one page. The version below maps to GV.RR and covers the decisions that carry consequence in a typical co-managed arrangement. In-house IT teams can use the same table, with business unit leaders in the executive column and outside vendors in the provider columns.
| Decision | Client executive | Provider vCIO | Provider technician | Evidence produced |
|---|---|---|---|---|
| Accept a documented risk | Accountable, signs | Recommends and quantifies | Reports the finding | Signed risk acceptance record |
| Grant a policy exception | Approves above threshold | Approves routine exceptions | Requests | Dated exception with expiry |
| Onboard a new SaaS vendor | Approves for tier 1 and 2 | Reviews and tiers | Flags discovery | Vendor tier record |
| Emergency change during an incident | Informed after | Consulted if reachable | Executes, documents within 24 hours | Change record with justification |
| Deviate from the patch window | Approves for production servers | Approves for endpoints | Requests | Patch deviation log |
The point of the evidence column is that governance only counts if it leaves a trail. An underwriter reviewing a claim, or an auditor sampling controls, doesn't want to hear that risk acceptance happens. They want five signed records from the last twelve months.
The other thing this table exposes is discovery. Nobody can approve vendor onboarding for tools they can't see, which is why unsanctioned SaaS quietly breaks GV.OC and GV.SC at the same time. Our write up on how providers find, price, and fix shadow IT covers the discovery side of that problem.
The insurance and procurement payoff
Governance work is hard to fund because the benefit sounds abstract. Insurance and procurement paperwork makes it concrete.
Cyber insurance applications ask who owns security, which policies exist, how vendors are vetted and whether anyone reviews the results. Those are Govern questions. A submission organized around the six CSF 2.0 function names gives underwriters and brokers a structure they recognize, and Govern evidence is how finance and security leaders show board level ownership.
Procurement follows the same pattern. When a security questionnaire arrives from an enterprise buyer or prime contractor, answering "we follow NIST CSF 2.0, here is our Govern evidence pack" beats assembling ad hoc responses for every questionnaire that arrives.
There's a defensive angle too. After an incident, the question shifts from what controls existed to who was responsible for deciding they were sufficient. A dated risk acceptance record signed by a named executive is a materially different position than a shrug.
In an r/msp thread on whether providers should adopt NIST CSF for their own business, the top reply argued that insurers don't move premiums much based on the controls you list, but might not pay a claim if a control you said you had turns out to be missing.
Your first 90 days
Sequence matters more than completeness. Build in this order and each artifact feeds the next.
- Days 1 to 30, context and roles. Write the GV.OC context statement and the GV.RR decision rights table. These two are prerequisites for everything else, and both are interviews rather than research. Two hours with the client executive gets you most of the way.
- Days 31 to 60, risk and policy. Convert the context statement into a GV.RM risk appetite statement with numeric thresholds, then build the GV.PO policy register. Register existing policies as they are, including gaps. An accurate register beats an aspirational one. The register can sit at the front of an IT policy and procedures manual.
- Days 61 to 90, oversight and supply chain. Set the GV.OV quarterly review agenda with three to five metrics, run the first review, and produce the GV.SC tiered vendor inventory. The first review is the point where governance becomes a habit instead of a document.
Anything not on that list, including maturity tier assessments, control mappings, and framework crosswalks, waits until v1 exists and has survived one oversight cycle.
Where governance programs stall
Three patterns show up again and again.
The first is writing strategy instead of artifacts. A 30 page governance charter that names no individuals and produces no records satisfies nobody. If a document doesn't create evidence, it isn't governance.
The second is oversight without data. GV.OV asks whether the program is delivering its promised outcomes. Answering that requires pulling patch compliance, backup verification, and identity hygiene numbers from wherever they live. When those numbers sit in six disconnected consoles with different reporting periods, the quarterly review turns into a data gathering exercise and gets skipped by the third quarter. This is a stack problem wearing a governance costume.
The third is treating the framework as a one time project. CSF 2.0 Organizational Profiles are meant to be revisited as the business changes. A governance package built once and never reopened is a snapshot of a company that no longer exists.
Picking the framework that fits
If you need a defensible governance layer and don't have one, start with CSF 2.0 Govern. If a contract requires a certificate, add ISO/IEC 27001 and keep CSF as the internal structure. If auditors need process level detail, layer COBIT 2019 and its 40 governance and management objectives beneath the categories you've already defined. If the service desk is the weak point, ITIL, in either ITIL 4 or Version 5, addresses delivery rather than governance, so it complements this work.
The tooling question is separate but connected. Govern's oversight category is only as good as the reporting underneath it, and a fragmented stack makes quarterly metrics expensive to produce. That's part of the argument for consolidation. (Disclosure: Flamingo builds OpenFrame.) OpenFrame is open, AI-native infrastructure for IT and security that covers large areas of RMM, patching, PSA ticketing and documentation in one place, so the patch compliance and ticket numbers GV.OV asks for come from one query rather than six consoles. Its agents work inline: Fae resolves support requests and Mingo runs IT operations, which frees technician time for the governance work itself. Pricing is $1 per device per month with 10 million AI tokens included, and there's a 14-day free trial.
OpenFrame doesn't back up data, replace endpoint protection or manage identities, so those tools still belong in your GV.SC vendor inventory. It won't write your risk appetite statement either, but it can keep the quarterly review supplied with current numbers.
Governance is the record you can hand someone twelve months later when they ask who decided, and when, and on what basis. Start with the six artifacts. Everything else is commentary.

Content Marketing Lead
Ohayo! I run content, SEO, social, and community at Flamingo. Before IT, I worked as a correspondent for Ukraine's Public Broadcasting Company and have a Master's in journalism.
Related Content
Frequently Asked Questions
/blog/it-governance-framework
Still deciding?
Ask Mingo answers from our docs and customer stories.