Cyberuptive

Does This Change Affect Your CMMC Boundary?

By Chuck Lerch, Founder and CEO, Cyberuptive ·

Treat each proposed system change as a boundary decision, not merely an IT ticket. Trace whether CUI or security protection data moves, identify assets and service dependencies, update scope records and evidence, then resolve uncertain classifications with the assessment owner before implementation or assessment.

CMMC means Cybersecurity Maturity Model Certification, and CUI means Controlled Unclassified Information, as defined in the DoD CMMC Scoping Guide, Level 2, version 2.13 (September 2024 guide). A new platform can affect an assessment boundary even when no user calls it a CUI system: it may handle CUI, hold security protection data, or provide a security function. Review the change before production.

What are the key takeaways?

  • Follow the data and security functions, not just the system name.
  • Check integrations and shared services as well as the new asset.
  • Update scope records and get uncertain classifications resolved before the assessment.

What changed in data movement?

Start with a concrete change description: what is being added or modified, who will use it, and what information it will receive, create, store, or send. Ask teams to trace CUI through normal use, support, backup, export, and failure-recovery paths. The DoD guide treats processing as using CUI, including accessing, editing, generating, or printing it; storage includes inactive data at rest, and transmission includes physical or digital transfer between assets (DoD Scoping Guide, v2.13). A product that is not intended for CUI may still receive it through a file share, pasted text, an API, or a support workflow, so check actual design and intended use rather than relying on a product label.

Draw the proposed flow from source to destination, including identity, administration, monitoring, and data-retention components. Mark where CUI appears, where security protection data is stored or processed, and which service can affect security for the assessed environment. The guide describes security protection data as security-relevant information used to protect the environment, with examples including security logs, configuration information, vulnerability status, and passwords for in-scope access (DoD Scoping Guide, v2.13). As a practical review step, confirm the flow with the system owner and the people who operate the integration; record unresolved assumptions rather than treating them as settled facts.

Which assets or services could the change touch?

Use the guide’s asset categories to frame the review, rather than trying to infer scope from a product name. The categories distinguish assets that handle CUI, provide security functions, can handle CUI but are not intended to, or have specialized constraints (DoD Scoping Guide, v2.13). The table below is a proposed review aid, not a government-prescribed change form.

Review possibilityChange-review questionPractical next step
CUI Asset: processes, stores, or transmits CUI (DoD guide)Could the system handle CUI in any normal workflow?Trace the data path and identify the affected asset and connections.
Security Protection Asset: provides a security function (DoD guide)Does it protect, monitor, or administer the assessed environment?Review the security capability and related data, even if it does not handle CUI.
Contractor Risk Managed Asset: capable of handling CUI, but not intended to (DoD guide)What policies and operating practices prevent CUI use?Check whether the intended restriction is practical and documented.
Specialized Asset: can handle CUI but cannot be fully secured (DoD guide)Does the change introduce equipment with specialized constraints?Account for how the organization manages it and describe its treatment.
Potentially out-of-scope asset: cannot handle CUI and provides no security protection (DoD guide)Can the team support both parts of that conclusion?Preserve the rationale and identify any connection that could change it.

An integration can change the answer for an existing asset, too. A new connector might make a previously separate application a route for CUI, or cause a service to provide a security function. Review the boundary impact of the whole connection, not only the new endpoint. When categorization is unclear, document the competing interpretations and ask the assessment owner to resolve them before the design becomes difficult to change.

What do shared services and providers contribute?

List services that support the changed system, including identity, cloud hosting, help desk, endpoint management, logging, backup, and a centralized security operations function. Ask what each service can access, what data it holds, and whether it provides a security capability. The guide says security protection assets can be logically separate from CUI assets and still be in scope when they contribute security functions; it also describes security protection data handled by those assets (DoD Scoping Guide, v2.13).

