DefenseEye.ai

CMMC Compliance

What Counts as CUI? A Plain-English Guide for Defense Contractors

Controlled Unclassified Information (CUI) is the trigger for CMMC Level 2 requirements — but the definition is notoriously hard to apply in practice. This guide explains what CUI is under 32 CFR Part 2002 and the NARA CUI Registry, what common categories defense contractors handle, what is not CUI, and how to identify CUI boundaries in your own environment.

Controlled Unclassified Information (CUI) is the single most important classification for defense contractors trying to understand their CMMC obligations. The legal framework comes from Executive Order 13556 (2010) and its implementing regulation, 32 CFR Part 2002, administered by the National Archives and Records Administration (NARA). In simple terms: CUI is government information that is sensitive enough to require safeguarding under law, regulation, or government-wide policy — but not sensitive enough to be classified as Confidential, Secret, or Top Secret. If your organization processes, stores, or transmits CUI, DFARS 252.204-7012 applies, and CMMC Level 2 certification is likely required on any affected contract.

The practical challenge is that the government's CUI definition spans over 100 registry categories, and contractors routinely make two costly mistakes: over-scoping (treating ordinary business information as CUI, which inflates CMMC assessment scope and cost) or under-scoping (failing to identify real CUI, which leaves the organization non-compliant and exposed to contract loss or False Claims Act liability). The NARA CUI Registry at archives.gov/cui is the authoritative source — consult it, and when uncertain, ask your Contracting Officer in writing.

What Is CUI? The Short Version

CUI is government-originated or government-related information that isn't classified — meaning it's not Secret or Top Secret — but still requires safeguarding because of laws, regulations, or government policies. Think of it as the large middle category between publicly available government information and classified intelligence: sensitive enough to protect, not secret enough to classify.

The National Archives maintains the official CUI Registry at archives.gov/cui, which lists every authorized category of CUI with its source law or regulation. The registry has over 100 categories. For defense contractors, the categories that come up most often are listed below.

The CUI Categories Defense Contractors Most Often Handle

  • Controlled Technical Information (CTI) — Technical data with military or space application, including specifications, engineering drawings, and software related to military systems. Subject to ITAR or EAR export controls.
  • Export Controlled — Information regulated under the International Traffic in Arms Regulations (ITAR) or Export Administration Regulations (EAR). Includes defense articles, services, and related technology.
  • Procurement & Acquisition — Contract proposals, source selection information, cost or pricing data, and contractor bid information. Very common in the prime/sub supply chain.
  • Privacy — Personally Identifiable Information (PII) related to DoD personnel, contractor employees with system access, or other individuals in government systems. Includes names combined with sensitive identifiers.
  • Operations Security (OPSEC) — Information about military operations, capabilities, or vulnerabilities that could provide adversaries with an advantage if disclosed.
  • Critical Infrastructure — Information about the location, configuration, or vulnerabilities of critical infrastructure systems supporting DoD missions.
  • Law Enforcement — Information related to investigations, intelligence sources, or methods. Less common for typical contractors but present in some programs.

What Is NOT CUI

This is where many contractors go wrong in the other direction — treating ordinary business information as CUI and over-scoping their CMMC environment, which dramatically increases cost and complexity.

  • General business information — Your pricing for commercial products, standard HR documents, internal meeting notes, expense reports
  • Publicly available information — Anything your government customer has publicly released, information from government websites, published DoD announcements
  • Unrelated contract data — Work performed for commercial clients has nothing to do with CUI, even if the same company also has DoD work
  • Federal Contract Information (FCI) alone — FCI (non-public information provided by the government under contract) is not automatically CUI. FCI triggers CMMC Level 1; CUI triggers Level 2.
  • Commercial off-the-shelf (COTS) product documentation — Standard user manuals, commercial licensing agreements, vendor product specifications
  • Aggregated open-source data — Combining publicly available information doesn't automatically create CUI unless the combination reveals something sensitive

How CUI Gets Into Your Environment

