FCI vs CUI comes down to what your contract has you hold. FCI is non-public information the government gives you or you create for it. CUI is a narrower slice that a law, regulation or governmentwide policy says needs safeguarding.
FCI stands for Federal Contract Information, and CUI for Controlled Unclassified Information. Our guide to CMMC requirements for small business sorts the whole program by situation. This page sits one step earlier. It helps you look at the RFQs, purchase orders, subcontracts and drawings already on your desk, the paperwork a prime or an agency actually sends a small shop, and say which kind each one is.
The rules quoted here were read on November 22, 2026. It’s readiness education, not a legal opinion. We don’t certify anyone, and we can’t classify your data for you.

FCI vs CUI in plain words
Federal Contract Information is information, not intended for public release, that the government provides or that’s generated for it under a contract to develop or deliver a product or service. FAR 52.204-21, renumbered 52.240-93 in the FAR Overhaul, leaves out two things: information the government gives the public, such as on public websites, and simple transactional information, such as what’s needed to process payments.
CUI is narrower. Under 32 CFR 2002.4 it’s information that a law, regulation or governmentwide policy requires or permits an agency to handle with safeguarding or dissemination controls, whether the government created it or a contractor created or holds it on the government’s behalf. Classified information isn’t CUI. Neither is anything you’re free to publish.
So the two nest. CUI you hold under a contract is also FCI. The reverse isn’t true. Most FCI never becomes CUI.
Reading your paperwork for FCI vs CUI
Six things a Southern California supplier commonly finds in its inbox, and what each one tends to signal. They’re signals, not verdicts. Where a row says ask, ask the person who sent it.
| What you received | What it signals | What to do next |
|---|---|---|
| An RFQ or purchase order that lists FAR 52.204-21 (or 52.240-93) and no DFARS cyber clause | FCI. The contract information you’ll hold isn’t public, and basic safeguarding applies. | Plan for the 15 basic safeguards on the systems that hold it. |
| An email with your delivery schedule, quantities and part numbers | FCI. It was generated under the contract and wasn’t meant for release. | Keep it on the same safeguarded email and file systems. |
| A payment remittance, or a drawing the agency posted on a public website | Neither, on its own. FAR 52.204-21 excludes public information and simple payment details. | Don’t build scope around it. Check what’s attached to it, though. |
| A subcontract that carries DFARS 252.204-7012 | Ask. The clause covers covered defense information, which is CUI. It doesn’t prove any will reach you. | Ask the prime, in writing, what CUI flows to you and on which systems. |
| A drawing or model with “CUI” across the top and a designation indicator | CUI. A banner marking is the plainest signal there is. | Store, send and print it only where NIST SP 800-171 is met. |
| An older technical drawing with a distribution statement but no CUI banner | Ask. Older DoD technical data often predates CUI markings and may still be controlled. | Handle it as controlled until the sender tells you otherwise in writing. |
One stack can hold all six. That’s normal, and it’s why the answer is usually “both, in different places.”
How CUI shows up on a drawing
Start with the first line on the sheet. Marked CUI carries a banner at the top of the page, the word “CUI” or “CONTROLLED”, and a designation indicator that names, at a minimum, the agency that designated it, so you can tell who to ask. The National Archives keeps the CUI Registry, the official list of what counts as CUI, category by category.
Look for these:
- The banner itself, plus any category after it, such as “CUI//SP-” for a specified category
- Controlled Technical Information, marked “CUI//SP-CTI”: technical data with military or space application, the category machine shops and electronics builders meet most
- Export Controlled data. ITAR or EAR wording in the notes block is a strong hint
- A distribution statement on an older drawing
Basic or Specified?
CUI Basic gets the standard handling. CUI Specified is CUI where the authority behind it sets extra rules, and those rules come along with the data. The marking tells you which. If it doesn’t, ask.


