CMMC Level 2 requirements are the 110 security requirements of NIST SP 800-171 Revision 2, which a contract asks for when your company handles Controlled Unclassified Information, assessed by your company itself or by an outside assessor.
Our guide to CMMC requirements for small business covers the whole program. This page zooms in on Level 2, the one for a supplier whose work involves Controlled Unclassified Information (CUI).
It reflects the rules as of November 2026, including a July 2026 class deviation. Treat it as readiness education. It won’t certify your company, and neither will we.

Who has to meet CMMC Level 2 requirements
Controlled Unclassified Information is information the government creates or gives you that a law, regulation or policy says must be protected, though it isn’t classified, and a drawing or technical data package marked CUI is the usual sign. If your systems process, store or transmit CUI, Level 2 reaches them.
Start with scope. Your contract decides whether Level 2 applies at all. Where it does, 32 CFR 170.19 sorts your assets into categories, and assets that hold CUI or protect it get assessed. A laptop that can’t touch CUI stays out of scope, and so does an endpoint set up as a bare remote-desktop client.
The 14 families behind CMMC Level 2 requirements
NIST SP 800-171 Revision 2 files the 110 under 14 families, numbered 3.1 to 3.14, and CMMC keeps them as written. The plain-words column is our own paraphrase, so NIST’s text controls. The last column gives examples of where a person might look, not a list DoD publishes. Keep NIST open.
| NIST | Family and requirements | In plain words | Where you might look |
|---|---|---|---|
| 3.1 | Access Control, 22 | Limit who can reach CUI, what each person can do with it, and how it moves in and out, remote and wireless access included. | Account and permission lists, remote-access settings |
| 3.2 | Awareness and Training, 3 | Make sure people know the risks and their own security duties, insider threats included, with training matched to the role. | Training rosters and materials |
| 3.3 | Audit and Accountability, 9 | Keep logs that show who did what on the systems, protect those logs, and review them so any action traces to one person. | Log settings and review records |
| 3.4 | Configuration Management, 9 | Set a baseline for every system, track changes to it, and allow only the functions and software the work needs. | Baseline settings, change records, software lists |
| 3.5 | Identification and Authentication, 11 | Know every user and device, confirm identity before access, and use multifactor sign-in where NIST calls for it. | Sign-in, multifactor and password settings |
| 3.6 | Incident Response, 3 | Have a plan to detect, report and handle security incidents, and test it. | The incident response plan and a test record |
| 3.7 | Maintenance, 6 | Service systems on a schedule, control who does it and with what tools, and clean equipment that leaves the building. | Maintenance logs, vendor access records |
| 3.8 | Media Protection, 9 | Protect, mark and control CUI on paper and removable media, and wipe or destroy media before disposal or reuse. | Media inventory, wipe records, removable-drive settings |
| 3.9 | Personnel Security, 2 | Screen people before they get CUI access, and protect CUI when someone leaves or changes jobs. | Screening records, an offboarding checklist |
| 3.10 | Physical Protection, 6 | Limit physical access to systems and sites, escort visitors, keep access logs and protect CUI at alternate work sites. | The visitor log, key and badge records |
| 3.11 | Risk Assessment, 3 | Assess risk on a regular schedule, scan for vulnerabilities, and fix what the scans find. | The risk assessment and scan reports |
| 3.12 | Security Assessment, 4 | Check your own controls, write plans to fix the gaps, and keep a system security plan that draws your boundary and says how each requirement is met. | The system security plan and the plan of action |
| 3.13 | System and Communications Protection, 16 | Protect networks and data in transit and at rest: boundary defenses, public systems kept separate, and FIPS-validated encryption for CUI. | Firewall rules, a network diagram, encryption settings |
| 3.14 | System and Information Integrity, 7 | Find and fix flaws, guard against malicious code, keep that protection current and watch for unauthorized use. | Patch records, anti-malware settings, security alerts |
How CMMC Level 2 scoring and plans of action work
A perfect Level 2 score is 110. Each requirement that isn’t met takes off 5, 3 or 1 points, depending on how much it exposes CUI, and 32 CFR 170.24 sets each value. It can go below zero.
A plan of action and milestones (POA&M) lets you hold a Conditional status while you finish. It’s narrow. Your score has to reach 80 percent of 110, which is 88, and only 1-point requirements can go on it, apart from one encryption case worth 3, while six requirements can never be on it, the system security plan among them, and you get 180 days to close it out under 32 CFR 170.21.
What a plan of action doesn’t do
It’s no substitute. A requirement you haven’t implemented scores NOT MET under the scoring rule in 32 CFR 170.24 whether or not a POA&M lists it, and an up-to-date system security plan has to exist when the assessment starts.


