What Is CUI? A Guide for Defense Contractors
Updated November 16, 2026
If you build parts, write software, or support a program for the Department of Defense, you handle government information every day. Some of it is public. Some of it carries rules. Knowing which is which decides your CMMC level, your system boundary, and how much security work lands on your team.
Quick Answer
CUI, or Controlled Unclassified Information, is unclassified government information that a law, regulation, or government-wide policy says must be safeguarded or limited in how it is shared. In defense work it often takes the form of technical drawings, specifications, test data, and export-controlled data. A contractor that handles CUI must protect it under DFARS 252.204-7012 and NIST SP 800-171, and CMMC Level 2 applies to the systems that store, process, or transmit it.
What Is CUI?
CUI is information the federal government creates or holds, or that a contractor creates or holds for the government, that a law, regulation, or government-wide policy says needs protection. It is not classified, so it does not need a security clearance. It does need controls on who can see it, where it is stored, and how it moves.
The National Archives (NARA) runs the government-wide CUI program through the CUI Registry, which lists the categories of information that qualify. Executive Order 13556 created the program, and 32 CFR Part 2002 sets the rules. The Department of Defense applies those rules through DoDI 5200.48, issued March 6, 2020.
Is CUI the Same as FCI, CDI, and CTI?
No. Four terms come up in almost every defense contract, and each one points to a different set of rules. Here is how they line up.
| Term | What it means | Where it comes from | CMMC level |
|---|---|---|---|
| FCI (Federal Contract Information) | Information not intended for public release that is provided by or generated for the government under a contract. It leaves out public information and simple transactional data such as payment details. | FAR 52.204-21 | Level 1 |
| CUI (Controlled Unclassified Information) | Unclassified information that law, regulation, or government-wide policy says to protect or control. | EO 13556, 32 CFR Part 2002, the CUI Registry | Level 2 or Level 3 |
| CDI (Covered Defense Information) | The DFARS term for unclassified controlled technical information or other CUI Registry information that requires safeguarding. | DFARS 252.204-7012 | Level 2 or Level 3 |
| CTI (Controlled Technical Information) | Technical information with military or space application that is subject to controls on access, use, release, or sharing. | DFARS 252.204-7012 and DoDI 5230.24 | Level 2 or Level 3 |
FCI is the broad group, and CUI is the narrower group with stricter rules. Every CUI document is also contract information, but most contract information is not CUI. In defense work, CDI and CUI usually describe the same data, and CTI is the type a manufacturer meets most often.
What Counts as CUI in Defense Work?
Defense contractors most often handle three groups of CUI. Each group has its own marking code.
| Category | Typical marking | Common examples |
|---|---|---|
| Controlled Technical Information | CUI//SP-CTI | Technical drawings, blueprints, plans, reports, software and its documentation |
| Export Controlled | CUI//SP-EXPT | Technical data that falls under export control rules such as ITAR or the EAR |
| Privacy | PRVCY | Personal information about employees or service members that a program must protect |
A machine shop that receives a drawing with a CTI marking holds CUI. A software team that gets test data for a weapon system holds CUI. A staffing partner that handles personnel records for a defense program may hold CUI as well. The category that fits depends on the contract, so the contract is the first place to look. Our guide for manufacturers shows how this plays out on a shop floor.
What Is the Difference Between CUI Basic and CUI Specified?
CUI Basic is information with a legal basis for protection but no detailed handling rules in the law itself. Agencies apply the standard controls from 32 CFR Part 2002 and the CUI Registry. CUI Specified is information where the law or regulation spells out particular handling rules, and those rules apply in addition to the baseline. The SP in a marking such as CUI//SP-CTI stands for Specified.
How Do I Know If I Have CUI?
Start with the contract and work outward. Most companies can answer the question in a few hours with the steps below.
- Read the contract clausesA contract that includes DFARS 252.204-7012 tells you that covered defense information may be involved.
- Check the statement of workLook for references to controlled data, technical data packages, or specific CUI categories.
- Look at the documents you receiveFind the CUI banner at the top and bottom of pages and the designation indicator block on the first page.
- Trace what you createReports, models, and drawings you build from CUI usually carry the same status as the source.
- Ask the sourceWhen markings are missing or unclear, ask your contracting officer or prime contractor to confirm in writing.
- Write it downRecord the answer in your system security plan so your scope and your assessor see the same facts.
What Does a CUI Marking Look Like?
The DoD marks CUI with two required elements. The first is the banner, which is the word CUI in bold capital letters at the top and bottom of every page. DoD authorizes the term CUI and does not use the longer alternative that civilian agencies may choose. The second is the designation indicator block on the first page. The person who creates the document applies these markings.
| Designation indicator line | What goes there |
|---|---|
| Controlled by | The DoD component or organization that designated the information. |
| CUI Category | The category, such as CTI or Export Controlled. |
| Distribution Statement or LDC | The distribution statement or limited dissemination control that applies. |
| POC | The name and phone number or office mailbox of the originating component. |
The DoD Inspector General has found that some CUI documents were created without the designation indicator block, so markings on documents you receive may be incomplete. Treat a missing marking as a question for your contracting officer and not as an answer.
What Does a Contractor Do to Protect CUI?
Contractors protect CUI on their own systems with NIST SP 800-171 Revision 2, which has 110 requirements. DFARS 252.204-7012 makes those requirements part of the contract. CMMC Level 2 is how the DoD checks them. Our guide to CMMC Level 2 explains the levels, and the CMMC compliance requirements page lists them.
Five habits keep CUI under control.
- Keep CUI in a defined set of systems, so the boundary stays small. An enclave is one way to do that, and our comparison of enterprise and enclave approaches covers the options.
- Use a platform built for government data. Microsoft GCC High is a common choice for contractors that handle CUI.
- Train every person who touches CUI. DoDI 5200.48 calls for initial and annual CUI training for DoD personnel and contractors who handle it.
- Report cyber incidents within the 72-hour window in DFARS 252.204-7012. The DFARS learning center has the details.
- Record where CUI lives in the system security plan, and update the plan when that changes. Our SSP guide shows how.
How Does CUI Set Your CMMC Level and Scope?
The information you handle sets the level. Contracts with FCI only call for Level 1. Contracts with CUI call for Level 2, which is assessed by a self-assessment or by a C3PAO depending on the contract. The most sensitive programs can call for Level 3.
CUI also sets scope. Every system, person, and location that stores, processes, or transmits CUI falls inside the assessment boundary, and so do the security systems that protect them. A smaller footprint of CUI means a smaller boundary, fewer systems to document, and a shorter assessment. See what to expect during a Level 2 assessment to see how scope is checked.
A note on timing. In July 2026 the Department announced it was suspending the CMMC Phase II rollout. Phase I self-assessment requirements remain in place, and the DFARS 252.204-7012 obligations still apply. Self-assessments and select government-led assessments continue to enforce the Revision 2 requirements. See the Department announcement of July 13, 2026, 32 CFR Part 170, and DFARS 252.204-7025.
CMMC Readiness AssessmentFind out which of your systems fall into scope and where the gaps sit before the real assessment.
Frequently Asked Questions
What does CUI stand for?
Is all unclassified government information CUI?
Who decides what counts as CUI?
Does CUI have to be marked?
What is covered defense information?
Do subcontractors need to protect CUI?
Not sure where your CUI lives?
Sentinel Blue helps defense contractors map their CUI, set a clean boundary, and get ready for CMMC Level 2.