Technical guide
Patterns and product fit: securing AI retrieval at enterprise and lean scale
By Richard White ·
Free, no form.
Abstract
The architecture update connects DSPM findings, catalogs, policy as code and runtime enforcement, including permission-aware retrieval, derived indexes and cache handling.
Many AI security failures sit in the gaps between products: a label that never reaches the warehouse, a search index that ignores row access, a gateway asked to do a retrieval system’s job. This seventeen-page technical guide sets out the patterns that close those gaps, then shows how current products fit them.
It covers one classification vocabulary across Cyera, Microsoft Purview, Snowflake, Databricks and data.world; enforcement at the data; permission-aware retrieval and vector stores; SharePoint as a source; what belongs at the AI gateway; and semantic layers across platforms, including AtScale. Every product statement carries a source and a release status checked in October 2026.
Two lean stacks, one on Snowflake and one on Databricks, show how a PE or VC-backed company can reach a governed AI answer with native features and three part-time roles, and when to add more. It closes with ten release tests that prove the negative. Products are named as examples of patterns, not endorsements.
In the paper
Three passages, as published
Not the gateway’s job
Permission trimming belongs in the retrieval call.
Edition matters
A Standard Edition account can’t use native masking, row access policies or Access History.
SharePoint
If a route cannot carry the permissions, restrict it to content that everyone in scope may already read.
Next step
Discuss this paper against your own program.
A free sixty-minute working session with Richard on your top gaps. You leave with a one-page summary within three business days, and three next questions.