Previous All Posts Next

Information may be CUI in accordance with the law, regulation, or government policy cited by the designating agency, and this guide shows you how to make that determination.

This guide is written for defense contractors, subcontractors, and compliance leaders who have seen the phrase "information may be CUI in accordance with" on a government document or in a contract and need to know what it means, what obligations follow, and how to decide whether their systems fall in scope. It covers the origin of Controlled Unclassified Information, the marking and handling rules, the DFARS and CMMC requirements that attach once you hold CUI, and a practical decision process you can run against your own contracts.

Key Takeaways

  • CUI status comes from the underlying law, regulation, or government-wide policy that the designating agency cites, not from the contractor's judgment alone. Executive Order 13556, signed November 4, 2010, created the program, and 32 CFR Part 2002 is the government-wide rule.
  • Inside the Department of Defense, DoD Instruction 5200.48, issued March 6, 2020, implements the CUI program, and DoD marks documents under its own CUI guidance alongside distribution statements under DoD Instruction 5230.24.
  • Once you receive or generate CUI, the full safeguarding obligation of NIST SP 800-171 applies to your covered systems, which is the foundation of DFARS 252.204-7012 and CMMC Level Two.
  • Marking matters as much as classification: 32 CFR 2002.20 requires a CUI banner on every page containing CUI plus a designation indicator naming the designating agency.
  • If you cannot tell whether your contract involves CUI, treat the question as a scope decision with real assessment cost, and resolve it deliberately rather than by default.

What "Information May Be CUI in Accordance With" Actually Means

Where CUI comes from

Controlled Unclassified Information was created by Executive Order 13556, signed November 4, 2010. The order designated the National Archives and Records Administration as the Executive Agent for the CUI program, and 32 CFR Part 2002 is the government-wide rule that implements it.

Within the Department of Defense, DoD Instruction 5200.48, issued March 6, 2020, implements the CUI program inside DoD.

CUI Basic and CUI Specified

32 CFR Part 2002 divides CUI into two kinds, and the distinction drives your obligations.

  • CUI Basic carries the uniform controls: a moderate confidentiality baseline that applies to all CUI unless the underlying authority adds more.
  • CUI Specified carries handling controls written directly into the underlying law, regulation, or policy. Dissemination limits, access restrictions, or destruction requirements may apply on top of the baseline.

When you evaluate whether information may be CUI in accordance with a cited authority, part of the evaluation is determining which kind you are holding. The cited law, regulation, or policy tells you. If it adds handling requirements beyond the baseline, the information is CUI Specified. If it does not, it is CUI Basic.

Marking: what you should see on the document

Under 32 CFR 2002.20, every page containing CUI carries a CUI banner marking, and the document carries a designation indicator naming the designating agency. Under 32 CFR 2002.16, only the designating agency may apply limited dissemination controls,

One point that trips up defense contractors regularly: DoD Instruction 5230.24 governs distribution statements on technical documents, and a distribution statement does not satisfy CUI marking requirements. The two are applied in parallel. A technical document with a distribution statement may also be CUI, and the CUI banner and designation indicator must appear independently.

When Information May Be CUI in Accordance With a Contract: The Decision Criteria

Contractors rarely receive a clean, labeled package of CUI. More often the question arrives sideways: a solicitation references technical data, a prime sends drawings with an unfamiliar legend, or a program office mentions that a deliverable "may contain CUI." Here is the evaluation we walk clients through.

Step one: find the cited authority

Read it. The authority is the law, regulation, or government policy under which the agency designated the information.

Step two: confirm the government is the designating source

CUI designation is a government act. This is why the designation indicator names the designating agency.

Step three: distinguish FCI from CUI

This is the most consequential fork in the evaluation, and it determines which regulatory regime applies to you.

