Flamingo Raises $4.5M Seed Round

Skip to content

Cybersecurity frameworks list for MSPs and IT teams (2026)

Best Practices
Security
MSP
May 11, 2026
2,551 views
Cybersecurity frameworks list for MSPs and IT teams (2026)

For MSPs and in-house IT teams scoping security work: CIS IG1 vs IG2 safeguard counts, CSF 2.0 profiles and tiers, PCI DSS duties for service providers, EU and UK rules, and a control-to-evidence map.


Updated: November 2026

A cybersecurity frameworks list for SMB security work starts with NIST CSF 2.0, CIS Controls v8.1, ISO/IEC 27001, SOC 2, HIPAA, PCI DSS and CMMC, then adds NIS2, DORA, Cyber Essentials and the Essential Eight for organizations operating in the EU, UK and Australia. Each entry below gives the current version (checked November 2026), who it applies to and whether anyone certifies it. MSPs and in-house IT teams can use it to pick a framework per client or business unit, then map controls to the tools already deployed.

TL;DR

  • The short answer. NIST CSF 2.0, CIS Controls, CMMC, ISO 27001 and SOC 2 are the frameworks MSPs and IT teams meet most, with HIPAA and PCI DSS wherever health or card data flows.
  • Pick per client or business unit. Industry and contract terms decide, not preference.
  • Mapping. Controls map onto tools you already run.
  • Common mistake. Treating a framework as a document rather than a control set.
  • Status, November 2026. CIS Controls v8.1 and NIST CSF 2.0 are current, PCI DSS v4.0.1's future-dated requirements have applied since March 31, 2025, and CMMC Phase 2 is suspended pending review.
  • No guarantees. A framework measures posture; only an auditor, assessor or regulator rules on compliance.

What a cybersecurity framework is (and why MSPs get stuck on them)

A cybersecurity framework is a structured set of controls, processes, and outcomes meant to reduce risk to information systems. Some are regulations with the force of law (HIPAA in the US, NIS2 and DORA in the EU). Others are voluntary best-practice guides published by standards bodies (NIST CSF, CIS Controls). A few are contractual requirements imposed by buyers, card brands or government customers (CMMC, SOC 2, PCI DSS).

MSPs hit two recurring problems. First, prospects ask "are we compliant with NIST?" without realizing NIST CSF is not a pass/fail certification. Second, MSP owners assume one framework will cover every client across healthcare, manufacturing, and SaaS, then they sell flat-rate "compliance packages" that collapse when an audit shows up. Frameworks are scoping tools, not products. Treat them that way and the conversation gets shorter.

Internal IT teams meet the same confusion from the other side, when a customer security questionnaire or a cyber insurance application asks which framework the company follows. The answer shapes the next year of work, so it pays to pick deliberately.

The cybersecurity frameworks list MSPs see most often in 2026

The list starts with the eight frameworks that come up across SMB work in the US and Australia, then adds the EU and UK schemes that reach any organization operating in Europe. Each entry carries its current status, checked in November 2026.

NIST Cybersecurity Framework (CSF) 2.0

NIST CSF 2.0 landed in February 2024 and added a sixth function (Govern) to the original five (Identify, Protect, Detect, Respond, Recover). It's the most flexible framework on this list. There's no certification, no auditor, no checklist with pass/fail rows. You assess current state, define a target profile, and close the gap. That makes CSF the right starting point for clients who have nothing in place yet, and the right communication layer when you need to translate technical controls into board-friendly language. Government contractors and critical infrastructure operators get pushed toward CSF because federal agencies reference it in procurement.

The Govern function is the part that catches MSPs off guard. It demands documented roles, risk appetite statements, supply chain risk management, and policy oversight cadence. None of those are tool problems; they're documentation and meeting-cadence problems. Build a quarterly governance review into the client's contract and the function gets handled. Skip it and the next gap assessment scores everything red.

CSF 2.0 breaks the six functions into 22 categories and 106 subcategories, so it reads like a long checklist until you scope it. NIST's answer is the Organizational Profile. A Current Profile records which outcomes the organization meets today, a Target Profile records the outcomes it needs, and the gap between the two becomes the project plan. Tiers 1 to 4 (Partial, Risk Informed, Repeatable, Adaptive) then describe how mature the risk management behind those outcomes is, which helps when a client asks how far to go.

