The Defense Compliance ReportCMMC 2.0 & the Defense Industrial Base
Trust guide

FCI vs CUI explained for small DoD contractors

Two government data labels that look similar and trigger very different obligations. Misclassifying them is the most common source of CMMC overspend.

The Defense Compliance Report Editorial TeamIndependent CMMC and DIB compliance research
Published: Last reviewed:
Editorial research — not formally reviewed by a CMMC Subject Matter Advisor. Verify scope and applicability with a Registered Practitioner before acting.

Federal Contract Information (FCI) and Controlled Unclassified Information (CUI) are both protected categories of unclassified government data, but the obligations they trigger are different in kind, not just in degree. The distinction is the single most important early decision a contractor makes about CMMC scope.

Federal Contract Information (FCI)

FCI is information "not intended for public release" that is provided by or generated for the government under a contract to deliver a product or service. It is broad and mundane: most contract performance data that is not already public qualifies. Protecting FCI requires the 15 basic safeguarding requirements at FAR 52.204-21 and, under CMMC, status at Level 1.

FAR 52.204-21 — Basic Safeguarding of Covered Contractor Information Systems

The 15 basic safeguarding requirements every federal contractor that processes FCI must implement. CMMC Level 1 maps to this clause.

View at acquisition.gov

Controlled Unclassified Information (CUI)

CUI is information the government requires safeguarding or dissemination controls for, consistent with applicable laws, regulations, and government-wide policies, but that is not classified. The National Archives maintains the authoritative CUI Registry, which catalogs CUI categories (e.g. Controlled Technical Information, Export Control, Privacy, Defense). In a defense context, CUI most commonly appears as engineering data, technical drawings, specifications, source selection information, and proposal materials.

Protecting CUI on non-federal systems requires the 110 NIST SP 800-171 Revision 2 security requirements and, under CMMC, status at Level 2 (or Level 3 for designated high-priority programs).

32 CFR Part 2002 — Controlled Unclassified Information

The CUI program rule. Establishes the CUI Registry, lawful safeguarding requirements, and the basis for NIST SP 800-171's application to non-federal systems.

View at ecfr.gov

How the distinction shows up in real contracts

Why misclassifying costs money

Two failure modes drive the overspend. The first is treating FCI as CUI — paying for an enclave, GCC High licensing, and a Level 2 C3PAO assessment for contracts that only required Level 1. The second is treating CUI as FCI — failing to implement 800-171, posting a low SPRS score, and becoming ineligible for the contracts that pay for the program. Both are recoverable; both are expensive.

Once you know whether your contracts touch CUI, the level decision and the partner-routing decision follow.