TL;DR: Governance gaps, not experimentation, sit at the centre of AvePoint's most-read 2025 blogs, which point to the same pressure across agents, data and resilience. Identity, access and recovery controls have to be planned together or scale turns into operational sprawl.
Editorial analysis by NHI Mgmt Group, based on content published by AvePoint: “Best Reads 2025: Turning AI Ambition to Governed, Secure Reality”.
Key questions
Q: Why do organisations need a data risk assessment before scaling gen AI or cloud data sharing?
A: A data risk assessment helps organisations identify unknown sensitive data, excessive access, and policy gaps that become more dangerous as AI and integrations spread.
Q: What are the signs that AI governance controls are not keeping pace with adoption?
A: Common warning signs include unclear ownership for AI use cases, inconsistent approval processes, limited visibility into where sensitive data enters models, and weak evidence for audits or assessments.
Q: How should organisations govern AI agents that act as business units of work?
A: Organisations should govern AI agents as first-class non-human identities.
Practitioner guidance
- Define agent ownership before rollout Assign a named business and technical owner to every AI agent before it touches production workflows, and require explicit approval for scope changes.
- Classify and limit data access paths Map the data sets each AI workflow can reach, then remove unnecessary access paths that expand the blast radius of agent actions.
- Build recovery tests into resilience reviews Test whether restored systems preserve integrity, permissions and operational usability rather than checking only that backup jobs completed.
Bottom line: The central risk in this roundup is not AI experimentation itself, but the governance gap that appears when agents, data and operational access scale faster than control ownership.
Glossary terms: Agentic AI, AI Governance, Data Security Posture Management, Control sprawl
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
AI governance is moving from policy to runtime control. The article’s strongest signal is that organisations are no longer debating AI adoption in the abstract; they are trying to govern live agent behaviour, data access and operational ownership. That makes governance a runtime discipline, not a committee output. The practical conclusion is that AI programmes need enforceable control points where action can be limited, reviewed or revoked.
A few things that frame the scale:
- 52% of respondents see AI security decision-making power shifting toward platform and infrastructure teams rather than the executive suite, according to the 2026 Infrastructure Identity Survey.
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: Should teams prioritise AI governance or supply chain visibility first?
A: Teams should treat them as linked priorities, because AI tools, generated code, and supply chain components now share the same delivery path and trust assumptions. Start with the visibility that identifies where AI is used, then extend that same inventory discipline to the dependencies and identities it relies on.
👉 Read our full editorial: AI agent governance, data security and resilience define 2025