NIST keeps adding free companion material instead of revising the framework itself. The CSF 2.0 resource center holds Quick-Start Guides for common starting points, including one written for small businesses, and the final CSF 2.0 Informative References Quick-Start Guide published in 2026 shows how to find and apply mappings between CSF outcomes and other standards. CSF 2.0 remains the current version two years after its February 2024 release (checked November 2026). For an internal IT team, the Current and Target Profiles double as the board report; for an MSP, they become the scope of work.

CIS critical security controls v8 and v8.1

The Center for Internet Security publishes 18 prioritized controls grouped into three Implementation Groups (IG1, IG2, IG3) based on organizational size and risk tolerance. IG1 is the floor for any SMB, what CIS calls "essential cyber hygiene." Patch management, MFA, endpoint protection, basic logging. For MSPs, CIS is the most operationally useful framework because every control maps to a specific tool action you can verify in an RMM or SIEM console. If a client wants something concrete, start with CIS IG1, then layer NIST CSF on top for governance.

CIS published Controls v8.1 in June 2024 as an iterative update to v8. It keeps the 18 Controls and 153 Safeguards, aligns the mappings with NIST CSF 2.0, adds the Govern security function, revises asset classes and adds glossary definitions for terms like plan, process and sensitive data. CIS still lists v8.1 as the current version (checked November 2026) and keeps v8 and v7.1 available for teams that mapped to them earlier.

The Implementation Groups decide how much of that list a client or business unit takes on, and each group includes everything in the one before it.

Implementation GroupSafeguardsWho it fitsWhat changes for the MSP or IT team
IG156Small and mid-sized organizations with limited IT and security staffEssential cyber hygiene: inventory, patching, MFA, malware defenses, backups
IG256 plus 74 (130 total)Organizations with dedicated IT staff, several departments and some regulatory burdenAdds Safeguards that depend on enterprise-grade tools and specialist setup, such as centralized audit logs
IG3All 153Organizations with security specialists and sensitive data or functions under regulatory oversightAdds the remaining Safeguards, such as threat modeling and internal penetration tests

The CIS Controls are free for any organization to use on its own environment. MSPs and consultants that deliver them inside a paid service are asked to join CIS SecureSuite as a Consulting or Product Vendor member, or to become an authorized Supporter, so check CIS's terms before you package an IG1 offering.

Here are the 18 Controls, with the evidence that typically shows each one is working.

#CIS ControlTypical evidence
1Inventory and Control of Enterprise AssetsDevice inventory from the RMM or MDM
2Inventory and Control of Software AssetsInstalled software report, approved software list
3Data ProtectionData inventory, encryption status
4Secure Configuration of Enterprise Assets and SoftwareConfiguration baselines, CIS Benchmark scan results
5Account ManagementAccount list from the identity provider, dormant account reviews
6Access Control ManagementMFA enrollment, access review records
7Continuous Vulnerability ManagementPatch compliance and vulnerability scan reports
8Audit Log ManagementLog retention settings, log review records
9Email and Web Browser ProtectionsEmail filtering and DNS filtering settings
10Malware DefensesAnti-malware or EDR coverage by device
11Data RecoveryBackup job history, restore test results
12Network Infrastructure ManagementFirewall and switch firmware and configuration records
13Network Monitoring and DefenseAlert history from network monitoring or the SIEM
14Security Awareness and Skills TrainingTraining completion records
15Service Provider ManagementVendor inventory and contract terms
16Application Software SecuritySecure development records, where the organization builds software
17Incident Response ManagementIncident response plan, incident ticket history
18Penetration TestingTest reports and remediation tickets

CMMC 2.0

The Cybersecurity Maturity Model Certification 2.0 applies to Department of Defense contractors and subcontractors. Three levels: Foundational (Level 1, self-assessment), Advanced (Level 2, self-assessment or third-party C3PAO assessment depending on the contract, for handling Controlled Unclassified Information), and Expert (Level 3, government-led). The program rule took effect on December 16, 2024, and Phase 1, which puts self-assessment requirements into new contracts, started on November 10, 2025. On July 13, 2026 the Pentagon suspended Phase 2, the C3PAO assessment requirements due on November 10, 2026, while a CMMC Reform Task Force reviews the program; Phase 1 self-assessments and DFARS 252.204-7012 obligations still apply (checked November 2026). If you serve any defense supply chain client, even a tier-three machine shop making bolts, CMMC will come up. Skip it for clients with no federal exposure.

Our CMMC compliance guide walks through the levels, the NIST SP 800-171 controls behind Level 2 and the self-assessment score a contractor reports.

