All Posts Next

In order to obtain access to CUI on a Department of Defense contract, your company must meet the safeguarding requirements tied to that contract, typically NIST SP 800-171 Rev 2, and hold the CMMC level the solicitation specifies.

This guide is written for defense contractors and subcontractors who have been told a contract involves Controlled Unclassified Information and need to understand what that obligates them to do. It explains what CUI is, how CMMC 2.0 gates access to it, which DFARS clauses apply, what the current rule timeline looks like after the Phase II suspension, and how to evaluate your path to compliance.

Key Takeaways

  • CUI is unclassified information the government protects because disclosure would harm its missions. It was created by Executive Order 13556, signed 2010-11-04, with the National Archives and Records Administration as Executive Agent and 32 CFR Part 2002 as the government-wide rule.
  • Only contractors that receive or generate CUI take on the full NIST SP 800-171 obligation of 110 controls. Contractors handling only Federal Contract Information must meet the 15 basic safeguarding requirements of FAR 52.204-21.
  • When DFARS 252.204-7021 appears in a solicitation or contract, the contractor must hold a valid CMMC certificate at the specified level before award. Only a C3PAO can issue a CMMC Level 2 certificate.
  • The CMMC Program rule, 32 CFR Part 170, took effect 2024-12-16, and the 48 CFR acquisition rule took effect 2025-11-10. On 2026-07-13 the DoD CIO announced suspension of the 2026-11-10 Phase II deadline; Phase I self-assessments remain in force and later milestones are paused until further notice. These are separate dates: the acquisition rule is in effect now, while the Phase II certification deadline for existing contracts is paused.
  • Enclaving CUI into a narrowly scoped boundary, such as a GCC High tenant or a dedicated cloud landing zone, keeps the 110 controls from applying across the entire enterprise network.

What CUI Is and Who Decides You Can Have It

Controlled Unclassified Information is information the federal government creates or possesses that is sensitive but not classified. Executive Order 13556 established the program in 2010, and 32 CFR Part 2002 governs how agencies mark, handle, and disseminate it. Inside the Department of Defense, DoD Instruction 5200.48, issued 2020-03-06, implements the CUI program.

CUI Basic and CUI Specified

32 CFR Part 2002 divides CUI into two categories. CUI Basic carries a uniform set of controls built around a moderate confidentiality baseline. CUI Specified carries handling controls written into the underlying law, regulation, or agency policy that designated it. In practice, a defense contract may involve both, and the handling requirements can differ between them.

Marking rules you will encounter immediately

32 CFR 2002.20 requires a CUI banner marking on every page that contains CUI, along with a designation indicator naming the designating agency. 32 CFR 2002.16 allows only the designating agency to apply limited dissemination controls, which means a contractor cannot invent its own distribution restrictions on CUI. Separately, DoD Instruction 5230.24 governs distribution statements on technical documents. A distribution statement does not satisfy CUI marking requirements; the two are applied in parallel. Contractors new to CUI frequently confuse these systems, so it is worth confirming with the contracting officer exactly what you are receiving and how it is designated.

Access is a contract matter, not a clearance matter

That is why the practical question for most companies is not "do I have a clearance" but "which clauses and which CMMC level are in my solicitation."

The Requirements You Must Meet in Order to Obtain Access to CUI

The requirements depend on what kind of contract information you handle. The distinction between Federal Contract Information and CUI drives everything else.

FCI versus CUI

Every DoD contractor handling Federal Contract Information must meet the FAR 52.204-21 baseline: 15 basic safeguarding requirements, an annual self-assessment, and an annual senior official affirmation to DoD. That is CMMC Level 1. Only contractors that receive or generate CUI take on the full NIST SP 800-171 obligation, which is CMMC Level 2: all 110 practices of NIST SP 800-171 Rev 2, organized into 14 domains, with a C3PAO assessment for most programs, triennial reassessment, and an annual senior official affirmation. Level 3 adds selected controls from NIST SP 800-172 on top of Level 2 and is assessed by the government through DCMA DIBCAC, not by a C3PAO.

