Help Center

Everything you need to model threats in ThreatTree — from your first forest to a signed-off risk register. Every section below walks through the real UI, with a worked example you can follow along with.

Getting Started

ThreatTree organizes your work into Forests. A forest is a container for one system, product, or engagement — inside it you build Data Flow Diagrams (DFDs) to map architecture, and Attack Trees to decompose specific threats against that architecture. Findings roll up automatically into a Risk Register, which you can export as a PDF report.

Forest 1 system / engagement DFD Attack Tree(s) Risk Register auto-populated PDF Report executive-ready export

The core ThreatTree workflow: everything lives inside a forest and rolls up to a report.

Not sure where to start? Start from an example

Every plan, Free included, comes with five finished threat models: one of an on-premise network and four of SaaS apps (all five are described on the threat model examples page). Each has one data flow diagram, two attack trees and 10 to 12 scored risks, every risk with framework tags, a treatment plan and an owner. Pick the one closest to how your app is built:

  • Ironbridge (on-premise): a company's own data center: edge router, firewalls, a DMZ with a load balancer and WAF, core and access switches, Wi-Fi, DNS and DHCP, Active Directory, hypervisors, SAN, backups and a management network.
  • Quillpad (shared hosting + AI): an AI writing assistant: Laravel and MySQL on a Hostinger or GoDaddy-style hosting plan, calling the OpenAI API.
  • Lexibase (AWS + AI): an AI document assistant: multi-tenant document Q&A on Amazon Bedrock with Cognito, ECS Fargate, Lambda, S3 and OpenSearch.
  • Teamscope (Azure + Google Cloud): a people analytics app: Entra ID sign-in on Azure, BigQuery and Gemini on Google Cloud, joined by workload identity federation.
  • Invoicely (simple): a small SaaS invoicing app with a web API, admin console, Stripe and file storage. It's the system from our step-by-step walkthrough.
  1. On your Dashboard, click New Forest, then the Start from an example tab, and Open the one you want. Until you have a forest, the same examples are listed on the dashboard itself.
  2. The diagram opens with a blue banner. Click any element to read its threats, open Attack Trees at the top right, then See the risk register.
  3. Relabel and extend it for your own system. An example stays out of your forest list until you click Save to my forests; on the Free plan it only counts towards your 3 forests once saved. Opening the same example again takes you back to your copy.

On Pro and Enterprise (including members of a Pro organization), the same Start from an example tab also lists the industry templates: Fintech Payment Flow, Healthcare EHR, AI Agent Pipeline, Connected Vehicle TARA, Connected Insulin Pump, Water Treatment Plant OT, Electricity Grid & Substation OT, Pharma Manufacturing Plant OT and B2B SaaS Platform. On Free they appear locked, with a link to upgrade.

The shared-hosting, AWS and Azure + Google Cloud examples draw their AI services (OpenAI, Bedrock, Vertex AI) with the AI element types. You can edit them on any plan; adding new AI elements needs the AI & ML Industry Module. In the same way, the Connected Vehicle, Connected Insulin Pump and Water Treatment Plant templates are drawn with their industry's elements (ECUs, the therapy actuator, PLCs and so on): editable on Pro, while adding more needs that Industry Module.

1. Create your first forest

  1. From your Dashboard, click New Forest (top right).
  2. Give it a Name — e.g. "Acme Corp Threat Model" — and an optional Description (scope, system under analysis).
  3. Click Create Forest. You're dropped into the empty forest, ready to add your first diagram.

2. Add a diagram

Inside a forest, click New DFD or New Attack Tree (or use the generic Add Tree flow, which opens a modal where you name the tree and pick its type: Data Flow Diagram — "Map system components and trust boundaries" — or Attack Tree — "Decompose a threat with AND/OR logic"). If you choose Attack Tree, you can optionally link it to an existing DFD right there, or do it later — see Linking DFDs & Attack Trees.

3. Which one do I build first?

Most engagements start with a DFD to establish what the system actually looks like — its processes, data stores, trust boundaries, and external actors — and then build one or more Attack Trees against specific goals an attacker might pursue within that architecture (e.g. "Exfiltrate customer PII", "Achieve unauthorized admin access"). You don't have to link them, but doing so keeps your threat model traceable back to the architecture it's describing.

Plan limits

The Free plan is fully-featured but capped in size; Pro adds unlimited forests, collaboration, backup & restore, full compliance standards mapping, audit logs, STIX 2.1 export, and Industry Modules, and Enterprise adds SSO/SAML, IP allowlisting, and custom integrations on top of that. Core threat-elicitation frameworks (STRIDE, LINDDUN, OWASP Top 10, CAPEC), encryption, and the Risk Register PDF export are available on every plan.

PlanForestsDFDs / forestAttack Trees / DFDPrice
Free335$0
ProUnlimitedUnlimitedUnlimited$29/user/mo
EnterpriseUnlimitedUnlimitedUnlimitedQuote on request

ℹ️ Members of an Organization aren't capped

If you're a Member, Admin or Owner of a Pro or Enterprise Organization (see Collaboration & Organizations), the Free-plan limits don't apply to you, even if your own personal plan shows as Free. Free viewers are the exception: they read the organization's forests, and their own forests stay on the Free plan's limits.

Feature comparison

FeatureFreeProEnterprise
DFDs, Attack Trees, MITRE ATT&CK alignment, Risk register✓✓✓
Core frameworks (STRIDE, LINDDUN, OWASP Top 10, CAPEC)✓✓✓
Full compliance standards mapping (ISO 27001, NIST SP 800-53, NIST CSF, CIS Controls, ASVS, PCI DSS, SOC 2, NIS2, DORA, and the industry standards listed under Standards Controls)—✓✓
Forest encryption (AES-256-GCM)✓✓✓
Team collaboration (invite members to a forest)—✓✓
Company Organizations (domain-wide access)—✓✓
Risk Register PDF export✓✓✓
Board-ready forest PDF report—✓✓
Forest Backup & Restore—✓✓
Audit logs—✓✓
Asset register and mitigation catalogue—✓✓
Custom risk matrix (3×3 to 7×7, your own bands)—✓✓
STIX 2.1 export—✓✓
Industry Modules (Fintech, Healthcare, Automotive, Medical Devices, Critical Infrastructure, AI & ML, SaaS & Startups)—✓✓
Self-serve seat management (add/remove seats)—✓✓
Free view-only seats (3 per paid seat)—✓✓
SSO / SAML——✓
SCIM provisioning with IdP groups and role mapping——✓
IP allowlisting for sign-in——✓
Import DFDs from OpenAPI, CloudFormation or Terraform——✓
Ticketing sync — Jira, ServiceNow, Linear, Azure DevOps (two-way)——✓
SIEM feed (Splunk)——✓
GRC evidence sync (Vanta, Drata)——✓
Live diagram embeds in Confluence and Notion——✓
Configurable data retention——✓

See the full breakdown and current pricing on the Membership & Pricing page.

The product tour

New accounts get a short guided tour: eleven tips, each shown when you reach the point it explains, and each pointing at the control to use next. Together they follow one path, from an empty forest to its risk register.

  1. Start quickly from an example on your dashboard: the tip names the free example threat models, and one click opens one with its diagram, attack trees and scored risks, and the tour then walks you through it, from the diagram to the risk register. See all examples also lists the Pro industry templates, or you can start blank. A new blank forest opens straight away.
  2. Map the system first: in the forest, New DFD creates a data flow diagram.
  3. Open your diagram: the new DFD appears in the forest's list of trees, and the tip points at its name. Clicking the name opens it in the editor.
  4. Add the parts of your system from the element palette.
  5. Connect the parts with data flows: once the diagram has two elements, the tip offers to start the first connection for you.
  6. Turn the diagram into attack trees with Generate attack trees, once the diagram has a connection.
  7. Open an attack tree: the tip points at the Attack Trees button in the DFD editor, which lists the trees built from the diagram.
  8. Score each threat on likelihood and impact.
  9. Open the risk register: once a threat has a score, the tip points at the forest's name in the breadcrumb. Back on the forest page, it points at Risk Register, above the list of trees.
  10. Click a risk to review it: in the risk register, the tip points at the first row. Each row opens the risk it shows, where you can review its score, treatment, mitigations and owner, and change what needs it before exporting.
  11. Your risk register: Export PDF, the register as a document to share.

You don't have to close a tip to move on. When you do what a tip asks (connect two elements, score a threat), it goes away and the next one appears.

Only one tip shows at a time, never over an open dialog. Skip tour on any tip ends it for good, on every device you use. Viewers don't see the tips that ask them to change something, and on a phone only the tips on the dashboard, the forest page and the risk register appear, because the editors need a larger screen.

To see it again, choose Restart product tour from your user menu, or use the button below. The tour then walks you through your own forests: each tip has a Next button that takes you to the next page, from the dashboard into a forest, its diagram, one of its attack trees and finally the risk register.

Getting started checklist and emails

Once you have your first forest, the dashboard shows a Getting started card with six steps: create a forest, add a data flow diagram, add the parts of your system, connect them, build an attack tree, and score a threat. It is ticked from what your forests really contain, not from the tour, so it is right on every device. Continue opens the place where the next step is done. The card goes away once a threat has a score; Hide removes it from this browser before then. Example drafts you haven't saved don't count.

New accounts also get up to four short emails in their first two weeks: a welcome when you verify your address, then one about a day, three days and a week after signing up. Each names your next step and links back to it. The last one adds how many diagrams, elements and attack trees you have. The emails contain counts only, never the names of your forests, diagrams or threats. They stop as soon as you score a threat, and the follow-ups wait if you have used the app in the last 12 hours. To stop them yourself, use Stop these emails at the bottom of any of them, or turn off Getting-started tips in Settings → Preferences. Accounts that joined to work on someone else's forest don't get them.

The first time you open the risk register of a forest you own and it has a scored risk, a Your first risk register is ready panel says how many risks are scored and offers Export PDF. On Pro and Enterprise it also offers Invite a reviewer, which opens the forest's invite dialog. Exporting or Dismiss removes the panel for good in that browser.

On a forest's page, type in Search this forest above the list of trees. It finds trees by name, and DFD elements, threats and goals by name, description or element type. Each result says where it is; click it to open that tree with the item selected. Use ↓ and ↑ to move through the results, Enter to open the first one, and Esc to clear. Encrypted forests can't be searched.

To search all your forests at once, use the search box under My Forests on the dashboard. It finds forests, trees, and the elements, threats and goals inside them, in every forest you can open. Every word you type must match. While you search, the dashboard shows only the forests with a match; press Enter to close the list of results and look at them, and Clear search to see every forest again.

The dashboard (My Forests)

The dashboard lists every forest you can open, newest activity first, with totals for your forests, data flow diagrams and attack trees.

  • Each forest card shows its number of DFDs and attack trees, when it was last updated and your role. Labels flag what needs attention: Review due, its approval state when it uses review and approval, the number of threats to re-review after a diagram change, the number of open discussions (click it to open them), and Encrypted for a locked forest.
  • Search all your forests from the box under the title. It finds forests, trees, and the elements, threats and goals inside them, and shows only the matching forests while you search (see Search).
  • For you lists the comments that mention you or reply to you, until you open them or click Mark all as read (see Comments and discussions).
  • Risk portfolio (Enterprise) opens every risk across your forests in one place (see Risk portfolio).
  • The ··· menu on a forest you own renames it, edits its description, marks it as reviewed, exports it or deletes it.

Review due

A threat model goes out of date when the system changes. A forest that has at least one attack tree, and that nobody has changed for 90 days, gets a Review due label on its dashboard card. Any change to its diagrams clears the label. If you have looked and the model still holds, the forest's owner can choose Mark as reviewed from the card's ··· menu: the 90 days start again, and the audit log records it.

With Review reminders on in Settings → Preferences, the owner also gets an email saying how many of their models are due, at most once per model every 90 days. The email never names the forests. New accounts start with reminders on; accounts created before this feature have them off until they turn them on. Stop review reminders at the bottom of the email turns them off.

Data Flow Diagrams

A DFD maps what your system is made of and how data moves through it: processes, data stores, external actors, and the trust boundaries between them. It's the architecture layer your Attack Trees get built against.

The palette

The left-hand palette holds every element you can drag onto the canvas, in collapsible groups (listed below). Every item also works from the keyboard: Tab to it and press Enter or Space to place it at the canvas centre, no mouse required. Use the search box at the top of the palette to filter by name if you're hunting for one specific element.

Classic DFD notation ("DFD Elements" group)

ElementShapeRepresents
ProcessCircleSomething that transforms data — an application, a service, a function.
External EntityRectangleAn actor outside your system's control — a user, a third-party service, another company's system.
Data StoreOpen-ended linesData at rest — a database, a file store, a cache. Has extra fields for Database System (20 options across SQL/NoSQL, each with its own icon and color) and Data Classification (Public / Internal / Confidential / Restricted).
Trust BoundaryDashed rounded rectangleA line across which trust level changes — a network segment, a process boundary, a cloud account edge. See below for its sub-type and cloud-branding options.

"Standard Elements" group — infrastructure

These aren't part of classic DFD notation, but they let you be specific about the infrastructure sitting behind a Process without inventing a workaround. The group also has generic Application Server and Database elements. Each renders as a colored box with a two/three-letter badge.

ElementBadgeTypical use
Firewall—Network or application-layer traffic filtering.
Router—Network routing between segments.
Load Balancer—Distributes traffic across multiple instances of a process.
Networking DeviceNDSwitches, generic network appliances.
WAFWAFWeb Application Firewall.
CDNCDNContent Delivery Network edge.
Storage ArraySABlock/object storage infrastructure (as distinct from a logical Data Store).
Storage ServerSSA dedicated file/storage server.
API GatewayAGCentralized API entry point — auth, rate limiting, routing.
Message QueueMQAsync messaging infrastructure (queues, brokers, event buses).
Identity ProviderIDAuth/identity system — internal IdP or a federated one.
CacheCHIn-memory or distributed caching layer.
DNS ServerDNSName resolution infrastructure.

Containers, cloud and SaaS building blocks (every plan)

GroupElements
ContainersKubernetes Cluster, Kubernetes Node, Kubernetes Pod, Container
AWS / AWS SecurityEC2, S3, Lambda, RDS, DynamoDB, API Gateway, IAM, VPC, CloudFront, SQS; and GuardDuty, Security Hub, CloudTrail, Config, Macie, Inspector, Detective, WAF, Shield, Network Firewall, Firewall Manager, PrivateLink, Cognito, Directory Service, KMS, Secrets Manager, Certificate Manager
Azure / Azure SecurityVirtual Machine, Blob Storage, Functions, SQL Database, Cosmos DB, API Management, Microsoft Entra ID, Virtual Network, Front Door / CDN, Service Bus; and Defender for Cloud, Sentinel, Monitor, Policy, Purview, Web Application Firewall, DDoS Protection, Firewall, Firewall Manager, Private Link, Azure AD B2C, Entra Domain Services, Key Vault
GCP / GCP SecurityCompute Engine, Cloud Storage, Cloud Functions, Cloud SQL, Firestore, API Gateway (Apigee), Cloud IAM, VPC, Cloud CDN, Pub/Sub; and Security Command Center, Google Security Operations, Cloud Logging, Sensitive Data Protection, Cloud Armor, Cloud IDS, Private Service Connect, Identity Platform, Managed Service for Microsoft AD, Cloud KMS, Secret Manager
ApplicationWeb Client (SPA), Mobile App, Admin Panel, Background Worker, Webhook Endpoint
Data & SecretsBackup / Snapshot, Secrets Store, Data Warehouse, Search Index, Logging / Observability
DevOps & Supply ChainCI/CD Pipeline, Source Code Repository
Third-Party ServicesPayment Provider, Email / SMS Service, Third-Party API / SaaS, Third-Party Script / Tag
IoTIoT Device, Device Firmware, Sensor / Actuator, IoT Gateway / Hub, Wireless Link (BLE / Zigbee / LoRaWAN / Wi-Fi), MQTT Broker, Device Provisioning / Identity, OTA Update Service, Device Shadow / Twin, Companion App. AWS IoT Core and Azure IoT Hub are in the AWS and Azure groups.