ISO/IEC 27001 and 27002

ISO 27001 is the international standard for an Information Security Management System (ISMS). It's certifiable, audited annually, and recognized globally, which is why SaaS clients pursuing international enterprise deals want it. ISO 27002 is the companion document listing the specific controls (93 in the 2022 edition, mirrored in ISO 27001's Annex A and grouped into four themes: organizational, people, physical and technological, down from 114 in the 2013 edition). The big lift for an SMB pursuing ISO 27001 isn't the controls. It's the documented management system, internal audits, and management reviews. MSPs that win this work bring a virtual CISO function alongside the tooling, and they price the engagement around documentation hours, not license seats. Certification bodies expect a defined Statement of Applicability, recorded management reviews at planned intervals, and evidence that internal audits produced findings the company addressed.

For AI systems, ISO/IEC 42001 sets up the same kind of management system, and our AI governance framework template maps its clauses to day-to-day controls.

The transition from the 2013 edition closed on October 31, 2025, and 2013 certificates lost validity that day, so a client still holding one needs a full ISO/IEC 27001:2022 certification audit rather than a transition audit (checked November 2026). Internal IT teams can scope a first certification to one business unit, which keeps the Statement of Applicability manageable.

SOC 2 (Trust Services Criteria)

SOC 2 reports come from CPA firms following AICPA standards, not from a security body. There are two flavors: Type 1 (point-in-time control design) and Type 2 (operating effectiveness over a 6-12 month window). The five Trust Services Criteria are Security, Availability, Processing Integrity, Confidentiality, and Privacy. Security is the only required category; SMB SaaS clients add Availability or others when their customers ask. SOC 2 is the dominant framework for B2B SaaS in North America; if your client sells software to enterprises, expect SOC 2 to come up in every procurement cycle.

Our SOC 2 compliance guide covers the audit steps, from readiness assessment to the Type 2 observation window.

HIPAA Security Rule

The HIPAA Security Rule applies to covered entities and business associates handling protected health information (PHI). It splits controls into Administrative, Physical, and Technical Safeguards. There's no certification, enforcement comes through HHS Office for Civil Rights audits, often triggered by a breach notification. The proposed HIPAA Security Rule update published in January 2025 would remove the "addressable" implementation specification flexibility and tighten encryption, MFA, and incident response requirements. HHS's regulatory agenda now projects final action for July 2027 (checked November 2026), so the current rule stays in force until then. MSPs serving medical practices, dental offices, behavioral health groups, or any vendor touching PHI need to track this update closely. The annual risk analysis is the most-cited audit deficiency under HIPAA; if you sign a Business Associate Agreement, you owe a risk analysis of your own systems that handle ePHI, separate from the covered entity's, and "we did one last year" doesn't satisfy an OCR reviewer.

PCI DSS v4.0.1

PCI DSS v4.0.1 has been the only active version since v4.0 retired on December 31, 2024, and the 51 future-dated requirements (including the contentious anti-script controls in 6.4.3 and 11.6.1) became mandatory on March 31, 2025 (checked November 2026). Twelve top-level requirements covering network security, access control, monitoring, and policy. Self-assessment via SAQ for smaller merchants, on-site Qualified Security Assessor audit for Level 1. Any client that processes, stores, or transmits cardholder data falls under PCI, including retail clients, restaurants, and SaaS billing platforms. A January 2025 revision of SAQ A dropped 6.4.3 and 11.6.1 for e-commerce merchants that fully outsource their payment pages, replacing them with an eligibility check that the merchant's site isn't open to script attacks.

Essential Eight (Australia)

The Australian Signals Directorate's Essential Eight is the most operationally tight framework on the list. Eight mitigation strategies (application control, patch applications, configure Microsoft Office macro settings, user application hardening, restrict administrative privileges, patch operating systems, MFA, regular backups) at four maturity levels (0 through 3). It's mandatory for non-corporate Commonwealth entities and increasingly cited in Australian SMB cyber insurance policies. MSPs with AU/NZ clients see this constantly.

NIS2 and DORA (European Union)

NIS2 (Directive (EU) 2022/2555) sets cybersecurity duties for medium and large organizations across 18 sectors, and it names managed service providers and managed security service providers as in scope. Member states had until October 17, 2024 to write it into national law; Cullen International counted four that still hadn't by May 2026, so check the law in each country where a client operates. In-scope organizations need risk-management measures that include supply chain security, MFA and incident handling, an early warning to the national authority within 24 hours of a significant incident and a fuller notification within 72 hours, and management bodies that approve and oversee those measures.

