Context
The dashboard's provider selector includes Yandex Cloud.
Yandex Cloud
Track Yandex Cloud projects in the dashboard and use the sovereignty lens to make jurisdiction, residency and exit explicit.
- Dashboard-tracked provider · jurisdiction lens
- Dashboard-tracked · control coverage expanding
- 4 relevant pillars
- 4 starting points
What Wombat adds to the provider view.
Yandex Cloud is available in the dashboard's provider selector. Because the jurisdiction is different from the EU providers, the sovereignty and exit questions matter as much as the security baseline. Control-pack coverage is expanding; verify the current resource types in the controls catalogue.
Yandex Cloud is available as a provider in the dashboard. Treat the Wombat score as partial until the relevant control pack covers the resource types you use.
Context
Framework control packs currently cover AWS, Azure, GCP, STACKIT, OVHcloud and Hetzner Cloud; Yandex Cloud coverage is expanding.
Context
Use the sovereignty hub to make jurisdiction, residency and exit part of the assessment.
Known regions in the dashboard map.
Approximate locations only. The dashboard maps 2 region codes for this provider; below are the distinct locations in that map.
Approximate region locations from the dashboard map. Not a datacenter map.
Moscow, Russia
Data and verification
Data status. The region labels for Yandex Cloud are compiled from the WOMBATpass dashboard region map. The current extract is dated 31 Oct 2026. The page currently lists 2 region codes from that map.
Verification. The data has not been cross-validated with the provider. It may be incomplete, approximate or outdated.
Intended use. The information is provided for general orientation only. It is not a guarantee of service availability, a representation of exact datacenter locations, or a statement of provider certification.
Corrections. Providers and other parties may submit corrections — including the provider name, the affected region code or control count, and a public source — to page@wombat-gov.dev or open a correction issue ↗.
Trademarks. Provider names and trademarks are the property of their respective owners. Wombat is not affiliated with, endorsed by or sponsored by these providers; the names are used solely for identification.
License. The provider data on this page is published under CC BY 4.0. It is a derived compilation from the WOMBATpass dashboard and the Wombat framework control pack. Attribution: Wombat Community. The data is provided without warranty. Data license.
Methodology. Read the data methodology →
Pillars that matter on Yandex Cloud.
The same control model applies across providers, so the comparison stays consistent when the estate does not.
WAF-SOV
Sovereign
Jurisdiction, data residency, key custody and exit are the primary questions for this provider.
Read the Sovereign pillar →WAF-SEC
Security
Identity, network boundaries and encryption remain the technical baseline.
Read the Security pillar →WAF-REL
Reliability
Recovery and portability determine whether an exit is credible.
Read the Reliability pillar →WAF-OPS
Operational Excellence
Supplier oversight, incidents and evidence need an operating model.
Read the Operational Excellence pillar →Start here.
Use the provider-native guidance for depth, and the Wombat baseline for the cross-provider score, comparison and evidence.
Sovereignty hub
Open →Controls catalogue
Open →WOMBATpass quickstart
Open →Trust center
Open →Make jurisdiction part of the score
Use the dashboard to track the workload, then use the sovereignty hub to make residency, key custody and exit explicit.