The boundary, on one page.
The portal brings together your program records: posture, POA&M, evidence pointers, documents. The Enclave module adds the enclave itself, so the build and the program are read in one place.
Build stage
The four stations, with the day count: day N of 60 for Standard, or of 14 for Express.
Named users and seats
Who is inside the boundary, and the seat count.
License counts
Business Premium (GCC High) and the Defender and Purview add-on, assigned against seats.
Boundary inventory
What is inside the enclave and what is outside it, in one list.
The four workloads
Teams, Exchange, SharePoint, and OneDrive, each with its status.
Change requests
Add-user and remove-user requests, with where each one stands.
Program links
Links to the SSP, POA&M, and evidence already in the portal.
What an enclave record looks like.
Sample Co., user roles, day count, and statuses are invented for illustration. The layout will change as the module is built.
Status, in plain words.
| System | Status | What that means for you |
|---|---|---|
| Enclave module | Implemented records | Records are maintained by the inDirectIT delivery team. There is no live telemetry collection from the tenant yet. |
| Client portal | Access in preparation | Commercial Microsoft 365 and GCC High sign-in require separate tenant setup and acceptance. Native tickets and work tracking remain unavailable until integrations are ready. More on the portal. |
| CUI in the portal | Metadata and pointers | Metadata and pointers only. CUI stays inside the enclave. |
Zero CUI, by design. The portal is where the enclave is managed, never where CUI is kept. It records what is inside the boundary and where the program artifacts are, not the CUI itself.
Questions we get about it
Is the Enclave module showing live data from our tenant?
Not yet. The record views are implemented, with client access pending tenant setup and acceptance. Its records are maintained by the inDirectIT delivery team; there is no live telemetry collection from the tenant yet, and we will say so until there is.
Does the portal store any of our CUI?
The portal is designed for metadata and pointers only. Keep CUI and evidence files inside your approved enclave boundary.
Where do the SSP, POA&M, and evidence live?
The portal records document metadata and evidence pointers. Evidence files stay in your approved boundary; the Enclave module links to the program records.
See your enclave in the portal.
We walk prospective clients through the portal with their own scope in mind, including where the Enclave module stands on the day you ask.
Or call 240-331-6256, or email rj@indirectit.com.
Or email rj@indirectit.com. Share high-level requirements only; do not send CUI or sensitive files.