RequirementCMMC Level 1CMMC Level 2CMMC Level 3
Information coveredFCICUICUI on highest-sensitivity programs
Control set15 basic safeguarding requirements from FAR 52.204-21All 110 practices of NIST SP 800-171 Rev 2 across 14 domainsLevel 2 plus selected NIST SP 800-172 controls
AssessmentAnnual self-assessmentC3PAO assessment for most programs, triennial reassessmentGovernment assessment by DCMA DIBCAC
AffirmationAnnual senior official affirmationAnnual senior official affirmationGovernment-led

The DFARS clauses behind the requirements

DFARS 252.204-7012 requires adequate security, defined as the 110 controls of NIST SP 800-171, on every covered contractor information system. It also imposes incident reporting duties: a cyber incident affecting covered defense information must be reported to DoD within 72 hours of discovery through the DoD reporting portal at dibnet.dod.mil, which requires a DoD-approved medium assurance certificate obtained in advance. After a reported incident, the contractor must preserve images of affected systems and monitoring data for at least 90 days, submit isolated malicious software to the government, and hold cloud providers to a FedRAMP Moderate baseline. The clause must be flowed down to subcontractors, including for commercial products and services, when performance involves covered defense information; a subcontractor reports its own incidents to DoD and gives the report number to the next higher tier.

DFARS 252.204-7019 requires a current NIST SP 800-171 assessment summary score in SPRS when an offer is submitted. DFARS 252.204-7020 governs how that assessment is conducted under the DoD Assessment Methodology and gives DoD access to verify it. The SPRS self-assessment score ranges from minus 203 to 110, with controls weighted at 1, 3, or 5 points. When DFARS 252.204-7021 appears in a contract or solicitation, the contractor must hold a valid CMMC certificate at the specified level before award.

Encryption requirements are stricter than they look

NIST SP 800-171 requires FIPS-validated cryptography to protect the confidentiality of CUI. Strong but unvalidated encryption does not meet the requirement. DoD CIO FAQ clarifications add that encrypted CUI is still CUI, and encrypted CUI in a cloud still needs FedRAMP Moderate or equivalency. Another clarification worth noting: VDI endpoints are out of scope only in a KVM-only configuration. These details routinely change a contractor's scope assumptions, so verify them against your own architecture rather than assuming.

POA&Ms have limits

POA&Ms are allowed only for "not met" requirements within the limits of 32 CFR 170.21, with a 180-day closeout.

How Certification Works: The Ecosystem That Controls Access

The CMMC Program rule, 32 CFR Part 170, was published 2024-10-15 and took effect 2024-12-16. The acquisition rule in 48 CFR, which implements DFARS 252.204-7021, was published in the Federal Register on 2025-09-10 (document 2025-17359) and took effect 2025-11-10.

Who can certify you

Only a C3PAO can issue a CMMC Level 2 certificate. The C3PAO submits results to eMASS and the certificate is stored in SPRS. A Registered Provider Organization such as Petronella Technology Group, Inc. prepares a contractor for assessment but cannot conduct the assessment or issue a certificate; authorized C3PAOs conduct Level 2 certification assessments. The list of authorized C3PAOs is maintained at cyberab.org/marketplace. DoD's scope estimate for the program is 220,966 entities, and there were 103 C3PAOs as of the March 2026 Town Hall, so assessor scheduling is a real planning input. Level 2 certifications grew from 773 in January 2026 to 1,391 in May 2026.

Where the timeline stands after the suspension

On 2026-07-13 the DoD CIO announced the suspension of the 2026-11-10 Phase II deadline. Phase I self-assessments remain in force, and later milestones are paused until further notice. It is important not to conflate this with the acquisition rule: the acquisition rule took effect 2025-11-10, which means DFARS 252.204-7021 can already appear in solicitations and contracts today, and when it does, a valid certificate at the specified level is required before award. A DoD class deviation also keeps DFARS 252.204-7012 on NIST SP 800-171 Revision 2 for now.

Enclaving: the decision that shapes everything else

Enclaving CUI into a narrowly scoped boundary, for example a GCC High tenant or a dedicated cloud landing zone, keeps the 110 controls from applying across the entire enterprise network. This reduces the assessment surface and the ongoing cost of maintaining compliance. Our team discusses enclave design as part of CMMC consulting and readiness services, and the broader program context is covered in our CMMC compliance services.

How to Evaluate Your Path in Order to Obtain Access to CUI

