Executive white paper · CMMC 2.0 · November 2026

Right-Sizing Your CMMC 2.0 Boundary

How government contractors can modernize business operations while protecting Controlled Unclassified Information (CUI), through evidence-based scoping and a carefully governed separation of systems.

A practical framework for assessing asset categories, information flows, and the safeguards needed for a defensible CMMC boundary.

SSSI official logoxpdOffice official logo

Published by Scientific Systems & Software International, Corporation (SSSI), developer of xpdOffice™. No registration required.

A more precise way to approach CMMC scope

Not every system in a government contracting business necessarily belongs in the same CUI environment. But keeping CUI documents elsewhere does not, by itself, establish that a business platform is out of scope. Asset capabilities, security functions, connectivity, and actual information flows must be assessed.

Understand Level 2 asset categories

Distinguish CUI Assets, Security Protection Assets, Contractor Risk Managed Assets, Specialized Assets, and Out-of-Scope Assets under 32 CFR § 170.19.

Examine real information flows

Review records, attachments, integrations, endpoints, identity systems, exports, logs, and the possibility of CUI entering routine workflows.

Evaluate a reference-only pattern

Consider whether neutral links can direct authorized users to customer-controlled CUI repositories without the business platform retrieving or processing protected content.

Ask better due-diligence questions

Identify the safeguards and evidence needed to support a defensible scoping decision, including AI ingestion, indexing, previews, and spillage handling.

Illustrative design pattern

CUI-decoupled reference architecture

A non-CUI business platform, a managed user endpoint, and a separately secured CUI repository can be considered as distinct logical zones. Any claimed separation must be demonstrated through technical controls and a customer-specific assessment.

Three-zone CUI-decoupled reference architecture showing a non-CUI business platform, a managed endpoint, and a separately secured customer CUI environment, with a proposed barrier against direct backend CUI transit.

Figure 1. CUI-decoupled reference architecture (illustrative only; not a validated deployment or CMMC scoping determination).

Boundary clarification: “CUI stays in designated zone” means CUI remains within the assessed customer boundary, including authorized endpoints as applicable; no CUI enters the business platform. “No … logs” means no CUI content in business-platform logs; required security logging is retained.

View full-size architecture diagram

Architecture explained

  1. Zone 1: Non-CUI business platform: operational transactions and screened neutral references only; no CUI uploads, previews, retrieval or AI ingestion.
  2. Zone 2: Customer-managed endpoint: authorized user follows a reference and authenticates to the protected repository; assess browser, endpoint, session and identity scope.
  3. Zone 3: Customer CUI enclave: controlled documents, access management and required security logging remain in the assessed customer environment.

Proposed barrier: no backend API synchronization, file proxying or direct CUI transit into the business platform. Verify with negative tests and documented data flows.

Five questions for GovCon leaders

  1. Which specific data, documents, and system-generated records are designated CUI?
  2. Which systems can store, process, or transmit CUI, or provide security protection to CUI systems?
  3. Can business workflows operate using non-CUI metadata and neutral references, without CUI transfer?
  4. Have integrations, browser behavior, AI features, indexing, logs, and accidental uploads been tested?
  5. What asset inventories, system diagrams, responsibility assignments, and assessment evidence support the proposed boundary?
Important distinction: This white paper is educational and presents a reference architecture for evaluation. It is not a representation that xpdOffice is CMMC certified, FedRAMP authorized, or automatically outside a contractor's CMMC assessment scope. Each contractor must determine its obligations and system scope based on actual deployment and applicable requirements.

Explore the full white paper

Read the asset-category discussion, architectural safeguards, and buyer due-diligence checklist.

Download the white paper (PDF)