QuestionFederal Contract Information (FCI)Controlled Unclassified Information (CUI)
What is it?
What safeguarding applies?The 15 basic safeguarding requirements of FAR 52.204-21The full 110 controls of NIST SP 800-171 on covered contractor information systems
What assessment regime?CMMC Level One: annual self-assessment and annual senior official affirmationCMMC Level Two: C3PAO assessment for most programs, triennial reassessment, annual affirmation
Who bears it?Every DoD contractor handling FCIOnly contractors that receive or generate CUI

Every DoD contractor handling FCI must meet the FAR 52.204-21 baseline. Only contractors that receive or generate CUI take on the full NIST SP 800-171 obligation.

Step four: trace where the CUI will live

Once you know CUI will flow, map the systems that will store, process, or transmit it. DFARS 252.204-7012 requires adequate security, defined as the 110 controls of NIST SP 800-171, on every covered contractor information system. Contractors who enclave CUI into a narrowly scoped boundary, such as a GCC High tenant or a dedicated cloud landing zone, keep the 110 controls from applying across the entire enterprise network. Our CMMC consulting team treats the CUI boundary decision as the first major milestone of any engagement for exactly that reason.

What Changes Once You Hold CUI: DFARS, SPRS, and CMMC

Determining that information may be CUI in accordance with a contract's cited authority is not the end of the analysis.

The DFARS foundation

It requires the 110 controls of NIST SP 800-171 on every covered contractor information system, and it 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,

The clause also carries incident response duties with real operational weight. 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. Note that 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 guidance adds that encrypted CUI is still CUI, and encrypted CUI in a cloud still needs FedRAMP Moderate or an equivalency.

SPRS scoring and the assessment clauses

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 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.

Where CMMC fits

The CMMC Program rule, 32 CFR Part 170, was published October 15, 2024 and took effect December 16, 2024. 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.

The program has three levels. Level One covers FCI with the 15 basic safeguarding requirements of FAR 52.204-21, an annual self-assessment, and an annual senior official affirmation. Level Two covers CUI: all 110 practices of NIST SP 800-171 Revision 2, organized into 14 domains, with a C3PAO assessment for most programs, triennial reassessment, and annual affirmation. Level Three adds selected controls from NIST SP 800-172 on top of Level Two and is assessed by the government through DCMA DIBCAC rather than a C3PAO.

On July 13, 2026, the DoD CIO announced the suspension of the November 10, 2026 Phase II deadline; Phase I self-assessments remain in force and later milestones are paused until further notice. A DoD class deviation keeps DFARS 252.204-7012 on NIST SP 800-171 Revision 2 for now.

Enforcement is not theoretical

The Department of Justice's Civil Cyber-Fraud Initiative has produced settlements against contractors that misrepresented their security posture: 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 September 30, 2025.

How to Evaluate Your Own Exposure

Run a contract inventory

Pull every active DoD contract and subcontract. For each, identify whether DFARS 252.204-7012 appears, whether covered defense information is defined in the contract, and whether any document delivered or received carries CUI markings.

Score yourself honestly before anyone else does

POA&Ms are allowed only for "not met" requirements within the limits of 32 CFR 170.21, with a 180-day closeout, A typical CMMC Level Two readiness engagement runs 12 to 14 weeks for a mid-size contractor: Discovery in week one, Gap Analysis in weeks two through four, a Remediation Sprint in weeks five through twelve, and C3PAO Readiness Handoff in weeks thirteen and fourteen. From gap assessment to C3PAO-ready, the full path typically takes 6 to 18 months depending on starting security posture and CUI environment complexity.

Know who can do what

Only a C3PAO can issue a CMMC Level Two certificate; the C3PAO submits results to eMASS and the certificate is stored in SPRS. The list of authorized C3PAOs is maintained at cyberab.org/marketplace. A Registered Provider Organization such as Petronella Technology Group, Inc. prepares a contractor for assessment but cannot conduct the assessment or issue a certificate, and we do not promise guaranteed pass outcomes. What a prepared contractor gets is an SSP covering all 110 controls with owners and evidence pointers, 14 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. If you are sorting out which kind of help you need, our compliance services hub lays out the options, and Why Petronella covers our background, including continuous BBB A+ accreditation since 2003.