What FCI and CUI each ask of your systems
FCI brings the 15 basic safeguarding requirements in FAR 52.204-21: limit access, identify and authenticate users, sanitize media, patch, scan for malicious code. CUI on a DoD contract brings DFARS 252.204-7012, which points you to NIST SP 800-171 and to cyber incident reporting within 72 hours of discovery. CMMC Level 2 uses its Rev. 2, with 110 requirements.
CMMC follows the same line. Under 32 CFR 170.23, a subcontractor that handles only FCI needs Level 1 (Self), and one that handles CUI needs at least Level 2 (Self). Our page on CMMC Level 1 vs Level 2 compares the two levels row by row.
Scope it right, not big
Calling everything CUI feels safe. It isn’t free, because every system that touches CUI comes into Level 2 scope, from the shared drive to the CAD workstation next to the mill, and each of those systems then has to meet all 110 requirements. Calling nothing CUI is worse. Keep CUI in as few places as you can, and write down where.
FCI vs CUI by the clause
Four figures, each from the rule that sets it.
72 hours
To report a cyber incident affecting covered defense information
Source: DFARS 252.204-7012(c)
Sources checked November 22, 2026.
Once you know what you hold
FCI only: the 15 safeguards
Each basic safeguard is read in plain words in our CMMC Level 1 requirements guide, one at a time.
CUI: the 110 requirements
Our CMMC Level 2 requirements guide maps all 110 to NIST’s 14 families and explains how scoring works.
Turn it into steps
The clause and the record behind every step sit side by side in our CMMC compliance checklist.
Talk scope through with us
Readiness guidance and referrals to certified assessors come through our CMMC and compliance readiness service.
Two posts for suppliers further down the chain
- Does CMMC apply to my company? A first check before any of this
- What a prime will still ask its CUI subcontractors for, clause by clause
What suppliers ask about FCI and CUI
Is FCI part of CUI, or the other way round?
CUI held under a government contract is also FCI, but most FCI never rises to CUI. Think of CUI as the smaller circle inside.
That’s why a CUI contract’s safeguards also cover the FCI on the same systems, and why an FCI-only shop doesn’t automatically need the CUI rules.
So is a purchase order FCI?
Short answer: the order details usually are, and the payment details usually aren’t.
Quantities, delivery dates and part numbers were created under the contract and aren’t public, so they’re FCI, while the simple transactional information needed to process a payment is carved out by FAR 52.204-21. The drawings attached to the order are a separate question, and the one that matters most.
If we only handle FCI, do we need an outside assessor?
Level 1 (Self) is a self-assessment, so the rule doesn’t call for a third-party assessor when FCI is all you handle.
You still post the result in SPRS, the Supplier Performance Risk System, and a senior official affirms it every year.
Does FCI have to carry a marking?
The better question is whether your CUI is marked, since FCI has no banner of its own in FAR 52.204-21.
FCI is defined by where it came from, not by a label. CUI is the one with a banner. An unmarked drawing can still be CUI, especially older technical data, so a missing banner is a reason to ask, not a green light.
What if our prime handles CUI but our part of the job doesn’t touch it?
Common, and it’s settled by what actually flows to you, not by what the prime holds.
Under 32 CFR 170.23 the level that flows down to you depends first on the information your own subcontract will process, store or transmit, and only then on the level the prime’s contract carries. Get the answer in writing. A prime that says “no CUI” today can send a marked drawing next quarter, and then the answer changes.
Can the cluster tell us whether our data is CUI?
We can’t make that call for you, because the agency or prime that created the information decides whether it’s CUI.
We provide readiness guidance and gap assessments, including help reading your clauses and markings so you ask the right questions. Formal CMMC certification requires a third-party assessment organization. Third-party CMMC assessments by certified assessors involve fees charged directly by those providers, not by the cluster.
Sort your paperwork with the cluster
Membership and cluster-funded services are provided at no cost to eligible participating businesses, subject to program requirements and available resources.