Once you know which level applies, the work becomes a sequence of concrete steps. Here is how we advise contractors to evaluate their own path.

Step one: confirm what you actually handle

Ask the contracting officer whether the contract involves FCI or CUI, and which clauses are included. If you handle only FCI, the FAR 52.204-21 baseline and an annual self-assessment may be all that applies; our guide to the CMMC Level 1 self-assessment walks through that path. If CUI is involved, the full NIST SP 800-171 obligation follows, and the SPRS scoring requirement under DFARS 252.204-7019 applies when you submit an offer.

Step two: baseline your current state

A gap analysis against the 110 controls tells you where you stand and produces the evidence you need for an SPRS score. A typical CMMC Level 2 readiness engagement runs 12 to 14 weeks for a mid-size contractor: Discovery in week 1, Gap Analysis in weeks 2 through 4, a Remediation Sprint in weeks 5 through 12, and C3PAO Readiness Handoff in weeks 13 and 14. The path from gap assessment to C3PAO-ready typically takes 6 to 18 months depending on starting security posture and the complexity of the CUI environment. Readiness deliverables include a system security plan covering all 110 controls with owners and evidence pointers, 14 control-family policies plus an incident response plan, acceptable use policy and media protection policy, a live POA&M, a mock assessment using the Cyber AB CMMC Assessment Process, a baselined SPRS score, and a C3PAO shortlist with warm introductions.

Step three: decide on scope and enclave design

Before remediating, decide where CUI will live. A narrowly scoped enclave means fewer systems to assess, fewer policies to maintain, and a smaller annual evidence burden. This is also where cloud decisions matter: encrypted CUI in a cloud still needs FedRAMP Moderate or equivalency, and FIPS-validated cryptography is required, so platform selection is a compliance decision, not just a technical one.

Step four: plan for continuous compliance

CMMC compliance is continuous. The system security plan is a living document, the POA&M is reviewed at least quarterly, and re-assessment occurs every three years. Treat certification as the start of an operating rhythm rather than a finish line. For a structured walkthrough of the full control set, see our CMMC Compliance Checklist 2026, and for the wider compliance landscape beyond CMMC, our compliance services hub covers the frameworks regulated businesses juggle alongside defense work.

What enforcement looks like

The DOJ Civil Cyber-Fraud Initiative has produced settlements that make the stakes concrete: Verizon $4.09M in 2023, Penn State $1.25M in 2024, Raytheon $8.4M in May 2025, and Georgia Tech $875K on 2025-09-30.

A Step-by-Step Plan in Order to Obtain Access to CUI

Contractors who succeed in obtaining access to CUI tend to follow the same sequence. The order matters because each step produces the evidence the next step depends on. Here is the plan we walk through with clients at Petronella Technology Group, Inc.

  1. Confirm whether you actually have CUI. Review your contracts and solicitations. Federal Contract Information triggers the FAR 52.204-21 baseline and Level 1 obligations. Only contracts that deliver or generate Controlled Unclassified Information trigger the full NIST SP 800-171 obligation and, where DFARS 252.204-7021 appears, a CMMC Level 2 certificate before award. If you are unsure what a clause means, ask the contracting officer in writing.
  2. Scope your CUI boundary. Decide where CUI will live and, just as important, where it will not. Enclaving CUI into a narrowly scoped boundary, such as a GCC High tenant or a dedicated cloud landing zone, keeps the 110 controls from applying across your entire enterprise network. This reduces audit surface, shortens timelines, and lowers ongoing cost.
  3. Run a gap analysis against NIST SP 800-171 Revision 2. Assess all 110 practices across the 14 domains. Score yourself honestly using the point weights DoD uses, where controls carry 1, 3, or 5 points, so your result is comparable to the SPRS self-assessment scale that runs from minus 203 to 110.
  4. Post your current score to SPRS. DFARS 252.204-7019 requires a current NIST SP 800-171 assessment summary score in the Supplier Performance Risk System when an offer is submitted. DFARS 252.204-7020 governs how the assessment is conducted and gives DoD access to verify it.
  5. Remediate in priority order. Close the gaps that protect CUI confidentiality first. Remember that NIST SP 800-171 requires FIPS-validated cryptography to protect the confidentiality of CUI. Strong but unvalidated encryption does not meet the requirement.
  6. Write and maintain your documentation. Build a System Security Plan covering all 110 controls with named owners and evidence pointers, the 14 control-family policies, an incident response plan, an acceptable use policy, and a media protection policy. Treat the SSP as a living document from day one.
  7. Track remaining gaps on a POA&M. Plans of Action and Milestones are allowed only for "not met" requirements within the limits of 32 CFR 170.21, with a 180-day closeout. Review the POA&M at least quarterly.
  8. Prepare for and schedule a C3PAO assessment. Only a C3PAO can issue a CMMC Level 2 certificate. The authorized list is maintained at cyberab.org/marketplace. A mock assessment using the Cyber AB CMMC Assessment Process is a standard readiness deliverable before the real thing.
  9. Sustain the program after certification. Certification is not a finish line. Reassessment occurs every three years, the senior official affirms annually, and evidence must be refreshed continuously.

