Enclave Console
Your enclave, next to the rest of your program.
CUIckStart enclave records are managed in the inDirectIT client portal, alongside your SSP, POA&M and evidence pointers. Your delivery team maintains the records. Client sign-in opens after tenant setup and acceptance.
- Where
- inDirectIT client portal
- Shows
- Build, users, workloads, requests
- Records kept by
- The delivery team
- Live telemetry
- Not yet
- Record scope
- Metadata and pointers only
CUIckStart 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 implemented, and what is still pending.
The portal and Enclave record views are implemented. Client access opens after tenant configuration and acceptance. Enclave records are kept by the inDirectIT delivery team; live tenant telemetry, native tickets and work tracking remain unavailable until integrations are ready.
- Client portal: posture, POA&M, evidence pointers, documentsACCESS IN PREPARATION
- Commercial Microsoft 365 and GCC High work identitiesTENANT SETUP PENDING
- Enclave records: build tracker, users, workloads, requestsIMPLEMENTED
- Live tenant telemetry, native tickets and work trackingUNAVAILABLE
Keep CUI inside your approved boundary.
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.