Jargonautica
Security and Privacy

Threat Model

Writing down who might attack your system, what they want, and what they can do, before deciding what to defend. Without it, security work becomes a list of controls with no way to judge whether it is enough. For AI systems the useful starting question is what the model can reach and whose text it reads.

Technical view

Structured approaches such as STRIDE enumerate categories of threat against a decomposed architecture with trust boundaries marked. AI-specific additions include the training pipeline, the model artefact itself, the prompt and context assembly path, tool and connector surfaces, and the output path into downstream systems. Adversary classes run from opportunistic users through malicious insiders to sophisticated actors, and the model itself should be treated as an untrusted component in the flow.


Part of AI Terminology Index, section: Security and Privacy.

How it connects

Threat Model links to 7 other terms. The faint lines are links between those terms. See it in the full graph.

Least PrivilegeLeast PrivilegePrompt InjectionPrompt InjectionConfused DeputyConfused DeputyZero TrustZero TrustAttack SurfaceAttack SurfaceRed TeamingRed TeamingData Protection Impact AssessmentData Protection Imp…Threat Model