Mistral Security Boundary

Overview

Apply controls at the application boundary because model instructions do not enforce identity, tenancy, authorization, or side-effect safety. Treat user content, retrieval, files, and output as untrusted.

Prerequisites

• A data-flow diagram covering browser, app, Mistral, stores, and tools.
• Credential, retention, tenant, moderation, and incident policies.
• An inventory of stateful APIs, files, retrieval stores, and actions.

Current Contract

Bearer credentials authorize provider calls but not application users. Classifiers can support policy but do not replace controls. ZDR eligibility differs between stateless and stateful products.

Authentication

Keep keys server-side and environment-scoped; rotate on exposure. Enforce user and tenant authorization before retrieval, provider calls, files, and tools.