# Enforce permissions outside the model

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Enforce permissions outside the model

ID: MHC-D-RESEARCH-0315 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/enforce-permissions-outside-the-model

A sentence in a prompt is guidance. An authorization check is a control.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A workflow relies on prompt instructions such as 'never access other users' data' or 'only admins may delete.'

### Avoid when

- Deterministic authorization still needs correct policy, testing, auditability and secure identity handling.

### Explanation

Put access rules in deterministic downstream code or policy enforcement points that validate every protected request. The model can help choose an action, but it should not be the component that decides whether the caller is allowed to perform it.

### Example

A delete API checks the user's role and record scope even when the agent confidently claims the deletion is allowed.

### Check

Changing or bypassing the model prompt cannot bypass the downstream authorization rule.

### Limits

- Deterministic authorization still needs correct policy, testing, auditability and secure identity handling.

### Evidence and sources

- supports: OWASP recommends enforcing critical authorization and privilege-separation controls independently from the LLM in deterministic, auditable systems. — RS-A650FC1839E382FF. External controls still need correct policy design and testing; moving a decision out of the prompt does not make it correct automatically. (Ensure security controls are enforced independently from the LLM)
- RS-A650FC1839E382FF: LLM07:2025 System Prompt Leakage — https://genai.owasp.org/llmrisk/llm072025-system-prompt-leakage/

No review details supplied.
