Cybertech Texas Mission · Mar 14 to 21, 2027 · Austin, San Antonio, Houston. Join the waitlist
Back to blog
By Thiago Vieira 12 min read

CMMC for Startups: Levels, Scope and Readiness

Startup founders reviewing an office scope plan

CMMC applies to your startup only if you hold, or want, a Department of Defense (DoD) contract or subcontract and will handle federal contract information (FCI) or controlled unclassified information (CUI) on your own systems. If that describes you, the work is to scope narrowly, pick the right level, document how you meet each requirement, and treat the self-assessment as a real exercise. In July 2026 DoD paused the third-party assessment rollout, but the underlying security obligations did not go away.

This guide walks through the levels, scoping, a readiness assessment, realistic timelines and costs, and how security evidence can become a sales asset for a young company.

TL;DR

  • CMMC is the DoD program that sets cybersecurity requirements for contractors and subcontractors that handle FCI or CUI. It flows down the supply chain, so a startup can be covered as a subcontractor.
  • Level 1 is a self-assessment against 15 basic requirements. Level 2 follows NIST SP 800-171 Revision 2 and its 110 requirements. Level 3 adds selected NIST SP 800-172 requirements.
  • On July 13, 2026, DoD suspended the rollout. Agencies may currently require only Level 1 (Self) or Level 2 (Self), and DFARS 252.204-7012 still applies.
  • The biggest cost lever is scope. Keep CUI in a small, defined enclave instead of across the whole company.
  • Plan for months, not weeks. Document policies and keep evidence that your controls operate.

Table of Contents

When CMMC applies to a startup

CMMC is the DoD program that sets cybersecurity requirements for defense contractors and subcontractors. According to 32 CFR Part 170, it covers DoD contract and subcontract awardees that process, store or transmit FCI or CUI on unclassified contractor information systems. The requirements are phased into solicitations and contracts, and they flow down to subcontractors.

Three situations are common for startups:

  • You are a prime contractor on a small research or prototype award. The solicitation states the level you must hold.
  • You are a subcontractor to a larger defense company. Your prime passes the requirement down, often before you have signed anything.
  • You are selling software or a service that will touch a defense customer’s data. Even if you are not named on a contract, a prospect’s security team may ask where you stand.

The key question is data, not company size. If you never receive FCI or CUI, CMMC does not attach to you. If you might, decide early, because retrofitting controls is slower and more expensive than designing for them.

What FCI and CUI mean in practice

FCI is information the government provides or generates under a contract that is not meant for public release. CUI is a narrower category that needs safeguarding under law or government policy, such as certain technical drawings, export-controlled data or sensitive defense research. The contract, or your prime, should tell you whether CUI is involved. When it is unclear, ask in writing before you design your environment.

Technical drawing spread across a drafting table

Where the program stands in late 2026

The regulation sets a four-phase rollout. Per 32 CFR Part 170, Phase 1 begins on the effective date of the companion 48 CFR part 204 acquisition rule, and each later phase begins one calendar year after the one before, ending in full implementation at Phase 4.

Then the schedule changed. According to one law firm’s client alert, on July 13, 2026 DoD suspended the CMMC rollout and Phase 2. As a condition of award, agencies may require only Level 1 (Self) or Level 2 (Self). The same alert notes that DFARS 252.204-7012 obligations remain in effect, and that the Level 2 third-party and Level 3 government-led assessment requirements are paused.

What this means for you:

  1. The security work is still due. DFARS 252.204-7012 already points contractors toward NIST SP 800-171 controls for covered information. A pause on certification assessments is not a pause on safeguarding.
  2. Self-assessments are the near-term test. Your score and affirmations are what contracting officers and primes will look at.
  3. Rules can move again. Check the DoD CIO CMMC page for the current schedule before you commit budget to a third-party assessment.

Startups that build the controls now will be ready whichever way the schedule goes, and they will have the evidence a prime or investor asks for.

CMMC levels explained

The model has three levels. Per 32 CFR 170.14, Level 1 uses FAR 52.204-21, Level 2 uses NIST SP 800-171 Revision 2, and Level 3 uses selected NIST SP 800-172 requirements from February 2021. The DoD model overview says the same.

