Stop Saying No: Enable AI With Data Governance, Not a Blanket Block
The fastest way to lose influence as a security leader is to be the person who says no every time the business proposes an AI use case. The fix is visibility, not courage.
The fastest way to lose influence as a security leader is to be the person who says no every time the business proposes a new AI use case. Yet that’s where most CISOs find themselves. Boards ask for an AI strategy. Sales pilots copilots without telling anyone. Engineering pipes production data into an LLM for a quick demo. Security, asked late, responds with the only safe default available: stop.
George Gerchow, CSO at Bedrock Data, named the pattern on episode 95: the job now is “to enable a lot of the technology that we’re seeing today, how to have the gumption to stand up to the board when the board is saying, how are we using AI — which is the wrong question.”
The default-to-no posture isn’t laziness. It’s the rational response when a security leader has no visibility into the data the business is about to feed into a model. Without visibility, every yes is a guess. The fix is not more courage. It’s the visibility itself, delivered through AI data governance.
The wrong question
“How are we using AI” sounds like leadership. It’s actually the question that creates the default-to-no problem, because it assumes AI is a project to deploy and skips the prerequisite: what data do we have, who owns it, what is it classified as, and what are we contractually allowed to do with it?
That question is uncomfortable because most enterprises can’t answer it. Pranava Adduri, Co-Founder and CTO of Bedrock Data, described what he saw at AWS: “If I have 100 petabytes of data, what data do I back up? I can’t back up everything. There has to be a risk-based approach.” The same logic now applies to AI. You can’t feed 100 petabytes into an AI program — you have to pick, and the picking is the governance problem, not the technology problem. The right reframe pushes the conversation upstream into the data layer — the same scoping discipline that separates confident security leaders from defensive ones.
Data-first beats endpoint and perimeter thinking
A program built on endpoint and perimeter controls can’t keep up with AI, because the threat surface is the data itself and it crosses every endpoint by design. Gerchow framed the shift: “We’ve always tried endpoint, identity, perimeter… it’s about the data. So why not look at it from a data-first perspective?”
Data-first threat modeling starts with the asset and works outward: what’s the most sensitive data we hold, where is it, which AI workloads consume it, and what’s the blast radius if a model trained on it leaks part of it. That last point matters because an agent with broad data access is a security boundary on its own — endpoint controls don’t prevent a misconfigured agent from exfiltrating data it was authorized to read. Only governance over the data, and least privilege on the agent, do. It’s the same realization that moved the control point upstream in shift-left application security; with AI it moves further still, into the data.
What it looks like in practice
AI data governance is a working system that answers a few questions on demand: for any dataset, where it came from, who owns it, how it’s classified, and what you’re allowed to do with it; for any workload, which datasets feed it and under what terms; for any user or agent, which subset they’re entitled to see; and for any output, whether it’s consistent with the requester’s entitlements. When a system answers those instead of a human chasing spreadsheets, security stops being the bottleneck. The business proposes a workload, governance returns a yes-no-with-conditions in minutes, and the conversation moves on.
Three primitives turn governance from a brake into an enabler:
- Visibility — a real, continuously-discovered inventory of every dataset, including the shadow stores AI teams spin up without review.
- Lineage — where each dataset originated, what transformations it underwent, and which models consumed it, so you can reason about blast radius.
- Entitlements — who may use each dataset, for what, at what stage, reaching down to model inference, not stopping at the database table.
Gerchow’s phrase captures the posture shift: “Good brakes help you go faster.”
Repositioning security as an enabler
The reposition is real work, not a slide:
- Pick three live AI workloads as the test cases. Avoid hypotheticals — they never apply pressure.
- Build the data inventory for those three — source, sensitivity, lineage, entitlements, owner.
- Replace the meeting with a query. Every yes-no decision comes from the governance system, not group chat.
- Publish the turnaround time. A 48-hour answer changes how the business plans; a two-week answer pushes them to bypass security entirely.
- Expand only after the three are in steady state.
Done well, security becomes the layer that makes bigger, security-conscious deals closeable rather than the reason they stall — the same way turning security into a sales asset wins the stickier customers. The brakes are there. They just work fast enough to let the car go fast.