Understanding how CUI flows into your organization is critical to defining your CMMC assessment boundary. The most common entry points are:

  • Contract Deliverables and Data Items: Your contract's Contract Data Requirements List (CDRL) or Statement of Work (SOW) specifies what technical data you must produce or handle. Technical specifications, design drawings, and test reports related to defense systems are almost always CUI.
  • Government-Furnished Information (GFI): Technical data, specifications, or reference materials the government provides to support your work. If the government hands it to you for contract performance, treat it as CUI unless told otherwise.
  • DoD System Access: If you have accounts in DoD systems — email, portals, collaboration platforms — messages and files in those systems may contain CUI.
  • Subcontractor Flow-Down: If you're a prime, CUI flows to your subs when they need it to perform their portion of the work. If you're a sub, CUI may come from the prime.
  • Export-Controlled Technical Data: Some technical data is controlled under ITAR or EAR before it even reaches a government contract. If you work with defense-related hardware or software, this is likely in scope.

How to Identify CUI in Your Environment: A Practical Approach

  • Read your contracts: The surest indicator is your contract language. Look for clauses referencing DFARS 252.204-7012 (CUI requirements) or DFARS 252.204-7021 (CMMC).
  • Look for CUI markings: Properly handled CUI should be marked. Government documents are marked 'CUI' with the relevant category (e.g., 'CUI // CTI'). If you receive marked documents, that's CUI.
  • Ask your Contracting Officer (CO): If you're unsure whether specific data is CUI, the government CO is the right person to ask. Get the answer in writing.
  • Map data flows: Trace where data enters your organization, how it's processed, stored, and transmitted. Apply the CUI category definitions to data at each touchpoint.
  • Review shared drives and email: CUI often lives in SharePoint folders, network shares, and email inboxes labeled only by project name. Search for common CUI keywords: classification markings, ITAR language, technical data designations.
  • Engage your prime contractor: If you're a sub, your prime knows what CUI they're passing to you. Ask them to formally identify CUI in your Statement of Work.

Once You Identify CUI: What the Rules Require

Once you've confirmed your organization handles CUI, two frameworks apply simultaneously: the CUI Federal Rule (which governs how the government itself handles CUI) and DFARS 252.204-7012 / CMMC (which governs how contractors protect it). For contractors, the key requirements are:

  • Implement all 110 NIST SP 800-171 controls (CMMC Level 2 requirement)
  • Pass a Certified Third-Party Assessment Organization (C3PAO) assessment for most CUI contracts
  • Report cyber incidents involving CUI to DoD within 72 hours
  • Submit and maintain a current SPRS score in the PIEE portal
  • Maintain a System Security Plan (SSP) describing how each control is implemented
  • Flow down CUI protection requirements to subcontractors who access your CUI
  • Store CUI in FedRAMP Moderate or equivalent cloud environments (for cloud storage)

Practical First Step: Define Your CUI Boundary

The most valuable step before investing in CMMC compliance technology or consulting is formally defining your CUI boundary — the specific systems, people, and processes that touch CUI. A narrow, well-defended boundary keeps assessment scope manageable and cost proportionate. Every system inside the boundary must meet all 110 NIST 800-171 controls; every system outside it does not. Document your CUI data flows in your System Security Plan and have your Contracting Officer confirm the CUI categories in scope.

Authoritative Sources

  • NARA CUI Registry — archives.gov/cui: the official, complete list of all authorized CUI categories, subcategories, and the laws/regulations that authorize them
  • Executive Order 13556 — federalregister.gov: 'Controlled Unclassified Information' — the executive order establishing the CUI program
  • 32 CFR Part 2002 — ecfr.gov: the implementing regulation for the CUI program, defining what CUI is and how agencies must handle it
  • DFARS 252.204-7012 — acquisition.gov: 'Safeguarding Covered Defense Information and Cyber Incident Reporting' — the contract clause that makes NIST 800-171 compliance mandatory for CUI
  • DoD CUI Program — dcsa.mil: the Defense Counterintelligence and Security Agency's resources on CUI identification and handling for contractors
  • NIST SP 800-171 Rev. 2 — csrc.nist.gov: the 110-control framework contractors must implement to protect CUI under CMMC Level 2