# Access path

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

An access path is one route by which an identity can reach a resource: a chain of a role, a trust relationship, a network route and a permission. A resource usually has many. Removing a path requires breaking one link, and one change at the right layer can break many.

## An example, sourced

Act's home page says its guided, structured campaigns eliminate thousands of access paths and protect crown jewels with a single policy change. The SACR report on Act describes its Access Map as combining identity, network, resource and organizational controls and as separating configured, effective and observed access. These are the vendor's and the analyst's descriptions, and the counts are not independently checked here.

## Why it matters here

Counting paths is how a class-level change is shown to be worth its risk. A claim of thousands of paths should come with the model that counted them and a simulation of the removal. The path view also helps a reviewer decide which link to cut, since the cheapest link is not always the one nearest the resource.

## Related pages

- [ChatOps approval: meaning and an example](/glossary/chatops-approval/)
- [Infrastructure as code pull request: meaning and an example](/glossary/infrastructure-as-code-pull-request/)
- [IAM role: meaning and an example](/glossary/iam-role/)
- [All of them](/glossary/)

## Sources

- https://act.security (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://ciemtools.com/glossary/access-path/
