Topic starter
05/07/2026 6:48 pm
TL;DR: OpenClaw highlights how employees are delegating real work to AI assistants that can browse, execute tasks, install skills, and touch internal systems, turning ordinary workflows into part of the attack surface, according to Lakera. The security problem is not model output alone but authority delegation that outpaces visibility, guardrails, and least-privilege controls.
Editorial analysis by NHI Mgmt Group, based on content published by Lakera: “OpenClaw Shows What Happens When AI Agents Act on Human Authority”.
By the numbers:
- 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.
Key questions
Q: What breaks when AI assistants are allowed to act on behalf of users without policy checks?
A: The assistant can make legitimate-looking requests that exceed the user's intended scope, especially when it can retrieve data, call APIs, or generate responses across sensitive systems.
Q: Why do AI assistants expand enterprise risk even when the model output looks harmless?
A: Because the security impact comes from execution, not language quality.
Q: What are the signs that AI governance is failing in the enterprise?
A: Common warning signs include rapid growth in AI use without matching policy coverage, sensitive files being copied into personal accounts, and a large share of AI apps carrying high or critical risk.
Practitioner guidance
- Map delegated AI actions to identity ownership Inventory which assistants can browse, execute tasks, install skills, or operate across enterprise systems, and assign an accountable owner for each action path.
- Constrain connectors and skills to least privilege Review every connector, plugin, and skill as a high-risk integration, then remove any permissions not required for the assistant's actual work.
- Classify untrusted content for agent consumption Treat documents, links, spreadsheets, and tickets as inputs that can steer behaviour, and block assistants from processing high-risk external content by default.
Bottom line: AI assistants become a security concern when they can act under human authority across enterprise systems, not when they merely produce content.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
05/07/2026 7:07 pm
Delegated AI authority is now an identity problem, not just an application problem. The article shows that the decisive risk is not what the assistant says but what it is allowed to do under a human's authority. Once an assistant can browse, execute tasks, or touch internal systems, the organisation has created a delegated access path that must be governed as identity behaviour. Practitioners should treat this as an access model redesign, not a content-safety tweak.
A few things that frame the scale:
- 88% of organisations have embedded AI agents in their workflows, according to KPMG's 2026 report.
A question worth separating out:
Q: Should organisations treat AI assistants and autonomous agents the same way?
A: No. AI assistants that act inside a human session can often be governed through delegated access and user accountability, while autonomous agents need their own identity, lifecycle records, and monitoring. Mixing the two creates false comfort and leaves the wrong party accountable for access decisions.
👉 Read our full editorial: OpenClaw shows how AI agent authority expands enterprise risk