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 plan
v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/tradecraft-attack-path-mappingWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package22fce7dd…49e4f33f
22fce7dd7abf…703749e4f33f1 file · 1.5 KBScanLowno findings
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/tradecraft/tradecraft-attack-path-mapping@ee0e0c5
On this page
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
- Nodes: assets (hosts, buckets, DBs), identities (users, roles, service accounts), and secrets.
- Edges = a technique you can actually run: "user→host" (valid creds / RCE), "host→identity"
(token/cred theft —
privesc-*,cloud-imds-ssrf), "identity→identity" (delegation, role assumption —ad-*,cloud-iam-privesc), "identity→data" (read access). Label each edge with its skill. - Build the graph: BloodHound (AD), PMapper/Cartography (AWS/cloud IAM), or a hand-drawn graph
in
notes.mdfor smaller scopes. - Query for paths: shortest path from a controlled node to the objective; enumerate alternates.
- Pick the path: lowest cost/noise, highest reliability. Each edge becomes an ordered lead in
the scenario (
tradecraft-attack-scenarios). - Defensive read: rank edges by how many objective-paths traverse them — those are the remediation priorities (kill the edge, not just the node).
Gotchas
- An edge you can't actually execute is not an edge — validate the technique, don't assume it.
- Graphs go stale as you change the environment (new creds, revoked tokens); re-query after each win.
- Don't collect the whole graph when one path proves impact — least action.
Verify success
You can state the full path — node by node, edge by edge, each edge a runnable technique — from a starting position to the objective, and name the one edge whose removal breaks it.
References
BloodHound / SharpHound; NCC PMapper; AWS/GCP Cartography; MITRE ATT&CK flow.
Files in this version
- SKILL.md2.6 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | 22fce7dd | Signed | – |
More from NoorQureshi
All from this publisherMore in Active Directory and Windows
See the category- offensive-windows-mitigationssnailsploit/offensive-windows-mitigations4
- active-directory-attack-pathssecurityskills/active-directory-attack-paths3
- analyzing-powershell-script-block-loggingmukul975/analyzing-powershell-script-block-logging3
- offensive-windows-boundariessnailsploit/offensive-windows-boundaries3
- evil-winrmaeondave/evil-winrm3
- bloodyadaeondave/bloodyad3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login