CUI · 2026-10-26

Do We Actually Have CUI? How a Small Shop Tells FCI from CUI

How a small defense supplier tells FCI from CUI: the legal definitions, distribution statements, what primes send, and what each answer requires.

Nicolas Cano · Founder, Valontirsecurity researcher with a background in vulnerability analysis2026-10-26

If your shop machines, assembles, coats, or tests parts from drawings and specifications that came down a defense supply chain, the question "do we have CUI?" usually has a knowable answer, and it is written in two places: your contract's clauses and the markings on the data you were sent. Controlled Unclassified Information (CUI) is information the government creates or possesses, or that a company creates or possesses for the government, that a law, regulation, or government-wide policy requires to be safeguarded. Federal Contract Information (FCI) is the broader, lower tier: any non-public information provided by or generated for the government under a contract. Nearly every defense supplier has FCI. The ones who also have CUI, most often in the form of controlled technical data like drawings with distribution statements, carry a much heavier set of obligations. This article walks through how to tell which one you are.

The definitions, exactly

Four terms do all the work, and each has a precise legal definition.

Federal Contract Information (FCI), from FAR 52.204-21: information, not intended for public release, that is provided by or generated for the government under a contract to develop or deliver a product or service. It excludes information the government has released publicly and simple transactional data such as what's needed to process a payment. The purchase order itself, the delivery schedule, pricing, performance reports: if it came from or goes to a government contract and isn't public, it's FCI. If you hold a federal contract or a subcontract under one, you have FCI almost by definition.

Controlled Unclassified Information (CUI), from 32 CFR 2002.4: information the government creates or possesses, or that an entity creates or possesses for or on behalf of the government, that a law, regulation, or government-wide policy requires or permits an agency to handle using safeguarding or dissemination controls. The key phrase is law, regulation, or government-wide policy: something on the books has to require the protection. The authorized categories live in the CUI Registry maintained by the National Archives. Information doesn't become CUI because it feels sensitive; it becomes CUI because it falls in a Registry category backed by an authority.

Controlled Technical Information (CTI) is the Registry category that matters most to a manufacturer, defined in DFARS 252.204-7012: technical information with military or space application that is subject to controls on its access, use, reproduction, modification, performance, display, release, disclosure, or dissemination. The clause gives the test: CTI is technical information that would meet the criteria for distribution statements B through F under DoD Instruction 5230.24 if it were disseminated, and it excludes information that is lawfully publicly available without restrictions. "Technical information" means technical data or computer software as DFARS 252.227-7013 defines them, which is recorded information of a scientific or technical nature. Engineering drawings, specifications, process sheets and technical reports are the textbook examples, and they are the things on your shop floor.

Covered Defense Information (CDI) is the term your DoD contract actually uses, defined in the same clause: unclassified CTI or other CUI-Registry information requiring safeguarding that is either (1) marked or otherwise identified in the contract, task order, or delivery order and provided to you by or on behalf of DoD, or (2) collected, developed, received, transmitted, used, or stored by you in support of performing the contract. Read prong (2) again. The data doesn't have to be handed to you to be covered. What you generate while performing, if it carries the controlled technical content, is covered too.

In practice, for a defense supplier, "do we have CUI?" almost always means "do we have CTI?", and that almost always means "do we receive or produce defense technical data?"

Why the answer decides everything downstream

The FCI/CUI line is the fork in the regulatory road, and the two paths are not close in size.

FCI only: FAR 52.204-21 applies, requiring 15 basic safeguarding controls on any system that processes, stores, or transmits FCI (access control, authentication, media sanitization, malware protection, and so on). Under the CMMC program, this is Level 1: an annual self-assessment against those 15 requirements, entered in SPRS, with an affirmation.

CUI: DFARS 252.204-7012 applies, and with it the full stack this blog exists to explain: the security requirements of NIST SP 800-171 (all 110 of them) on the systems that handle covered information, a System Security Plan, 72-hour cyber incident reporting to DoD, flow-down to your own subcontractors, and, through DFARS 252.204-7019 and 7020, a current self-assessment score posted in SPRS computed from the official weights. Under CMMC it maps to Level 2, and a senior official affirms continuing compliance annually.