Self-assessment or third-party assessment
Level 2 has two paths. Your contract names the one you follow. Under Level 2 (Self), your company scores itself against NIST SP 800-171A and posts the result in SPRS, the Supplier Performance Risk System, while under Level 2 (C3PAO) a certified third-party assessment organization does the assessing and its results reach SPRS through DoD’s own system.
After either one, you assess again within three years, your Affirming Official affirms in SPRS every year, and the evidence stays on file for six full years from the status date. Both entries matter. Our post on SPRS scores and affirmations covers the entries.
Where the cluster fits
We provide readiness guidance and referrals to certified assessors. We don’t certify anyone. Third-party CMMC assessments by certified assessors involve fees charged directly by those providers, not by the cluster. If a referral involves outside fees, your point of contact tells you before anything moves forward.
Level 2 in four numbers
Each figure comes from the rule or the NIST publication that sets it.
Sources checked November 20, 2026. The 88 is 80 percent of 110, the threshold in the rule.
Keep going with these CMMC guides
Level 1, one requirement at a time
The 15 basic safeguards behind Level 1 are read one by one in our CMMC Level 1 requirements guide.
A working CMMC checklist
Eight steps, with the clause and the record behind each, in our CMMC compliance checklist.
CUI and your subcontractors
What a prime will still ask of its CUI subcontractors is covered in our CMMC flow-down post.
CMMC & Compliance Readiness
Readiness guidance and referrals to certified assessors come through our CMMC and compliance readiness service.
More from the resource library
- Reference documents library, with the DoD CMMC overview, NIST SP 800-171 and DFARS 7012
- Useful websites and tools for registration, contracting and compliance
Questions small contractors ask about Level 2
Is CMMC Level 2 just NIST SP 800-171?
Almost, because the 110 Level 2 requirements are identical to those in NIST SP 800-171 Rev. 2, and CMMC adds the assessment, scoping and reporting rules around them.
The wording comes from NIST. What 32 CFR part 170 adds is who assesses you, how your scope is drawn, how a score is worked out and how results reach SPRS.
What separates Level 1 from Level 2?
Fifteen requirements against 110, and Federal Contract Information against Controlled Unclassified Information.
Level 1 is self-assessed only. Level 2 allows a limited plan of action, expects a system security plan and, on some contracts, an outside assessor. Not sure which one your contract means? Our post on whether CMMC applies to your company walks through the check.
Do we need an outside assessor?
Short answer: only if your contract names Level 2 (C3PAO), because the rule sets both a self-assessment path and an authorized-assessor path.
As of November 2026, DoD’s class deviation 2026-O0025 lets requiring activities include Level 1 (Self) or Level 2 (Self) assessments. Check the solicitation. Then check every amendment for the level it names. Our post on what CMMC still requires explains the pause.
Can we have gaps and still hold a Level 2 status?
Only within limits, and only as a Conditional status that expires after 180 days if the gaps aren’t closed.
Your score has to reach 88 of 110, a plan of action can hold only 1-point items plus one 3-point encryption case, and six requirements can never go on one, because a plan of action isn’t a substitute for a finished requirement under 32 CFR 170.24.
What does a Level 2 assessment cost?
The better question is what drives it, because nobody can honestly name one figure for a company they haven’t scoped.
How many systems touch CUI, how much of the 110 you already meet and have documented, and who does the work all move the number. Scope it first. Third-party CMMC assessments by certified assessors involve fees charged directly by those providers, not by the cluster.
Does CMMC use NIST SP 800-171 Revision 3?
CMMC as written names Revision 2, the 110-requirement version, and the July 2026 class deviation keeps it as the baseline under DFARS 252.204-7012.
NIST withdrew Revision 2 on May 14, 2024, when it published Revision 3, so NIST’s own page and your contract can look like they disagree about which revision applies. Ask your contracting officer which revision your contract holds you to. Don’t guess.
Take your Level 2 questions to the cluster
Membership and cluster-funded services are provided at no cost to eligible participating businesses, subject to program requirements and available resources.
