Glossary · Attack path

What is an attack path?

An attack path is a chain of access steps an attacker can take from an entry point to a valuable target, such as production systems or sensitive data.

Book a demoAll terms
cursor-ciEntry: AI coding agentEntry
deploy tokenCredential it can read
ci-deployerPermission it can assume
customer dbTarget: PII in productionCritical
ATTACK PATH

In practice

Each step in an attack path can be legitimate on its own: a valid login, an approved OAuth grant, a role that was assigned on purpose. The risk comes from how the steps connect. Security tools that look at one permission at a time see a list of findings. Attack path analysis connects them and shows which ones end at something that matters.

For AI agents, the entry point is often the agent itself or a credential it holds. See the full guide to AI agent attack paths.

DEFINITION

An attack path is a chain of access steps an attacker can take from an entry point to a valuable target, such as production systems or sensitive data.

HOW IT WORKS

How it works. Step by step.

The parts that make it up, in an environment with AI agents.

01Entry identity

Where the path starts: an AI agent, a token, a service account or an OAuth app.

02Credentials

What that identity holds or can read: keys in files, tokens in CI, grants on its account.

03Permissions

Roles and scopes those credentials unlock, including roles that can be assumed.

04Target

Sensitive data or a destructive action in production at the end of the chain.

EXAMPLE

What it looks like in Elmoz

A real path shape, drawn the way the Elmoz security graph shows it.

Security GraphFocus: cursor-ciAll assetsIdentitiesData stores
ATTACK PATH7 entities · 3 access steps
cursor-ciAI coding agent · CI!deploy.ymlGitHub Actions!.env fileDeploy token, 213 daysaws2ci-deployerAWS IAM roleawsprod-accountAWS accountStagingTest dataaws!Production roleAssumable3Findings3 issuescustomer dbProduction · PIIPII/NameData findingPII/EmailData finding
FAQ

Questions, answered.

Short answers about Attack path.

How is an attack path different from a vulnerability?

A vulnerability is a flaw in software. An attack path can be made entirely of valid access: a real token, an assigned role, an approved grant. Patching does not close it. Changing access does.

How do you break an attack path?

Remove or scope one step in the chain. The best choice is the breakpoint: the single change that closes the path with the least disruption to agents and people who depend on it.

Do AI agents create new attack paths?

Mostly they use access that already exists. What changes is speed and control: an agent can walk a path in seconds and can be steered by prompt injection, so a path that looked theoretical becomes usable.

See what your agents can reach. Before someone else does.

Book a demo and we walk through the access paths in an environment like yours.