FCI vs CUI: Which Do You Handle and Why It Matters

ISO Cloud Consulting editorial team
Illustration comparing a plain folder with one ring of protection and a technical drawing inside several rings

FCI is non-public information you receive or create under a government contract, and it needs CMMC Level 1: 15 basic safeguards. CUI is information the government requires to be protected under law, regulation or policy, such as controlled technical drawings, and it needs Level 2: all 110 NIST SP 800-171 requirements.

Key facts

  • FCI is defined in FAR 4.1901; CUI is defined in 32 CFR 2002.4.
  • FCI is protected by FAR 52.204-21 and CMMC Level 1: 15 requirements, no POA&M.
  • CUI is protected by DFARS 252.204-7012 and CMMC Level 2: 110 requirements and an SPRS score.
  • Almost every company that handles CUI also handles FCI.
  • The CMMC level is set by the most sensitive information you handle, within the scope you define.

What is Federal Contract Information (FCI)?

FCI is any non-public information provided by or generated for the government under a contract to deliver a product or service. Public information and simple payment details are excluded.

The FAR definition reads: "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 to the Government, but not including information provided by the Government to the public (such as that on public Web sites) or simple transactional information, such as that necessary to process payments."

For a small machine shop, FCI typically includes purchase orders and their line items, quantities, delivery schedules, non-public statements of work, and correspondence about the contract. Invoice and payment details on their own are usually the excluded transactional kind.

What is Controlled Unclassified Information (CUI)?

CUI is information the government creates or possesses, or that a contractor creates or possesses for the government, that a law, regulation or government-wide policy requires or permits to be safeguarded. It is unclassified, but its handling is controlled.

CUI comes in categories listed in the National Archives CUI Registry. For manufacturers and suppliers, the most common are:

  • Controlled technical information: drawings, specifications, models and process sheets with military or space application, usually marked with a distribution statement (B through F).
  • Export-controlled information: technical data controlled under export regulations.
  • Other contract-specific CUI: anything your contract or the documents themselves mark as CUI.

In DoD contracts, CUI in your systems is often called covered defense information, the term DFARS 252.204-7012 uses.

What is the difference between FCI and CUI?

The difference is sensitivity and the rules that follow from it. FCI needs basic hygiene; CUI needs a full security program with documentation, scoring and incident reporting.

FCI CUI
Definition FAR 4.1901 32 CFR 2002.4
Typical examples Purchase orders, quantities, delivery schedules Marked technical drawings, export-controlled data
How you recognize it Non-public contract information; usually unmarked Usually marked "CUI" or with a distribution statement
Contract clause FAR 52.204-21 DFARS 252.204-7012 (plus 7019 and 7020)
CMMC level Level 1 Level 2 (Level 3 for a small number of programs)
Requirements 15 110 (320 assessment objectives)
Scoring Met or not met SPRS score from 110 to −203
POA&M Not allowed Limited: score of 88 or more, eligible items, 180 days
System Security Plan Not required Required (3.12.4)
Incident reporting None under FAR 52.204-21 To DoD within 72 hours under 7012

Can you create CUI yourself?

Yes. CUI includes information a contractor creates for or on behalf of the government, not only what the government sends you. If you create it under a contract, and it falls in a CUI category, it is CUI.

For suppliers this usually happens with derivatives. A CNC program written from a controlled drawing, a process sheet that reproduces controlled dimensions, an inspection report containing the drawing's specifications, or a photo of a controlled part can all carry the same controlled technical information as the original. Treat derivatives the way you treat the source document: store them inside your CUI boundary, mark them as your contract requires, and include them in your data-flow map. If you are unsure whether a derivative is CUI, ask your customer, as you would for the original.

How do you tell which one you handle?

Check your contract clauses, check the markings on what you receive, and ask the customer in writing. Do not guess.

  1. Read the clauses. FAR 52.204-21 means FCI. DFARS 252.204-7012 means you may receive CUI. A stated CMMC level tells you what the customer expects.
  2. Check the markings. Look for "CUI" banners, distribution statements B through F on drawings, and export-control notices.
  3. Trace the flow. Follow a real order from receipt of the drawing to shipment. Note every inbox, share, workstation, machine and person it touches.
  4. Ask in writing. Send your prime or contracting officer a short list of the document types you receive and ask which are CUI. Keep the reply.
  5. Decide your scope. Record the answer in your SSP or scope statement, and decide where CUI will be allowed to live.

