Test runner
Records the tenant isolation, object ACL and route separation test packs.
Internal GCCAP operating surface
This page is retained behind the public client website.
GCCAP does not delete operating records, trial packs, hardware activation surfaces or evidence automation layers. They are preserved for authorised client portal, command-centre and internal operating use while the public website stays clean for airline first impressions.
Open portal accessInternal GCCAP surface
Control tenant tests, denial evidence, report ownership and evidence-vault ACL readiness.
The lab is the internal operating surface for production tenant isolation evidence. It keeps permission tests, cross-tenant denials, route separation and tenant readiness gates governed before external client onboarding.
StatusInternal / restricted surface. Not part of the public client walkthrough.
GCCAP
Sensor
Gateway
Evidence
Watchdog
Journey intelligenceRepresentative demo
APIs/api/tenant-isolation/*
PurposeAccess evidence
StatusBlocked until tests pass
BoundaryClient vs GCCAP staff
Operational layer
Lab controls
Use these APIs to seed, review and update tenant isolation readiness evidence.
Denial evidence
Captures planned and executed cross-tenant denial scenarios.
Permission matrix
Keeps roles, allowed actions and denied actions explicit.
Audit pack
Collects production evidence before live user cutover.
Governance
Cutover rule
Do not onboard external users until the readiness scan is green.
- Every client-facing API must include tenant ownership enforcement.
- Every export/download must validate ownership before object access.
- Every command/admin API must be inaccessible to client sessions.
- Every denial must be logged and retained as evidence.