Getting the answer wrong is expensive in both directions. A shop that has CUI and builds a 15-control program has unimplemented contractual obligations and an indefensible posture. A shop that has only FCI and buys a 110-requirement program has spent a year of effort on obligations it doesn't carry. Scoping is the first compliance decision, and everything else inherits it.

Start with the contract, not the file server

The fastest reliable evidence is in your contracts and purchase orders, because the clauses are the government's own statement of what it thinks you handle.

  1. Look for DFARS 252.204-7012 in your prime contracts and in the terms your primes flow down on purchase orders. Primes are required to include it in subcontracts whose performance will involve covered defense information. If 7012 is in your PO terms, your customer has concluded that the work involves CDI. That is not always right (primes flow clauses down broadly to be safe), but it is where the conversation starts, and it is a contractual obligation either way until resolved.
  2. Look for 252.204-7019 and 7020. Their presence means the SPRS assessment machinery applies to you if you're implementing 800-171, and their arrival in your POs is usually accompanied by the questionnaire asking for your score.
  3. Look for FAR 52.204-21 alone. A contract carrying only the FAR clause, with no 7012, is the signature of FCI-only work.
  4. Read the statement of work and the technical exhibits. CDI prong (1) says covered information is "marked or otherwise identified in the contract." Contracts that involve CUI are supposed to say so, in the SOW, a CUI attachment, or the marked deliverables list.

Then ask the operational question: what did they actually send you, and what do you make from it?

Then read the data itself: markings and distribution statements

Defense technical data announces itself, when it's marked correctly.

Distribution statements. DoD technical documents carry a distribution statement under DoDI 5230.24. Statement A means approved for public release: not CTI. Statements B through F restrict distribution (to U.S. government agencies, to DoD and contractors, by direction of the controlling office, and so on). A drawing bearing Distribution Statement B, C, D, E, or F meets the CTI test by the clause's own definition. For a machine shop, this is the single highest-value thing to check: pull a sample of the drawings you build from and read the title block and margins.

CUI banner markings. Documents marked under the current program carry "CUI" in a banner, often with a category marking such as CTI and a dissemination control. Under the DoD's CUI program (DoDI 5200.48), the designator who creates the document is responsible for marking it.

Legacy markings. Older documents in circulation carry "FOUO" (For Official Use Only), "Distribution D," export-control warnings, or ITAR notices. FOUO is a legacy marking the CUI program replaced; a document marked FOUO wasn't decontrolled by the rebranding, and its content should be evaluated under the current definitions. Export-controlled technical data (ITAR/EAR) is its own legal regime and also a CUI Registry category; a defense drawing is frequently both export-controlled and CTI at once.

What you generate. This is the part shops miss. Your CAM program written from the controlled drawing, the first-article inspection report recording the controlled dimensions, the job traveler carrying the geometry, the photos of the part on the CMM: material you create in performance that embodies the controlled technical content falls under CDI prong (2). The boundary of "where CUI lives" in your shop is drawn by where that content flows, not by where the customer's original PDF sits.

The unmarked-drawing problem

The messiest real-world case: your contract carries 7012, the work is plainly a defense part, and the drawing arrives with no distribution statement and no CUI banner. Three things are true at once.

First, marking is the government's and the designator's job, not yours; you are not expected to run a declassification office. Second, the clause itself covers this case. Prong (1) of the CDI definition depends on marking or identification, but prong (2) covers controlled technical information "received" or "used" by you in support of performing the contract, with no marking condition. If the drawing meets the CTI definition, an upstream marking failure does not convert it into public data. Treating "it wasn't marked" as "it isn't controlled" is a bet your shop is making on someone else's paperwork. Third, you are allowed to ask, and should: put the question to your prime's buyer or the contracting officer in writing ("the drawings under PO 4512 carry no distribution statement or CUI marking; please confirm whether this technical data is controlled and provide marked versions if so") and keep the answer. A written determination from the customer is scoping evidence an assessor and your own affirmation can stand on.

The inverse discipline also matters: do not self-designate everything in the building as CUI out of caution. Over-marking expands your assessment boundary, your cost, and your obligations without any requirement behind it. The definition is the test; the Registry category and the authority behind it are what make something CUI.