Level 1 Level 2 Level 3
Protects FCI CUI CUI at higher risk
Based on FAR 52.204-21 (15 requirements) NIST SP 800-171 Rev. 2 (110 requirements) Selected NIST SP 800-172 requirements
Assessment Annual self-assessment and affirmation Self-assessment or third-party assessment, depending on the contract; affirmation each year Government-led
Status validity Reassessed annually Three years from the status date Set by the program rules

The DoD CIO About CMMC page states that Level 1 needs an annual self-assessment and affirmation, and that Level 2 needs a self-assessment every three years plus an annual affirmation, with status valid for three years from the status date.

Which level should a startup expect?

Most early-stage companies fall into one of two groups:

  • Level 1 if you only touch FCI, for example you are a small vendor on a services or software contract with no sensitive technical data.
  • Level 2 if you will handle CUI, which is typical for research, engineering or security products supporting defense programs.

Level 3 is rare for startups and is driven by the contract. The solicitation names the level, so do not guess: read the clauses.

The DoD Inspector General notes that Level 2 assessments are performed by authorized third-party assessors (C3PAOs) before contract award. Under the July 2026 pause, that step is not currently the default condition of award, so confirm what your specific solicitation says.

Scoping: the decision that sets your cost

Scope is the set of people, systems, facilities and service providers that handle FCI or CUI. Everything inside it must meet the requirements. Everything outside it does not.

For Level 1, the DoD scoping guide says you must specify the assessment scope before the self-assessment, and that in-scope assets process, store or transmit FCI. You should consider people, technology, facilities and external service providers, and a significant change to your architecture or boundary calls for a new assessment.

A practical scoping pass for a startup:

  1. Map the data. Where will contract data land: email, a shared drive, a code repository, a ticketing tool?
  2. List the people who truly need access. Fewer is cheaper.
  3. List the cloud services you will approve for that data, and confirm each one’s responsibilities in writing.
  4. Decide how devices are managed: which laptops, which configuration baseline, who can administer them.
  5. Draw the boundary. One practitioner guide for startups recommends defining a secure enclave early if CUI is likely, noting that narrow scoping reduces cost and complexity.

An enclave separates the CUI environment from the rest of your infrastructure. PreVeil’s checklist makes the same point: limiting endpoints and people in scope directly affects cost.

The trade-off for a startup is cultural as much as technical. Engineers who need CUI work inside the enclave. Everyone else works the way they always have. Decide who is in which group before your first defense deal, not after.

A step-by-step path to readiness

  1. Confirm whether you will handle CUI. Read the contract or ask your prime. Document the answer.
  2. Define the enclave or boundary as described above.
  3. Write a living system security plan (SSP). The SSP explains how you meet each of the 110 NIST SP 800-171 requirements. PreVeil advises adding a responsibility matrix for cloud and external service providers that shows which controls are inherited and which are shared.
  4. Document policies and procedures: asset inventory, access reviews, incident response, configuration management. The same startup guide stresses that CMMC requires repeatable processes, not just strong passwords or cloud tools.
  5. Implement the technical controls around the boundary: multifactor authentication, encryption, logging, patching, endpoint management.
  6. Keep evidence that controls operate: screenshots, logs, review records, training attendance. Evidence is what turns a claim into a pass.
  7. Run the assessment (next section), fix the gaps, and submit your results.

If you are already building toward another framework, you have a head start. Our guide to ISO 27001 for startups covers a lean management system that overlaps with many of the policy and risk-management expectations buyers look for. If your product is AI-driven, the NIST AI RMF guide covers the separate governance layer.

CMMC readiness assessment: how to find your gaps

A readiness assessment compares what you do with what the requirements say, then lists the difference.

Self-assessing against the right method

Per 32 CFR 170.16, a Level 2 self-assessment must follow NIST SP 800-171A and the CMMC Level 2 scoping requirements for the systems in scope. Work through every requirement and assessment objective, and mark each one met, not met or not applicable, with evidence.

Think like an assessor

The CMMC assessment process document from the accreditation body explains that assessors test evidence for adequacy and sufficiency: do they have the right evidence, and enough of it. Gaps in evidence are recorded as weaknesses in implementation and can drive a “not met” finding. For your own review, ask of each requirement:

  • Is it written down in a policy or in the SSP?
  • Is it actually configured that way today?
  • Can I show proof from the last few months, not just a setting someone changed yesterday?

