From Clawdbot To Openclaw: Practical Lessons In Building Secure Agents
Akamai Technologies, Wednesday, February 18th, 2026
From Clawdbot to Moltbot to its current form OpenClaw, this technology has compressed years of security lessons into weeks. This agent doesn't just 'talk'; it has hands. It can execute shell commands, manage files, and interact directly with websites and APIs that you as a user might have access to - moving beyond passive access into active execution.
OpenClaw's rapid evolution from prototype to widespread deployment revealed fundamental security gaps in autonomous agent design, emphasizing that robust traditional security controls are non-negotiable foundations.
The agent's vulnerabilities align with the OWASP Top 10 for Agentic Applications, including threats such as goal hijacking, tool misuse, privilege escalation, supply chain risks, and more.
Practical security measures include separating instruction and data channels, implementing capability-based access controls, using dedicated service accounts, verifying third-party extensions, enforcing sandboxing, and continuous runtime monitoring.
A defense-in-depth strategy is essential, combining traditional security, architectural controls, and runtime protections to mitigate both conventional and agent-specific risks.
The key takeaway: Secure agent deployment requires balancing autonomy with risk management, using OpenClaw's lessons as a blueprint for building and operating safer AI agents.