attacktree
v0.1.0Attack trees with attacker profiles, AND/OR path simulation, control roadmaps, and control-to-test traceability
Get started
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/introduction/>Introduction
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/installation/>Installation
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/quickstart/>Quickstart
Concepts
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/attack-trees/>Attack trees
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/risk-model/>Risk model
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/simulation/>Simulation
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/evidence/>Verification
Guides
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/workflow/>Workflow
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/ci/>CI and code scanning
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/otm/>OTM interop
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/agentic-systems/>Agentic and LLM systems
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/troubleshooting/>Troubleshooting
Reference
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/commands/>Commands
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/cli/>Engine CLI
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/attack-tree-format/>File format
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/checks/>Checks
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/configuration/>Configuration
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/profiles/>Profiles
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/glossary/>Glossary
Project
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/design/>Design and roadmap
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/security/>Security
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/releasing/>Releasing
Documentation
AttackTree adds attack trees to <a href=https://github.com/github/spec-kit rel=external>Spec Kit’s Spec-Driven Development workflow. New here? Read <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/introduction/>What is AttackTree?, then follow the <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/quickstart/>quickstart. The rest is organised by what you need: concepts explain how and why it works, guides solve a task, and the reference lists every command, field, and setting.
Get started
What is AttackTree?
AttackTree is an open-source Spec Kit extension that builds attack trees from your spec, simulates which security controls cut the attack paths, and verifies each control with evidence.
<a class=doc-card href=https://hupe1980.github.io/spec-kit-attacktree/docs/installation/>Installation
Install the AttackTree extension into a Spec Kit project from a release archive, a catalog, or a local checkout, plus the optional preset and workflow.
<a class=doc-card href=https://hupe1980.github.io/spec-kit-attacktree/docs/quickstart/>Quickstart
Run AttackTree on the shipped example in five minutes, then build your first attack tree for your own feature with a coding agent.
Concepts
Attack trees explained
What an attack tree is, where the method comes from, how AND and OR nodes and leaf values work, and why attack trees rank threats better than a list.
<a class=doc-card href=https://hupe1980.github.io/spec-kit-attacktree/docs/risk-model/>Risk model
How AttackTree computes likelihood, feasibility, control effects, actor occurrence, and residual risk, with a worked example and the full risk matrix.
<a class=doc-card href=https://hupe1980.github.io/spec-kit-attacktree/docs/simulation/>Simulation
What the AttackTree simulation reports: most likely and cheapest paths, choke points, Achilles heels, single points of failure, what-if and defence in depth, the roadmap, and Monte Carlo.
<a class=doc-card href=https://hupe1980.github.io/spec-kit-attacktree/docs/evidence/>Verification and convergence
How AttackTree verifies security controls with evidence: verdicts, evidence levels, micro attack simulations and bypass rates, status roll-up, and the definition of converged.
Guides
Workflow
Use AttackTree across the Spec Kit lifecycle: two modelling passes, simulation before tasks, checks before implementation, convergence after, plus hooks, the companion preset, and the workflow.
<a class=doc-card href=https://hupe1980.github.io/spec-kit-attacktree/docs/ci/>Continuous integration
Run AttackTree's checks and simulation in CI without an agent, upload findings to GitHub code scanning as SARIF, and gate pull requests on residual risk.
<a class=doc-card href=https://hupe1980.github.io/spec-kit-attacktree/docs/otm/>Open Threat Model interop
Seed AttackTree goals and assets from an Open Threat Model (OTM) file exported by other threat modelling tools, link goals back to threats, and track drift.
<a class=doc-card href=https://hupe1980.github.io/spec-kit-attacktree/docs/agentic-systems/>Agentic and LLM systems
Model attack trees for LLM applications and AI agents: the five attack-surface zones, prompt injection and tool-misuse paths, probabilistic guardrails, and bypass-rate measurement.
<a class=doc-card href=https://hupe1980.github.io/spec-kit-attacktree/docs/troubleshooting/>Troubleshooting
Fixes for common AttackTree problems: missing Python runtime, feature detection, YAML parse errors, rejected merges, infeasible or unknown goals, truncation, and drift.
Reference
Commands
Reference for the four AttackTree agent commands: model, simulate, check, and converge. Arguments, what each command reads and writes, and when to run it.
<a class=doc-card href=https://hupe1980.github.io/spec-kit-attacktree/docs/cli/>Engine CLI
Reference for attacktree.sh, the deterministic AttackTree engine: global options, feature resolution, every subcommand with its flags, and exit codes.
<a class=doc-card href=https://hupe1980.github.io/spec-kit-attacktree/docs/attack-tree-format/>attack-tree.yaml format
Complete reference for attack-tree.yaml: actors, assets, goals, AND/OR nodes, attack vectors, controls, CR requirements, verification, decisions, reference rules, baselines, and drift hashes.
<a class=doc-card href=https://hupe1980.github.io/spec-kit-attacktree/docs/checks/>Checks
Reference for AttackTree's sixteen deterministic checks A1 to A16 with severities and fixes, and the ten semantic passes the check command adds.
<a class=doc-card href=https://hupe1980.github.io/spec-kit-attacktree/docs/configuration/>Configuration
Every AttackTree configuration key with its default and effect: profiles, enforcement, risk scenario and blocking levels, simulation, risk acceptance, model rendering and OTM, and verification.
<a class=doc-card href=https://hupe1980.github.io/spec-kit-attacktree/docs/profiles/>Profiles
AttackTree profiles supply the scales the engine computes with and libraries of actor archetypes, attack vectors, and controls: the default and agentic profiles, and how to write your own.
<a class=doc-card href=https://hupe1980.github.io/spec-kit-attacktree/docs/glossary/>Glossary
Definitions of the terms used by AttackTree: attack tree, goal, node, leaf, AND and OR gates, path, choke point, control, bypass rate, residual risk, scenario, and more.
Project
Design and roadmap
Why AttackTree is built the way it is: positioning next to threat lists and attacktree.online, design decisions, what is out of scope, and the roadmap.
<a class=doc-card href=https://hupe1980.github.io/spec-kit-attacktree/docs/security/>Security
AttackTree's own threat model: prompt injection through artifacts, overwriting human content, command execution, manipulated simulations, and how each is controlled.
<a class=doc-card href=https://hupe1980.github.io/spec-kit-attacktree/docs/releasing/>Releasing
Maintainer checklist for releasing AttackTree: version bumps, the release workflow, install verification, and submission to the Spec Kit community catalog.
Attack trees for Spec-Driven Development. Open source under the MIT license.
Documentation
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/quickstart/>Quickstart
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/attack-trees/>Attack trees explained
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/commands/>Commands
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/attack-tree-format/>File format
Project
- <a href=https://github.com/hupe1980/spec-kit-attacktree rel=noopener>GitHub
- <a href=https://github.com/hupe1980/spec-kit-attacktree/releases rel=noopener>Releases
- <a href=https://github.com/hupe1980/spec-kit-attacktree/blob/main/CHANGELOG.md rel=noopener>Changelog
- <a href=https://hupe1980.github.io/spec-kit-attacktree/docs/security/>Security
Ecosystem
- <a href=https://github.com/github/spec-kit rel=noopener>GitHub Spec Kit
- <a href=https://www.schneier.com/academic/archives/1999/12/attack_trees.html rel=noopener>Schneier: Attack Trees
- <a href=https://attacktree.online/ rel=noopener>attacktree.online
Stats
Version
Install
Using the Specify CLI
specify extension add attacktree --from https://github.com/hupe1980/spec-kit-attacktree/archive/refs/tags/v0.1.0.zip