Attack Tree
Pronunciation: uh-TAK TREE
Definition
An attack tree is a hierarchical model that breaks an adversary's objective into alternative or combined steps required for success. Defenses against Attack Tree combine secure design, least privilege, validation, monitoring, rate or value limits, and tested containment and recovery procedures.
Overview
Meaning and scope
An attack tree is a hierarchical model that breaks an adversary’s objective into alternative or combined steps required for success. Defenses against Attack Tree combine secure design, least privilege, validation, monitoring, rate or value limits, and tested containment and recovery procedures.
Mechanism and operation
An attack tree begins with an unwanted outcome at its root, such as stealing treasury funds or taking over an account. Nodes may represent alternatives where any one method succeeds or combinations where several conditions are required. Teams can annotate branches with likelihood, cost, skill, prerequisites, detectability, impact, and existing controls to compare realistic routes. Attack trees support threat modeling, security reviews, incident exercises, and control prioritization. An attack tree converts a broad threat into structured paths, making assumptions, control gaps, and high-leverage defenses easier to evaluate. A theoretical weakness or scanner result involving combined steps required for success should not be reported as exploitation without corroborating logs, transactions, or configuration evidence.
Practical payment example
A security team maps several ways an attacker could redirect a refund, from account takeover to malicious configuration changes.
Operational checks
Assessment of Attack Tree should trace a hierarchical model that breaks an adversary’s objective into alternative or combined steps required for success from prerequisite and entry point through observable impact on the affected service. Prevention, detection, containment, and recovery for the Attack Tree context should be tested against the architecture associated with combined steps required for success.
Distinctions and limits
Branches describe the different conditions, techniques, or subgoals that could lead to that result. They are only as useful as their assumptions, so models should include people, third parties, operational workflows, and changing architecture rather than focusing solely on software exploits.
Related reading
Example
A security team maps several ways an attacker could redirect a refund, from account takeover to malicious configuration changes.
Comparison
Branches describe the different conditions, techniques, or subgoals that could lead to that result. They are only as useful as their assumptions, so models should include people, third parties, operational workflows, and changing architecture rather than focusing solely on software exploits.
Key Takeaway
An attack tree converts a broad threat into structured paths, making assumptions, control gaps, and high-leverage defenses easier to evaluate.
Sources
- NIST Documentation: Cyberframework — NIST (2026-07-30)