Individual skill
tradecraft-attack-path-mapping
Model the target as an attack graph — nodes (assets, identities, trust) and edges (a technique that gets you from one to the next) — and find the shortest path to the objective. Load when many findings need to be assembled into a route, on "how do these bugs connect", AD/cloud lateral- movement planning, or to explain how a foothold reaches crown jewels.
skills/tradecraft/tradecraft-attack-path-mapping/SKILL.md
Source commit ee0e0c50d2f6d941a14b73dd85a2b470d0ab976e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27
- Repository last updated
- Oct 14, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-security Repository topic
- application-security Repository topic
- blue-team Repository topic
- bug-bounty Repository topic
- claude-code Repository topic
- codex Repository topic
- detection-engineering Repository topic
- gemini Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Attack-path mapping
## When it applies
You have several footholds/findings and need to see how they combine into a route to the objective
— or you're defending and want to know which single edge, if cut, breaks the most paths.
## Why it works
Attackers think in graphs; defenders who do too find the choke points. Modelling
principals → permissions → resources as edges makes "can A reach D?" a reachability query, and
surfaces multi-step paths no single finding reveals (this is why BloodHound changed AD assessment).
## Method
1. **Nodes**: assets (hosts, buckets, DBs), identities (users, roles, service accounts), and secrets.
2. **Edges = a technique you can actually run**: "user→host" (valid creds / RCE), "host→identity"