Each of these has its own suggested threats in the threat dictionary, used by Generate attack trees.

The IoT threats, including those for AWS IoT Core and Azure IoT Hub, arrive already mapped: each cites the ETSI EN 303 645 provisions and NIST IR 8259A device capabilities it relates to, carries OWASP IoT Top 10 tags, and, where they fit, ISO 27001 and NIST CSF 2.0 controls and MITRE ATT&CK technique IDs. The tags and technique IDs are kept on every plan; the standard controls are kept on Pro and Enterprise. Use these elements for consumer and commercial devices. For medical devices, industrial control systems or vehicles, the Industry Module groups below are mapped to those industries' regulations instead.

Industry Module groups Pro+

When your organization turns on an Industry Module (see Billing & Seats), the palette gains that industry's own elements. Each one comes with suggested threats in the threat dictionary, so Generate attack trees drafts threats specific to it rather than generic process or data store ones. A group stays visible in any diagram that already uses one of its elements, and those elements stay editable if the module is later turned off; adding new ones needs the module.

Group (module)Elements
Industrial Control (OT) — Critical InfrastructurePLC, RTU, HMI, SCADA Server, Historian, Engineering Workstation, Safety Instrumented System (SIS), Field Device / Sensor / Actuator, Industrial Firewall, Data Diode, Remote-Access Jump Host
Automotive — AutomotiveECU, Central Gateway, Telematics Unit (TCU), Infotainment (IVI), In-Vehicle Bus (CAN / Ethernet), OBD-II Diagnostic Port, OTA Update Server, V2X Unit, Digital Key / Key Fob, Fleet Backend
Medical Device — Medical DevicesDevice Firmware / Controller, BLE / Wireless Link, Companion App, Device Cloud, Clinician Programmer, Therapy Actuator, Medical Sensor, Firmware Update Service
Healthcare — HealthcareEHR System, FHIR API Server, HL7 Interface Engine, PACS / DICOM Imaging, Patient Portal, Health Information Exchange, Clinical Device Gateway, e-Prescribing Service
Fintech — FintechCard Tokenizer / Token Vault, HSM, Card Network / Payment Switch, Core Banking Ledger, Fraud Engine, Open-Banking API (PSD2), KYC / AML Provider, Payment Rail Gateway (SEPA / SWIFT / ACH)
SaaS Tenancy — SaaS & StartupsTenant Isolation Layer, Admin / Support Console, Customer Webhook Delivery, SSO / SCIM Connector, Audit Log Store, Feature-Flag Service
AI & ML — AI & ML SystemsLLM / Model Endpoint, Vector Store, RAG Retriever, Agent / Orchestrator, Tool / Function, Training Pipeline, Dataset, MCP Server, Guardrail / Content Filter, Model Registry, Embedding Model, Evaluation Pipeline

Their threats come already mapped to the industry's standards: IEC 62443 and NERC CIP with MITRE ATT&CK for ICS technique IDs (OT), UN R155 and ISO/SAE 21434 (Automotive), the FDA premarket cybersecurity guidance (Medical Device), the HIPAA Security Rule (Healthcare), PCI DSS and DORA (Fintech), SOC 2 (SaaS Tenancy), and NIST AI RMF with OWASP LLM and Agentic tags for the newer AI & ML elements.

Telecom Industry Module Enterprise

The Telecom module is for mobile and fixed operators. Organization owners can't switch it on in Settings: ThreatTree enables it for an Enterprise organization on request (contact us). Settings → Membership & Billing → Industry Modules shows Enabled by ThreatTree once it's on, and the change appears in your organization's activity log.

  • Elements, in two palette groups:
    • Telecom: core & radio: AMF, SMF, UPF, UDM / AUSF / UDR, NRF, NEF, SEPP, core network function, base station (gNodeB / eNodeB), O-RAN RIC, MEC / edge node.
    • Telecom: signalling, subscribers & IT: SS7 / SIGTRAN STP & firewall, Diameter Edge Agent, GTP firewall, HLR / HSS, SIM / eSIM provisioning (SM-DP+), subscriber provisioning / SIM swap, SMSC / SMS firewall, USSD gateway, charging system, BSS / OSS, lawful intercept system, CPE / home router, roaming partner / IPX.
    Each comes with suggested threats in the threat dictionary.
  • Boundary sub-types: Operator core network, Radio access network (RAN) and Roaming interconnect (IPX / GRX), on logical and physical boundaries.
  • Standards in the picker: GSMA mobile network security guidelines (FS.07, FS.11, FS.19, FS.20, FS.31, FS.37, FS.40, SGP.22), 3GPP TS 33 series (33.501, 33.401, 33.117, the SCAS documents 33.511–33.519 and lawful interception 33.126–33.128) and the EU 5G Toolbox measures. NIS2 is pinned with them. Threats are mapped to these documents; this isn't a NESAS or SCAS certification.
  • Template: Mobile Operator & Mobile Money, with 1 DFD, 2 attack trees and 10 scored risks. It's in the New Forest dialog under Your organization's templates.

If the organization leaves Enterprise, or ThreatTree removes the module, existing telecom elements and their threats stay, but new ones can't be added. The module comes back on its own when the organization returns to Enterprise.

Trust boundaries in detail

A Trust Boundary has a Kind: Logical (default — a conceptual boundary with no further classification) or Physical. Physical boundaries unlock a Sub-type dropdown:

  • Trusted Network, Untrusted Network, Internet, On-Premise — each renders with a distinct fill/stroke color so boundary types are visually distinguishable at a glance.
  • Cloud Provider — unlocks a further Cloud Provider dropdown with 16 options (AWS, Azure, GCP, OCI, Alibaba Cloud, IBM Cloud, DigitalOcean, Linode/Akamai, Hetzner, Vultr, Scaleway, OVHcloud, Huawei Cloud, Tencent Cloud, Cloudflare Workers, Other). AWS, Azure, GCP, and OCI get their real brand colors on the boundary; the rest use a generic cloud style.

With the Critical Infrastructure module on, any boundary also gets a Purdue level (Level 0 physical process through Level 5 enterprise network, plus Level 3.5 for the industrial DMZ), shown on the boundary as Purdue L2 and in exports. The module also adds the Zone kind with a Security Level Target.

Drawing data flows (connections)

Select a node, then click Draw connection in the right-hand properties panel (it toggles to Cancel connection while active) — then click the node you want to connect to. You can also press C as a shortcut to start/cancel a connection on the selected node.

Canvas tools

  • Minimap — bottom-right overview of the whole canvas once your diagram is larger than the visible area; click anywhere on it to jump there.
  • Fit Labels — resizes every node so its shape fits its label text, useful after renaming several elements to something longer or shorter.
  • Undo / Redo — the arrow buttons next to Save (or Ctrl+Z / Ctrl+Y) step back and forward through your changes, including adding, deleting and connecting elements. Each step is saved, so an undone delete really brings the element back.
  • Standard zoom/pan — see Keyboard Shortcuts for the full list (+/- to zoom, F to fit the view, Space+drag to pan).

Linking to Attack Trees

An Attack Trees badge in the toolbar shows how many attack trees are currently linked to this DFD, with a dropdown to jump to any of them. See Linking DFDs & Attack Trees for how the link is made.

Worked example: a simple 3-tier web app

Let's map a small SaaS backend: a customer's browser talks to a web application running inside an AWS account, which reads and writes to a PostgreSQL database.

  1. Drag an External Entity onto the canvas, label it Customer.
  2. Drag a Trust Boundary onto the canvas around where your app will sit. Open its properties, set Kind → Physical, Sub-type → Cloud Provider, Cloud Provider → AWS. Rename it AWS Account — prod.
  3. Inside that boundary, drag a Process, label it Web App (Node.js).
  4. Also inside the boundary, drag a Data Store, label it Customer DB. Set Database System → PostgreSQL and Data Classification → Confidential.
  5. Select Customer, click Draw connection, click Web App — label the flow HTTPS request.
  6. Repeat in the other direction for the response, and between Web App and Customer DB for the query/result.
  7. Click Fit Labels to tidy up node sizing, then save.
Customer AWS Account — prod Web App (Node.js) Customer DB PostgreSQL HTTPS request response query result

The finished diagram — an External Entity, a cloud-branded Trust Boundary, a Process, and a Data Store, connected by four labeled data flows.

Generate attack trees from the DFD All plans

Once the diagram is drawn, Generate attack trees in the toolbar drafts attack trees for it from ThreatTree's threat dictionary, the same threats listed under Suggested Threats in the Attack Tree editor. On Enterprise, your organization's own threat library is offered too.

  1. Click Generate attack trees. Every element with dictionary threats is listed, and nothing is selected to start with. Elements of the same type share one row when they're all exposed or all internal (three internal PLCs show as PLC × 3), since the dictionary's threats are the same for each. An exposed element keeps its own row, so its exposure-specific threats aren't applied to the internal ones. Elements that talk to an External Entity or have a flow crossing a Trust Boundary are marked Exposed and listed first, since that's where most real threats are.
  2. Expand an element and tick the threats that apply, or tick the element itself to take all of its threats. Select: Exposed elements / All / None changes the whole list at once.
  3. Choose One tree (the default), which puts everything you picked under a single goal, grouped by attacker goal: Gain unauthorised access, Steal sensitive data, Tamper with data or code, Disrupt the service, Act without accountability. Or choose One tree per attacker goal to get a separate tree for each of those goals.
  4. Click Generate. Each tree has an OR gate per DFD element, or one per element type when the diagram has several of that type (for example PLC (2), or PLC (3: Dosing PLC, Filter PLC +1 more) when their names differ), with the threats as leaves tagged with their STRIDE category. If a threat differs between those elements, copy the leaf under each one. Trees are named after the elements in them, for example Threats: Web API, or Gain unauthorised access: Web API in per-goal mode.
  5. An OR gate with only one branch is left out (for example the element gate when you picked a single threat for it); the leaf's panel still names its DFD element. Each tree is laid out to print as large as possible on an A4 landscape page, the same arrangement as Fit to A4 in the Attack Tree editor, so long threat names wrap onto two or three lines.

Build trees in increments. Every run creates new attack trees; it never adds to earlier ones. Pick a few related threats at a time, for example the web tier first and the data tier next, and each tree stays small enough to read in the editor and in reports. A threat that is already in any attack tree linked to this DFD is locked in the list (already in a tree) and can't be selected again, so each threat ends up in exactly one tree. Deleting it from its tree makes it available again.

Pre-mapped threats. Threats for the Industry Module elements carry their references with them. A leaf generated from one arrives with its MITRE ATT&CK technique IDs (OT elements), its OWASP Top 10 for LLM Applications or OWASP Agentic tag (the newer AI & ML elements) and, on Pro and Enterprise, its standard controls already filled in: for example IEC 62443 SR 3.1, a UN R155 Annex 5 threat category, an FDA guidance control category, a HIPAA Security Rule safeguard, a PCI DSS requirement or DORA article, a SOC 2 criterion, or a NIST AI RMF category. The same happens when you add one of these threats from Suggested Threats in the Attack Tree editor. Review them like any other part of the suggestion.

Attackers who use AI. The AI & ML module covers attacks on AI systems. The dictionary also covers attackers who use AI against ordinary systems, on every plan and without a module. Look for these threats on these elements:

  • External Entity: AI-written spear-phishing, and a cloned voice or deepfake video of an executive asking for a payment.
  • Identity Provider: a cloned voice passing helpdesk checks for an MFA or password reset, and a deepfake passing remote identity checks.
  • Web Client (SPA): AI solving the CAPTCHA.
  • API Gateway: AI agents testing authorization at scale, and bots imitating human traffic.
  • Application Server: a shorter time from disclosure to working exploit.
  • Mobile App: AI-assisted reverse engineering.
  • Source Code Repository: leaked code mined for flaws.
  • CI/CD Pipeline: a coding assistant installing a hallucinated package.
  • Logging / Observability: self-rewriting malware, and intrusions that outpace manual alert review.
  • Email / SMS Service: AI-written emails impersonating your brand.
  • Admin / Support Console (SaaS module): a cloned-voice caller changing account access.
  • LLM / Model Endpoint (AI & ML module): automated jailbreak search.

Each of these threats carries MITRE ATT&CK T1588.007 (Obtain Capabilities: Artificial Intelligence) next to the technique it speeds up, plus ISO 27001, NIST CSF, SOC 2 or NIST AI RMF controls (filled in on Pro and Enterprise). That way you can see which leaves assume an AI-assisted attacker. Most of the time AI makes an attack you already model cheaper or faster rather than new, so when you review these, revisit the Likelihood of the leaves you already have, not only the new ones.

Generated leaves are suggestions: they're drawn with a dashed amber outline and stay out of the risk register until you review them. Open a tree and click Review suggestions to step through them. Accept one, or set its Likelihood and Impact, and it joins the register like any other leaf. Not relevant deletes it.

When the dictionary changes. ThreatTree adds threats to the dictionary and improves their wording over time. The dialog always lists the current dictionary, so new threats show up there, ready to select. Clicking Generate attack trees also brings this DFD's suggested threats up to date: a suggestion you haven't touched gets the dictionary's latest title, description and STRIDE category (and its technique IDs and standard controls, if you haven't changed those either), and the dialog tells you how many were updated. Threats you've accepted, scored or edited are yours, and are never changed. A suggestion whose threat was removed from the dictionary stays in its tree until you delete it.

The dictionary gives you a starting point, not a finished model

Dictionary threats are generic to the element type, and the trees they produce are flat lists. Keep the threats that are real for your system, then add the attack steps (AND paths) that only someone who knows it can describe.

Each generated tree counts towards your plan's attack-tree limit per DFD (5 on Free). If one tree per goal would go over it, choose One tree or select fewer threats. Generation isn't available in encrypted forests.

Security attributes and rules Enterprise

The dictionary matches threats to an element's type. Rules look at what you record about your own diagram. Select a data flow or element in the DFD editor and fill in its Security fields:

  • Data flows: Protocol, Encrypted in transit, Authentication, and Data carried.
  • Data stores: Encrypted at rest, and Internet-facing.
  • Processes and other elements: Authentication required, Internet-facing, and Privileged (admin).

Leave a field on Unknown when you don't know: no rule fires on an unknown value. Internet-facing defaults to what the diagram shows (the element exchanges a flow with an External Entity across a Trust Boundary); set it to Yes or No to override that. The fields are saved with the diagram, and are covered by undo, backups and exports.

In Generate attack trees, threats raised by rules are listed first under each element, tagged Rule, with a line saying why, for example Flow Mobile app → API crosses VPC, encrypted: no. As with dictionary threats, you pick the ones that apply. Generated leaves carry the rule's STRIDE category and ATT&CK techniques.

When the diagram changes. New rule hits simply appear in the dialog. If a rule that raised a threat no longer applies, for example because the flow is now encrypted, the dialog lists that threat at the top so you can check it and delete it if it's no longer real.