A typical CMMC Level 2 readiness engagement runs 12 to 14 weeks for a mid-size contractor: Discovery in week 1, Gap Analysis in weeks 2 through 4, a Remediation Sprint in weeks 5 through 12, and C3PAO Readiness Handoff in weeks 13 and 14. The path from gap assessment to C3PAO-ready typically takes 6 to 18 months depending on your starting security posture and the complexity of your CUI environment.

The Most Common Mistakes We See, and How to Avoid Them

Each one is avoidable if you know to look for it.

  • Guessing at CUI scope. Some contractors assume they have no CUI because they never touch classified material. CUI is unclassified. Others assume every system they own is in scope. Both errors are expensive. Confirm scope from the contract language and the markings on the documents themselves.
  • Conflating distribution statements with CUI markings. DoD Instruction 5230.24 governs distribution statements on technical documents, but a distribution statement does not satisfy CUI marking requirements. The two are applied in parallel. Under 32 CFR 2002.20, every page containing CUI needs the CUI banner marking and a designation indicator naming the designating agency.
  • Applying dissemination controls you are not authorized to apply. Under 32 CFR 2002.16, only the designating agency can apply limited dissemination controls. Contractors mark, handle, and safeguard; they do not invent new restrictions.
  • Using encryption that is strong but not FIPS-validated. This is one of the most common technical findings. The requirement is FIPS-validated cryptography, and DoD CIO FAQ clarifications add that encrypted CUI is still CUI. Encrypting a file does not remove it from scope.
  • Assuming a cloud provider solves the problem by itself. Encrypted CUI in a cloud still needs FedRAMP Moderate or an equivalency. The same baseline applies to cloud providers under DFARS 252.204-7012 after an incident.
  • Ignoring the flow-down obligation. DFARS 252.204-7012 must be flowed down to subcontractors, including for commercial products and services, when performance involves covered defense information. A subcontractor reports its own incidents to DoD and gives the report number to the next higher tier. If your suppliers are unprepared, your contract is at risk.
  • Overstating a self-assessment score. The DOJ Civil Cyber-Fraud Initiative has produced settlements including Verizon at $4.09M in 2023, Penn State at $1.25M in 2024, Raytheon at $8.4M in May 2025, and Georgia Tech at $875K on 2025-09-30. Score honestly, document honestly, and fix what is broken.
  • Treating the SSP as a one-time deliverable. The SSP is a living document and the POA&M is reviewed at least quarterly. A stale SSP unravels quickly under an assessor's questioning.
  • Waiting for perfect clarity on the timeline. The CMMC Program rule, 32 CFR Part 170, took effect 2024-12-16. Separately, on 2026-07-13 the DoD CIO announced suspension of the 2026-11-10 Phase II deadline; Phase I self-assessments remain in force and later milestones are paused until further notice. Those are two different dates doing two different jobs: 2025-11-10 is when the acquisition rule took effect, and 2026-11-10 was the Phase II milestone that has been suspended. The clause applies when it appears in a solicitation, so the practical requirement arrives contract by contract regardless of program-wide milestones.

How to Choose a Provider: The Questions to Ask