What if CUI arrives without a marking?

Ask. The government is responsible for identifying and marking CUI, but mistakes happen, and some documents arrive stripped of their markings after passing through several hands.

If a drawing looks like controlled technical information but carries no marking, treat it as CUI until your customer confirms otherwise in writing. Treating it as CUI costs a little effort. Treating real CUI as ordinary data can put you in breach of 7012 and make your affirmation inaccurate.

Why does the distinction matter so much?

Because it decides whether you owe 15 requirements or 110. That is the difference between a few days of cleanup and a months-long program.

It also works in both directions. Treating everything as CUI drags the whole company into Level 2 scope and multiplies cost. Treating nothing as CUI when you do receive it exposes you to contract and False Claims Act risk. The right answer is usually to confirm exactly what is CUI, then contain it in as small an environment as possible, often an enclave used only by the people who work on controlled parts.

Does handling CUI mean the whole company must meet Level 2?

No. Level 2 applies to the assets inside the assessment scope you define, not automatically to every computer you own. Keeping CUI in a small, well-defined environment is the most effective way to reduce cost.

A common approach is an enclave: a separate set of accounts, devices and storage used only for CUI work, often by a handful of engineers, programmers and quality staff. Everything outside it stays at Level 1, provided CUI genuinely cannot reach it. The CMMC rule lets you place assets that cannot handle CUI and do not protect CUI assets out of scope, but you must be ready to justify it. An enclave only works if people follow it, so pair it with clear rules: CUI arrives through one channel, is stored in one place and never goes into ordinary email.

Did the 2026 CMMC changes affect FCI or CUI?

No. The definitions of FCI and CUI, and the clauses that protect them, did not change. The July 2026 pause and the September class deviation affect who assesses Level 2, not what counts as CUI or what you must do to protect it.

If you handle CUI, DFARS 252.204-7012 still requires NIST SP 800-171, a current SPRS score and 72-hour incident reporting. If you handle only FCI, the Level 1 self-assessment and affirmation are due every year as before.

What mistakes do suppliers make with FCI and CUI?

  • Assuming "we just machine parts" means no CUI. The drawing is the CUI, not the part.
  • Letting CUI spread through email. One forwarded drawing puts every inbox it touches in scope.
  • Forgetting the shop floor. CNC machines and their controllers can hold CUI and must be documented.
  • Ignoring suppliers. If you send CUI to a plating shop or heat treater, the 7012 flowdown goes with it.

If you only handle FCI, our Level 1 self-assessment guide and the Free CMMC Level 1 Self-Assessment Checklist are the place to start. If you handle CUI, the CMMC Level 2 Starter Bundle ($175, was $207) gives you the scoring workbook, SSP and POA&M templates. The CMMC hub covers both levels and the 2026 changes. Templates help you prepare; only your customer can confirm what is CUI.

Last reviewed: 29 September 2026. CMMC rules are still moving. Check your contract, your prime's flowdown and the current rule before you rely on any date.

Back to blog

Frequently asked questions

Is a purchase order from the DoD FCI or CUI?

A non-public purchase order is usually FCI: it is information generated under a government contract and not meant for public release. It becomes CUI only if it contains or attaches controlled content, such as a technical drawing with a distribution statement or export-controlled data. Payment details on their own are typically excluded transactional information.

Can a company handle CUI without handling FCI?

In practice, almost never. If you receive CUI under a defense contract, you also receive ordinary contract information such as quantities and schedules, which is FCI. That is why CMMC treats Level 2 as covering Level 1: a Level 2 (Self) status satisfies the Level 1 requirement for the same assessment scope.

Who decides whether information is CUI?

The government, through the agency that creates or owns the information, following the CUI Registry and agency policy. Contractors must protect what they receive or create as CUI under their contract. When in doubt, ask your contracting officer or prime in writing and keep the answer with your scoping records.

Does CUI stored in the cloud change anything?

Yes. Under DFARS 252.204-7012, a cloud service that stores, processes or transmits CUI must meet security requirements equivalent to FedRAMP Moderate. Your own devices that connect to that cloud service remain in scope, and the provider's customer responsibility matrix must be reflected in your System Security Plan.

Templates that do this job

Editable Word and Excel files. Instant download. Licensed for one organization.