Enclave Console
Your enclave, next to the rest of your program.
CUI Track is managed in the inDirectIT client portal. One sign-in shows the enclave beside your SSP, POA&M, evidence, and support, and the delivery team works from the other side of the same records.
- Where
- inDirectIT client portal
- Shows
- Build, users, workloads, requests
- Records kept by
- The delivery team
- Live telemetry
- Not yet
- CUI stored
- None, ever
CUI Track enclave
ACME DEFENSE MFG · GCC HIGH
01
Draw the flow
02
Build the boundary
03
Name the users
04
Hold the evidence
- Named users
- 4
- 3 included · 1 added
- Business Premium
- 4
- GCC High seats
- Defender + Purview
- 4
- Add-on seats
- Change requests
- 1
- Add user · open
NAMED USERS
| Name | Role | MFA | Device |
|---|---|---|---|
| J. Reyes | Program manager | Authenticator | Compliant |
| A. Moss | Contracts | FIDO2 key | Compliant |
| K. Tran | Engineering lead | Authenticator | Compliant |
| L. Ortiz | Quality | Pending | Enrolling |
WORKLOADS
- TeamsCONFIGURED
- ExchangeCONFIGURED
- SharePointCONFIGURED
- OneDriveIN BUILD
What it shows
Six views of one enclave.
01
Build tracker
The four stations, the day count against 60 or 14, and the target ready date.
02
Named users and seats
Who is in the enclave, their role, MFA method, and device status, against your three included seats.
03
Licenses
Business Premium GCC High and the Defender and Purview add-on, counted per seat.
04
Workloads
Teams, Exchange, SharePoint, and OneDrive, each with its configuration status.
05
Boundary inventory
What is inside the enclave and what stays yours, as agreed in the first station.
06
Change requests
Add or remove a named user from the portal. The delivery team works the request and you see it close.
Status, stated plainly
What is live, and what is not yet.
The client portal is built and running, and clients are onboarded as their engagements start. The Enclave module is being built into it now. Until the tenant integration ships, enclave records are kept by the inDirectIT delivery team, not collected live.
- Client portal: posture, POA&M, evidence, documents, supportROLLING OUT
- Sign-in with the Entra identities we manage for youCONNECTING
- Enclave module: build tracker, users, workloads, requestsIN BUILD
- Live telemetry from the GCC High tenantNOT YET
The portal holds no CUI. Ever.
It keeps metadata and pointers. Evidence files stay inside your GCC High boundary.
Boundary review
See it on your own flow.
A boundary review ends with a map of your CUI and, if it fits, the enclave plan you would track in the console.