Notifications
Clear all
Topic starter
11/08/2026 3:12 pm
TL;DR: Enterprises adopting open-source AI need controls that follow data across prompts, tools, agents, and outputs because risk now spans the full chain of custody, according to Cyberhaven. The governance problem is no longer model choice but proving where sensitive data moved, who touched it, and whether agent behaviour violated policy.
NHIMG editorial — based on content published by Cyberhaven: Open-source AI Needs Security: Why Cyberhaven Is Joining the Open Secure AI Alliance
Questions worth separating out
Q: How should organisations govern external tools used by AI agents?
A: Organisations should review external tools as security inputs, not convenience features.
Q: Why do open-source AI environments create a data-governance challenge for security teams?
A: Because the security risk moves across models, harnesses, endpoints, cloud services, and business applications rather than staying inside one platform.
Q: What do security teams get wrong about prompt engineering for AI agents?
A: They often assume better wording is enough to create reliable control.
Practitioner guidance
- Define AI chain-of-custody requirements Require every AI workflow to record the data source, access path, transformation steps, and destination so security teams can prove what happened to sensitive information.
- Bind agent actions to scoped identities Assign each agent a distinct runtime identity with least-privilege tool access, short-lived credentials, and logs that tie actions back to a specific execution context.
- Separate policy from model selection Write policy for data handling, authorisation, and redaction once, then enforce it across open models, proprietary models, and different harnesses.
What's in the full article
Cyberhaven’s full post covers the operational detail this post intentionally leaves for the source:
- How its data-centric AI Security product reconstructs the complete chain of custody across prompts, files, tools, and outputs.
- What visibility and enforcement look like across open models, proprietary models, cloud infrastructure, endpoints, and on-premises systems.
- Why identity, isolation, evaluation, runtime visibility, and data protection are treated as the supporting security layers for open-source AI.
- How the vendor frames the alliance context around open source, AI infrastructure, and cybersecurity.
👉 Read Cyberhaven's post on open-source AI security and the Open Secure AI Alliance →
Open-source AI security and the data-custody gap for agents?
Explore further
11/08/2026 3:26 pm
Data custody, not model novelty, is the core AI security problem. The article is right to shift attention away from the model layer and toward the movement of sensitive data across AI workflows. That is where governance failures become visible, because prompts, files, tool calls, and outputs can each widen exposure if they are not continuously correlated. For practitioners, the implication is that AI governance has to be built around data lineage and policy enforcement, not only model approval.
A question worth separating out:
Q: How do you know if AI data trust controls are actually working?
A: Look for three signals: data is classified, access decisions are enforced where the data is touched, and non-human identities are visible in logs and reviews. If teams still need long manual approval loops to understand what an AI system can see, the control model is not working at runtime.
👉 Read our full editorial: Open-source AI security depends on data custody across agents