Get the determination reviewed by someone who does this weekly

Twenty minutes of discovery conversation typically gives our team enough to size a fixed-scope engagement within two business days. The first call is a free 30-minute scoping consultation run by a CMMC Registered Practitioner, delivered remote-first across all 50 states. When you are ready, contact us or call Penny, our AI assistant, at 919-348-4912.

A Step-by-Step Plan for Handling Possible CUI

Once you suspect that information in your custody may be CUI in accordance with a contract, law, or regulation, The best move is to work through a deliberate sequence that establishes what you hold, what rules apply, and what safeguarding obligation follows.

  1. Inventory the paper. Pull every active contract, solicitation, subcontract, and flow-down clause. Look for DFARS 252.204-7012, DFARS 252.204-7019, DFARS 252.204-7021, and FAR 52.204-21. Note which clauses actually appear in your documents rather than assuming they do.
  2. Identify the data itself. Walk your teams through what they receive, generate, and store for each contract: technical drawings, specifications, performance data, and anything marked or referenced as controlled. Ask where it lives, who touches it, and how it moves.
  3. Trace the designation. Where a document carries a CUI banner or designation indicator under 32 CFR 2002.20, record the designating agency and the category. Where the marking is absent but the underlying law, regulation, or policy suggests control, flag it for a determination rather than guessing.
  4. Separate FCI from CUI. Federal Contract Information triggers the 15 basic safeguarding requirements of FAR 52.204-21. Information that qualifies as CUI triggers the full NIST SP 800-171 obligation.
  5. Scope your environment. Decide whether CUI will live across your enterprise or inside a narrowly scoped enclave, such as a GCC High tenant or a dedicated cloud landing zone. Enclaving keeps the 110 controls from applying across the entire network, reduces audit surface, shortens timelines, and lowers ongoing cost.
  6. Assess against the requirement. Perform a self-assessment against NIST SP 800-171 Revision 2, the authoritative source for the CUI security requirements per NIST. Record a score, noting that controls carry 1, 3, or 5 point weights and the SPRS range runs from minus 203 to 110.
  7. Post your score and build your artifacts. DFARS 252.204-7019 requires a current assessment summary score in SPRS when an offer is submitted. Build or refresh your System Security Plan, your POA&M, and your control-family policies. Remember that POA&Ms are allowed only for "not met" requirements within the limits of 32 CFR 170.21, with a 180-day closeout.
  8. Determine your CMMC level. If a solicitation or contract includes DFARS 252.204-7021, you must hold a valid CMMC certificate at the specified level before award. Level One covers FCI with an annual self-assessment and senior official affirmation. Level Two covers CUI with all 110 practices of NIST SP 800-171 Rev 2 and, for most programs, a C3PAO assessment.
  9. Flow the obligation down. 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 and gives the report number to the next higher tier.
  10. Operate it continuously. The SSP is a living document and the POA&M is reviewed at least quarterly. Re-assessment occurs every three years for Level Two programs, with an annual senior official affirmation.

For a mid-size contractor, a typical Level Two readiness engagement runs 12 to 14 weeks: Discovery in week 1, Gap Analysis in weeks 2 through 4, a Remediation Sprint in weeks 5 through 12, and a 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 posture and the complexity of your CUI environment. Our CMMC consulting team runs this sequence with contractors across all 50 states, remote-first.

The Most Common Mistakes We See

