1. How Threat Tiger works
Threat modeling means looking at how a system is built and asking "what could go wrong?" before
attackers do. In Threat Tiger you draw the system as a data-flow diagram — processes,
data stores, external entities (users and outside systems) and the data flows between them — and mark
trust boundaries where data moves between areas with different levels of trust, such as
from the internet into your network.
For each part of the diagram you then consider the six STRIDE threat
categories. Each one is the opposite of a security property you want to keep:
- Spoofing (authentication): someone pretends to be another user, service or device.
- Tampering (integrity): data, code or configuration is changed by someone who should not change it.
- Repudiation (accountability): someone can deny having done something because there is no reliable record.
- Information Disclosure (confidentiality): data is exposed to people or systems that should not see it.
- Denial of Service (availability): the system is slowed down or stopped for legitimate users.
- Elevation of Privilege (authorization): someone gains more rights than they were given.
Select a component and open Threat Templates for ideas. Set the security
switches in Properties (for example "encrypted" or "stores PII") and draw trust
boundaries: Threat Tiger then suggests threats that follow from your design. The icon and name of a component
also count: a component drawn as a GPU server, a .env file or a WordPress site gets threats for that kind
of component. Record the threats that apply in the register, rate them by likelihood and impact, and track
how they are mitigated. The Insights tab lists every open suggestion (filter by component,
STRIDE category or reason) and shows what is still uncovered.
2. Open Source License &
Feedback
Threat Tiger
Threat Modeling With A Bite · v