RuleSTRIDEWhen it fires
Data intercepted on an unencrypted flow across a trust boundaryInformation DisclosureThe flow is marked as not encrypted and crosses a trust boundary, so anyone on the network path between the two sides can read it.
Data modified in transit on an unencrypted flowTamperingWithout transport encryption the flow has no integrity protection either: an attacker on the path can change requests or responses without either side noticing.
Sensitive data sent in clear textInformation DisclosureThe flow carries confidential or restricted data and is marked as not encrypted.
Plain HTTP flow without confirmed TLSInformation DisclosureThe protocol is HTTP and encryption isn't recorded.
Unauthenticated callers reach the targetSpoofingThe flow into the target is marked as needing no authentication, so the target can't tell who is calling.
Anonymous outside access to an internal functionElevation of PrivilegeAn external entity calls the target across a trust boundary with no authentication.
Password-only authentication across a trust boundarySpoofingThe flow authenticates with a password across a trust boundary, which leaves it open to credential stuffing, brute force and phishing.
Bearer token sent unencrypted can be replayedSpoofingThe flow uses token authentication but isn't encrypted, so a captured token can be replayed until it expires.
Sensitive data leaves your controlInformation DisclosureConfidential or restricted data flows to the target, an external entity.
External entity reads or writes a data store directlyTamperingAn external entity connects straight to the data store the store, bypassing the application's validation and authorization.
Database protocol exposed across a trust boundaryInformation DisclosureA SQL connection crosses a trust boundary, which exposes the database's own login and query surface.
Remote shell reachable from outsideElevation of PrivilegeAn SSH flow comes from outside a trust boundary.
Sensitive data stored without encryption at restInformation Disclosurethe element holds confidential or restricted data and is marked as not encrypted at rest.
Data store without encryption at restInformation Disclosurethe element is marked as not encrypted at rest.
Data store exposed to the internetInformation Disclosurethe element is marked internet-facing.
Sensitive data store reached by an unauthenticated flowInformation Disclosurethe element holds confidential or restricted data, and a flow to or from it is marked as needing no authentication.
Sensitive data store reached over an unencrypted flowInformation Disclosurethe element holds confidential or restricted data, and a flow to or from it is marked as not encrypted.
Internet-facing component without authenticationSpoofingthe element is internet-facing and marked as not requiring authentication.
Unauthenticated internet-facing endpoint can be floodedDenial of Servicethe element accepts unauthenticated requests from the internet, so nothing ties a request to a caller to rate-limit.
Privileged function reachable from the internetElevation of Privilegethe element is marked privileged (admin) and is internet-facing.
Privileged component without authenticationElevation of Privilegethe element is marked privileged but doesn't require authentication, so whoever can reach it gets its privileges.
Privileged actions without accountabilityRepudiationthe element is privileged and reached by an unauthenticated flow, so its actions can't be tied to a person.

If your plan leaves Enterprise, the values you recorded are kept, but they can't be changed and rules stop being offered.

Suggested scores Enterprise

Threats drafted with Generate attack trees come with a suggested likelihood and impact. It saves typing and keeps scoring consistent across analysts, but it is only a suggestion. It doesn't count as a score, so the threat stays out of the risk register, tickets and alerts, until someone accepts it.

How the suggestion is worked out:

  1. Baseline: every threat in ThreatTree's dictionary has its own starting likelihood and impact, set by hand for that threat: how often it's seen in real attacks and how much damage it does. For example, credential stuffing against a login page starts far more likely than a SAML signature-wrapping attack, and a threat that disables a safety system starts with the highest impact. Threats in your organization's own threat library and threats raised by rules start from a default for their STRIDE category.
  2. Your matrix: the baseline is placed on your organization's own risk matrix, whatever its number of levels.
  3. Your diagram: likelihood goes up one level if the element is exposed (it talks to an External Entity or a flow crosses a Trust Boundary), and one more if a flow on it is marked unencrypted or unauthenticated (security attributes). Impact goes up one level if the element or its flows carry confidential or restricted data. If an asset on the element is rated higher, impact is raised to that rating.

In the Attack Tree editor, a suggested threat shows its Suggested score with the reasons. Accept with this score accepts the threat and sets that score; Accept, score later accepts it unscored. An accepted threat without a score shows Suggested score … Use it above its likelihood and impact, and a risk's page offers the same. Confirming a suggestion is recorded in the forest's activity log with who did it.

Risk portfolio Enterprise

The risk portfolio lists every risk from every threat model you can open, in one place, highest first. Open it with Risk portfolio on the My Forests page. It has four tabs: Overview, Trends, All risks and, for organizations with linked organizations, By organization.

  • Overview: open critical and high risks, high or critical risks without a ticket, open risks with no owner, risks to re-review after a diagram change, overdue mitigations, and threat models due for review or not approved. Click a figure to open All risks filtered on it.
  • The Overview also lists the top 10 open risks and overdue mitigations by owner.
  • All risks: every risk, filtered by threat model, severity, status, owner, treatment or standard control, with a search. Click a risk to open it.
  • Export CSV or Export PDF exports what the filters show, from the threat models you're allowed to export. Exports are recorded in the activity log.

You only see threat models you can already open. Severity is each threat model's own risk matrix band, so a risk keeps the same severity as in its own register. Encrypted threat models aren't included.

Linked organizations. Owners and admins of an organization with linked organizations also get a By organization tab. It shows counts for each linked organization (risks by severity, missing tickets and owners, overdue mitigations), never the risks themselves.

ThreatTree records the portfolio's figures every day, so you can see whether risk is going down. The Trends tab of the risk portfolio shows four charts over 30 days, 90 days or 1 year:

  • Open critical and high risks, stacked by severity.
  • Mitigations completed and overdue: tracked mitigations that are implemented or verified, and open ones past their due date.
  • Threat coverage: the share of diagram elements with at least one threat (see Coverage and change impact).
  • Risks to re-review after a diagram change.

Point at a chart, or tab to it and use the arrow keys, to see the figures for a day. Show as table lists them, and Download CSV exports every recorded day with all the figures. The one-year view shows one reading per week. Export PDF includes the last 90 days, with the change since the first reading.

On a forest's page, each posture tile shows a small line for the last 90 days.

  • When figures are recorded: the current day's figure is updated about every hour, so each day keeps its last reading. Nothing was recorded before this feature arrived, so the section says when trends start.
  • Which threat models: each day is counted over the threat models you can open today, the same ones as the portfolio. A deleted threat model, or one you lose access to, drops out of every day. Encrypted threat models aren't recorded.
  • Linked organizations: owners and admins of a parent organization see each linked organization's open critical and high risks over time on the By organization tab, from counts only.
  • Only counts are stored, never risk names or owners. History is kept for two years. If your plan leaves Enterprise, recording stops and the history stays; it's shown again if you come back to Enterprise.

Saved portfolio views Enterprise

