trust boundary
A line in a system where data passes between parts that trust each other differently, such as from the internet into your service or from your service to a vendor.
In more detail
Every crossing of a trust boundary needs a decision: what protects it, and whether the data should cross at all. Every request from the internet crosses one, so tokens and input must be validated there before use. Code paths are boundaries too: in injection bugs the boundary is the point where input reaches an interpreter.
Example
In the course, the only flow that stays inside one boundary is the one between the web app and the database in the same private network.Related terms
- claim — One statement inside a token, as a name and value, such as sub (subject), exp (expiry), iss (issuer), aud (audience) or scope.
- model validation — Checking that incoming data meets the rules, such as required fields and ranges, before the application acts on it.
- data flow — A path that data takes from one part of a system to another, described by where it starts, where it ends, what it carries and which network it crosses.
- threat model — A short, structured look at a design that asks what could go wrong and what you will do about it, before the thing is built.
- VPC — A virtual private cloud: your own isolated private network inside a cloud provider, with an address range you choose.
- payment gateway — An external service that processes card payments on a merchant's behalf.
- idempotency key — A unique value a client sends with a non-idempotent request, such as a create, so the server can recognise a retry and return the original result instead of acting twice.
Taught in
- Threat-Model An LLM App — AI Engineering: LLM Apps, RAG & Agents
- Authentication: JWTs and Claims — Modern .NET Core, C# & Enterprise Microservices
- The Threat Model Habit — Application Security & Threat Modeling for Engineers
- Injection In All Its Forms — Application Security & Threat Modeling for Engineers
- SQL Injection: The Exploit — Application Security & Threat Modeling for Engineers
- SQL Injection: The Fix — Application Security & Threat Modeling for Engineers
- Worked Design One: Ticket Booking, Correctness First — Scalable System Design & Distributed Architecture
References
- OWASP Threat Modeling Cheat Sheet
- Microsoft Threat Modeling Tool: trust boundaries
- AWS Well-Architected Framework: Reliability Pillar