What it means
A trust boundary marks where assumptions about identity, data, or authority change. It may lie between a browser and a server, between two organizations, or between processes running with different privileges. Crossing it requires an explicit decision about which claims and inputs can be accepted. A network perimeter is only one possible boundary.
Draw the boundary around responsibilities and trust assumptions, not merely around equipment. Input arriving from an internal system can still be wrong or attacker-controlled. Identify what the receiving component must authenticate, authorize, validate, or constrain before it acts on that input.
AN ILLUSTRATIVE SCENARIO
A factory supplier file
A supplier uploads a parts file to a factory planning service. The supplier is trusted to provide part descriptions but is not trusted to choose database commands, operating-system paths, or another supplier's records. The upload crosses a boundary into the factory application. The receiving service checks the supplier identity and permitted scope, validates the file format, and handles the contents as data. A separate boundary limits what the file-processing worker can access if processing goes wrong.
Put it to work
- Draw the important actors, services, data stores, and flows, then mark places where ownership, privilege, or confidence in incoming data changes.
- For each crossing, state which claims must be verified and which actions the receiving component is allowed to perform.
- Test representative invalid inputs and unauthorized requests at the receiving boundary; check that failure is contained and visible to the right operator.
How to check your work
Choose one flow and trace its checks at each crossing. The diagram and implementation should agree on who verifies identity, who enforces permission, and where untrusted data becomes an action.
Connect the ideas
- Authorization
The decision about whether a person, device, workload, or anonymous requester may perform a particular action on a resource.
- Zero trust
An architecture approach that grants no implicit trust from network location or asset ownership and evaluates access to resources using identity, device, and other context.
- Least privilege
Granting each identity only the actions, objects, and time window required for the current job.
- Prompt injection
An attack that inserts instructions into model input so the model follows attacker text instead of the developer’s policy.