CMMC Cost by Company Size: What DoD's Estimates Cover, and What They Leave Out
DoD's own CMMC cost estimates come in two sizes, and the hours behind them show why a small company pays more for each one. What the estimates cover, what “small” means in them, and the readiness costs they leave out.
When the DoD published the CMMC rule, it estimated what an assessment would cost a small business: $37,196 over three years for a Level 2 self-assessment, or $104,670 with a C3PAO. Those are the figures most cost articles quote. They’re real, but they price only one part of the job, the assessment. The work of getting ready to pass it isn’t in them at all, by design.
Company size changes both parts, though not the way most people expect. DoD’s estimates come in just two sizes, small and other-than-small, and the hours behind them show something useful: in the Department’s own model, a small company spends far fewer hours on an assessment and pays far more for each one. Here’s what the estimates cover, what “small” means in them, and where the readiness cost they leave out comes from.
DoD priced the assessment, not the readiness
The estimates are in the rule’s regulatory impact analysis (89 FR 83092). For Levels 1 and 2 they count the hours to gather evidence, carry out the assessment (yourself or with a C3PAO), report the result and sign the affirmation. They assume you pass on the first attempt. And they leave out the work underneath:
Not in DoD’s estimate
- Implementthe Level 1 or Level 2 security requirements
- Maintainthem once they’re in place
- Remediatea plan of action for what isn’t
The reason is history. FAR 52.204-21 has required the 15 Level 1 safeguards since June 2016, and DFARS 252.204-7012 required the 110 requirements of NIST SP 800-171 by December 31, 2017. In DoD’s view, those costs “should already have been incurred and are not attributed to this rule” (89 FR 83179). Answering comments, the Department put it more bluntly: “Companies that are currently and validly attesting that they meet DFARS clause 252.204-7012 should not have difficulty passing a Level 2 self-assessment” (89 FR 83154).
That’s the hinge for any cost estimate. If your requirements really are in place, DoD’s numbers are close to the whole bill. If they aren’t, and the DoD Inspector General found in 2019 that contractors “did not consistently implement mandated system security requirements” (cited in the rule, 89 FR 83194), the gap is a cost the estimates never see. It’s yours to price.
“Small” can mean 1,000 people
Every DoD estimate comes in two versions: small entities and everyone else. “Small” follows the SBA’s size standards in 13 CFR 121.201, which are set industry by industry, and for defense manufacturing they run high:
- Machine shops: up to 500 employees
- Other aircraft parts and auxiliary equipment manufacturing: up to 1,250
- Search, detection, navigation and guidance instruments: up to 1,350
- Engineering services: up to $25.5 million in average annual receipts, or $47 million for military and aerospace equipment work
So a 12-person job shop and a 450-person machine shop get the same “small” estimate. Most of the defense industrial base is small by this measure: of the 31,338 companies a year whose DoD awards carried DFARS 252.204-7012 (the 2019 to 2021 average), 23,475, or 75%, were small entities (89 FR 83178).
What separates the two versions isn’t headcount. It’s an assumption about who does the work: “Non-Small Entities have a team of full-time cybersecurity professionals on staff while Small Entities do not” (89 FR 83154), and small entities “are likely to outsource IT and cybersecurity to an External Service Provider” (89 FR 83179).
Same assessment, different crew
DoD built each estimate from hours: which roles work on the assessment, for how long, at what rate. In-house staff are costed at $36.32 to $190.52 an hour, including fringe. An outside provider (ESP) or a C3PAO costs $260.28, including overhead and profit. Turn the Level 2 hours into working days and the difference between the two sizes is easy to see.
Self-assessment
With a C3PAO
DoD’s small company spends 19 days on a Level 2 self-assessment and its larger counterpart 55, yet the bills are $34,277 and $43,403: about a third of the hours, at four-fifths of the cost. Eleven of the small company’s 19 days are bought from an outside provider, so it pays about $225 an hour on average against the larger company’s $99. The C3PAO version tells the same story: 54 days against 107, and $101,752 against $112,345, with a three-person C3PAO team for 120 hours against five people for 200.
Level 1 makes the point most plainly. Both versions take the same 28 hours, but the small company’s costs $5,977 a year and the larger company’s $4,042, because 12 of those hours come from an outside provider instead of a manager and IT staff. (One step is the same for everyone: typing the score into SPRS, which “should only take five minutes,” 89 FR 83181.)
That’s DoD’s own answer to why CMMC weighs so heavily on a small manufacturer. The requirements don’t shrink with headcount, as we covered in scoping for a 5-person company vs. an enterprise, and without a security team on staff, the expertise is bought by the hour.
Treat the hours as the Department’s averages, not a quote. Commenters argued they were too low, from the cross-functional work in HR, physical security and training to outside-provider hours one commenter put at “125% to 175% too low” (89 FR 83153, 83155). DoD kept them, noting that “the size and complexity of the network within scope of the assessment impacts the costs as well,” and that market forces will “determine C3PAO pricing” (89 FR 83154, 83155). And during the current Phase 2 pause, contracts can require only self-assessments (what still applies), so the C3PAO rows describe a voluntary certification for now. The readiness work underneath is the same either way.
Where the readiness bill comes from, by size
The part DoD left out has no official figure, and it depends too much on your environment for anyone’s average to stand in for it. What we can describe is where it tends to come from at each size. These are patterns, not price bands.
Under about 50 people
This is the company DoD’s small-entity model describes best: no security team, so most of the readiness work is bought, from an MSP or a consultant, at outside rates. The other large lines:
- Where CUI lives. A common way to keep the scope compact is to hold CUI in one cloud service. DFARS 252.204-7012 requires that service to meet the FedRAMP Moderate baseline or equivalent, so moving email and files into one, and configuring it to match your SSP, is a cost of its own.
- Paperwork that doesn’t shrink. The SSP, policies, asset inventory and network diagram exist at any size. Spread across a dozen people, they cost far more per head than they do at a larger company.
- Your MSP’s side. If your MSP runs your security tools, its people and tools are in your scope, which we cover in Is my MSP CMMC compliant?
A few hundred people
Still “small” in DoD’s tables for most manufacturing codes, but often built differently from DoD’s model, with an in-house IT team and security as one of its jobs. The cost here tends to come from breadth:
- The scoping decision. Bringing the whole network up to Level 2 or building an enclave can move the number more than anything else on this list.
- The shop floor. CNC controllers, test equipment and other Specialized Assets have to be documented in your asset inventory, SSP and network diagram, and shown to be managed under your risk-based security policies (32 CFR § 170.19).
- Requirements that grow with people and places. Security awareness and role-based training (3.2.1, 3.2.2), screening people before access and protecting CUI through terminations and transfers (3.9.1, 3.9.2), and physical access control (3.10) all scale with headcount and sites. They’re the cross-functional hours commenters said DoD undercounted.
Larger organizations
DoD’s model gives them a security team on staff, so fewer hours are bought and more are spent: 55 days for a Level 2 self-assessment in the estimate above. The multiplier at this size is the number of scopes. The other-than-small estimate is per contractor information system (89 FR 83178), so a company that assesses several environments repeats it for each, and every new system used for a DoD contract needs its own SPRS entry (89 FR 83134).
The rule won’t help with the bill
Commenters asked DoD for grants, tax credits and higher contract prices to cover compliance. The answer was that “subsidizing costs for the defense industrial base compliance is not within the scope of this rule,” and that the rule “makes no change to the cost allowability parameters described in FAR 31.201-2” (89 FR 83154, 83152). Whether any of your costs can be recovered through your rates is a question for your contracts or accounting lead, under the same rules as any other cost.
Putting a number on your own
Use DoD’s estimate as a check on the assessment line, not as your budget. The rest is built in this order:
- Find the gap. Score yourself against all 110 requirements the way DoD scores them (how the Level 2 self-assessment works). DoD assumed the gap was zero; your readiness cost is the size of yours.
- Settle the scope before pricing anything else. Every later line depends on it.
- Decide who does the work. In DoD’s own model, in-house versus bought hours is the biggest difference between a small company’s bill and a large one’s.
- Price the assessment, with DoD’s hours as a sanity check.
- Add what recurs: annual affirmations, evidence upkeep, and the next assessment in the three-year cycle.
Step 1 is where an honest number starts, and it’s what our gap analysis does: your gaps, your CUI scope and your security risks, checked against every applicable CMMC objective by Certified Assessors.
Sources: CMMC Program final rule, 89 FR 83092 (October 15, 2024), preamble at 83134, 83152–83155, and regulatory impact analysis at 83178–83186 and 83194; 13 CFR 121.201, SBA size standards (checked November 2026); 32 CFR Part 170, § 170.19(c), Table 3; FAR 52.204-21 and 31.201-2; DFARS 252.204-7012; NIST SP 800-171 Revision 2, requirements 3.2.1, 3.2.2, 3.9.1, 3.9.2 and 3.10.