DORA (Regulation (EU) 2022/2554) has applied directly to EU financial entities, from banks and insurers to investment firms and payment institutions, since January 17, 2025. It covers ICT risk management, incident reporting, resilience testing and third-party risk, and it requires financial clients to keep a register of their ICT service contracts and to write specific clauses into them. The European Supervisory Authorities designated the first critical ICT third-party providers for direct oversight on November 18, 2025. An MSP serving an EU bank or insurer is unlikely to be on that list, but it will see DORA's audit, access and exit clauses in its contract.

Cyber Essentials (UK)

Cyber Essentials is the UK government-backed certification, owned by the National Cyber Security Centre and delivered through IASME, built on five technical controls: firewalls, secure configuration, user access control, malware protection and security update management. The basic level is a verified self-assessment, Cyber Essentials Plus adds a hands-on technical audit, and both renew every 12 months. The Danzell question set took effect on April 27, 2026, making MFA mandatory on every cloud service that offers it and tightening the marking criteria (checked November 2026).

UK central government contracts that handle personal information require Cyber Essentials, which puts it in front of SMB suppliers and the MSPs behind them. The security update control asks for high and critical patches within 14 days of release, so patch compliance reporting becomes part of the evidence.

How to pick the right framework for each SMB client

There's no universal answer, but the client's regulatory exposure and customer demands usually pick the framework for you. The table below is a quick-reference grid for MSP vCISO conversations and internal IT planning.

FrameworkTypical ClientCertifiableSelf-AttestableMSP EffortAnnual Maintenance
NIST CSF 2.0Any SMB, government-adjacentNoYesLow to MediumQuarterly review
CIS Controls v8.1 (IG1)SMB with no compliance mandateNoYesLowContinuous
CMMC 2.0 Level 2DoD subcontractorsYes (C3PAO)NoHigh3-year cycle plus annual affirmation
ISO/IEC 27001SaaS, global enterprise B2BYesNoHighSurveillance audit yearly
SOC 2 Type 2B2B SaaS in North AmericaYes (CPA)NoMedium to HighAnnual report
HIPAA Security RuleHealthcare providers, BAsNoYesMediumOngoing risk analyses
PCI DSS v4.0.1Retail, hospitality, paymentYes (QSA) or SAQSometimesMediumAnnual validation
Essential EightAU/NZ SMB and governmentNoYesMediumContinuous
NIS2EU organizations in 18 sectors, including MSPsNoNo (national supervision)Medium to HighContinuous, with incident reporting
DORAEU financial entities and their ICT providersNoNo (financial supervisors)HighYearly ICT risk framework review and testing
Cyber EssentialsUK SMBs and government suppliersYes (IASME certification body)Yes (verified self-assessment)LowYearly recertification

Read the table this way: pick the framework the client's customers or regulators force on them, then add CIS IG1 underneath as the operational layer. If neither customers nor regulators care, NIST CSF plus CIS IG1 covers ground without the audit overhead.

Organizations operating in the EU or UK add NIS2, DORA or Cyber Essentials on top of that base, because regulators and government buyers set those, not preference. Internal IT teams can run the same exercise per business unit: the unit that takes card payments or handles health data sets the floor for its slice of the network.

Mapping framework controls to your MSP tool stack

The fastest way to lose money on a compliance engagement is to treat the framework as a separate project from the tooling you already run. Every framework on this list breaks down into a similar set of practical capability areas. Map your stack to those capability areas once, then reuse the mapping across clients.

The eight capability areas that cover most controls: asset inventory and CMDB, vulnerability and patch management, identity and access (including MFA), endpoint detection and response, network segmentation and firewall hygiene, email and web filtering, backup and recovery, logging and SIEM. An RMM tool handles patch, asset inventory, and partial endpoint coverage. A dedicated EDR covers the rest. A PSA holds ticket evidence for incident response and change management. A documentation tool (or a proper MSP stack audit) holds the policies. A SIEM or managed SOC closes the logging requirement.

Once the mapping exists, framework gap analyses become reports rather than projects. A client asks "are we ready for SOC 2 Security criteria?" and you pull the eight capability columns, mark which Trust Services Criteria each one satisfies, and the gap list writes itself. The same exercise works for HIPAA Technical Safeguards or PCI Requirement 8. MSPs that productize compliance services tend to build this mapping once in a spreadsheet, then turn it into a customer-facing dashboard. The dashboard becomes the upsell artifact when a prospect asks how their current state compares to a target framework.

