Policy Sprawl Index
Distribute your JIT access policy surface across environments using the sliders below. Sliders must sum to exactly 100%. The Operational Overhead Index (OOI) is a heuristic, not a precise measurement, that scores how fragmented your policy surface is. Higher fragmentation across more platforms generally means more coordination overhead, more inconsistency risk, and higher operational cost; the scoring weights behind that are shown in full below the results.
How this score is calculated
The Operational Overhead Index is a heuristic model, not an empirically validated metric. It combines three factors: a weighted complexity score based on per-environment difficulty assumptions, a flat penalty for each additional active environment (8 points per environment beyond the first, reflecting coordination overhead), and additional penalties once on-premises share exceeds 20% or other/legacy share exceeds 10%, since both are harder for most JIT architectures to cover natively.
| Environment | Assumed relative complexity |
|---|---|
| SaaS applications | 0.8 (lowest, most JIT platforms integrate natively) |
| AWS | 1.0 |
| GCP | 1.0 |
| Azure | 1.1 |
| On-premises servers / databases | 1.5 |
| Other / legacy | 1.8 (highest, typically requires custom integration work) |
These weights reflect general architectural patterns covered elsewhere on this site, not a benchmark study. Treat the score as directional: useful for comparing scenarios against each other, not as a precise industry-validated figure.