# Reachability

Glossary term, read 10 Nov 2026

**In short.** Reachability is whether one resource or identity can get to another once network paths and IAM permissions are considered together. A resource may be allowed by policy and unreachable by network, or reachable and denied by policy. Access exists only where both tests pass.

## An example, sourced

Act's engineering blog says that to do anything in the cloud, an identity attached to a workload has to pass two tests at once: reachability from the network, and permission in IAM. Act argues these checks are evaluated separately, by separate teams using tools with no shared context, so nobody computes what an identity or a compromised workload can truly reach once both halves are fused. This is Act's framing.

## Why it matters here

Reachability is the measure that separates unused access from excess access. A permission that nothing can reach is a lower priority than one on an exposed workload, and a usage count cannot tell the two apart. A model that joins the two is the main difference between identity-only tools and the tools that score highest on the coverage criterion.

## Sources

- https://act.security/resources/network-and-identity-each-see-half-your-cloud-your-attacker-sees-both (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://cloudleastprivilege.com/glossary/reachability/
