Dependency profile
- Dependency owner
- Multiple cloud, colocation and owned-infrastructure operators
- Affected population
- Public portals, operational services, businesses and residents
- Substitutability
- CONSTRAINED
- Switching cost
- HIGH
- Replacement time
- Scenario-specific; must be measured and tested, not assumed.
- Concentration level
- HIGH
- Non-Domination Test
- PASS_REQUIREMENTS_DEFINED
Abuse and failure paths
Abuse: Account termination, region lock-in, proprietary control plane, surveillance and unpriced egress.
Failure: Provider outage, legal seizure, billing failure or control-plane compromise.
Required exit and alternatives
Exit: Multi-provider architecture, infrastructure-as-code, local backups, DNS independence and tested evacuation.
Portability: Portable images, state, logs, secrets rotation plans and data exports.
Interoperability: Open deployment, identity, observability and networking interfaces.
Independent alternative: Independent hosting provider and static degraded-mode publication.
Emergency handback: Fail over public records, preserve identity continuity, revoke provider credentials and conduct exit drill.
Disconfirming evidence
- Failed exit drill
- Unavailable independent alternative
- Retaliation for attempted exit
- Material portability gap
- Undisclosed common-mode dependency
Truth boundary
Static risk-governance record. It does not prove an operational service, market share, capacity, dependency, alternative, or successful exit drill.
Authority and record status
Responsible authority: National Engineering Directorate and service owners.
Static concentration-governance record; no operational alternative or exit drill is proven.
Revision date: . Public corrections may be initiated through the diplomatic contact route.