For a provider, distinguish the service’s role from the provider’s name. The guide states that an external service provider may be within the organization’s CMMC requirements when it meets CUI asset or security protection asset criteria, and that not every service provider is an external service provider (DoD Scoping Guide, v2.13). It also distinguishes providers that store, process, or transmit CUI from those that do not; the services used to meet the organization’s requirements can still be within its assessment scope (DoD Scoping Guide, v2.13).

As a proposed check, obtain the service description and identify the customer-provider split for the specific service being changed. Compare that with the actual data flow, contract language, and operational configuration. Where a centralized service supports several business units, confirm which instance, people, and data paths support the environment under review. For related role-allocation considerations, see the CMMC responsibility matrix.

What records and evidence need revision?

After the technical review, identify the records that would become misleading if left unchanged. The DoD guide says CUI assets, security protection assets, contractor risk managed assets, and specialized assets should be documented in the asset inventory and system security plan, with the in-scope assets shown on the network diagram (DoD Scoping Guide, v2.13). It also says the system security plan should describe how specialized assets are managed and document an external service provider’s use, relationship, and services (DoD Scoping Guide, v2.13).

A practical update set may include the inventory entry, diagram, system security plan description, data-flow records, access configuration, relevant procedures, and provider documentation. Decide which existing evidence the change invalidates and what new evidence would demonstrate that the intended controls operate. For example, a revised integration may warrant a current configuration view or an access test, while a changed data route may warrant a revised flow diagram. These are proposed evidence choices based on the change, not a universal required package.

Keep the review tied to the change: note the prior state, the proposed state, affected assets and services, the decision rationale, evidence owners, and any open issue. Use the CMMC readiness checklist to cross-check whether the change affects an existing readiness activity, without treating a checklist as a substitute for system-specific analysis. If the change also affects delivery of CMMC-related support, the CMMC compliance service overview can provide context about that service.

When should you ask the assessment owner or assessor?

Escalate when the team cannot establish whether CUI or security protection data resides on a service, when a provider’s role is uncertain, or when the proposed architecture conflicts with the documented boundary. The guide assigns the organization responsibility for determining whether a provider should be treated as an external service provider based on its services and whether CUI is processed, stored, or transmitted (DoD Scoping Guide, v2.13). That determination is a reason to bring the relevant facts to the assessment owner, not to guess from a provider’s marketing description.

From a U.S.-based security operations center (SOC), we would ask the change owner to trace the new service connection and identify who can administer it. We would document monitoring dependencies and unresolved access questions. The responsible compliance owner would decide how those facts affect the assessment scope.

Ask the assessment owner to clarify the question and provide the design, data flows, service description, and current records. If assessor input is needed, ask a focused question that separates facts from assumptions and capture the response with the change decision. The goal is not to seek a blanket ruling on every technology choice, but to ensure the people accountable for the assessment understand a material boundary change before relying on outdated scope documentation.

What else should buyers and operators know?

Should every new system be treated as in scope?

No. Review what the system can do, what data it handles, and whether it provides security protections. The DoD guide describes out-of-scope assets as unable to handle CUI and not providing security protections (DoD guide).

Does a system need to store CUI to affect the boundary?

No. Processing or transmitting CUI can matter, and an asset that provides security functions may also be relevant. The guide distinguishes these asset categories in its Level 2 scoping methodology (DoD guide).

When should the review happen?

A practical approach is to review during design, before production approval, and again if implementation differs from the proposal. This timing is an operational recommendation, not a schedule prescribed by the DoD guide.

Does a service provider always need its own CMMC assessment?

Not necessarily. The guide’s treatment depends on the provider’s role and whether it handles CUI or provides security services; confirm applicable contract and assessment expectations with the assessment owner (DoD guide).

What is the next step for your organization?

Bring your scope, current evidence, and unresolved responsibilities to a focused discussion. Get a CMMC readiness assessment or Call 833-92-CYBER to clarify the next practical actions.