Submitting results and closing gaps

Level 2 self-assessment results go into SPRS. According to 32 CFR 170.16, the submission includes the level, status date, assessment scope, CAGE codes, overall score and POA&M status if applicable, and you affirm the status at each assessment and annually after that.

A plan of action and milestones (POA&M) lets you carry some gaps for a limited time. For a conditional Level 2 (Self) status, the same section says you must remediate unmet requirements, run a POA&M closeout self-assessment and post results in SPRS within 180 days of the status date, or the conditional status expires. Treat the POA&M as a short repair window, not a place to park work.

How long it takes and what to budget

Expect months. Coalfire Federal says Level 2 readiness typically takes 12 to 24 months, and that a readiness gap assessment typically takes four to eight weeks and costs $15,000 to $75,000. Those figures reflect larger and more complex environments than most seed-stage companies have. A startup with a small team, cloud-native tooling and a tightly scoped enclave can often move faster and spend less, but the shape of the work is the same.

For the assessment itself, DoD estimated a small entity’s Level 2 certification assessment and affirmation activities at nearly $105,000, covering the triennial assessment and affirmation plus two additional annual affirmations. Implementation costs were not included. With third-party assessments paused, you may not owe that cost today, but it is a useful planning ceiling if the requirement returns.

Where the money actually goes:

  • Tooling for identity, endpoint management, logging and encrypted collaboration inside the enclave
  • Policy and SSP writing, whether in house or with outside help
  • Staff time on evidence collection, which founders often underestimate
  • Training and periodic reviews that keep the evidence current

The cheapest dollar is the one you do not spend on systems that never needed to be in scope.

Perspective

Most startups treat CMMC as a paperwork tax. We see it differently. A defense buyer, a prime or an investor is asking one question: can I trust what this company tells me about its security? Your SSP, your logs and your assessment results are the answer, and they are only as strong as the evidence behind them.

That is why we built Cybertech Acceleration around digital forensics. Judicial-grade evidence is the same discipline that makes a compliance claim credible: records that are complete, time-stamped and defensible when someone challenges them. A founder who designs product data and security records with that standard in mind is already closer to what an assessor, a procurement team or a court will accept.

Our advice is to scope narrowly, document as you build, and translate the result into plain commercial language. Buyers rarely read a control matrix, but they remember a founder who can explain in two sentences why their environment is trustworthy and show the proof. That translation from technical detail to business narrative is the work we do with the founders in our program.

Thiago Vieira

Turning compliance evidence into a market advantage

Security compliance is table stakes in defense. What separates one cybersecurity or AI startup from the next is whether its evidence stands up under scrutiny. Our guide to evidence by design explains how to make product data admissible in US court, which is the same habit of rigor that makes an SSP and its supporting records hold up. Founders who also sell into regulated hardware or government markets may want our overview of Common Criteria certification for another credential buyers recognize.

FAQ

Do I need CMMC if I am a startup with no defense contract yet?

Not until a contract or subcontract puts FCI or CUI in your systems. But if defense is on your roadmap, design your environment and records to the requirements early. It is much cheaper than rebuilding later, and primes often ask about your posture before they sign you.

Is CMMC still required after the July 2026 suspension?

The rollout of third-party and government-led assessments is suspended, but Level 1 and Level 2 self-assessments can still be required, and DFARS 252.204-7012 remains in effect. Check the DoD CIO page and your solicitation for the current position before you plan around any date.

What is the difference between Level 1 and Level 2?

Level 1 protects FCI with 15 basic requirements and an annual self-assessment. Level 2 protects CUI with the 110 requirements of NIST SP 800-171 Revision 2, with status valid for three years and an annual affirmation. Your contract says which level applies.

How can I keep CMMC costs down?

Shrink the scope. Limit which people, devices and cloud services touch CUI, and put them in a defined enclave. Fewer endpoints and users in scope means fewer controls to implement and evidence.

What is a C3PAO?

A C3PAO is a certified third-party assessment organization authorized to perform Level 2 assessments. Under the current pause, a C3PAO assessment is not the default condition of award, so confirm what your solicitation requires.

Sources

About the author

Thiago Vieira

Founder of Cybertech Acceleration Inc and digital forensics expert, leading the forensic component of every startup in the program.

Author website →

Related articles

US soft landing by country