What a CISO actually asks in an AI security review
The questions that stall AI pilots at the security review, from how many copies of your documents will exist to whether you can switch it off, and how K-Lake answers each one.
Insights
Practical writing on sovereign AI, retrieval that holds up under audit, marketplace procurement and what actually stops enterprise AI reaching production. No thought leadership for its own sake.
Four retrieval approaches, the same files and the same questions. How many tokens each one put into the conversation, what that means for an AI budget, and the limits of the test.
The questions that stall AI pilots at the security review, from how many copies of your documents will exist to whether you can switch it off, and how K-Lake answers each one.
Committed Azure spend is budget that already exists and has an expiry date. How Marketplace procurement works, and the condition that decides whether it counts.
Why grounded retrieval with source links is what makes an AI answer defensible to a regulator, and what to ask any vendor about it.
Most stalled AI rollouts are boundary problems, not model problems. The three architectural answers to "where does our data go?"
What we write about
We write where we have something specific to say. If a topic does not sit under one of these, it does not belong here.
Data residency, air-gapped deployment, and building AI into environments that cannot send data out.
Grounding, permission-aware access, citations, and why keyword search alone keeps failing enterprise users.
What stalls enterprise AI deals, how to prepare for the questionnaire, and marketplace and MACC mechanics.
DORA, the EU AI Act, NHS data governance and what they mean operationally rather than theoretically.
New pieces are published here first, then syndicated to LinkedIn. Subscribe by RSS, or follow the company page to get them in your feed.