The CMMC ecosystem includes several distinct roles, and confusion between them costs contractors time and money. Before you sign with anyone, ask these questions.

  • Are you an RPO or a C3PAO? A Registered Provider Organization prepares contractors for assessment. Only a C3PAO can conduct the Level 2 assessment and issue the certificate, and the C3PAO submits results to eMASS with the certificate stored in SPRS. Verify RPO status on the Cyber AB Marketplace.
  • Who holds the CMMC Registered Practitioner credential on my engagement? Ask for names. At Petronella Technology Group, Inc., every engineer assigned to a defense client holds the CMMC-RP credential: Blake Rea, Justin Summers, Jonathan Wood and Craig Petronella.
  • Will you help me scope an enclave? Enclaving CUI into a narrowly scoped boundary such as a GCC High tenant or a dedicated cloud landing zone reduces audit surface, shortens timelines, and lowers ongoing cost.
  • What are your deliverables? Look for a concrete list: an SSP covering all 110 controls with owners and evidence pointers, the 14 control-family policies plus an incident response plan, acceptable use and media protection policies, a live POA&M, a mock assessment using the Cyber AB CMMC Assessment Process, a baselined SPRS score, and a C3PAO shortlist with warm introductions.
  • Do you promise a pass?
  • What happens after certification? Reassessment occurs every three years, the POA&M is reviewed at least quarterly, and policies need refresh. Ask what the maintenance relationship looks like.

For a deeper look at the service itself, see our CMMC consultant services and our broader CMMC compliance program pages. If your environment also carries health data, our compliance practice hub covers how CMMC, HIPAA, and other frameworks fit together.

How Petronella Technology Group, Inc. Helps

Petronella Technology Group, Inc. is a Cyber AB Registered Provider Organization, RPO #1449. We prepare contractors for CMMC assessment; we do not perform CMMC certification assessments for any organization. Authorized C3PAOs conduct Level 2 certification assessments.

Our readiness work follows the structure described above. A typical CMMC Level 2 engagement is a 12 to 24 week initial build followed by years of POA&M tracking, annual evidence refresh, and re-assessment every three years. Deliverables include the SSP covering all 110 NIST SP 800-171 controls, the control-family policies, a live POA&M, a mock assessment using the Cyber AB CMMC Assessment Process, a baselined SPRS score, and a C3PAO shortlist with warm introductions. Twenty minutes of discovery conversation typically gives us enough to size a fixed-scope quote within two business days.

Every practitioner on the compliance team holds the CMMC Registered Practitioner designation. Craig Petronella, who founded the company in 2002, holds CMMC-RP, CCNA, CWNE, North Carolina Licensed Digital Forensic Examiner license #604180, and an MIT AI certificate, with more than 30 years of experience. The firm has been BBB accredited with an A+ rating continuously since 2003.

Engagements are delivered remote-first across all 50 states. The first call is a free 30-minute scoping consultation run by a CMMC Registered Practitioner. For contractors whose exposure extends beyond CUI, our vCISO practice provides a named security officer of record for CMMC senior official authorization, with formal designation documentation provided, and the team rehearses audits with clients twice before the assessor arrives.

Primary sources for this guide: 32 CFR Part 170 - CYBERSECURITY MATURITY MODEL CERTIFICATION (CMMC) PROGRAM, SP 800-171 Rev. 2, Protecting Controlled Unclassified Information in Nonfederal Systems an.

Related reading

Frequently Asked Questions

Do I need CMMC certification in order to obtain access to CUI?

Not always. The requirement attaches when DFARS 252.204-7021 appears in your contract or solicitation, and in that case you must hold a valid CMMC certificate at the specified level before award. Separately, DFARS 252.204-7012 requires adequate security, defined as the 110 controls of NIST SP 800-171, on every covered contractor information system regardless of whether a certificate is required yet.

What level of CMMC do I need for CUI?

Level 2 covers Controlled Unclassified Information and requires all 110 practices of NIST SP 800-171 Revision 2 across 14 domains, with a C3PAO assessment for most programs, triennial reassessment, and an annual senior official affirmation. Level 1 covers only Federal Contract Information with 15 basic safeguarding requirements from FAR 52.204-21. Level 3 adds selected controls from NIST SP 800-172 on top of Level 2 and is assessed by the government through DCMA DIBCAC.

Can I self-assess for CMMC Level 2?

