Topic starter
06/07/2026 9:43 am
TL;DR: Claude Cowork expands enterprise AI from answering questions to taking actions across browsers, desktop apps, and connected tools, which widens the trust boundary and makes built-in sandboxing, RBAC, and prompts necessary but not sufficient, according to Backslash Security. Continuous governance, connector review, and visibility into agent actions now matter more than endpoint assumptions.
Editorial analysis by NHI Mgmt Group, based on content published by Backslash Security: “The CISO’s Field Manual for Claude Cowork Security”.
Key questions
Q: How should security teams govern browser sessions used by AI agents?
A: Security teams should treat browser sessions used by AI agents as shared execution environments, not simple user logins.
Q: Why do MCPs and plugins increase risk in agentic AI environments?
A: They extend the agent’s trust boundary into other systems, so a malicious prompt, poisoned content, or weakly governed integration can trigger actions outside the original intent.
Q: What breaks when AI agents are given broad inherited permissions?
A: Broad inherited permissions break the assumption that access is tied to a narrow business need.
Practitioner guidance
- Define the agent’s operational identity Classify the AI agent as a governed non-human actor and assign explicit ownership for what it may access, execute, and delegate across enterprise systems.
- Review browser-session inheritance paths Identify where the agent can act through an authenticated browser session, then restrict those sessions to tasks that are safe to execute under inherited trust.
- Approve connectors as privileged access paths Require review for every MCP, plugin, and integration that extends the agent’s reach into SaaS tools, APIs, or internal systems.
Bottom line: Claude Cowork matters because it turns enterprise AI into an action-taking identity that can operate across authenticated sessions, connectors, and desktop workflows.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/07/2026 10:00 am
Agent identity governance is now the right frame for enterprise AI security: Claude Cowork is not just a content assistant, it is an action-capable identity that can operate inside real enterprise sessions. That shifts the control question from prompt safety to delegated authority, connector scope, and reviewable action boundaries. The practitioner implication is that AI access must be governed like an operational identity, not an interface.
A few things that frame the scale:
- 53% of security leaders expect AI to run major portions of their infrastructure autonomously within the next three years, according to the 2026 Infrastructure Identity Survey.
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How do organisations know whether sandboxing is actually reducing AI agent risk?
A: They test for what happens after a breakout. If the workload can still read secrets, open new outbound connections, or reach internet-exposed systems, the sandbox is not reducing blast radius enough. The useful signal is not whether the sandbox exists, but whether escape leaves the workload with usable authority.
👉 Read our full editorial: Claude Cowork security shows agentic AI now needs identity governance