2 min lesson
Data exfiltration & retention via models
Compare two rows from "Data exfiltration & retention via models", then say when each one fits.
Step 1 of 3
The code and prompts an agent sends to a model are some of the most sensitive data a company has. Once they cross the boundary to a provider, the questions are: does the provider train on them, how long are they retained and could one customer's data ever surface in another's session.
This section closes the loop on the trifecta's exit channel and adds the data-protection layer the JD calls out: logging and retention safeguards that prevent inappropriate retention or leakage of customer and code data. Be ready to reason about both the obvious channel - the provider request - and the sneaky ones an injection drives.
Learn more
Full explanation
Cross-tenant leakage
Cross-tenant leakageone customer's context must never reach another's
The failure that ends a B2B security review is one tenant's code or context bleeding into another tenant's session. Caches keyed without a tenant dimension, shared embeddings and logs that mix customers are the usual culprits. Tenant isolation has to be a property of the system, enforced in code, not a convention people remember to follow.