Readiness check
Services / Enclave · Build

The accredited boundary, stood up in your cloud.

Enclave is the build engagement. We architect and deploy the CUI boundary in the FedRAMP-authorized cloud you already run — mapped control by control to NIST 800-171, ready to hand to Cadence to operate.

Scope an Enclave build See Cadence (run) →
The CUI boundaryAletheon
Identity & accessAC · IA
Network & boundarySC
Encryption & keysSC · MP
Logging & monitoringAU · SI
Audit evidenceCA · AU
AWSAzureGCP
built to NIST 800-171 · on the cloud you run
Scope

Scope is the biggest lever on cost. We draw the boundary tight.

The enclave holds only what touches CUI — and the security stack that protects it. Everything genuinely separated stays outside the assessment. Fewer assets assessed; all 110 requirements still applied in full inside.

In scope · assessed
CUI assets and the security stack that protects them.
Documented
Risk-managed and specialized assets, kept on the record.
Out of scope
Genuinely separated — enforced, not asserted.
See how CUI scoping works →
How the build runs

Four phases. Then Cadence takes over.

01
ASSESS

Read the clause, scope the CUI, map current state to the 110 controls.

02
ARCHITECT

Design the boundary in your cloud region, control by control, with your IT lead.

03
DEPLOY

Stand it up as infrastructure-as-code. Migrate CUI workloads into the boundary.

04
HANDOFF

Deliver the SSP and evidence baseline. Cadence begins operating the boundary.

What you get

Deliverables, not slideware.

The boundary itself

A running, accredited CUI enclave in your cloud — as code, versioned, and yours.

System Security Plan

An SSP mapped to all 110 controls, with the shared-responsibility split written down.

Evidence baseline

The first evidence set against the 320 objectives, ready for Cadence to keep current.

Start with the clause, not the migration.

A readiness check tells you what the Enclave build takes — before you commit to anything.

Book a readiness check