Air-gapped deployment doesn’t care about your delicate identity spreadsheets or your neat RBAC diagrams. When you scale a system behind a disconnected wall, each new service, integration, or team brings its own gravity. Teams split. Workloads fork. Roles accumulate invisible overlaps. Before long, you face large-scale role explosion—hundreds, sometimes thousands, of narrowly-defined roles that must be maintained across code, config, and infrastructure.
The problem is ruthless because air-gapped environments remove the safety nets. No cloud sync. No quick permission audits with online tooling. Every change is manual, regimented, and bound by whatever limited automation fits inside your locked perimeter. The stakes grow with every deployment. Each redundant role increases attack surface and fragility. Every over-privileged role is a silent breach waiting to happen.
At scale, the complexity feeds itself. Engineers add “just one temporary role” for a one-off task. It never leaves. Another service demands access to a resource under another team’s namespace. A new integration needs admin-like powers “just for testing.” Multiply that by dozens of teams and you have the makings of a permissions sprawl too big to visualize, too messy to govern.