What is threat modeling?

Question

IT Interview Practice · Accepted Answer

**Threat modeling** is a structured process for identifying potential **security threats** to a system and planning defenses — systematically thinking about what could go wrong, who might attack, and how. It's a proactive approach to security, done during design.

## What threat modeling is

```text
Threat modeling = systematically analyzing a system to find SECURITY THREATS and decide
how to mitigate them — BEFORE building (or as a review):
  → understand the system (data flows, components, trust boundaries, assets)
  → identify THREATS (what could an attacker do? where are the weak points?)
  → assess and prioritize risks; plan MITIGATIONS
→ proactive security: design defenses by thinking like an attacker, early.
```

## Common approach (and STRIDE)

```text
Typical questions:
  1. What are we building? (diagram the system, data flows, trust boundaries)
  2. What can go wrong? (identify threats)
  3. What do we do about it? (mitigations)
  4. Did we do a good job? (review)
STRIDE → a framework for categorizing threats:
  Spoofing, Tampering, Repudiation, Information disclosure, Denial of service,
  Elevation of privilege
→ helps systematically consider threat types per component/data flow.
```

## Why and when

```text
✓ PROACTIVE → find/address security issues at DESIGN time (cheaper than after a breach)
✓ Focuses security effort on real RISKS (the most important threats to the system)
✓ Especially valuable for sensitive/critical systems and significant new features
✓ Part of "security by design" / shift-left → build security in, not bolt on
→ A structured way to think about and improve a system's security posture.
```

## Why it matters

Understanding threat modeling is valuable senior-level knowledge because it's a **proactive, structured approach to security** that finds and addresses threats at design time, so it's important for building secure systems thoughtfully.

Threat modeling — **systematically analyzing a system to identify security threats and plan mitigations**, by understanding the system (data flows, components, trust boundaries, assets), identifying what could go wrong, and deciding how to defend — represents a proactive, design-time approach to security (thinking like an attacker early, rather than reacting to breaches).

Understanding the **common approach** (the questions: what are we building, what can go wrong, what do we do about it, did we do well — diagramming the system and identifying threats) and frameworks like **STRIDE** (categorizing threats as Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, and Elevation of privilege — helping systematically consider threat types) provides structure for doing it effectively rather than ad-hoc.

Understanding **why and when** threat modeling is valuable — being proactive (finding and addressing issues at design time, far cheaper than after a breach), focusing security effort on the real, most important risks, being especially valuable for sensitive/critical systems and significant features, and embodying **security by design / shift-left** (building security in rather than bolting it on) — reflects mature security thinking.

Threat modeling is how thoughtful teams systematically improve their security posture during design, addressing threats before they become vulnerabilities.

Since proactive, design-time security (finding and addressing threats before building) is more effective and cheaper than reactive security, and since threat modeling provides a structured way to do this (systematically identifying threats and mitigations, using frameworks like STRIDE), and since understanding it reflects mature security practice, understanding threat modeling is valuable senior-level knowledge — an important proactive security practice for building secure systems thoughtfully, embodying security-by-design, and reflecting the structured, attacker-minded security thinking expected for senior roles who design and review systems for security.

What threat modeling is

Common approach (and STRIDE)

Why and when

Why it matters

Related questions