No. Only a C3PAO can issue a CMMC Level 2 certificate. Self-assessments apply to Level 1 and to the SPRS summary score required under DFARS 252.204-7019, but the Level 2 certification assessment must be conducted by an authorized C3PAO listed at cyberab.org/marketplace.

Does the suspended Phase II deadline mean I can wait?

The suspension announced on 2026-07-13 paused the 2026-11-10 Phase II milestone, while Phase I self-assessments remain in force and later milestones are paused until further notice. The practical driver has not changed: when DFARS 252.204-7021 appears in a solicitation, a valid certificate at the specified level is required before award.

What happens if we have a CUI incident?

DFARS 252.204-7012 requires reporting a cyber incident affecting covered defense information to DoD within 72 hours of discovery through the reporting portal at dibnet.dod.mil, which requires a DoD-approved medium assurance certificate obtained in advance. After a reported incident you must preserve images of affected systems and monitoring data for at least 90 days, submit isolated malicious software to the government, and hold cloud providers to a FedRAMP Moderate baseline.

How long does it take to become CMMC Level 2 ready?

A typical readiness engagement runs 12 to 14 weeks for a mid-size contractor, moving through Discovery, Gap Analysis, a Remediation Sprint, and C3PAO Readiness Handoff. The full path from gap assessment to C3PAO-ready typically takes 6 to 18 months depending on starting security posture and CUI environment complexity, and scoping CUI into a narrow enclave is one of the levers that shortens that path.

To talk through your specific contracts and timeline, call Penny, our AI assistant, at 919-348-4912, or reach us through our contact form. The first consultation is a free 30-minute scoping call with a CMMC Registered Practitioner.

Online course from the Petronella Technology Group, Inc. Training Academy

CMMC Level 2 Security Awareness: Common Core

Foundational CMMC Level 2 awareness for all roles: CUI, insider threat, phishing, passwords and MFA, physical security, and incident reporting.

Price: $49

View the course Team packs

Get the CMMC Compliance Guide

Free, practical, and specific to regulated environments. We will email it to you.

No spam. Unsubscribe anytime.

Need help implementing these strategies? Our cybersecurity experts can assess your environment and build a tailored plan. Prefer to write? Send us a message.
Call Penny 919-348-4912

About the Author

Craig Petronella, CEO and Founder of Petronella Technology Group
CEO, Founder & AI Architect, Petronella Technology Group

Craig Petronella founded Petronella Technology Group in 2002 and has spent 30+ years professionally at the intersection of cybersecurity, AI, compliance, and digital forensics. He holds the CMMC Registered Practitioner credential issued by the Cyber AB and leads Petronella as a Cyber AB Registered Provider Organization (RPO #1449). Craig is an NC Licensed Digital Forensics Examiner (License #604180-DFE) and completed MIT Professional Education programs in AI, Blockchain, and Cybersecurity. He also holds CompTIA Security+, CCNA, and Hyperledger certifications.

He is an Amazon #1 Best-Selling Author of 15+ books on cybersecurity and compliance, host of the Encrypted Ambition podcast (95+ episodes on Apple Podcasts, Spotify, and Amazon), and a cybersecurity keynote speaker with 200+ engagements at conferences, law firms, and corporate boardrooms. Craig serves as Contributing Editor for Cybersecurity at NC Triangle Attorney at Law Magazine and is a guest lecturer at NCCU School of Law. He serves as a digital forensics expert witness for law firms on matters involving cybercrime, cryptocurrency fraud, SIM-swap attacks, and data breaches.

Under his leadership, Petronella Technology Group has served hundreds of regulated SMB clients across NC and the southeast since 2002, earned a BBB A+ rating every year since 2003, and been featured as a cybersecurity authority on CBS, ABC, NBC, FOX, and WRAL. The company leverages SOC 2 Type II certified platforms and specializes in AI implementation, managed cybersecurity, CMMC/HIPAA/SOC 2 compliance, and digital forensics for businesses across the United States.

CMMC-RP NC Licensed DFE MIT Certified CompTIA Security+ Expert Witness 15+ Books
Related Service
Achieve Compliance with Expert Guidance

CMMC, HIPAA, NIST, PCI-DSS - we have 80% of documentation pre-written to accelerate your timeline.

Learn About Compliance Services
All Posts Next
Questions about this topic? Talk to our team. Call Penny 919-348-4912 Message us