Slide 22 of 27
Part 4 · PreventionSlide 22
Slide 22 ยท Mitigation 4 of 6
Keep sensitive logic in backend code, not the model.
๐Ÿ“„ OWASP LLM Top 10:2025 ยท LLM07 Prevention โ€” Privilege Separation
OWASP โ€” Privilege Separation
Separate Sensitive Logic from Model Context

“Decouple the processing of sensitive information from the language model itself, using more traditional backend systems for tasks that require high levels of data security or confidentiality.”

The GitHub Copilot extraction (slide 11) exposed internal tool descriptions and function signatures because they lived in the model’s context. The model needed them to describe its capabilities โ€” but by embedding them, it made them extractable. The same logic that drives capability also drives disclosure.

โ†’ The model’s job is to understand intent and route requests โ€” not to hold the full specification of every backend service
โ†’ Tool descriptions in the prompt should describe behavior at a user-facing level, not expose internal API structures
โ†’ Business rules are enforced by backend validation; the model is told “route this to the billing service” not “here are the billing rules”
โ†’ Sensitive computation happens outside the context window the model can read

List everything in your system prompt. For each item, ask: does this need to be in the prompt, or could a backend service handle it? Every item that moves out of the prompt is one less thing that can be extracted.

๐Ÿ’ผ Business takeaway

Ask your team which business rules live inside the AI prompt versus in your application code. Rules that live only in the prompt can be circumvented if the prompt is visible; rules enforced in code cannot.

โ† BackNext โ†’ M5 โ€” Red-team extraction