liveBook · Manning

Threat model

A threat model is a structured analysis or representation of a system’s relevant threats, adversaries, assets, attack paths, assumptions, and possible mitigations.

How 7 Manning books explain it

Secure APIs

A threat model is a structured representation of a system's potential threats, attack paths, vulnerabilities, and impacts.

How it is used
Uses system analysis to identify API attack paths, prioritize risks, select mitigations, and guide continuous security testing.
How deep it goes
Explains decomposition, threat ranking, mitigation, review, and recurring reassessment, while deferring detailed treatment of individual vulnerabilities.
Examples
Uses SQL injection on GET /products, SSRF input, service communication, privilege escalation, stolen tokens, and business-flow abuse.
What you can do after
Diagnose attack paths, prioritize mitigations, collaborate on risks, and derive targeted security tests from the model.

Read how Secure APIs explains threat model →

AI-Powered Developer: Build software with ChatGPT and Copilot

A threat model is a documented representation of a system's potential threats, vulnerabilities, effects, and mitigation strategies.

How it is used
Guides proactive identification, prioritization, and mitigation of application-security threats across the development lifecycle.
How deep it goes
Defines an iterative process and demonstrates AI-assisted STRIDE analysis, while deferring to current authoritative security resources.
Examples
Demonstrates e-commerce and IT asset-management scenarios, including spoofing and repudiation risks with proposed controls.
What you can do after
Apply it via ChatGPT to brainstorm threats, assess risks, propose mitigations, and verify findings with authoritative sources.

Read how AI-Powered Developer: Build software with ChatGPT and Copilot explains threat model →

Real-World Cryptography

A threat model is a structured description of the assets, adversaries, capabilities, and attack scenarios relevant to a system's security.

How it is used
Guides decisions about what an application protects and whether end-to-end encryption is needed.
How deep it goes
Defines protection goals and trust choices, but stops short of a detailed threat-modeling procedure or formal analysis.
Examples
Uses online applications, central message servers, government access, email encryption, and secure messaging as concrete security scenarios.
What you can do after
Evaluate trust assumptions and choose protections that limit application operators’ access to user data.

Read how Real-World Cryptography explains threat model →

Data-Driven Cybersecurity

Threat modeling is a structured analysis of possible threats, attack paths, vulnerabilities, and mitigations for a system or design.

How it is used
Integrates early threat identification and mitigation into software design and secure-development work.
How deep it goes
Defines threat modeling through threats, actors, attack vectors, and mitigations, but gives no procedural modeling steps.
Examples
Places attack-vector identification in early design and situates security measures at design reviews, prototyping, and testing.
What you can do after
Apply it to identify potential threats and attack vectors, then determine mitigating measures for a system.

Read how Data-Driven Cybersecurity explains threat model →

Build AI-Enhanced Web Apps

A threat model is a structured process for identifying potential vulnerabilities and assessing which application components are most at risk.

How it is used
Guides security analysis before input validation and processing in AI-powered web applications.
How deep it goes
Defines a three-part inspection process covering endpoints, input locations, and data sensitivity, then connects findings to validation priorities.
Examples
Uses React server-component POST requests, API routes, forms, user inputs, and personal data as analysis targets.
What you can do after
Evaluate application exposure and prioritize server-side validation for endpoints, inputs, and sensitive data.

Read how Build AI-Enhanced Web Apps explains threat model →

Automating API Delivery

Threat modeling is the systematic identification and analysis of threats, vulnerabilities, likelihood, impact, controls, and countermeasures affecting a software system.

How it is used
Protects APIs by identifying security risks and selecting controls across design, development, testing, and runtime operation.
How deep it goes
Defines threats, vulnerabilities, attacks, controls, vectors, actors, and impact, but does not detail a complete modeling workflow.
Examples
Uses airline ticket purchasing and cancellation abuse to demonstrate sensitive business-flow exploitation.
What you can do after
Evaluate API risks and choose controls for vulnerabilities that automated linting cannot identify.

Read how Automating API Delivery explains threat model →

Cyber Threat Hunting

Threat modeling is the systematic analysis of threats, attack methods, assets, and potential attack paths affecting a system or organization.

How it is used
Prioritizes relevant, high-effect threats and turns them into focused threat-hunting plays.
How deep it goes
Breaks scenarios into actors, targets, vectors, effects, and indicators, then continues through hypothesis, scope, and data-source preparation.
Examples
Uses a Kubernetes container-escape scenario involving privileged access, API-server activity, malicious resources, and unexpected API calls.
What you can do after
Diagnose/debug with it by selecting a high-priority threat, forming a hunt hypothesis, defining scope, and choosing relevant logs.

Read how Cyber Threat Hunting explains threat model →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.