Keep the figures, lists and charts you check most as a named view of the risk portfolio, for example "Mobile money: open critical without an owner", and share it with your organization. Open the Saved views tab of the risk portfolio.

  1. Click New view, give it a name, and choose 1 to 4 columns.
  2. Set its filters (threat model, severity, status, owner, treatment, standard control, framework). They apply to every risk in the view.
  3. Add widgets: a figure (any of the portfolio's numbers), the top open risks, a risk list, risks counted by threat model, owner, severity, treatment, standard or framework, overdue mitigations by owner, a trend chart, or the linked-organizations table. Drag them to reorder, or use ↑ ↓. Each can have its own title.
  4. Save view. Organization owners and admins can tick Share with the organization; everyone else keeps their views to themselves.
  • Everyone sees their own numbers: a shared view counts only the threat models the person looking can open, so it never shows them more than they could already see.
  • Default view: owners and admins can make a shared view the organization default. The risk portfolio then opens on it.
  • Export PDF prints the view as shown, on the same grid; Export CSV has its lists and counts. Exports only cover threat models you're allowed to export, and are recorded in the activity log.
  • On a figure, See these risks opens All risks with the view's filters. Duplicate starts a new view from an existing one.
  • If your plan leaves Enterprise, saved views are kept but not shown; they come back with Enterprise.

Coverage and change impact Enterprise

A threat model goes stale when the architecture changes and nobody revisits the threats. ThreatTree watches the diagram for you.

Which threats belong to which element. Threats drafted with Generate attack trees already know their element, and so do leaves you add under an element's branch. For any other threat, select it in the Attack Tree editor and tick the elements under Threatens.

When the diagram changes. When you change something that matters for security, the threats on that element are marked Re-review, with the reason. Examples:

  • an element's type, data classification or security attributes
  • moving it into or out of a trust boundary
  • adding or removing a flow, or changing a flow's attributes
  • deleting the element

Renaming an element, or moving it within the same zone, doesn't count. The reason reads like Orders DB: moved out of VPC; flow from API: encrypted unknown → no.

The reasons appear on the risk's page and in the Attack Tree editor. Click Mark as reviewed once you've checked the threat still applies and its score is right; that is recorded in the activity log. In the Risk Register, the Status filter has Needs re-review. Forests with threats to re-review show a badge on the dashboard.

Coverage. The forest page shows the share of diagram elements that have at least one threat (trust boundaries don't count), and how many threats are waiting for a re-review. In the DFD editor, click Coverage to outline in red the elements nothing threatens yet, exposed ones included. The forest PDF report lists them per diagram.

ℹ️ Good to know

Tracking starts from the diagram as it is the first time it's saved or its coverage is opened after this feature arrives, so earlier changes aren't flagged. Encrypted forests aren't tracked. If your plan leaves Enterprise, no new threats are flagged, and the ones already flagged can still be marked as reviewed.

Your organization's threat frameworks Enterprise

Next to STRIDE, LINDDUN, OWASP, CAPEC and the other built-in frameworks, your organization can define its own: a group methodology, internal fraud categories, a sector taxonomy. They're offered wherever you tag a threat.

  1. Create them in Settings → Threat frameworks: a name, a colour and a list of categories, each with an optional description. Or import a CSV with the columns framework, category, description, one row per category. Owners and Admins can change them, as can a custom role with Manage frameworks. Everyone else in the organization can see them.
  2. Tag threats in the Attack Tree editor (Threat Framework, under Your organization) or on a risk's page.
  3. Filter the Risk Register and the risk portfolio by framework. The tags also appear in the PDF report and the exports.
  • Renaming a framework or a category updates every threat already tagged with it.
  • Archiving a category or a whole framework keeps it on the threats that have it, but stops offering it. A framework or category that's used can't be deleted, only archived.
  • Whose frameworks: a forest uses the frameworks of the organization that owns it, the same rule as the threat library. Someone invited from another company sees and uses your frameworks there, not their own.
  • Your frameworks are offered in the threat library form too, and library threats tagged with them keep the link, so renames reach them.
  • If your plan leaves Enterprise, existing tags stay and stay filterable, but frameworks can't be changed or added to threats.

Your organization's threat library Enterprise

The threat dictionary is generic. Your own threats can sit next to it: the ones your security team writes up again and again, or the ones specific to your industry or platform. Add them once in Settings → Threat library, and Generate attack trees and Suggested Threats in the Attack Tree editor offer them, marked Your library and listed first, in every forest your organization owns.

  1. Go to Settings → Threat library and click Add threat.
  2. Pick the Element type it applies to (the DFD element it threatens, for example Process or API Gateway), and give it a Title and Description.
  3. Set its STRIDE category. The generator uses it to file the threat under an attacker goal and tags generated leaves with it.
  4. Optionally add MITRE ATT&CK techniques (for example T1557; T1078.004), framework tags (pick a framework, including your organization's own, then a category) and standard controls (pick a standard, then search its controls). Only names from the lists can be added, the same ones the Attack Tree editor offers. Leaves made from the threat arrive with them filled in, ready to review.

Import and export. Export CSV downloads the library, and Import CSV adds a file with the same columns: element_type, title, description, stride_category, mitre_techniques, frameworks, std_controls. Inside a cell, separate several values with ; and write pairs as name | value, for example CAPEC | CAPEC-94: Adversary in the Middle. Framework and standard names must match the lists exactly (or one of your organization's frameworks); rows with other names are listed as errors. A row with the same element type and title as an existing threat updates it. If any row is invalid, nothing is imported and the rows to fix are listed. A library holds up to 2,000 threats, and one import up to 500.

Who sees it. Only your organization's forests offer its threats. That includes people invited to one of those forests from outside your organization, who see your library while they work in it. Your threats are never shown to other organizations, and outside editors never bring their own organization's library into your forests. Every member can read the library in Settings. The owner, admins, and members whose custom role includes Manage the threat library can change it. Adding, editing, deleting and importing threats is recorded in the organization activity log, and the library is included in the organization data export.

Changing or deleting a threat. Untouched suggestions made from a library threat pick up its new wording the next time someone clicks Generate attack trees in that DFD, just like dictionary threats. Deleting a threat from the library leaves the leaves already made from it where they are.

ℹ️ If your plan changes

The threat library needs Enterprise. If your organization leaves Enterprise, its threats are kept and can still be read and exported in Settings, but they can't be changed, and the editors stop offering them. Leaves already made from them stay in your attack trees. Everything comes back when the organization returns to Enterprise.

Asset register Pro+

An asset is what your model protects: customer data, a payment ledger, signing keys, a service that must stay up. Each forest has its own asset register: on the forest page, click Assets next to Risk Register.

  1. Open the forest's Assets page and click + Add asset.
  2. Give it a Name, a Type (Data, Service, Infrastructure or Other), and optionally a Classification (the same values as a data store's data classification) and an Owner.
  3. Rate how much a breach would hurt: Confidentiality, Integrity and Availability, each on the impact scale of your risk matrix (for example 4 · Major).
  4. Tick the DFD elements it sits on: where it's stored, processed or passes through. You can also do this in the DFD editor: select an element and use Assets here in its properties.

Threats against an asset. Click an asset to see the risk register entries raised against the elements it sits on, with their severity, and open any of them. A threat counts for an element when it was generated for that element with Generate attack trees, or when it sits under that element's branch in an attack tree, including leaves you added there by hand. In the Risk Register, the Asset filter shows the same threats.

Reports and exports. The forest PDF report has an Asset Register section with each asset's ratings, elements and threats. Export CSV on the Assets page downloads the register, and the organization data export includes it.

Who can change it. Everyone who can open the forest can see its assets. People who can edit its diagrams can add, change, link and delete them, so a custom role without Edit diagrams is read-only here too. Adding, changing, linking and deleting assets is recorded in the forest's activity log.

ℹ️ Good to know

Asset names and descriptions aren't encrypted, so a forest with assets can't be locked: export and delete them first. Restoring a backup keeps each asset's links to the elements in that backup. If your plan goes back to Free, the assets stay in the forest, its report and exports, but can't be changed until it's on Pro or Enterprise again. On the forest page, people without Pro see the Assets link locked.

Mitigation catalogue Pro+

A control such as MFA on all admin access usually treats several risks. In the mitigation catalogue you track it once, with an owner, a status and a due date, and link it to every risk it treats. On the forest page, click Mitigations next to Risk Register.

  1. Click + Add mitigation. Give it a Title, a Status (Planned, In progress, Implemented, Verified or Won't do), an Owner and a Due date, and optionally a description and standard controls (pick a standard, then search its controls).
  2. Under Risks it treats, tick every risk it applies to. Risk-register entries are listed with their severity.

From a risk's page. Under the Treatment plan, Tracked mitigations lists the catalogue mitigations linked to that risk. Link one with Link a mitigation…, type a title and click Add to create one already linked, or click Track on a treatment to move it into the catalogue. The free-text treatment plan stays as it is for notes.

Following up. The Mitigations page counts mitigations by status and how many are overdue (planned or in progress, past their due date). Click a count to filter by it, or filter by owner. Each mitigation shows how many risks it treats and the highest severity among them. Change a status straight from a mitigation's dialog.

Review the score when the work is done. When every mitigation linked to a risk is Implemented or Verified (Won't do is ignored), the risk's page and the mitigation say so: review that risk's likelihood and impact. ThreatTree never changes the score or marks the risk mitigated by itself.

Reports and exports. The forest PDF report has a Mitigation Plan section, Export CSV on the Mitigations page downloads the catalogue, and the organization data export includes it. Creating, changing, linking and deleting mitigations is recorded in the forest's activity log.

Who can change it. Everyone who can open the forest sees its mitigations. People who can edit its risk register can change them, including members whose custom role allows only Edit risk register.

ℹ️ Good to know

Mitigation titles and descriptions aren't encrypted, so a forest with catalogue mitigations can't be locked: export and delete them first. Restoring a backup keeps each mitigation's links to the risks in that backup. If your plan goes back to Free, the mitigations stay in the forest, its report and exports, but can't be changed until it's on Pro or Enterprise again. On the forest page, people without Pro see the Mitigations link locked.

Import a DFD from code Enterprise

Instead of drawing a DFD by hand, generate one from the configuration that already describes your system. On a forest's page, click Import from code, then upload a file or paste it in. The format is detected automatically:

SourceWhat you get
OpenAPI 3 / Swagger 2 (JSON or YAML)An API consumers external entity on the internet side, and the API as a trust boundary with one process per tag (or per first path segment, if operations aren't tagged). Each data flow lists its HTTP methods and endpoint count, and calls out unauthenticated endpoints and plain-HTTP servers. OAuth 2 / OpenID Connect adds an identity provider.
CloudFormation / SAM (JSON or YAML, including !Ref-style tags)Your AWS resources as AWS elements (EC2, Lambda, RDS, S3, DynamoDB, API Gateway, load balancers, queues, KMS…), placed inside their VPC and subnet trust boundaries. References between resources become data flows, and internet-facing entry points get an Internet users entity.
Terraform (.tf files, or terraform show -json output)The same for AWS, Azure and Google Cloud resources: VPCs/VNets and subnets as nested boundaries, resources inside them, references as data flows. For a configuration built from modules, import terraform show -json output, since modules in .tf files aren't expanded.

Before anything is created you get a preview: a small drawing of the diagram, a list of every element with where it came from, and warnings about anything the import couldn't know (for example, resources that aren't diagram elements, like IAM roles). Untick anything you don't want. Unticking a boundary keeps what's inside it. Then name the diagram and click Create diagram. The result is always a new DFD, laid out and ready to edit; it never changes an existing one.

Checking drift from a pipeline. With the ThreatTree API, a CI/CD job can send the same Terraform, CloudFormation or OpenAPI file and compare it with the forest's existing DFD instead of creating a new one. The answer lists the elements that are in the code but not in the diagram, and the ones in the diagram but no longer in the code, so architecture changes show up before they ship. Elements are matched by type and name. See the API documentation for an example.

ℹ️ Treat it as a strong first draft

Data flows are inferred from references in the file, so traffic that only exists in application code won't appear. An API spec describes the API surface, not the databases behind it. Check the flows, add what's missing, then threat-model as usual. Re-importing after the configuration changes produces a fresh DFD to compare against, which is a quick way to spot drift. Files up to 2 MB and 300 elements are supported; encrypted forests can't be imported into.

Attack Trees

An Attack Tree decomposes one attacker goal into the specific ways it could be achieved, using AND/OR logic — then lets you score, categorize, and plan a response for each concrete threat at the leaves.

The four node types

NodeMeaningHas scoring/framework fields?
GoalThe attacker's top-level objective — e.g. "Exfiltrate customer PII". One per tree; the palette disables the Goal item once one exists on the canvas.Yes
OR GateThe goal (or parent node) is achieved if any one of its children succeeds. Use this for "there are several independent ways in".No — purely structural
AND GateThe parent is only achieved if all of its children succeed together. Use this when an attack needs multiple conditions to line up.No — purely structural
Leaf NodeA concrete, atomic threat or technique — the bottom of the decomposition. This is where the real risk data lives.Yes

ℹ️ Gates are pure logic, not risk items

OR and AND gates only have a Label, a Label Color, and a Description — no likelihood/impact, framework tags, MITRE mapping, treatment plan, or standards controls. Those fields only appear on Goal and Leaf nodes, since a gate doesn't represent a single scoreable threat — it just describes how its children combine.

Likelihood, Impact, and risk score

On a Goal or Leaf node, set Likelihood and Impact. The risk score is simply Likelihood × Impact, and the editor shows a colored severity badge automatically. With the default 5×5 risk matrix both scales run 1–5 (score 1–25) and the bands are:

Score rangeSeverity
1 – 4Low
5 – 9Medium
10 – 15High
16 – 25Critical

For example, a leaf scored Likelihood 4 × Impact 4 = 16 → Critical; Likelihood 2 × Impact 3 = 6 → Medium.

Your own risk matrix Pro & Enterprise

If your organization already has a risk matrix, ThreatTree can use it so your scores line up with the rest of your risk reporting. Go to Settings → Risk matrix. In an organization, the owner, admins, and members with a custom role that includes Manage the risk matrix can change it, and it applies to every forest owned by a member. On a solo Pro or Enterprise account, it applies to your own forests.

  • Size: 3 to 7 likelihood levels and 3 to 7 impact levels, set separately, so 4×5 or 3×5 are fine. Start from a preset (3×3, 4×4, 5×5, an impact-weighted 5×5, or 6×6) or build your own.
  • Levels: give each level a name and a description, for example Rare: less than once in 10 years. The editor shows them in the Likelihood and Impact dropdowns.
  • Bands: 3 to 5 severity bands with your own names and colours. Assign them by score thresholds, or paint the cells one by one for an asymmetric matrix where impact weighs more than likelihood. A cell can never be less severe than one with lower likelihood and impact.
  • Critical band: pick the band that triggers critical-risk alerts and the top ticket priority.

If threats are already scored, saving shows a preview first. You can rescale the existing values to the new scale (for example 5→3 maps 1,2→1, 3→2, 4,5→3, and you can edit the mapping), or keep them and flag the ones outside the new scale as needs re-scoring. The change is recorded in the activity log, and PDF reports show the matrix they were scored against. Encrypted forests can't be rescaled while they're locked. The score is always likelihood × impact: there are no custom formulas or extra axes.

"Include in risk register"

Every scoreable node has an Include in risk register checkbox. Its default depends on the node:

  • A Leaf node with no children (a true terminal point in the tree) defaults to checked — it's assumed to be a concrete, reportable risk.
  • Any other node (a Goal, or a Leaf that has further nodes hanging off it) defaults to unchecked.

You can always override the default in either direction — the checkbox reflects your explicit choice once you've touched it, not just the terminal-leaf heuristic.

Threat frameworks All plans

Tag a Goal or Leaf with one or more categories from six threat-classification frameworks. Pick a framework from the dropdown, then a category within it — each tag shows as a colored chip on the node.

FrameworkUse it forExample categories
STRIDEGeneral-purpose software threat classificationSpoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege
LINDDUNPrivacy-specific threatsLinkability, Identifiability, Detectability, Disclosure of Information…
OWASP Top 10Web application risk (2021 edition)A01 Broken Access Control, A03 Injection, A10 SSRF…
OWASP Top 10 for LLM ApplicationsLLM-specific threats (2025 edition)LLM01 Prompt Injection, LLM04 Data and Model Poisoning…
OWASP Top 10 for Agentic ApplicationsAgentic/multi-agent AI system threatsMemory Poisoning, Tool Misuse, Rogue Agents in Multi-Agent Systems…
OWASP IoT Top 10Connected devices and their ecosystem (2018 edition)I1 Weak, Guessable, or Hardcoded Passwords, I4 Lack of Secure Update Mechanism, I10 Lack of Physical Hardening
CAPECConcrete, technique-level attack patternsCAPEC-66 SQL Injection, CAPEC-62 CSRF, CAPEC-600 Credential Stuffing…

ℹ️ MITRE ATLAS appears automatically for AI frameworks

As soon as a node is tagged with OWASP Top 10 for LLM Applications or OWASP Top 10 for Agentic Applications, a second MITRE ATLAS technique field appears alongside MITRE ATT&CK — ATLAS is MITRE's adversarial-ML/AI-specific technique catalog, the AI-world counterpart to ATT&CK.

MITRE ATT&CK / ATLAS technique mapping

Type one or more technique IDs into the MITRE ATT&CK field (comma-separated, e.g. T1078, T1110.003) or the MITRE ATLAS field (e.g. AML.T0051). Valid-format IDs render as clickable chips that link straight to the official MITRE technique page. This is free-text entry — you look up the technique ID yourself on attack.mitre.org / atlas.mitre.org and paste it in.

Treatment Plan

Record how you're responding to a leaf's risk. Each entry has a type and free-text description:

TypeMeaning
MitigateReduce the likelihood or impact with a control.
AvoidEliminate the risk by removing the feature/component that causes it.
TransferShift the risk elsewhere — insurance, a third-party contract, a managed service.
AcceptConsciously decide to live with the risk as-is.

Standards Controls Pro+

Map a node to specific controls from compliance/security standards — useful for showing an auditor exactly which control addresses which threat. Pick + Add standard, then search within it for the specific control to attach.

StandardExample control
ISO 27001:2022A.8.24 Use of cryptography
NIST SP 800-53 Rev 5AC-6 Least Privilege
NIST CSF 2.0PR.AA-03 Users, services, and hardware authenticated
CIS Controls v8CIS 6.3 Require MFA for Externally-Exposed Applications
OWASP ASVS 4.0V5.3 Output Encoding and Injection Prevention
PCI DSS v4.0Req 8.4 MFA implemented to secure access into the CDE
SOC 2CC6.1 Logical access security software, infrastructure, and architectures
NIS2 Directive (EU) 2022/2555Art. 21(2)(d) Supply chain security, including relationships with direct suppliers and service providers
DORA (EU) 2022/2554Art. 9 Protection and prevention
IEC 62443SR 1.13 Access via untrusted networks (every IEC 62443-3-3 system requirement is listed)
NERC CIPCIP-005 Electronic Security Perimeter(s)
ISO/SAE 21434:202115.6 Attack path analysis
UN R155Annex 5 4.3.3 Threats to vehicles regarding their update procedures
FDA Premarket Cybersecurity GuidanceAppendix 1: Code, Data, and Execution Integrity
HIPAA Security Rule164.312(e)(1) Transmission Security
NIST AI RMF 1.0MANAGE 1 AI risks from MAP and MEASURE are prioritized, responded to and managed
ETSI EN 303 6455.1 No universal default passwords (all 13 consumer IoT provisions and the clause 6 data protection provisions)
NIST IR 8259ASoftware Update (the six IoT device core baseline capabilities)

Turning on an Industry Module pins its standards to the top of the picker: PCI DSS and DORA (Fintech), HIPAA (Healthcare), SOC 2 and DORA (SaaS), ISO/SAE 21434 and UN R155 (Automotive), the FDA premarket cybersecurity guidance (Medical Devices), IEC 62443 and NERC CIP (Critical Infrastructure), and NIST AI RMF (AI & ML).

Control names corrected in October 2026

Some control names were checked against the standards' own text and corrected. ISO/SAE 21434 now uses the standard's sub-clause numbers (the TARA methods are clause 15, the concept phase clause 9, updates 13.4). In SOC 2, several criteria had labels that described something else: CC6.4 is physical access, CC6.5 disposal of physical assets, A1.1 processing capacity and A1.2 environmental protections, backup and recovery infrastructure. Risks you had already mapped were moved to the corrected names automatically; a risk mapped to the old "CC6.4 Access removed when no longer needed" now shows CC6.2, and the old "CC6.5 Logical access credentials" shows CC6.1. Snapshots taken before the change keep the old names, and so do encrypted forests, which the server can't read.

Canvas tools

  • Auto Layout — automatically re-arranges the whole tree into a clean top-down layout. Handy after freehand-building a tree that's gotten tangled.
  • Fit Labels — resizes nodes to fit their current label text.
  • Undo / Redo — the arrow buttons next to Save (or Ctrl+Z / Ctrl+Y) step back and forward through your changes, including adding, deleting and connecting elements. Each step is saved, so an undone delete really brings the element back.
  • Fit to A4 — re-arranges the tree so it prints as large as possible on one A4 page. Choose A4 landscape for the attack tree PDF export or A4 portrait for the forest report. Long goal and leaf labels wrap onto extra lines to keep wide trees narrow, and a dashed outline shows the page until your next layout change. A message tells you roughly how large the labels will print; if that's very small, consider splitting the tree. Undo (Ctrl+Z) restores the previous arrangement.
  • Draw connection — same mechanism as the DFD editor: select the parent, click Draw connection (or press C), then click the child.

Worked example: "Compromise customer accounts"

A goal with two independent paths in (OR logic), one of which itself needs two things to line up (AND logic):

  1. Drag a Goal node, label it Compromise customer accounts.
  2. Drag an OR Gate underneath it, connect Goal → OR Gate. Label it Account takeover vector (any one path below is sufficient).
  3. Drag a Leaf under the OR Gate: Credential stuffing using leaked passwords. Set Likelihood 4, Impact 4 (→ 16, Critical). Tag STRIDE → Spoofing. MITRE ATT&CK: T1110.004. Treatment: Mitigate — "Rate-limit login attempts; enforce breached-password check on signup."
  4. Drag a second Leaf under the OR Gate: Phishing email harvests login credentials. Likelihood 3, Impact 4 (→ 12, High). STRIDE → Spoofing. MITRE ATT&CK: T1566.001. Treatment: Mitigate — "Enforce MFA so a stolen password alone isn't sufficient."
  5. Drag an AND Gate as a third child of the OR Gate, label it Session hijacking via XSS (this path needs both children below to be true).
  6. Under the AND Gate, add Leaf Stored XSS in user-generated content (Likelihood 2, Impact 5 → 10, High; OWASP Top 10 → A03 Injection; CAPEC-86) and Leaf Session token readable by JavaScript (no httpOnly flag) (Likelihood 5, Impact 3 → 15, High; OWASP ASVS → V3.4 Cookie-based Session Management).
Compromise accounts OR Account takeover Credential stuffing 16 · Critical Phishing email 12 · High AND Session hijack via XSS Stored XSS in UGC 10 · High No httpOnly flag 15 · High

The finished tree — an OR gate covering three independent attack paths, one of which (session hijacking) itself requires two conditions via an AND gate.

Linking DFDs & Attack Trees

Linking ties an Attack Tree back to the architecture diagram it's threatening — so your threat model stays traceable to what it's actually describing, not a set of orphaned trees.

How to link

Linking is one-directional in setup but shows on both sides. There are two ways to create the link:

  1. From the Attack Tree editor — if the tree isn't linked yet, a Link to DFD ▾ button appears in the toolbar. Click it and pick a DFD tree from the same forest.
  2. At creation time — when you create a new tree via Add Tree and choose Attack Tree as the type, an optional Link to DFD dropdown appears right in that modal.

Where the link shows up

  • In the DFD editor, an Attack Trees badge in the toolbar shows a count of every attack tree linked to that DFD, with a dropdown to jump straight to any of them.
  • An attack tree can be linked to at most one DFD at a time; unlink it the same way you'd change the link, or leave it unlinked if it's exploratory and not tied to a specific architecture yet.

ℹ️ Linking is optional

You can build and score attack trees with no DFD at all — useful for a quick "what-if" exercise, or when you're modeling a threat conceptually before the architecture is finalized. Link it later once you have a DFD to attach it to.

Risk Register

The Risk Register is a forest-wide, auto-populated table of every scoreable finding across every attack tree in the forest. There's no separate data entry: click a risk to open and change it, and the change saves to the node in its attack tree.

How it's populated

Every Goal/Leaf node across every Attack Tree in the forest with Include in risk register checked (see Attack Trees for the default logic — terminal leaves default to included) shows up here automatically as soon as you save the node. There's nothing to separately "add" to the register, and no way to: a new risk starts as a node in an attack tree.

Editing a risk

You can update a risk from either place: from the register through its own page, or by selecting its node in the Attack Tree editor. Both change the same node.

Click a risk to open its own page. Viewers see it read-only. If you can edit the forest, every change saves automatically, and the bar at the top of the page shows the risk's severity and whether the last change saved:

  • Name: click the title and type. Press Enter to save, or Esc to cancel.
  • Risk score: click a square on the risk matrix to set likelihood and impact together, or use the two dropdowns beneath it. Clear removes the score.
  • Owner and collaborator: type a name, pick a forest member, or use Assign to me. Status is a switch between Not mitigated and Mitigated.
  • Undo and redo: the arrows at the top of the page step back and forward through your changes to this risk. Ctrl+Z and Ctrl+Y do the same, except inside a text box, where they apply to what you're typing. The steps last until you leave or reload the page.
  • Treatment plan: pick a type, describe the treatment and press Enter. Existing treatments can be edited where they are. Removing one offers Undo for a few seconds.
  • MITRE ATT&CK: type a technique ID such as T1078 and press Enter. It becomes a chip that links to MITRE. ATLAS works the same way, and appears once a risk has an LLM or agentic framework.
  • Threat frameworks: pick a framework, then a category to add it.
  • Compliance standards: add a standard, then search its controls and press Enter or click one to add it.

Still to do under the title lists what a risk is missing, and each item takes you to that field. If you opened the risk from the register, the arrows next to Open in attack tree move through the register's list in its current order and filters.

Each change saves straight away to the node in its attack tree, so it's the same data you see in the Attack Tree editor and in PDF exports. Scored nodes show their severity on the tree itself. A tree open in another tab of the same browser updates straight away; on another device or for another person, it updates within about 20 seconds. If that tab has unsaved changes to the same node, they're saved over the risk page's change.

Changing a risk's name or description needs permission to edit diagrams, so a custom role limited to the risk register can change everything else but not those two. A risk's Type comes from its place in the tree and is changed there, since each tree has one goal. Open in attack tree opens the tree with that node selected.

Columns

ColumnMeaning
RiskThe calculated score and severity badge (Low/Medium/High/Critical).
NodeThe node's label — the threat itself.
TypeGoal or Leaf.
L / ILikelihood and Impact, on your risk matrix's scales (1–5 each by default).
Attack TreeWhich tree the node belongs to. The link opens that tree with the node selected.
MITREAny MITRE ATT&CK / ATLAS technique chips and threat framework tags attached to the node.
MitigationsCount of Treatment Plan entries and standards controls recorded on the node.
StatusWith no linked tickets, set it to Mitigated or Not mitigated on the risk's page or in the tree editor. With ticketing sync Enterprise tickets linked, the status follows them and can't be set by hand: links to the node's tickets, In progress while any is open, and Mitigated once every linked ticket is closed.
Owner / CollaboratorFree-text assignment fields, set on the risk's page (with autocomplete against forest members) — who's responsible for this risk and who else is working it. You can also set them in the tree editor's properties panel.

Filtering

Four filters at the top of the register, combinable: Filter by tree (narrow to one Attack Tree), Min risk (hide anything below a score threshold), Owner (narrow to a specific assignee), and Status (Mitigated / Not mitigated).

Example

Continuing the worked example from Attack Trees: as soon as those four leaves are saved, the register shows all four rows — Credential stuffing (16, Critical), Phishing email (12, High), Stored XSS in UGC (10, High), and No httpOnly flag (15, High) — each linked back to the "Compromise customer accounts" tree. Set Min risk to 13 and only the Critical entry remains; assign an Owner to each so it's clear who's tracking the fix.

Exporting & Reporting

Exports come in several kinds, each for a different purpose: raw diagram data, images, a machine-readable threat-intel format, and PDF reports for stakeholders.

Risk Register PDF All plans

From the Risk Register page, Export PDF generates a structured, landscape A4 report of the register as it's currently filtered — cover page with severity-count summary, then the full table (threat, attack tree, type, likelihood/impact, risk score & severity, MITRE technique, mitigation count, owner, collaborator). Unlike the forest-level report below, this one is available on every plan, including Free.

From inside an editor (per-diagram)

Open the Export menu in either the DFD or Attack Tree editor (STIX is in the Attack Tree editor only):

OptionWhat you getPlan
Download JSONThe raw diagram data (nodes, edges, properties) as JSON — for backup, scripting, or moving data outside ThreatTree.All plans
Download STIX 2.1The diagram re-expressed as a STIX 2.1 bundle (attack-pattern / relationship objects, with MITRE ATT&CK external_references and risk score as custom x_threattree_* properties) — for feeding into a SIEM, TIP, or other STIX-consuming tool.Pro+
Download PDFA single-diagram PDF of just that tree.All plans
Download PNG / JPGAn image of the diagram, rendered the same way as the PDF, for slides and documents.All plans

Forest-level PDF report

From a forest, open Export ▾ → Forest Report (PDF) (available on Pro and Enterprise, and to free viewers of a forest whose owner is on Pro or Enterprise) to build a full executive-ready PDF covering the whole forest, not just one diagram. Before generating, you set a Report title, a Classification (Confidential / Internal / Public), a Version string, and optional Version notes — all of which land in the report's Document Control section. The generated PDF includes:

  • Cover page & document metadata
  • Executive summary & risk posture
  • Ranked risk register
  • Threat analysis, per Attack Tree
  • Architecture overview, per DFD
  • Controls & standards mapping
  • Contributors & activity log
  • Appendix & forest metadata

If you've set an organization logo in Settings → Branding, it appears on the report cover — otherwise the report page shows a reminder link to add one.

All exports are server-side enforced

Every export option is gated on the server, not just hidden in the UI for lower plans — calling the export endpoint directly without the right plan returns an error rather than a file, so there's no way to bypass the STIX/PDF plan requirements from outside the app either.

The same Export ▾ menu has Export STIX 2.1 (all attack trees), one STIX bundle covering every attack tree in the forest (Pro and Enterprise).

Live embeds in Confluence and Notion Enterprise

Instead of exporting a PNG and pasting it into your documentation every time a diagram changes, you can embed the diagram itself. An embed is a read-only link that always shows the diagram as it is right now: edit it in ThreatTree and the next time someone opens the Confluence or Notion page, they see the new version.

  1. In the forest, click the </> (Embed) icon next to a DFD or Attack Tree, then Create embed link and Copy. Forest owners and editors can do this.
  2. Notion: on the page, type /embed, paste the link and choose Embed link. Drag the block's corner to resize it.
  3. Confluence Cloud: type /iframe to insert the iFrame macro, paste the link as the URL and set a height (600–800 px works for most diagrams). Confluence Data Center: use the HTML macro (your Confluence admin has to enable it) with <iframe src="LINK" width="100%" height="700"></iframe>.

The embed shows the diagram, its name and when it was last changed. Viewers don't need a ThreatTree account and can't edit anything or see the rest of the forest.

ℹ️ Good to know

Anyone who has the link can see that diagram, so share it only in pages with the right audience. The Embed window lists each link with how often it has been viewed, and Revoke stops a link immediately (pages using it show "Diagram unavailable"). A link also stops working by itself if the forest is encrypted, if the person who created it loses edit access to the forest, or if the plan is no longer Enterprise. Deleting a diagram deletes its links. Encrypted forests can't be embedded, because ThreatTree can't read them.

Backup & Restore Pro+

Point-in-time snapshots of a whole forest — every tree, node, edge, and DFD link — that the forest owner can create on demand and roll back to later.

Creating a snapshot

From a forest, the owner-only Backup & Restore button opens the Backup & Recovery panel. Give the snapshot an optional label and click Create snapshot. Manual snapshots are capped at 5 per hour per forest to stop runaway backup creation, and the oldest snapshots are pruned automatically once a forest passes 20 total (manual and automatic combined).

ℹ️ Fintech Industry Module: release version tagging

If your organization has the Fintech Industry Module enabled (see Billing & Seats), snapshots can also carry a release version string, so a snapshot can be tied back to a specific release for compliance traceability.

Restoring

Click Restore next to any snapshot in the list. Because this replaces everything currently in the forest, you're asked to re-enter your password to confirm before anything happens. ThreatTree also takes an automatic safety snapshot of the forest's current state immediately before restoring — so a restore is never a one-way trip, even from a snapshot you didn't mean to pick.

Restore is owner-only, and replaces everything

Only the forest owner can restore — Editors and Viewers won't see the button. Restoring doesn't merge or selectively apply the snapshot; it replaces all current trees, nodes, and edges in the forest with the snapshot's contents wholesale.

Encryption All plans

Forest encryption is client-side: your browser holds the key and does the encrypting, and ThreatTree's server never sees the key unless you choose to email yourself a copy (see below). While you work, a forest is stored in plaintext. Locking it replaces every readable copy ThreatTree holds with ciphertext.

What "lock a forest" actually does

From a forest's Forest Settings, click Lock & encrypt forest. Your browser then, entirely locally:

  1. Generates a fresh AES-256-GCM key using the Web Crypto API (crypto.subtle) — never sent anywhere.
  2. Encrypts every diagram name, node label, node property blob, and edge label, tree by tree.
  3. Uploads only the resulting ciphertext to the server — replacing the plaintext there.
  4. Encrypts the forest's Backup & Recovery snapshots with the same key, so no readable backup is left behind. They're decrypted again when the forest is unlocked, and can then be restored as usual.
  5. Removes the diagram, node and connection names from the forest's earlier activity log entries. The entries themselves stay (who did what, and when). This can't be undone by unlocking.
  6. Downloads the key as a .json file to your device. If you ticked Also email me a copy of the key, it's also emailed to your account's address — convenient as a second copy, but that copy passes through ThreatTree's server and your email provider, and anyone who can read that mailbox can decrypt the forest. Leave it unticked for true zero-knowledge encryption.
  7. Marks the forest encrypted — every member now sees a lock screen instead of the forest's contents, until someone unlocks it.

Telling locked forests apart

While a forest is locked its name is encrypted too, so ThreatTree identifies it by its number and a key ID (for example 7F3A-91C2). The key ID is also in the key file's name (threattree-key-<forest-name>-<number>-key-7F3A-91C2-<date>.json) and in the key email, so you can match each key to its forest. When you paste or upload a key on the lock screen, it tells you straight away whether the key matches. You can also give the forest a label shown while locked when you lock it. That label is not encrypted, so use a code name if the real name is sensitive. The key ID is derived from the key but reveals nothing useful about it. The label and key ID are cleared when the forest is unlocked.

What encryption does and doesn't cover

Encrypted: the forest's name and description, every diagram name, node label, node property (likelihood, impact, mitigations, notes and so on) and edge label. Not encrypted, because the diagrams need them to render: the number and types of nodes, their positions, which nodes are connected, and timestamps. Someone with access to the database could see a diagram's shape, but not what any of it says.

Each encrypted value is protected with its own random nonce and authenticated (AES-GCM), so it can't be read or altered without the key. It's also bound to where it belongs, meaning this forest and the field it fills, and each diagram's content is bound to that diagram's name. If someone with database access moved an encrypted value somewhere else, unlocking would refuse it instead of showing the wrong content. Forests locked before November 2026 don't have this binding until they're unlocked and locked again. Treat the key file like a password, and keep the forest's regular access controls tight as well.

Forests with assets or tracked mitigations. The asset register and the mitigation catalogue aren't encrypted, so a forest that has either can't be locked. Export them (Assets or Mitigations page → Export CSV) and delete them first.

Copies locking can't reach

Locking can't recall copies that already left ThreatTree. That means tickets already created in Jira, ServiceNow, Linear or Azure DevOps, events already pushed to your SIEM, and Slack, Teams or email alerts already sent. Before you lock, the confirmation lists the tickets created from the forest, and says whether your organization has pushed to a SIEM, so you can clean those up. While a forest is locked, nothing more about its content is sent anywhere. ThreatTree's own database backups age out within 30 days.

Unlocking

The forest owner unlocks it with the key — either upload the .json key file or paste the base64 key string directly. Unlocking is a one-time action: your browser decrypts the data, uploads the plaintext, and turns encryption off for the whole forest — it's not a personal, per-session unlock. Once unlocked, the forest behaves normally again until someone re-locks it (which generates a brand new key).

If the key is lost, the data is gone — permanently

There is no server-side recovery path, by design — that's what makes it real zero-knowledge encryption. An encrypted forest also cannot be deleted until it's decrypted first, so a lost key leaves the forest permanently locked and stuck. Keep the downloaded key file (and the email copy, if you chose one) somewhere durable before you rely on this.

Want an email copy after all? On the lock screen, load or paste the key, then use Email this key to me — the same trade-off applies: the key passes through ThreatTree's server and your email provider. This only works if you already have a valid copy of the key; it can't regenerate a lost one.

Collaboration & Organizations

There are two independent ways to share access: inviting individuals to one specific forest, or creating a company Organization that gives everyone on your domain access to every forest owned by the org.

Inviting members to a forest Pro / Enterprise

  1. Inside a forest, click + Invite member next to Members (forest owners only).
  2. Enter their Email address and pick a Role.
  3. Click Send invite. They receive an email with a link to accept, and can create a free account from it if they don't have one. They appear in the Members list once they accept.
RoleCan do
OwnerFull control — implicitly held by whoever created the forest. Only an Owner can invite/remove members, change roles, delete the forest, or lock/unlock encryption.
EditorCan view and edit diagrams — create/edit/delete trees, nodes, and edges — but can't manage membership or delete the forest.
ViewerRead-only access to everything in the forest.

Someone outside your organization uses a paid seat as an Editor and is free as a Viewer, up to 3 viewers per paid seat — see Free viewers. An invite that doesn't fit is refused with the reason, and one sent earlier can't be accepted until there's room.

Free viewers Pro / Enterprise

People who only read a threat model don't need a paid seat. Each paid seat includes 3 free viewers. They can open forests read-only and download reports, but can't change anything. Anyone who can edit uses a paid seat.

  • In your organization: in Settings → Team, invite someone on your domain with the Viewer role, or change an existing member's Role to Viewer in the Members list to free up their seat. Viewers can read every forest in the organization. Changing a Viewer's role to Member gives them edit access and needs a free seat.
  • Outside your organization: click + Invite member in a forest's Members section and invite anyone by email. As a Viewer they're free and count towards your 3 per seat. As an Editor they use a paid seat, however many forests they're on. They get an email with a link to accept, and can create a free account from it.
  • Free viewers don't get paid features for their own work. They can still create their own forests on the Free plan's limits (3 forests, 3 DFDs per forest, 5 attack trees per DFD). Those forests count as part of the organization, so its Members can see and edit them.
  • In the editors a viewer sees a "view-only access" banner, with no palette, Save, Undo or layout tools. Clicking an element still shows its details, read-only.

Organizations Pro / Enterprise

An Organization is a bigger, domain-wide alternative to inviting people one forest at a time. Register your company's email domain once, and every forest owned by any member of the organization automatically grants Editor-level access to every other member — no per-forest invites needed. Organization Viewers get read-only access instead.

To give one org member less than Editor on a particular forest, invite them to that forest directly with the Viewer role. A role set on the forest itself replaces the automatic organization access for that forest, so they can still see it but not change it.

  1. In Settings → Team, Create your organization using your own company email domain (personal email providers like Gmail/Outlook aren't eligible).
  2. Click Invite a teammate at the top of the Team page and enter their email — they must share the same verified domain.
  3. The Members tab lists everyone with their role, access, groups and an SSO label for people who sign in through your identity provider. Invitations nobody has accepted yet are listed there too, marked Invited: each one holds a paid seat (or a free viewer place) until it's accepted, and Cancel invite frees it. Groups and Custom roles are the tabs next to it.
  4. Organizations are seat-limited (set by your plan); the top of the Team page shows paid seats and free viewers used, and blocks new invites that don't fit. Viewers can still be invited when every seat is taken.

ℹ️ Org membership overrides personal plan limits

If your organization is on Pro/Enterprise, every member gets that access level for forests within the org context — regardless of what plan shows on their own individual account. Free viewers are the exception: they only read the organization's forests.

Organization roles

Every member has one of four roles. The owner can delegate day-to-day team management without handing over the whole organization:

RoleCan do
OwnerEverything below, plus can change anyone's role from the Role dropdown next to their name (Admin, Member or Viewer), and is the only role that can act on another Admin (remove them, etc.). One per organization — implicitly whoever created it.
AdminCan invite and remove Members, but can't invite someone directly as an Admin, remove another Admin, or change anyone's role — those stay owner-only, so an org can't grow its admin group without the owner's involvement.
MemberGets the org's automatic forest access; can't manage other members.
ViewerFree: reads every forest in the organization and downloads reports, but can't change anything or manage members. Doesn't use a paid seat. See Free viewers.

Groups

A group is a set of people in your organization, such as a squad, a project team or your auditors. Give a group access to a forest once, and everyone in it gets that access, including people you add to the group later. Owners and Admins manage groups in Settings → Team → Groups.

  1. Click New group and name it. Its Add people list opens straight away: tick the members to add and click Add.
  2. Under Forest access, click Give access to a forest, choose one of the forests you own and a role (Editor or Viewer). A forest's owner can also add a group from that forest's Members panel.
  3. Pick a group in the list on the left to see who is in it and which forests it opens. Change a forest's role there, or take the access away. Only a forest's owner can change its access, so other forests are listed read-only.
  4. In the Members tab, each person's groups are listed next to them. Click a group to open it, or the + button to add the person to a group or take them out.

A group's role on a forest replaces the organization-wide Editor access for its people there, so giving a group Viewer is how you make one forest read-only for a team. Someone in several groups gets the highest of their groups' roles, and a role set on one person in the forest's Members panel comes first. Deleting a group, or removing someone from it, takes that access away and leaves them with their usual organization access.

SSO / SAML Enterprise

Enterprise organizations can configure SAML 2.0 single sign-on so members authenticate through your company's identity provider instead of a ThreatTree password. From Settings → Sign-in and access, the organization owner configures the IdP's Entity ID, SSO URL, and x509 certificate, and is given the SP metadata/ACS URL to hand to the IdP admin. Once enabled, a Sign in with SSO option appears on the login page — signing in there looks up your email's domain, redirects to your company's IdP, and provisions/links your ThreatTree account automatically on first login.

Setting up a new Enterprise organization? Start with Enterprise Setup, which gives the order of the steps and how seats work under your contract.

Your IdP must send the Name ID as an email address

ThreatTree identifies the signed-in user from the SAML Name ID and requires it to be a real email address on your organization's verified domain. If the Name ID isn't (for example an opaque user ID, or a UPN on another domain), ThreatTree uses the assertion's email claim instead, provided that one is on your domain. Every walkthrough below covers the exact setting to check. If this is misconfigured, sign-in fails with "Your identity provider account does not match this organization."

Microsoft Entra ID (Azure AD)

  1. In the Entra admin center: Enterprise applications → New application → Create your own application, then choose "Integrate any other application you don't find in the gallery (Non-gallery)."
  2. Open the new app → Single sign-on → SAML.
  3. Under Basic SAML Configuration, set Identifier (Entity ID) and Reply URL (Assertion Consumer Service URL) to the SP Entity ID and ACS URL shown in ThreatTree's Settings → Sign-in and access → SSO.
  4. Under Attributes & Claims, edit the Unique User Identifier (Name ID) claim: set the format to Email address and the source attribute to user.mail (or user.userprincipalname if that's what carries your users' real email address). If you leave the default UPN Name ID, ThreatTree falls back to Entra's default emailaddress claim (user.mail), so that claim must hold an address on your domain.
  5. Leave the Signing Option on Entra's default, Sign SAML assertion (or Sign SAML response and assertion). ThreatTree requires a signed assertion. MFA, Windows Hello, passkeys and Conditional Access all work: ThreatTree doesn't ask Entra for a specific sign-in method.
  6. From the SAML Certificates section, download the Certificate (Base64) and copy the Login URL and Microsoft Entra Identifier.
  7. Paste those three values into ThreatTree's IdP Entity ID / IdP SSO URL / IdP x509 certificate fields, check Enable SSO for this organization, and save.
  8. Under Users and groups, assign whoever should have access — Entra won't let unassigned users through even with a valid domain match.
  9. Optional: people can also open ThreatTree from their My Apps portal. Entra's IdP-initiated sign-in works without any extra setting.

Okta

  1. In the Okta Admin Console: Applications → Create App Integration → SAML 2.0, and name the app (e.g. "ThreatTree").
  2. Under Configure SAML, set Single sign-on URL to ThreatTree's ACS URL and Audience URI (SP Entity ID) to ThreatTree's SP Entity ID.
  3. Set Name ID format to EmailAddress, and confirm the application username maps to the user's real email.
  4. On the app's Sign On tab, click View Setup Instructions to get the Identity Provider Issuer, Identity Provider Single Sign-On URL, and download the X.509 Certificate.
  5. Paste those into ThreatTree's IdP fields, enable SSO, and save.
  6. On the app's Assignments tab, assign the people or groups who should get access.

Google Workspace

  1. In the Google Admin console: Apps → Web and mobile apps → Add app → Add custom SAML app, and name it (e.g. "ThreatTree").
  2. Google shows its own SSO URL, Entity ID, and Certificate on this screen — copy those into ThreatTree's IdP fields.
  3. On the Service provider details screen, set ACS URL and Entity ID to the values from ThreatTree's Settings → Sign-in and access → SSO.
  4. Set Name ID format to EMAIL and Name ID to Basic Information > Primary email.
  5. Finish setup, then turn the app ON for everyone or scope it to specific organizational units/groups under User access.
  6. Back in ThreatTree, paste Google's values, check Enable SSO for this organization, and save.

ℹ️ Testing before you roll it out

Save your IdP configuration, then open a private/incognito window and sign in at the login page using Sign in with SSO instead with your own work email. A successful first sign-in auto-provisions your ThreatTree account into the organization — no separate invite required. If it fails, double-check the Name ID format first; that's the most common misconfiguration across all three providers above.

What happens when someone signs in with SSO

  • New to ThreatTree: an account is created on the spot as a Member of your organization, already verified, with no ThreatTree password. It uses a paid seat. Their name comes from the display name, or the first and last name, your IdP sends.
  • Already a member of your organization (for example invited earlier, or the owner): they're signed in to that account and keep their role. A Viewer stays a Viewer.
  • Has a personal ThreatTree account on your domain that isn't in the organization: sign-in is refused until the owner or an Admin invites that address from Settings → Team and the person accepts. This stops anyone who controls your IdP from taking over an existing personal account.
  • Belongs to another organization: refused.
  • Who may sign in is decided in your IdP: only people assigned to the ThreatTree app get through, and their email must be on your organization's domain.

Require SSO

By default SSO is an extra way in, and members can still use a password. Turn on Require SSO for this domain in the SSO settings and password sign-in stops for everyone except the owner, who keeps it so a broken IdP setup can never lock the organization out. It can only be turned on once SSO is fully configured and enabled, and SSO can't be turned off while it's required. Accounts created through SSO or SCIM never have a usable password either way.

Troubleshooting SSO sign-in

Message on the ThreatTree sign-in pageWhat to check
"SSO is not configured for this organization."The email typed after Sign in with SSO instead isn't on your organization's domain, or Enable SSO for this organization isn't saved.
"SSO sign-in failed."The IdP Entity ID or certificate in ThreatTree doesn't match the IdP (often after the IdP certificate is renewed: paste the new one), or the assertion isn't signed.
"Your identity provider account does not match this organization."Neither the Name ID nor the email claim is an address on your domain. See the Name ID notes above.
"This organization has reached its seat limit."Every paid seat is in use. Free one up (remove someone, or make a Member a Viewer) or add seats. See Seats under an Enterprise contract.
"An account with this email already exists…"The person has a personal account. Invite the address from Settings → Team; once they accept, SSO works.
"This account already belongs to a different organization."The address is a member of another ThreatTree organization and must leave it first.
"Sign-in from this network isn't allowed…"The person is outside your IP allowlist.
"This organization requires SSO for sign-in." (password form)Require SSO is on: use Sign in with SSO instead.

Errors shown on Microsoft's own sign-in page come from Entra ID: AADSTS50105 means the user isn't assigned to the ThreatTree app, AADSTS50011 means the Reply URL doesn't match ThreatTree's ACS URL, and AADSTS700016 means the Identifier (Entity ID) doesn't match ThreatTree's SP Entity ID.

SCIM provisioning and IdP groups Enterprise

With SCIM, your identity provider (Okta or Microsoft Entra ID) creates ThreatTree accounts for the people you assign, keeps their names up to date, and removes them from the organization when they're unassigned or deactivated. It can also push groups, so that who can see which forests, and who is an organization Admin, follows group membership in your IdP instead of being re-done by hand in ThreatTree.

The organization owner turns it on in Settings → Sign-in and access → SCIM provisioning. Enabling it shows the SCIM base URL and an API token. The token is shown only once, so copy it straight into your IdP. New token issues a replacement and the old one stops working immediately.

Provisioned accounts must use an email address on your organization's domain, and each one takes a seat. People join as Members unless a group mapping (below) makes them Admins.

How pushed groups work

  • Each group your IdP pushes appears under Settings → Team → Groups with a From your IdP label. Its name and members are managed in the IdP, so they can't be edited in ThreatTree.
  • Give the group access to forests the usual way, from Team → Groups or from a forest's Members panel. Anyone the IdP adds to the group gets that role on the forest, in place of the organization-wide default; anyone it removes goes back to the default. A role set directly on one person still takes precedence over their groups.
  • The owner can set Organization role for its members to Admin on a pushed group. Every IdP-provisioned member of that group becomes an organization Admin, and goes back to Member when they leave all Admin-mapped groups. People you invited by hand, and the owner, are never changed by a mapping.
  • If a group with the same name already exists in ThreatTree, your IdP can link to it rather than create a new one (Okta's "link group" option). From then on it's managed by the IdP.
  • Deleting a pushed group in your IdP deletes it in ThreatTree and removes the forest access it gave.

Okta

  1. In your ThreatTree app integration, open General → Edit and set Provisioning to SCIM.
  2. On the Provisioning → Integration tab, set SCIM connector base URL to ThreatTree's SCIM base URL, Unique identifier field for users to userName, tick Push New Users, Push Profile Updates and Push Groups, and choose HTTP Header authentication with the API token. Test and save.
  3. On Provisioning → To App, enable Create Users, Update User Attributes and Deactivate Users.
  4. Assign people on the Assignments tab, then on Push Groups choose the groups to send to ThreatTree.

Microsoft Entra ID

  1. In your ThreatTree enterprise application, open Provisioning and set Provisioning Mode to Automatic.
  2. Under Admin Credentials, set Tenant URL to ThreatTree's SCIM base URL and Secret Token to the API token, then Test Connection and save.
  3. Under Mappings, make sure Provision Microsoft Entra ID Groups is enabled if you want groups pushed.
  4. Assign users and groups to the application under Users and groups, then turn Provisioning Status on. Entra provisions in cycles, so changes can take up to about 40 minutes to reach ThreatTree.

ℹ️ Good to know

Only groups assigned to the application are pushed, and nested groups aren't expanded: add people to the pushed group directly. Changing an IdP-provisioned person's role by hand in ThreatTree lasts only until their group membership next changes in the IdP, while any group is mapped to Admin. If your plan lapses off Enterprise, your IdP can still update and deactivate people, so leavers are still removed, but it can't add anyone new, and a group mapped to Admin stops making new Admins. Members who already belong to the organization keep signing in with SSO; nobody new joins through it.

IP allowlisting Enterprise

Once SSO covers who can sign in, IP allowlisting adds where from: restrict authentication to specific IP addresses or CIDR ranges, on top of password login and SSO alike. From Settings → Sign-in and access, the organization owner lists the allowed IPs/ranges (one per line) and enables the restriction. Sign-in attempts from outside the list are rejected — even with the correct password or a valid SSO assertion.

The list also applies after sign-in, on every request. If a member who is signed in moves to a network outside the list (for example, takes a laptop home without the VPN), their session ends on the next action and they're returned to the sign-in page; unsaved changes in an open editor are lost. Turning the list on does the same, straight away, to anyone already signed in from outside it. It covers every member of your organization, the owner included. It doesn't cover people outside your organization who were invited to a single forest, or calls from your identity provider (SCIM) and your integrations.

Don't lock yourself out

Settings → Sign-in and access shows your own current IP address next to an Add my IP shortcut. If you try to save a list that doesn't cover the IP you're saving from, ThreatTree warns you before saving — since that save would end your own session at once and lock you (and everyone else outside the list) out, with no self-service way back in. The list can only be changed or turned off from a network that's on it. If you do get locked out, contact ThreatTree support — staff access is a separate sign-in system not subject to any organization's allowlist.

If your plan lapses off Enterprise

Single sign-on, Require SSO and the IP allowlist stay in force, so nobody is let in who wasn't before. Their settings stay open to the owner in Settings → Sign-in and access, marked as no longer included in your plan: you can change them (for example, paste your identity provider's new certificate, or add your new office's network) or turn them off, but not turn them on again.

Review and approval Enterprise

When a threat model needs signing off, submit it for review. Named approvers approve it or ask for changes, and the approved version is kept as a baseline.

  1. On the forest page, under the forest's name, the Review panel shows its state: Draft, In review, Approved or Changes requested.
  2. Click Submit for review, tick the approvers or type their email under Add by email, and add a note if you like. You can pick anyone who can open the forest, including free Viewers, but not yourself. Each approver gets an email.
  3. Someone who can't open the forest yet? Type their email: if you can invite people to the forest (its owner or admins), they're invited as a free Viewer and listed as Invited. As soon as they accept, they become the approver and get the review email.
  4. Approvers open the forest and click Approve, or Request changes with a comment saying what needs to change. Whoever submitted it gets an email with the outcome.
  5. When approved, ThreatTree saves a copy of the whole forest in Backup & Restore, labelled Approved by … on …. Approved copies are never removed to make room for newer backups.

Changes after approval. Any change to the forest's diagrams (or its name) puts it back to Draft, and the panel says it changed since its approval. Submit it again to get the changes approved. If the model changes while it's in review, approvers see a warning, and approving approves it as it is at that moment.

Switching it on. Review and approval is off until an owner or admin ticks Use review and approval in Settings → Review and approval. While it's off, it doesn't appear anywhere: no review panel on forest pages, no approval badges on the dashboard and no approval line in reports. It can't be switched off while a review is in progress.

On or off, per forest. Each forest's Review panel has a setting, Review and approval for this forest: Organization default, On or Off. Its owner or admins change it. When it's off, the forest has no review workflow and isn't marked as not approved. It can't be turned off while a review is in progress.

Organization defaults. In Settings → Review and approval, owners and admins choose whether all threat models need approval by default, and whether one approver is enough or every approver must approve. Every forest left on Organization default follows it; Apply the default to every forest puts back the forests that chose otherwise. Models that need approval and aren't approved are marked Not approved on the dashboard, and their risk register says so.

Every step is recorded in the forest's activity log, with who did it and their comment, and the forest PDF report shows the approval on its cover. The person who submitted a review, or the forest owner, can cancel it while it's in progress.

ℹ️ Good to know

Members with a custom role can only be chosen as approvers if their role includes Approve threat models. If your plan leaves Enterprise, no new reviews can be submitted or decided, reviews in progress can be cancelled, and past reviews and approved copies are kept. Review and approval can then be turned off, for a forest or as the default, but not on.

Comments and discussions Enterprise

Discuss a threat model inside ThreatTree instead of in email: comment on a risk, a diagram element, a data flow or the forest as a whole, mention people, and resolve the thread when it's settled.

  • Where: on a risk's page (Discussion), in the Attack Tree and DFD editors (select a node or a connection, then Discussion under its properties; the number is its open threads), and on the forest page (Discussions lists every thread with a link to where it is, and starts threads about the whole forest).
  • Who: anyone who can open the forest, Viewers included, so reviewers can comment without edit rights. A custom role can leave out Comment. Authors edit and delete their own comments; the forest owner can delete any. A deleted comment shows as "Comment deleted" and its text is gone.
  • @mentions: type @ and pick someone who can open the forest. They get a notice under For you on the dashboard and an email. Everyone in a thread is told about replies. Turn the emails off in Settings → Preferences.
  • Resolve a thread when it's settled, and Reopen it if needed. Forest cards on the dashboard show the open discussions, and so does the risk portfolio.
  • Text is plain: line breaks and links are kept. Ctrl+Enter sends.
  • Comments are in the activity log (created, edited, deleted, resolved; never the text), in the organization export, and in Discussions → Export CSV.

ℹ️ Good to know

Comments aren't encrypted, so a forest with comments can't be locked: export them and use Delete all comments first. Comments follow the forest owner's plan: if it leaves Enterprise, existing comments stay readable and can be deleted, but new ones can't be added.

Approval stages and accepted risks Enterprise

Stages. In Settings → Review and approval, choose Several stages in order and name them, for example Architect then CISO (up to five). Each stage has its own rule (one approver is enough, or every approver must approve) and optional default approvers.

  • When a model is submitted, the approvers are chosen per stage, prefilled with the defaults. A person can approve in one stage only.
  • Only the first stage is asked at first. When it approves, the next stage gets an email, and so on. The review panel shows which stage is in progress.
  • Changes requested at any stage send the model back to its editors. The approved version, and the PDF report cover, name the approvers of each stage.

Accepted risks. In the same place, choose whether accepting a Critical risk, or a High or Critical one, needs a sign-off. When a risk at that level gets the treatment Accept, its page shows Accepting this risk needs a sign-off.

  • Owners and Admins sign off, as can anyone with a custom role that can approve threat models, never the person who accepted the risk. A sign-off can run until a Review by date; after it, the risk shows Sign-off expired.
  • A rejection needs a reason. Change the treatment, or remove Accept and add it again to ask once more.
  • If the risk's score rises after the sign-off, a new sign-off is needed. Removing Accept removes the request.
  • The Risk Register filters on Acceptance to sign off, and so does the risk portfolio. Every request and decision is in the activity log.

Custom roles Enterprise

Owner, Admin, Member and Viewer cover most teams. When you need something in between, for example an auditor who can read everything but change nothing, or a compliance lead who maintains the risk register but not the diagrams, the organization owner can define custom roles in Settings → Team → Custom roles and assign one to any Member from the Members list.

In forests, a custom role only ever narrows what a Member can do: the first three permissions below are things a Member has by default and loses unless the role ticks them. The last four are extras a plain Member doesn't have. Viewing the forests they have access to is always allowed; each role then allows any of:

PermissionWhat it allows
Edit diagramsCreate, change and delete DFDs, attack trees, nodes and connections, as a normal Editor can.
Edit risk registerChange the risk fields of existing attack-tree threats (likelihood, impact, mitigations, risk owner and collaborator, compliance and MITRE mappings), in the Attack Tree editor or the Risk Register. Labels, descriptions, layout and DFDs stay read-only.
ExportDownload forest reports, risk register PDFs, and PDF, PNG, JPG and STIX exports.
View the organization activity logOpen the organization-wide activity log from Settings → Data and records, without any other admin rights.
Manage the risk matrixChange the organization's risk matrix (likelihood and impact scales, severity bands, and rescaling existing scores), which otherwise only the Owner and Admins can do.
Manage the threat libraryAdd, edit, import and delete the organization's own threats in its threat library, which otherwise only the Owner and Admins can do.
Approve threat modelsBe chosen as an approver in review and approval. Members without a custom role can always be chosen; a custom role must include this.
Manage frameworksCreate, rename, archive and import the organization's own threat frameworks. Enterprise.
Manage API keys and webhooksCreate, rotate and revoke API keys, and add, change and delete webhooks. Enterprise.
CommentStart, reply to and resolve discussions, including on forests the member can only view. Members without a custom role can always comment; a custom role must include this. Enterprise.

A role with nothing ticked is read-only. Creating, editing, assigning and deleting roles is recorded in the organization activity log.

ℹ️ Good to know

Custom roles apply to Members only: Owners and Admins always have full access, and promoting a Member to Admin removes their custom role. A role never gives more than the Member's access to a particular forest already does, so a Viewer stays a Viewer. It covers forests owned by people in your organization, not forests the Member created themselves or ones shared with them from outside. If the owner's plan drops below Enterprise, existing roles keep restricting their members until the owner deletes them or unassigns them; only creating and assigning roles needs Enterprise.

ThreatTree API Enterprise

A REST API for pipelines, scripts and internal tools: read and build threat models, generate attack trees, manage risks, registers and your threat library, import architecture from Terraform, CloudFormation or OpenAPI, and fail a release from CI/CD when risk is too high. Full reference and CI examples: ThreatTree API documentation.

Through the API you can read forests, their diagrams (every element, data flow and threat), risks in full, the asset register, the mitigation catalogue, discussions, review and approval, risk trends, the portfolio and the activity log; download the PDF report and the STIX export; update risks one at a time or up to 100 at once (scores, owner, status, treatments, tags, controls and techniques); open tickets for risks; export the registers as CSV; create, change and delete diagrams, elements and connections, and generate attack trees from a DFD; manage the organization's threat library and its own frameworks; post and resolve comments; take backups; search; list members; import from code; submit a model for approval; and run the release gate, as JSON or as SARIF for GitHub code scanning. Writes follow the same rules as the app. Approving a model, signing off an accepted risk, deleting a forest and restoring a backup stay with people in the app.

  1. In Settings → API keys, click New API key. Organization owners and admins can do this, as can a custom role with Manage API keys and webhooks.
  2. Give it a name, pick its scopes (what it may do), and optionally an expiry, the forests it may reach and the IP addresses it may be used from.
  3. Copy the key when it's shown: it isn't shown again. Store it as a secret in your CI system.
  • A key belongs to the organization, not to you, and doesn't use a seat. Everything it changes is in the activity log as "API key: <name>".
  • Rotate gives a key a new secret (the old one stops working at once); Revoke stops it for good. The list shows when and from where each key was last used.
  • The organization's IP allowlist applies to keys too. Locked (encrypted) forests are listed with their label only; their content is never read through the API.
  • If the organization leaves Enterprise, API calls are refused until it's back; keys are kept, and you can still revoke them.

Webhooks Enterprise

Webhooks send ThreatTree events to your own systems (a SOAR, a SIEM, a chat bot, an internal portal) as they happen: a risk becomes high or critical, a model is submitted, approved or sent back, threats need re-review after a diagram change, a comment is posted or resolved, a mitigation changes, a DFD is imported, diagrams are created or deleted. They fire whether a person or an API key made the change. For critical-risk alerts in a Slack or Teams channel, use Settings → Integrations → Slack / Teams alerts instead.

  1. In Settings → Webhooks, click Add webhook. Organization owners and admins can do this, as can a custom role with Manage API keys and webhooks.
  2. Enter an HTTPS URL (on a public address) and tick the events it should receive.
  3. Copy the signing secret when it's shown. Your receiver uses it to check the ThreatTree-Signature header of each request; the API documentation shows how.
  4. Click Send test to send a test event and see the answer.
  • A delivery that fails (no 2xx answer within 5 seconds) is retried after 1, 5, 30, 120 and 720 minutes. Deliveries shows the last 30 days: status, attempts, the answer and the body; Send again resends one.
  • Turn off pauses a webhook; New secret replaces the signing secret at once.
  • Locked (encrypted) forests send their events without the forest name or labels.
  • If the organization leaves Enterprise, nothing is sent until it's back; you can still delete webhooks.

Linked organizations Enterprise

For holding companies with several subsidiaries, and MSSPs running threat modeling for client companies: link those organizations to yours to see their headline numbers in one place, without separate logins. Each subsidiary or client keeps its own organization, members and billing.

  1. The owner of your (Enterprise) organization opens Settings → Linked organizations and enters the other organization's domain.
  2. That organization's owner sees the request in their own Settings → Linked organizations → Parent organization, with an explanation of what you'll see, and accepts or declines.
  3. Once accepted, your owner and admins see, for each linked organization: member count, number of forests, DFDs and attack trees, risk counts by severity (Critical, High, Medium, Low), the date of the last activity, and totals across all of them.

That's all you see. Linking never shows the other organization's diagrams, risk details, names of forests or threats, or its member list, and it gives nobody access to any forest. Encrypted forests are counted but left out of the risk counts, since their contents can't be read. Either owner can unlink at any time, and every request, acceptance and unlink is recorded in both organizations' activity logs.

ℹ️ Good to know

Links are one level deep: an organization with linked organizations can't itself be linked to a parent, and an organization can have only one parent. If your plan drops below Enterprise, links stay in place but the numbers stop showing until you renew.

Roadmap requests Enterprise

Enterprise organizations have a direct line into what ThreatTree builds next. Anyone in the organization can submit a request from Settings → Roadmap requests: what you need, and why it matters (the problem, who needs it, any deadline such as an audit or a renewal).

The ThreatTree team reads every request and gives it a status: Under review, Planned, In progress, Shipped, or Not planned, usually with a written response explaining the decision. Everyone in your organization can see your organization's requests, their status and our response, and the person who submitted a request gets an email whenever its status changes. Other organizations never see your requests.

If your plan drops below Enterprise, your past requests and their status stay visible, but new ones can't be submitted.

Data retention Enterprise

By default ThreatTree keeps your organization's records for as long as the account exists, except sign-in history, which is deleted after 1 year on every plan. Enterprise organizations can instead choose how long each kind of record is kept; anything older is permanently deleted in a daily clean-up. The organization owner sets this in Settings → Data and records → Data retention.

RecordWhat it coversOptions
Activity logsThe organization activity log, and the activity log of every forest owned by a member of the organization.Keep forever, 90 days, 1, 3 or 7 years
Sign-in historyMembers' sign-in records, including IP address, browser and country.1 year (the default, and the maximum on every plan), 30 or 90 days
Forest snapshotsBackups and snapshots of members' forests. The limit of 20 per forest still applies on top.Keep forever, 30 or 90 days, 1 year

Before you save, the form shows exactly how many records the next clean-up would delete, and asks you to confirm if there are any. Each clean-up that deletes something is recorded in the organization activity log with the number of records removed. Deleted forests and diagrams don't need a setting: they're removed straight away when you delete them.

ℹ️ Good to know

Deleted records can't be recovered, including from snapshots. The shortest windows are long enough for the features that read this data: weekly digests, GRC evidence and the activity views keep working. With a short sign-in history, a device you haven't used for longer than the window counts as new again, so you may get a "new sign-in" email for it. If the owner's plan lapses off Enterprise, clean-ups stop and nothing more is deleted.

Ticketing sync Enterprise

Enterprise organizations can connect Jira, ServiceNow, Linear, or Azure DevOps so remediation work is tracked where your engineers already work, without a second copy in ThreatTree to keep up to date. Sync works in both directions:

  • ThreatTree → ticket: whenever a node is scored High or Critical risk, a ticket is opened in every connected system. This is the same trigger that sends the email alert and, if configured, the Slack/Teams message. The ticket includes the forest name, the node's label, the risk score, and a link back into ThreatTree. If a risk dips below High and comes back while its ticket is still open, no duplicate ticket is created.
  • Ticket → ThreatTree: when the ticket is closed, the risk is marked Mitigated in the Risk Register. If the ticket is reopened, the risk goes back to open. If a mitigated risk is later scored High or Critical again, a new ticket is opened.

Set it up from Settings → Integrations → Ticketing sync (organization owner only). Click Connect next to a provider, fill in its fields, tick Create tickets and sync their status, and save. Saving tests the connection against the live system first, so a mistyped token or project is caught immediately, not later when a real risk silently fails to open a ticket. Credentials are stored encrypted and never shown again after saving; leave the credential field blank on later saves to keep the stored one.

ProviderWhat you need"Closed" means
Jira CloudSite URL (https://yourcompany.atlassian.net), the account email, an API token from Atlassian account → Security → API tokens, and a project key. Issue type defaults to Task; saving checks that the project has that issue type and lists the ones it does have if not.Any status in Jira's Done category, whatever your workflow calls it.
ServiceNowInstance URL, a dedicated integration user with the itil role (or write access to the table), and its password. Table defaults to incident; any task-based table works.The record is no longer Active. For incidents, Resolved also counts.
LinearA personal API key from Settings → Security & access, and the team key issues go into (e.g. SEC).The issue is in a Completed or Canceled state.
Azure DevOpsOrganization URL (https://dev.azure.com/yourcompany), project name, and a personal access token with Work Items (Read & Write) scope. No other scope is needed. Work item type defaults to Task; saving checks that the project has it.Any state in the work item type's Completed, Resolved or Removed category, whatever your process calls it. (Connected before November 2026? Save the provider again to pick up a custom process's state names; until then Done, Closed, Resolved, Completed and Removed are recognized.)

How status gets back to ThreatTree

ThreatTree checks linked tickets' statuses automatically about every 15 minutes, with no setup on your side. Each round checks up to 100 tickets per connected system, starting with the ones checked least recently, so a very large backlog is covered over a few rounds. Each provider row in Settings also has a Sync now button that checks every ticket straight away and reports how many changed.

For instant updates, you can also point your ticketing system at the status webhook URL shown after you first save a provider:

  • Jira: Settings → System → WebHooks → Create a WebHook. Paste the URL and tick Issue → updated. Optionally, add a JQL filter such as labels = threattree, since every ticket ThreatTree opens carries that label.
  • Linear: Settings → API → Webhooks → New webhook. Paste the URL and select Issues.
  • Azure DevOps: Project settings → Service hooks → + → Web Hooks, trigger Work item updated. Paste the URL.
  • ServiceNow has no built-in outbound webhook. Add a Business Rule on the table (When: after, Update; Advanced ticked; condition Active changes or State changes) with this script:
(function executeRule(current, previous) {
  var r = new sn_ws.RESTMessageV2();
  r.setEndpoint('PASTE_THE_WEBHOOK_URL_HERE');
  r.setHttpMethod('post');
  r.setRequestHeader('Content-Type', 'application/json');
  r.setRequestBody(JSON.stringify({ sys_id: current.getUniqueValue(), number: current.getValue('number') }));
  r.executeAsync();
})(current, previous);

The webhook only tells ThreatTree which ticket changed. ThreatTree then reads that ticket's real status back from your ticketing system with the saved credential, so a forged or replayed webhook call can't mark anything mitigated. Even so, treat the URL like a password: if it leaks, use Regenerate to invalidate it, then paste the new one into your ticketing system.

ℹ️ Good to know

On a risk with linked tickets, the ticket link and the Mitigated status are set by the sync only. They show in the Risk Register's Status column, in the Attack Tree editor's properties panel, and on the PDF risk register, but can't be edited by hand. If more than one system is connected, a risk counts as mitigated only once every linked ticket is closed. Restoring a forest snapshot keeps each node's ticket links. Only plaintext forests are synced; encrypted forests' risk scores are never visible to the server, so they never open tickets. Disconnect deletes the stored credential and unlinks every ticket from its risk (the tickets themselves stay in your ticketing system). If an owner's plan lapses off Enterprise, ticket creation and status sync stop straight away.

SIEM feed Enterprise

Enterprise organizations can push a STIX 2.1 feed of every forest with an attack tree to Splunk, so a security team's SIEM stays continuously up to date instead of relying on someone remembering to re-run the manual "Download STIX 2.1" export. From Settings → Integrations, the organization owner enters a Splunk HTTP Event Collector (HEC) URL and token. Saving tests the connection immediately, and once enabled the feed is pushed automatically about once an hour. A Push now button sends an immediate feed, so you can confirm it's working right away rather than waiting for the next hourly push. The Last pushed time under the form shows when the most recent push happened.

Currently Splunk only — Microsoft Sentinel isn't yet supported, since its ingestion APIs need a full Microsoft Entra ID app registration rather than a simple token. Each push sends one STIX 2.1 bundle per forest as a single event, covering every attack tree in that forest; forests with no attack tree yet are skipped. Create your HEC token from Splunk's Settings → Data Inputs → HTTP Event Collector.

  • HEC URL: for Splunk Cloud it looks like https://http-inputs-yourstack.splunkcloud.com/services/collector/event; for Splunk Enterprise, https://your-host:8088/services/collector/event. If you paste only the host and port, ThreatTree adds the rest.
  • The collector must be reachable from the internet over HTTPS with a certificate from a public authority. A Splunk Enterprise collector still using its default self-signed certificate, or one only reachable inside your network, is refused.
  • Saving checks the token itself, not just that Splunk is up: a wrong or disabled token is rejected with "Splunk rejected the HEC token". The check sends no event.
  • In Splunk the events arrive with source threattree and sourcetype threattree:stix21, in the token's default index. Tokens with indexer acknowledgment turned on work too.
  • Every push sends the current state of each forest again, not only what changed, so searches should take the latest event per forest. A very large forest makes a large event: if a push shows a forest as failed, check your collector's maximum event size.

GRC evidence sync Enterprise

Enterprise organizations can send their threat-model evidence to Vanta or Drata on a schedule, instead of exporting PDFs by hand before every audit. ThreatTree attaches one dated PDF per push to a document in Vanta or a control in Drata. It contains:

  • every forest owned by a member of your organization, with its owner and whether it's client-side encrypted;
  • the risk register of each forest: threat, likelihood, impact, risk score, status (Mitigated when every ticket linked through ticketing sync is closed), mitigations, mapped standards controls (ISO 27001, SOC 2…) and risk owner;
  • the organization's audit-log events since the previous push (the last 30 days for the first one), up to the 1,000 most recent.

Encrypted forests are listed but their contents aren't included: they're encrypted in your browser, so ThreatTree can't read them. The organization owner sets this up in Settings → Integrations → GRC evidence sync. Saving tests the connection straight away. Evidence is then sent weekly or monthly, whichever you pick, and Push now sends a file immediately. If a scheduled push fails, ThreatTree tries again about an hour later, and the error is shown under the form.

Vanta:

  1. In Vanta, open the document (evidence request) the file should go to, for example a custom document called "Threat model and risk assessment", and copy its ID.
  2. In Vanta's Developer Console, create a Manage Vanta application and copy its client ID and client secret. ThreatTree requests the vanta-api.all:read, vanta-api.all:write and vanta-api.documents:upload scopes. Create an application just for ThreatTree: Vanta allows one active access token per application, so sharing one with another tool makes the two sign each other out.
  3. In ThreatTree, choose Vanta, paste the client ID, client secret and document ID, tick Enable and save.

Each push uploads the PDF to that document and submits it, so it's visible to your auditor.

Drata:

  1. In Drata, create an API key under Settings → API Keys with the Controls permissions Get Control and Map External Evidence.
  2. Find the numeric ID of your workspace and of the control the evidence belongs to (for example your risk-assessment control). Use the control's numeric ID, not its code.
  3. In ThreatTree, choose Drata, pick your Drata region (North America, Europe or Asia-Pacific, matching the address you sign in to Drata at), paste the API key, workspace ID and control ID, tick Enable and save.

Each push adds the PDF to the control as external evidence. Its renewal date is set one month ahead for weekly pushes and two months ahead for monthly ones, so it never shows as expired between pushes. An API key only works in its own region, so a key refused with "check the region" usually means the wrong region is selected.

ℹ️ Good to know

The client secret or API key is encrypted at rest and never shown again after saving. Leave the field blank to keep it when you change other settings. Disconnect deletes the stored credential; evidence already sent stays in Vanta or Drata. OneTrust isn't supported. If the owner's plan lapses off Enterprise, pushes stop straight away.

Audit logs Pro+

Pro and Enterprise forests keep an audit trail of member activity — invites, role changes, tree/node/edge creation and deletion, encryption lock/unlock, and more — viewable per forest, filterable by category.

Enterprise Setup

Enterprise is set up together with ThreatTree support rather than by card checkout. The steps below build on each other, so follow them in order. Your people only come in at the last step.

Setting up your organization

  1. Choose the organization owner. Pick a named person with an email address on your company domain, not a shared mailbox such as hello@ or it@. The owner is the only one who can configure SSO, SCIM, IP allowlisting and data retention, change members' roles and transfer ownership. They also keep password sign-in when SSO is required, which makes this account your way back in if your identity provider breaks. Have them turn on two-factor authentication.
  2. The owner creates a ThreatTree account at Get started with that email address, and verifies it from the email they receive.
  3. Send ThreatTree support the owner's email address. We switch that account to Enterprise. If the owner already pays for Pro by card, we cancel that subscription first, so a card renewal or cancellation can't overwrite your contract later.
  4. The owner creates the organization in Settings → Team, using your company email domain (for example acme.com). It must be the domain of the owner's own email address. Then let support know.
  5. We set your seats to the number in your contract. The Team tab shows them, for example "1 of 25 seats used".
  6. Connect your identity provider. The owner sets up SSO / SAML in Settings → Sign-in and access, with step-by-step guides for Microsoft Entra ID, Okta and Google Workspace. Test it with your own work email in a private window before going further.
  7. Optional: turn on the rest. SCIM provisioning (automatic accounts, removals and groups), Require SSO, IP allowlisting, custom roles, data retention and integrations such as ticketing sync.
  8. Roll out. Assign people (or groups) to the ThreatTree app in your IdP. Each one gets an account the first time they sign in with SSO, or as soon as SCIM pushes them, so there's nobody to invite by hand. Send them to the login page and Sign in with SSO instead.

Seats under an Enterprise contract

  • The seat count is a ceiling. Your contract's seats are available from day one, whether or not they're used, and adding people inside that number doesn't change your bill.
  • Who uses a seat: the owner, Admins, Members and pending invitations for those roles. The owner counts as one, so with 25 seats, 24 more people can edit.
  • Free viewers come on top: 3 read-only Viewers per seat, so 75 with 25 seats.
  • SSO and SCIM always create Members. For someone who only needs to read, either invite them as a Viewer from Settings → Team and have them accept the email invitation before their first SSO sign-in, or let them sign in and have the owner change their role to Viewer in the Members list, which frees their seat.
  • When every seat is taken, new people are refused at sign-in with "This organization has reached its seat limit", and SCIM can't create them. Nobody already in loses access. Free a seat (remove someone, or make a Member a Viewer), or ask ThreatTree support to raise your seat count.
  • Lowering the seat count never removes anyone. It only stops new people being added until usage is back under the number.

When people leave

  • With SCIM: unassign or deactivate the person in your IdP. ThreatTree removes them from the organization, which frees their seat.
  • Without SCIM: remove them in Settings → Team and unassign them in your IdP. Removing them ends their access to the organization's forests straight away. Unassigning stops future SSO sign-ins. Do both: if you only remove them, a person still assigned in the IdP is added back the next time they sign in with SSO.
  • Forests belong to the person who created them, so once someone leaves, the rest of the organization loses access to the forests they created. Check what they own before removing them, and contact ThreatTree support if that work needs to stay with the organization.

Changing the owner

The owner transfers ownership from Settings → Team. Contact ThreatTree support first so the new owner's account is switched to Enterprise: SSO, SCIM and IP allowlist settings can only be opened by an owner on Enterprise. Sign-in for your members keeps working throughout.

ℹ️ Need a hand?

Open a request from Support and include your organization's domain.

Settings & Account

Everything about your own account and org-wide branding lives under the avatar menu → Settings, split into nine tabs.

TabWhat's there
ProfileDisplay name and (read-only) email address.
SecurityChange password, set up two-factor authentication and backup codes, set a session inactivity timeout (Never / 5m / 15m / 30m / 1h / 4h / 8h), view active sessions and past login activity, and a Danger Zone to permanently delete your account (password re-confirmation required).
Membership & BillingCurrent plan badge, usage against Free-plan limits, self-serve upgrade/downgrade and seat management, a link to the Stripe billing portal, and (Pro/Enterprise org owners) Industry Modules — see Billing & Seats.
PreferencesTheme (Light / Dark / System default), default diagram type for new trees, and email notification toggles (product updates, security alerts, weekly activity digest, getting-started tips, review reminders). The digest goes out on Monday mornings (from 08:00 UTC) and summarizes the past week's activity across your forests; weeks with no activity send nothing. Getting-started tips are described under Getting started checklist and emails.
Team Pro+Create/view your Organization, invite people as Member, Admin or free Viewer, change roles, and manage groups and seats — see Collaboration & Organizations. Enterprise owners can also define custom roles. The owner can transfer ownership here.
Branding Pro+Organization name, website URL, and report footer tagline (shown on PDF report cover/footer), plus logo upload (PNG/JPG/SVG/WebP, max 2MB) for the report cover page.
Linked organizations EnterpriseSubsidiaries or client organizations linked to yours, and your parent organization — see Linked organizations.
Roadmap requests EnterpriseAsk ThreatTree for what your organization needs next, and follow each request's status — see Roadmap requests.
Review and approval EnterpriseWhether threat models need approval, approval stages, and sign-off of accepted risks — see Review and approval.
Sign-in and access EnterpriseOwner only: single sign-on, SCIM provisioning and IP allowlisting, with what is turned on at a glance.
Data and records Pro+The organization activity log, the organization data export (password re-confirmation required), and (Enterprise, owner-only) data retention.
Risk matrix Pro+Your own likelihood × impact scales and severity bands — see Your own risk matrix.
Threat library EnterpriseYour organization's own threats, offered by Generate attack trees and Suggested Threats in your forests — see Your organization's threat library.
Threat frameworks EnterpriseYour organization's own frameworks and their categories — see Your organization's threat frameworks.
Tools and alerts Pro+Slack/Teams critical-risk alerts, and (Enterprise, owner-only) ticketing sync with Jira, ServiceNow, Linear, or Azure DevOps, plus the SIEM feed and GRC evidence sync.
API keys EnterpriseKeys for the ThreatTree API.
Webhooks EnterpriseSigned event notifications to your own systems — see Webhooks.

Two-factor authentication

Settings → Security lets you require a second step at sign-in, on top of your password. Two methods are available, and only one can be active at a time:

MethodHow it works
Email codeA 6-digit code is emailed to you at every sign-in. Simple, but only as secure as your email account.
Authenticator appScan a QR code once with an app like Google Authenticator, Authy, 1Password, or Microsoft Authenticator. The app then generates a new 6-digit code every 30 seconds, without needing email access.
  1. In Settings → Security, click Enable next to the method you want and confirm your password.
  2. For the authenticator app: scan the QR code (or type the key shown below it into your app manually), then enter the 6-digit code your app generates to confirm setup.
  3. The first time you turn on either method, you're shown 10 backup codes — save them somewhere safe. Each works once, as a way back into your account if you lose your phone or email access. Use Regenerate any time to invalidate the old set and get a fresh 10.

Backup codes are shown once

They're stored only as a hash, the same way your password is — nobody, including ThreatTree, can look them up after the fact. If you lose them without saving a copy, regenerate a new set while you still have your normal method available.

ℹ️ Theme applies instantly across the whole app

Switching theme in Preferences previews immediately and applies everywhere — every page (including this Help Center) reads the same stored preference.

Notifications and emails

Choose which emails you get in Settings → Preferences. Each one can be turned off on its own:

EmailWhen it's sent
Security alertsA sign-in from a device or network ThreatTree hasn't seen on your account before. On by default.
Critical risk alertsA risk in one of your forests becomes high or critical. On by default. Organizations can also send these alerts to Slack or Microsoft Teams.
Comments (Enterprise)Someone mentions you in a comment, or replies in a discussion you're part of. On by default. The notice also appears under For you on the dashboard, even with the email off.
Review remindersOne of your threat models hasn't changed or been reviewed in 90 days (see Review due).
Weekly activity digestMonday morning: a summary of the past week's activity across your forests.
Getting-started tipsUp to four emails in your first two weeks.
Product updatesOccasional news about ThreatTree.

Emails that are part of a workflow are always sent: invitations, review and approval requests and decisions, accepted-risk sign-offs, password resets and sign-in codes.

Sessions and sign-in history

  • Inactivity timeout: in Settings → Security, choose how long you can stay idle before you're signed out: never, 5 or 15 minutes, 30 minutes, 1, 4 or 8 hours.
  • Active sessions: see where you're signed in and sign out any other session.
  • Sign-in history: recent sign-ins with their date, IP address, browser and country. It's kept for at most a year, or less if your organization sets a shorter retention.
  • Signing out ends that session, and changing your password signs out every other session. An organization's IP allowlist also signs you out as soon as you leave an allowed network.

Billing & Seats

Paying for Pro is self-serve, from Settings → Membership & Billing (or the plans page). Enterprise is billed under your contract instead: ThreatTree support switches the owner to Enterprise and sets the contracted seat count, and the Stripe controls below don't apply. See Enterprise Setup.

  • Upgrading — pick Pro, choose how many seats you're buying (1 if it's just you), and you're taken to a Stripe Checkout page. If you buy more than one seat, a company Organization is created for you automatically once payment succeeds — see Organizations.
  • Who uses a seat — everyone who can edit, including Editors from outside your organization, plus pending invites to edit. Viewers are free, up to 3 per paid seat.
  • Managing payment — Manage billing opens Stripe's hosted billing portal to update your card, view past invoices, or cancel.
  • Changing seat count — the organization owner can raise or lower the seat count at any time. Before confirming an increase, ThreatTree shows the exact prorated amount Stripe is about to charge; if that charge fails (e.g. insufficient funds), the seat count is left unchanged rather than granting seats that weren't paid for. Lowering seats can't drop below the number of seats currently in use.

ℹ️ Industry Modules

Also on the Membership & Billing tab (Pro/Enterprise organization owners): toggle industry-specific frameworks — Fintech (PCI DSS v4.0, DORA & Secure SLC, plus the Fintech element group), Healthcare (HIPAA Security Rule, plus the Healthcare element group), SaaS & Startups (SOC 2 and DORA, plus the SaaS Tenancy element group), Automotive (ISO/SAE 21434 and UN R155, plus the Automotive element group), Medical Devices (the FDA premarket cybersecurity guidance, plus the Medical Device element group), Critical Infrastructure (IEC 62443 & NERC CIP, plus the Industrial Control (OT) element group and Purdue levels on boundaries — see Industry Module groups), and AI & ML Systems (AI element types such as LLM endpoints, vector stores, agents and tools in the DFD editor, each with AI-specific suggested threats; a Context Window trust boundary for the prompt; Training Data, Model Weights and PII in Prompts classifications; and NIST AI RMF in the standards picker, plus an AI & ML Threat Coverage section in the forest PDF report showing which OWASP LLM / Agentic items and MITRE ATLAS techniques your attack trees address, and which they don't). Enabling one surfaces extra industry-specific fields and mapped controls in the DFD and Attack Tree editors for the whole organization. The Telecom module (GSMA, 3GPP and EU 5G Toolbox, plus the telecom element groups and operator zones) isn't on this list: ThreatTree enables it for Enterprise organizations on request — see Telecom Industry Module.

Account lockout after failed sign-ins

After 5 consecutive failed password attempts against your account, sign-in is temporarily blocked for 15 minutes — even if a later attempt uses the correct password. This protects against someone repeatedly guessing your password, and applies per account regardless of which device or network the attempts come from.

The lockout clears itself automatically 15 minutes after the last failed attempt; there's no manual unlock needed. A single successful sign-in also resets the count immediately.

⌨️ Keyboard Shortcuts

Both the DFD and Attack Tree editors share the same shortcut set — also available any time from the ? button next to the zoom controls.

ShortcutAction
Del / BackspaceDelete the selected node(s)/edge
Ctrl+Z / Ctrl+YUndo / redo, also available as the arrow buttons in the toolbar. Covers adding, deleting, connecting, moving, resizing and editing properties, for up to 100 steps until you leave or reload the page. Inside a text box, these keys apply to what you're typing.
Ctrl+SSave
Ctrl+ASelect all
FFit view to canvas contents
+ / -Zoom in / out
CDraw / cancel connection on the selected node
Space+dragPan the canvas
EscapeDeselect / cancel current action