Scope
CUI flow first
Map where controlled information is stored, processed, transmitted, shared, and administered.
Who it is for
Contractors deciding whether CUI should move into GCC High, a separate enclave, a segmented workflow, or another architecture path after scoping is understood.
What is inside
- CUI workflow questions that should drive cloud and enclave decisions.
- FedRAMP and external-provider prompts to review before architecture commitments.
- Decision criteria for contained tenant, enclave, and segmented workflow options.
- Evidence and administration questions that affect long-term maintainability.
Preview
A representative decision structure for choosing architecture based on CUI movement and operations.
Cloud
Provider baseline
Identify which cloud services touch CUI and what evidence is needed for each service relationship.
Enclave
Containment option
Evaluate whether a smaller enclave reduces scope without creating unsustainable operations.
Evidence
Administration model
Clarify owners, access paths, logging, configuration, and evidence refresh before migration work starts.
Related service
GCC High and Enclave Strategy
Review consulting support for secure cloud and contained CUI architecture decisions.
Related tool
Scoping Boundary Builder
Use scoping inputs before choosing a cloud or enclave path.
Related article
Do We Need GCC High?
Read why GCC High is not automatic and why the right answer depends on scope.
Explore the CMMC Consulting Hub, browse the template index, open the tools hub, or review the consulting path.