Insights

FCI or CUI? How to Scope Your CMMC Assessment Before You Start Fixing Gaps

November 20, 2026

Before you fix security gaps, you need to know which information you hold and which systems touch it. This guide explains the difference between Federal Contract Information and Controlled Unclassified Information, how 32 CFR 170.19 defines CMMC assessment scope, and practical scoping steps for Inland Empire defense suppliers, based on official regulation text and DoD guidance.

Scope first, then fix

Most CMMC readiness projects start with a list of security gaps. The better starting point is a smaller question: which information do you actually hold, and which systems, people, and places touch it? Under 32 CFR 170.19, the CMMC Assessment Scope must be specified before an assessment, and it is defined as the set of all assets in your environment that will be assessed against CMMC security requirements.

Get the scope wrong and you either spend money hardening systems that never needed it, or you leave a laptop, file share, or cloud service exposed that an assessment will treat as in scope anyway. This guide walks Inland Empire aerospace and defense suppliers through the two kinds of information that drive CMMC, Federal Contract Information (FCI) and Controlled Unclassified Information (CUI), and how the official scoping rules sort your assets. With Phase I self-assessment requirements still in place during the Phase II pause, this is work you can do now.

What counts as Federal Contract Information (FCI)

FAR 4.1901 defines FCI as 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. It does not include information the Government provides to the public, such as content on public websites, or simple transactional information, such as what is needed to process payments.

In practice, FCI is the everyday non-public contract material many small suppliers handle: statements of work, delivery schedules, contract correspondence, and similar records. If your contracts include FAR 52.204-21, the systems holding that information are what CMMC Level 1 covers. Our earlier post on the 15 FAR safeguards behind a Level 1 self-assessment explains those requirements.

What counts as Controlled Unclassified Information (CUI)

32 CFR 2002.4(h) defines CUI as 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. CUI does not include classified information. The DoD CUI Program puts it simply: CUI is a control marking, not a classification marking, and it replaces older agency-specific labels such as FOUO.

Controlled Technical Information is the category most machine shops meet

For aerospace and defense manufacturers, the CUI you are most likely to hold is Controlled Technical Information (CTI). DFARS 252.204-7012 defines CTI as technical information with military or space application that is subject to controls on its access, use, reproduction, release, or dissemination, and notes that it would meet the criteria for distribution statements B through F under DoD Instruction 5230.24. The CUI Registry entry for CTI lists examples such as engineering drawings, specifications, standards, process sheets, manuals, technical reports, data sets, and software source and executable code. Information that is lawfully publicly available without restrictions is not CTI.

CUI you create counts too

DFARS 252.204-7012 calls the information it protects covered defense information. That includes CUI that is marked or otherwise identified in the contract and provided to you by or on behalf of DoD, and also CUI that is collected, developed, received, transmitted, used, or stored by you or on your behalf in support of performing the contract. A CNC program or inspection report you build from a controlled drawing deserves the same scrutiny as the drawing itself. If you cannot tell whether something is CUI, the DoD CUI Program directs contracting companies to their Government contracting office representative.

How Level 1 scoping works

For a Level 1 self-assessment, 32 CFR 170.19(b) puts in scope the information systems that process, store, or transmit FCI. Systems that do not are out of scope, with no documentation required. Specialized Assets, a defined list that includes IoT and industrial IoT devices, operational technology, Government Furnished Equipment, restricted information systems, and test equipment, are not part of the Level 1 assessment scope. The rule asks you to consider the people, technology, facilities, and external service providers that handle FCI. DoD's CMMC Level 1 Scoping Guide gives more detail.

How Level 2 scoping works: five asset categories

Level 2 applies where CUI is involved, and 32 CFR 170.19(c) sorts every asset into one of five categories. The CMMC Level 2 Scoping Guide adds that an asset processes CUI when CUI is used on it (accessed, entered, edited, generated, manipulated, or printed), stores CUI when CUI is at rest on it, including on paper, and transmits CUI when it moves CUI from one place to another.

CUI Assets process, store, or transmit CUI. They go in your asset inventory, System Security Plan (SSP), and network diagram, and are assessed against all Level 2 requirements.

