# The eight access paths, counted across the ledger

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

Eight access paths explain how access to cloud data was gained in the ledger: leaked access keys, stolen user credentials, over-permissioned identities, public resources, cross-tenant flaws, third-party access, exposed network services and retained access. Each path has a definition, a two-paragraph explanation from provider documentation and the kind of preventive control.

| Access path | Incidents | Kind of control |
| --- | --- | --- |
| [Leaked access keys and secrets](/access-paths/leaked-access-key/) | 27 | replace long-lived keys with short-lived credentials issued to the workload, and scan code, logs and files for secrets before they are published |
| [Stolen user credentials and session tokens](/access-paths/stolen-user-credentials/) | 47 | require phishing-resistant multifactor authentication for every person with access to the data platform, and limit what any single sign-in can reach |
| [Over-permissioned identities](/access-paths/over-permissioned-identity/) | 13 | scope each identity to the actions and resources its task needs, cap delegated permissions with boundaries, and remove access that is unused |
| [Public storage, databases and services](/access-paths/public-resource/) | 15 | enforce an account-wide or organization-wide block on public access to storage, and require sign-in for every database and service |
| [Cross-tenant access](/access-paths/cross-tenant/) | 3 | validate the tenant and issuer on every token an application accepts, and turn off cross-tenant features that are not in use |
| [Third-party access](/access-paths/third-party-access/) | 25 | grant each vendor a scoped role bound to a customer-specific condition, review integrations on a schedule, and revoke tokens the vendor no longer needs |
| [Exposed network services and request paths](/access-paths/exposed-network-service/) | 8 | require session-based metadata access on every instance, close management ports to the internet, and limit the role attached to each workload |
| [Retained access after departure or change](/access-paths/retained-access/) | 7 | remove every credential and grant tied to a departing person or retired app on the day it ends, and review unused access on a fixed schedule |

## Related pages

- [Cloud breaches by cloud and provider](/clouds/)
- [Cloud breaches by year, 2019 to 2026](/years/)
- [Disclosed cloud attack techniques, with sources](/techniques/)

Last reviewed 16 Nov 2026. Canonical: https://cloudsecuritybreaches.com/access-paths/
