Topic starter
14/07/2026 4:22 pm
TL;DR: The gap is no longer adoption, but governance that can keep pace with AI operating across collaboration channels, according to Proofpoint’s 2026 AI and Human Risk Landscape report. The report finds that 87% of organizations already have AI assistants beyond pilot, 76% are rolling out autonomous agents, and 52% are not fully confident their controls would detect a compromised AI, based on a survey of 1,400+ security professionals across 12 countries.
Editorial analysis by NHI Mgmt Group, based on content published by Proofpoint: “AI is changing collaboration security faster than most organizations realize: key insights from the 2026 AI and Human Risk Landscape report”.
By the numbers:
- 87% of organisations already have AI assistants deployed beyond pilot.
- 76% are actively rolling out autonomous agents.
- 52% are not fully confident their controls would detect a compromised AI.
Key questions
Q: What breaks when AI assistants and agents are not governed across collaboration channels?
A: Security teams lose the ability to see AI-mediated activity as one chain of action.
Q: Why do autonomous agents increase the risk of compromised collaboration workflows?
A: Because they can move through trusted channels at machine speed, using delegated access and workflow permissions that were originally designed for human users.
Q: How can security teams tell whether AI lifecycle controls are working?
A: They should look for evidence that access requests, policy enforcement, and usage visibility are centrally recorded and current.
Practitioner guidance
- Map AI actions to collaboration channels Inventory where assistants and agents operate across email, SaaS, file-sharing and collaboration tools, then classify those paths as governed execution surfaces rather than ordinary user activity.
- Prove cross-channel detection coverage Test whether your controls can preserve actor identity, prompt context and session context as activity moves between collaboration platforms and security tools.
- Unify incident correlation across tool stacks Build a workflow that correlates alerts from collaboration, SaaS and identity systems so analysts can reconstruct AI-mediated activity without manual stitching.
Bottom line: AI assistants and autonomous agents are already in production across most organisations, but security strategy is still catching up to the collaboration surface they now inhabit.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
14/07/2026 5:06 pm
Collaboration security has become AI governance by another name: once assistants and agents operate inside email, SaaS and file-sharing workflows, the control question is no longer only who has access, but what machine-mediated action is permitted to happen in the first place. That expands governance from static permissioning to runtime oversight across delegated actions. Practitioners should treat collaboration channels as a governed execution surface, not just a messaging layer.
A question worth separating out:
Q: Should organisations manage AI assistants and agents as identity problems or collaboration problems?
A: They need to manage both. Collaboration is the operating surface, but identity is what determines who or what is allowed to act, and under what authority. If those controls are separated, organisations will keep spotting events without being able to govern the actor behind them.
👉 Read our full editorial: AI collaboration risk is outpacing security controls in 2026