Security Protection Assets provide security functions for the assessment scope, such as the tools that manage identities, logs, or endpoint protection. They are documented the same way and assessed against the Level 2 requirements relevant to the capabilities they provide.

Contractor Risk Managed Assets can, but are not intended to, handle CUI because of your security policies, procedures, and practices. They do not have to be separated from CUI assets. They are documented in the inventory, SSP, and diagram; if the SSP documentation is sufficient they are not assessed against other requirements, but an assessor can run a limited check if your documentation raises questions.

Specialized Assets can handle CUI but cannot be fully secured, such as OT, IoT, test equipment, and Government Furnished Equipment. For a shop floor, that can include networked machine tools and inspection equipment. They are documented in the inventory, SSP, and diagram and must be shown to be managed under your risk-based policies; they are not assessed against other CMMC requirements.

Out-of-Scope Assets cannot process, store, or transmit CUI and do not provide security protections for CUI Assets. They are physically or logically separated from CUI assets, and you should be prepared to justify why they cannot handle CUI. An asset that fits any in-scope category cannot be called out of scope.

Separation and enclaves

Scope can be limited by separating the assets that handle CUI from those that do not. The Level 2 Scoping Guide describes logical separation as preventing data transfer between connected assets with software or network controls such as firewalls, VPNs, and VLANs, and physical separation as assets with no wired or wireless connection at all. It follows NIST SP 800-171 Rev. 2, which allows organizations to limit the scope of the security requirements by isolating designated system components in a separate CUI security domain.

Many small suppliers choose a CUI enclave: a defined set of users, devices, and services where controlled work happens, while general office systems stay outside it. 32 CFR 170.19 also states that an endpoint running a VDI client configured to allow nothing beyond keyboard, video, and mouse traffic to the virtual desktop is out of scope. The guide cautions that a new assessment is required after significant architectural or boundary changes, such as network expansions or mergers, so plan the boundary with growth in mind.

Cloud services and IT providers are part of the picture

32 CFR 170.19(c)(2) addresses External Service Providers (ESPs). Under 32 CFR 170.4, a provider counts as an ESP for CMMC only if CUI or Security Protection Data, such as log files, configuration data, vulnerability information, and passwords for the in-scope environment, is processed, stored, or transmitted on its assets.

If a cloud service provider handles your CUI, it must meet the FedRAMP requirements in DFARS 252.204-7012, which call for security equivalent to the FedRAMP Moderate baseline. If a provider that is not a cloud provider handles your CUI, its services are assessed as part of your assessment. A provider handling only Security Protection Data, which often describes a managed IT or security provider, has its services assessed as Security Protection Assets. Either way, the relationship belongs in your SSP and in the provider's customer responsibility matrix, which spells out who does what.

A practical scoping checklist

1. Read your contracts. Note which ones include FAR 52.204-21 and which include DFARS 252.204-7012, and what information each one actually provides or requires you to produce.

2. Follow the data. Trace where drawings, specifications, and contract files arrive (email, customer portals, removable media, paper), where they are stored, who opens them, and where they go next, including CAM workstations, machine controllers, printers, and backups.

3. Build the asset inventory and network diagram. Put every in-scope asset in one of the categories above, and write down why each out-of-scope system cannot handle CUI.

4. Decide on the boundary. Consider whether a smaller enclave would reduce cost and effort compared with bringing the whole company into scope.

5. Document providers. List every cloud service and IT or security provider that touches CUI or Security Protection Data, and get their responsibility matrix.

6. Record it in the SSP and revisit it. Update scope when you add systems, locations, providers, or contracts.

How Integrity Security Defense Corp can help

We help Inland Empire defense contractors map where FCI and CUI live, build asset inventories and network diagrams, and design practical enclaves through our CMMC compliance work, then operate and protect those environments with managed cybersecurity and managed IT. See the industries we serve. We are not a C3PAO, we are not an authorized CMMC assessor, and we do not certify companies. This article is general information, not legal advice; your contract and the current regulations control. To talk through your scope, contact us or call (909) 310-2022.

Official sources

Next step

Get a practical review of where you stand.

Integrity Security Defense Corp helps Inland Empire defense contractors with CMMC readiness and managed cybersecurity. We are not a C3PAO and do not perform official certification assessments.