Common cases for a machine shop

  • Build-to-print drawing of a defense part, Distribution Statement B/C/D on the title block: CTI, therefore CUI, therefore CDI under your contract. The core case.
  • The purchase order, pricing, and delivery schedule for that job: FCI. Not CUI by itself.
  • A commercial catalog part sold to a prime with no technical data exchanged: likely FCI only, and if it's a pure COTS sale, possibly outside these clauses entirely.
  • An RFQ package with a controlled drawing attached, no award yet: the drawing is still controlled technical data, and often export-controlled, so handle it that way now. The 7012 safeguarding obligations attach through the contract once you are performing, but export-control rules apply the moment you hold the data.
  • Your CAM files, travelers, and inspection reports derived from a controlled drawing: covered under CDI prong (2); they carry the controlled content.
  • Your payroll, HR records, and internal financials: not CUI and not FCI. They're your information, not the government's.
  • A part you designed yourself and sell commercially, also bought by DoD: your own proprietary data isn't CUI; the government contract wrapper around the sale still produces FCI.

What to do with each answer

If you conclude FCI only: implement and document the 15 FAR 52.204-21 safeguards, complete the Level 1 self-assessment and affirmation where your contracts require it, and revisit the question whenever new work arrives, because one PO with controlled drawings changes the answer. Be honest about the conclusion: writing "we have no CUI" down, with the reasoning, is itself the scoping record that protects you later.

If you conclude CUI: the 800-171 program applies, and the sequence is scoping first. Map where the controlled technical data enters, which systems and people touch it, and where it leaves; shrink that boundary deliberately (a defined set of workstations and storage rather than the whole building); then build the SSP, the POA&M, and the score from honest statuses. The technical fixes along the way are your IT provider's or consultant's work; the scoping determination, the record of it, and the score your company posts are yours.

That record-keeping is the job Valontir was built for: the scoping questions are the first thing its onboarding asks, and from there it tracks every 800-171 requirement against its assessment objectives, keeps the evidence behind each one current, and computes your SPRS score from the official weights as statuses change, working alongside whoever does your IT. Whether your answer today is "FCI only" or "we have CUI," the defensible version of that answer is a written one.

FAQ

Is FOUO the same as CUI? FOUO is a legacy marking that the CUI program replaced. Content marked FOUO was not decontrolled by the change; evaluate it under the current CUI definitions, and expect current documents to carry CUI markings instead.

Are drawings we create ourselves CUI? Your own independently developed, proprietary designs are not CUI. Documents you create that carry controlled technical content from a defense contract (CAM programs, inspection reports, derived drawings) fall under covered defense information through the "collected, developed... in support of performance" prong of DFARS 252.204-7012.

Is ITAR data the same as CUI? They are separate legal regimes that overlap heavily. Export-controlled technical data is its own compliance obligation under ITAR/EAR and is also a CUI Registry category, so a defense drawing is often both at once.

Who is responsible for marking CUI? The designating agency or document creator, under 32 CFR 2002 and, within DoD, DoDI 5200.48. When data arrives unmarked but appears controlled, ask the prime or contracting officer for a written determination rather than guessing in either direction.

Does unmarked data count as CUI? If the information meets the definition, a missing marking doesn't remove the safeguarding obligation; it signals an upstream marking failure. Get the determination in writing and keep it with your scoping records.

If we only have FCI, do we still have to do anything? Yes: FAR 52.204-21's 15 basic safeguarding requirements apply to any system handling FCI, and contracts under the CMMC program's current phase can require an annual Level 1 self-assessment and affirmation in SPRS.


Valontir is a compliance workspace for small defense contractors: every 800-171 requirement, every piece of evidence, and your live SPRS score in one place, so your annual affirmation has evidence behind it. Book a demo or request access.

Sources: 32 CFR Part 2002 (CUI rule, definitions at § 2002.4) · FAR 52.204-21, Basic Safeguarding of Covered Contractor Information Systems · DFARS 252.204-7012 (definitions of controlled technical information and covered defense information) · CUI Registry (National Archives) · 32 CFR Part 170 (CMMC program) · NIST SP 800-171 Rev. 2

Put evidence behind your signature.

Valontir keeps your requirements, evidence, and score in one place, ready whenever a prime asks. We’re onboarding early customers deliberately.