What is CUI? Controlled Unclassified Information Explained
Controlled Unclassified Information (CUI) is government information that is not classified but still requires protection. If your contract includes drawings, specifications, or test data, some may qualify as CUI.
Talk to a CMMC Advisor
Submit your details below to schedule your confidential 30-minute scoping review:
Introduction (CUI: Controlled Unclassified Information)
So, what is CUI? CUI stands for Controlled Unclassified Information. It refers to sensitive government information that is not classified but must be safeguarded. Under 32 CFR Part 2002, federal agencies and contractors must follow specific rules for handling it.
If you work in the Defense Industrial Base (DIB), your contract may give you access to CUI data. CMMC (Cybersecurity Maturity Model Certification) verifies how the DoW expects contractors to protect that information. Contractors handling CUI need CMMC Level 2, based on the 110 requirements of NIST SP 800-171.
What CUI Is
6 key characteristics of CUI
Government information
CUI is information the government creates or owns, or that others create for it, which law or policy requires them to safeguard.
Not classified
CUI is unclassified, but mishandling it can violate contract requirements.
Different from FCI
Federal Contract Information (FCI) is basic, non-public contract information. CUI has stricter handling requirements.
Basic or Specified
CUI Basic follows standard safeguarding rules. CUI Specified has additional requirements set by law or regulation, such as export control.
Listed in the CUI Registry
The National Archives maintains the official CUI category list. Use it to check whether your information qualifies.
Passed down the supply chain
If a prime contractor shares CUI with you, you are responsible for protecting it, regardless of company size.
CUI vs. FCI
| Comparison | FCI | CUI |
|---|---|---|
| What it is | Non-public information provided by or created for the government under a contract | Government information that law or policy requires to be safeguarded |
| Standard | FAR 52.204-21 (15 basic safeguarding requirements) | NIST SP 800-171 (110 requirements) |
| CMMC level | Level 1 (annual self-assessment) | Level 2 (self-assessment or C3PAO assessment, as required by the contract) |
| Typical examples | Contract terms, invoices, delivery schedules | Engineering drawings, specifications, test data, manuals |
CUI Identification Checklist
- Identify which files and engineering drawings contain CUI
- Apply standardized CUI banner and portion markings
- Determine who inside your team is authorized to handle them
- Isolate in-scope systems to minimize assessment scope
Know your CUI location. Control what you protect
1. Contract receipt
Check your contract for DFARS clauses (252.204-7012, 7020, 7021).
2. People
Identify the engineers, project leads and administrators who handle CUI.
3. Systems and networks
Define the boundary around workstations, file servers and cloud services that handle CUI.
4. Physical facilities
Control access through badges, visitor escorts and locked server rooms.
Long form Sections
Explanations of requirements, timelines, and assessor expectations.
1. Identify CUI Before it Enters your Systems
Start with your contract to identify CUI. Look for DFARS 252.204-7012, then check whether your work involves drawings, specifications, test data or other information the government creates or owns. Compare that information against the categories in the National Archives’ CUI Registry.
An absent marking does not mean information is not CUI. If you’re unsure, ask your prime contractor or contracting officer in writing. We also inspect your facility and with the people handling the information. CUI is often found in places where a questionnaire is not identified.
2. Apply and Retain the Right CUI Markings
CUI markings indications to handle a document that requires protection. The banner marking appears at the top of each page and reads “CUI.” For CUI Specified, the banner also identifies the category. The CUI Registry provides the required format.
The agency or organization designating the information applies to the initial markings. You must retain them on every copy, extract, or summary.
3. Know Which CUI Handling Rules Apply
CUI Basic follows standard federal safeguarding and sharing requirements. CUI Specified has additional handling requirements set by law, regulation or government-wide policy.
The CUI Registry identifies Specified categories and their additional requirements. Defense contractors may encounter Specified CUI when handling export-controlled technical data. Identify which category you hold before deciding how to store, share, and mark it.
4. Control How CUI is Accessed, Shared and Stored
CUI handling requires clear controls. Share it only with people authorized to access it for a lawful government purpose. Keep it within your defined system boundary. Never move it to personal email or unapproved applications.
Mark printed copies and secured them when not in use. Protect digital files both in transit and at rest. A CMMC Level 2 assessment checks how these controls work in your environment. Gaps often appear in day-to-day handling.
5. Meet Export Control Requirements Alongside CMMC
Some CUI is also subject to export control under the International Traffic in Arms Regulations (ITAR) or Export Administration Regulations (EAR). These are separate obligations. Meeting CMMC requirements does not satisfy export control requirements, or vice versa.
Access is a key concern. Sharing technical data with a foreign national or storing it in an unsuitable service can violate export rules. Check your contract and consult legal counsel when handling export controlled data.
6. Verify Your Cloud Provider's CUI Responsibilities
Cloud services can store or process CUI, but they must meet specific requirements. Under DFARS 252.204-7012, cloud providers handling CUI must meet the FedRAMP Moderate baseline or equivalent.
Ask your provider for its responsibility matrix. It identifies which controls the provider covers and which remain yours. Small contractors can also use a CMMC enclave to separate CUI into a dedicated environment and limit assessment scope.
7. Decontrol and Destroy CUI Through the Right Process
Only the agency that designated the information, or someone it authorizes, can decontrol CUI. This happens when information no longer requires protection. Do not remove markings yourself.
When CUI is no longer needed, destroy it. This is crucial to keep data safe. Shred paper records and securely wipe or destroy digital media using guidance such as NIST SP 800-88. Proper destruction prevents recovery and misuse.
8. Make CUI Handling Part of Everyday Work
Each person handling CUI must know how to identify it, apply markings, and determine who can access it. An annual course alone may not address the different ways engineers, administrators and managers handle CUI.
Train teams beyond their responsibilities. This helps them apply handling requirements in daily work and prepares your organization for assessment. CUI awareness is also part of the preparation we provide. To date, 100% of our prepared clients have passed their assessments.
CUI: Key Factors to Note
The numbers behind CUI data and the work we do to protect it.
The number of security requirements a contractor must meet to protect CUI and reach CMMC Level 2.
The specific checks in NIST SP 800-171A that an assessor uses to test each requirement.
Every client we have prepared for a CMMC assessment has passed to date.
We have helped more than 120 companies across the Defense Industrial Base, of every size and industry.
FAQs about CUI-The complete guide
Still have questions regarding your specific CMMC clauses or audit dates? Speak directly with our lead Registered Practitioner.
Not sure which information in your contracts qualifies as CUI?
Work with a Cyber AB Registered Provider Organization to identify your scope and requirements.