PCI compliance for MSPs and service providers

PCI DSS reaches past the merchant. If an MSP can affect the security of a client's cardholder data environment, for example by managing the firewall that segments it, the POS workstations or remote access into them, PCI treats the MSP as a third-party service provider and its own practices come into scope.

Two requirements set the terms. Requirement 12.8 makes the client keep a list of its service providers, hold written agreements with them, check their PCI status at least once every 12 months and record which requirements each provider manages (12.8.5). Requirement 12.9 makes the provider acknowledge in writing its responsibility for the account data it can affect (12.9.1) and share its compliance status and responsibility split when clients ask (12.9.2).

That leaves an MSP two routes. It can complete its own assessment, SAQ D for Service Providers or a QSA-led Report on Compliance, and hand clients the Attestation of Compliance, or it can join each client's assessment and answer the assessor's questions every time. The first costs more up front and scales across a client base; the second suits an MSP with one or two card-processing clients. Either way, segmentation that keeps the cardholder data environment small is the cleanest scope reduction, and the same holds for an internal IT team supporting a retail or hospitality business unit.

Common MSP mistakes when operationalizing frameworks

A few patterns show up repeatedly in failed compliance engagements.

  • Selling a "NIST package" without scoping the client's actual target profile. CSF is meaningless without a current and target profile defined; just shipping the 106-subcategory Core as a checklist guarantees fatigue and missed expectations.
  • Confusing certification with compliance. CIS, NIST CSF, HIPAA, and Essential Eight have no certifying body. Telling a client they're "NIST certified" creates legal exposure when something goes wrong.
  • Skipping documentation. ISO 27001 and SOC 2 fail more often on missing policies and evidence than on missing technical controls. The tool runs fine; the audit asks for the change management policy and nobody has one.
  • Ignoring the Govern function in NIST CSF 2.0. Roles, risk tolerance, supply chain risk management, and policy oversight aren't optional anymore. They're the new function added in 2024 and auditors notice.
  • Confusing PCI SAQ types. A client using Stripe Checkout fills out SAQ A; a client with their own card-present terminals fills out SAQ B-IP or C. The wrong SAQ invalidates the attestation.
  • Treating the framework as one-time work. Every framework on this list assumes continuous monitoring and annual recertification or attestation. The MSP that bills a one-shot project, then walks away, hands the next renewal to a competitor who positions ongoing assurance as a managed service.
  • Promising a compliance outcome. No MSP, tool or framework can guarantee that a client passes an audit or stays compliant; an auditor, QSA or regulator makes that call, and controls drift between assessments. Commit to posture instead: monitored controls, patch and backup SLAs, evidence on request and a written split of who owns which requirement.

Most of these come from treating frameworks as marketing assets rather than risk management tools. The clients who get value pair the framework with named ownership and quarterly review cadence; the ones who get audit findings bought a binder and shelved it.

The OpenFrame angle for framework-driven MSPs

Disclosure: Flamingo builds OpenFrame.

OpenFrame is an open, AI-native infrastructure layer for IT and security, used by MSPs and internal IT teams. It isn't a compliance tool and certifies nothing, but its RMM produces the patching evidence that framework controls ask for, such as patch status for each managed device. Mingo runs routine IT operations such as patch jobs, and Fae resolves support requests, so the work and its ticket history stay together. That evidence supports CIS Control 7, the Cyber Essentials security update control and PCI DSS Requirement 6.3.3, while policies, risk assessments and the audit itself stay with your vCISO and the assessor.

Pricing is $1 per device per month with 10 million AI tokens included, or $0.80 on annual billing, and there's a 14-day free trial. Because the platform is open, you keep access to that history if you swap components later, which matters for anyone weighing what an MSP platform should include before a compliance push.

The real test

The frameworks on this list aren't a menu. They're a map of where SMB risk and procurement collide, and the MSPs that grow margin in this space stop selling compliance as a product and start selling sustained operational discipline tied to whatever framework the client's market demands, then pick tooling that hands the evidence back the moment an auditor asks. For an internal IT team, the same discipline turns the next audit into a report instead of a scramble.

Kristina Shkriabina

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/cybersecurity-frameworks-list

Still deciding?

Ask Mingo answers from our docs and customer stories.

Loading related content and questions