Enterprise risk
Why most GenAI pilots never pass security review
The common reasons enterprise GenAI pilots stall in security, legal, and procurement — and how to design systems that survive review.
7 min read · Updated 2026-07-26
Key takeaways
- Security review fails when data paths, tool permissions, and audit trails are improvised.
- “We’ll harden later” is the most expensive sentence in enterprise AI.
- Review-ready artifacts should be generated as part of delivery, not as a side project.
The real blocker is rarely the model
Security and risk teams rarely reject GenAI because the model is unimpressive. They reject unclear data flows, unbounded tool access, missing logging, weak access control, and systems no one can explain under incident pressure.
Pilots optimized for demos systematically under-invest in the evidence reviewers need.
Five failure patterns
1) Data sprawl: embeddings and logs contain sensitive content without retention or residency policy. 2) Permission theater: retrieval ignores real ACLs. 3) Tool chaos: agents can call APIs without least privilege or human approval. 4) No audit story: reviewers cannot reconstruct who saw what and why. 5) Vendor black boxes: the organization cannot operate or exit the system.
Any one of these can freeze scale. Together they kill trust.
What “review-ready” looks like
A production path includes: data classification and boundaries, authentication and authorization design, tool allowlists, human-in-the-loop for high-risk actions, evaluation for unsafe outputs, logging and retention, incident response notes, and a clear ownership model after handoff.
These are delivery artifacts, not optional polish.
Design sequence that works
Start with the decision and risk class of the use case. Define data policy before chunking documents. Define tool boundaries before agent demos. Define acceptance criteria before vendor bake-offs. Run a security-facing readout early, while change is still cheap.
The goal is not zero risk. The goal is governed risk with evidence.
Map this to your environment
Book a Production Readiness Assessment to translate these principles into a concrete architecture, risk map, and first production path.