Protect data. Verify agents. Govern inference.

CMO’s Letter

Hi ala,

The AI Data friction tax does not show up on any invoice, but it is the biggest real cost of your AI budget.

Your AI pilot works. The business case holds. Then it enters security and compliance review, where months disappear and the use case that comes out the other side is narrower than the one that proved its value. That gap between the AI project you funded and the AI you actually ship has a name: the AI Data friction tax. It is paid three times:

In time-to-value
In the capability you quietly cut to get approval
In the audit overhead that never goes away

Caution is not the problem. The people approving agentic access to regulated and sensitive data are accountable for what happens next, and they're being asked a question they can't answer with confidence: can this agent be trusted with access? An agent can combine individually permitted requests into sensitive knowledge that never existed in any single record. No security or compliance reviewer can sign off on that with a checklist. More permissions won't fix it. More forms won't scale to it.

The fix is not a faster review. It's a different question: protect sensitive values at the data layer, preserve the structure and relationships AI needs, and resolve clear data only when policy authorizes it. At that point, the approval conversation stops being a trust exercise and becomes an evidence review: what stayed protected, where policy applied, when clear values were permitted. That's the difference between a review that takes months and one that takes days, and between agents that ship at a fraction of their design and ones that ship at full capability.

Governance does not disappear in that model. It just gets a repeatable way to say yes.

Where does your own approval process stand today? Take the 10 Qs AI Data Readiness Assessment to find out.

Chris Gaebler

Chief Marketing Officer, Protegrity

Editor’s Recommendation

Activate all your data. Accelerate all your AI.

Most approval conversations happen between security and engineering, but the real bottleneck is often executive: leaders need a shared standard for what “ready to activate” means before review even starts. This piece lays out how to set that standard so AI can move from proven pilot to protected production.

Read the piece

From The Team

Put a trust boundary below text-to-SQL

Conversational analytics becomes a production risk the moment a model-generated query runs directly against enterprise data — one wrong join and a chat interface exposes an entire table. This architecture separates proposal from execution: the model proposes a plan, deterministic validation decides what can run, and data-centric policy protects sensitive values beneath the model, whatever the query.

Explore the architecture

See secure AI architecture in action

Most teams ask the model to enforce policy, then inherit its mistakes. This session shows two ways around that: secure text analytics that never exposes raw values to the model, and a zero-exposure zone that keeps sensitive data protected through retrieval, reasoning and output. Reviewers get a concrete pattern, not a promise.

Watch the video

In the news

Protect sensitive data wherever AI uses it

Protegrity’s Clyde Williamson and Jessica Hammond discuss how retailers can move from AI pilots toward autonomous workflows while maintaining visibility, governance, and control over sensitive customer and operational data. The conversation highlights data-centric protection, scoped agent permissions, and approaches such as tokenization, encryption, masking, and anonymization that can help organizations put sensitive data to work without unnecessarily exposing the original information.

StorMagic PodMagic: Securing Retail AI & Agentic Workflows

On the Calendar

Cloudera EVOLVE NYC

27 October

Marriott Marquis

We’re sponsoring Cloudera EVOLVE NYC on 27 October. If your team is wrestling with the same production-approval bottleneck, come compare notes with us on the floor — no pitch required, just the conversation.