Avoiding them costs far less than discovering them in front of an assessor.

  • Treating "unmarked" as "uncontrolled." DoD Instruction 5200.48, issued March 6, 2020, implements the CUI program inside the Department of Defense, and 32 CFR Part 2002 is the government-wide rule.
  • Confusing distribution statements with CUI markings. 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.
  • Assuming encryption solves everything. 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.
  • Letting scope sprawl. Contractors who leave CUI distributed across the whole enterprise inherit the 110 controls everywhere. Enclaving into a narrowly scoped boundary is one of the biggest drivers of quote variance and timeline.
  • Guessing at the SPRS score. A self-assessment score posted to SPRS must be current when an offer is submitted under DFARS 252.204-7019, and DoD can verify it under 252.204-7020.
  • Ignoring the subcontractor tier. The obligation flows down.
  • Treating certification as the finish line. Post-certification, the SSP remains a living document, the POA&M is reviewed at least quarterly, and re-assessment occurs every three years.

How to Choose a Provider: The Questions to Ask

Before you sign anything, put these questions to any candidate.

  • Are you an RPO or a C3PAO? Only a C3PAO can issue a CMMC Level Two certificate; the C3PAO submits results to eMASS and the certificate is stored in SPRS. An RPO prepares a contractor but cannot conduct the assessment or issue a certificate. The list of authorized C3PAOs is maintained at cyberab.org/marketplace.
  • Who holds the credentials? Ask specifically whether every practitioner assigned to your engagement holds the CMMC Registered Practitioner credential, not just the founder.
  • What are your deliverables? A serious readiness engagement produces an SSP covering all 110 NIST SP 800-171 controls with owners and evidence pointers, 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.
  • How do you handle scope? Ask how they will enclave your CUI environment and what that does to your audit surface, timeline, and cost.
  • Do you promise a guaranteed pass?
  • What does ongoing support look like? Quarterly control reviews, policy refresh, training, and incident response capacity should be part of the conversation, because the program is continuous.

How Petronella Technology Group, Inc. Helps

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

Every Petronella engineer assigned to a defense client holds the CMMC Registered Practitioner (CMMC-RP) credential: Blake Rea, Justin Summers, Jonathan Wood, and Craig Petronella. Craig Petronella founded the company in 2002 and 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 first call is a free 30-minute scoping consultation run by a CMMC Registered Practitioner. Twenty minutes of discovery conversation typically gives us enough to size a fixed-scope quote within two business days.

Related guides from Petronella Technology Group, Inc.

Related reading

Frequently Asked Questions

What should I do first if I think I am handling CUI?

Confirm which contract clauses apply to you, then inventory where the information lives and who touches it. From there, perform a self-assessment against NIST SP 800-171 Revision 2 and record the score, since DFARS 252.204-7019 requires a current assessment summary score in SPRS when an offer is submitted.

Do I need a CMMC certificate right now?

It depends on your contracts. 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. Note that on July 13, 2026 the DoD CIO announced suspension of the November 10, 2026 Phase II deadline; Phase I self-assessments remain in force and later milestones are paused until further notice.

What is the difference between CUI Basic and CUI Specified?

Under 32 CFR Part 2002, CUI Basic carries uniform controls at a moderate confidentiality baseline, while CUI Specified carries handling controls written into the underlying law, regulation, or policy.

How quickly must I report a cyber incident involving covered defense information?

Within 72 hours of discovery, through the DoD reporting portal at dibnet.dod.mil. The portal requires a DoD-approved medium assurance certificate obtained in advance, and after a reported incident you must preserve images of affected systems and monitoring data for at least 90 days.

Do you promise a guaranteed pass?

No. Petronella Technology Group, Inc. is an RPO, not a C3PAO, and we do not promise "guaranteed pass" outcomes. We prepare contractors thoroughly, and only a C3PAO can conduct the Level Two certification assessment and issue the certificate.

If you are staring at a contract clause and wondering whether the information in front of you is CUI, do not wait for the question to answer itself. Call Penny, our AI assistant, at 919-348-4912, or use our contact form to schedule your free 30-minute scoping consultation 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
Previous All Posts Next
Questions about this topic? Talk to our team. Call Penny 919-348-4912 Message us