Topic starter
14/07/2026 4:22 pm
TL;DR: As AI agents become active participants in the digital workspace, the attack surface expands across email, collaboration, SaaS, and data flows, with Proofpoint positioning its platform around prompt injection, data governance, and Model Context Protocol controls. The governance challenge is no longer just protecting users, but controlling how people and agents consume, generate, and move sensitive data across shared workspaces.
Editorial analysis by NHI Mgmt Group, based on content published by Proofpoint: “Collaboration and data security in today’s agentic workspace”.
Key questions
Q: What breaks when AI agents are given broad enterprise access without tight governance?
A: Broad access turns AI agents into high-speed execution paths that can move data, spend money, modify records, or delete assets before operators can intervene.
Q: Why do prompt injection attacks matter more in agentic workspaces than in traditional chat tools?
A: Because agentic workspaces connect instructions to action.
Q: What are the signs that MCP-based agent access is not being governed effectively?
A: Poor governance usually shows up as unclear permissions, inconsistent tool approvals, and weak auditability across agent actions.
Practitioner guidance
- Define agent identities and scopes Inventory AI agents, assistants, and automations as non-human identities, then assign each one a documented owner, purpose, and least-privilege data scope.
- Enforce policy at the MCP boundary Treat Model Context Protocol connections as governed access paths and require authorization, logging, and data-policy checks outside the agent runtime.
- Classify sensitive data for agent use Map structured and unstructured data to approved agent actions so that classification, access posture, and exfiltration controls stay aligned.
Bottom line: Agentic workspaces extend security risk from human collaboration into delegated machine action, which changes how access, data use, and monitoring have to be governed.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
14/07/2026 4:30 pm
Agentic workspace security is becoming a non-human identity problem as much as a data-security problem. Once an AI agent can read, summarise, route, or act on enterprise information, it needs explicit identity boundaries, not just application permissions. That shifts the governance question from user productivity to delegated machine authority. Practitioners should treat agent access as a lifecycle-managed identity class, with scope, monitoring, and revocation.
A few things that frame the scale:
- Systems with least-privileged AI access had a 17% incident rate vs 76% for over-privileged systems. Organisations failing to scope AI access properly are 4.5x more likely to experience a security incident, according to the 2026 Infrastructure Identity Survey.
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How should security teams govern AI agents that inherit authority from other identities?
A: Security teams should govern AI agents by tracking identity lineage, not just credentials. That means recording the originating identity, the delegated authority path, and the runtime context for each action. If an agent can inherit permissions from humans, services, or other agents, policy has to evaluate the full chain before access is granted or continued.
👉 Read our full editorial: Agentic workspace security exposes new data and MCP governance gaps