TL;DR: Runtime governance is now the control point for enterprise AI systems with retrieval, tool use, and sensitive data access, according to DeepKeep. Security teams need evidence, policy consistency, and clear agent ownership to keep runtime behaviour inside approved boundaries.
Editorial analysis by NHI Mgmt Group, based on content published by DeepKeep: “DeepKeep Joins the Microsoft for Startups Pegasus Program to Advance Enterprise AI Security”.
Key questions
Q: Why do multimodal AI systems create new governance risks for identity teams?
A: Because the system can be reached legitimately and still be manipulated after access is granted.
Q: How should teams evidence AI policy decisions for audit and incident response?
A: They should retain logs for blocked actions, allowed actions, tool invocations, and policy outcomes in a format that operations and compliance teams can review.
Q: What fails when AI security focuses only on the model instead of the runtime system?
A: Model-only controls miss the application harness, where retrieval, tool calls, third-party services, and enterprise data access determine what the system can actually do.
Practitioner guidance
- Define the AI runtime control surface Map retrieval, tool use, external services, model artifacts, and enterprise data access as one governed security boundary.
- Test policy consistency across modalities Run the same safety and authorization checks against text, image, video, and multilingual inputs to expose inconsistent enforcement.
- Capture investigation-grade AI evidence Log policy decisions, blocked actions, allowed actions, and tool invocations in a form that supports incident response and audit review.
Bottom line: Enterprise AI security now depends on governing the runtime layer where retrieval, tools, and external services can change system behaviour.
Glossary terms: Runtime policy drift, Multimodal Attack Surface, Agentic AI Identity
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Runtime governance, not model performance, is now the decisive AI security control plane. The article correctly shifts attention from what a model can generate to what the surrounding application can do with retrieval, tools, and enterprise data. That is the point where unsafe action becomes possible and where policy must be enforced. For security teams, the practical conclusion is that model approval alone does not establish operational safety.
A few things that frame the scale:
- Only 23% of IT leaders were very confident in their organisation's ability to manage security and governance for GenAI deployments, according to a 2025 Gartner survey of 360 IT leaders.
A question worth separating out:
Q: How should organisations govern agents that access enterprise data and tools?
A: Treat them like privileged production workloads. Define what data they can retrieve, what tools they can call, what actions require approval, and how those permissions are audited, reviewed, and revoked as the system changes.
👉 Read our full editorial: Enterprise AI security now depends on runtime control beyond the model