Cybersecurity

When moving from intent to execution, the security model for Agentic AI shifts from intent interpretation to traditional systems hardening. Once an LLM can invoke tools and assume identities, the capabilities we grant an agent become the primary attack surface. This post continues from my first piece on [Loss of Intent as a Failure Mode in OWASP's Agentic AI Risks](/blog/loss-of-intent-as-a-failure-mode-in-owasp-agentic-ai-risks-2026). Here, I focus on the second bucket in the [OWASP Top 10 for Agentic Applications 2026](https://genai.owasp.org/resource/owasp-top-10-for-agentic-applications-for-2026/): agents with too much power.

OWASP recently released the Top 10 Vulnerabilities for Agentic Applications (2026). One thing is clear that the agentic systems fail differently than traditional applications or simple LLM integrations. The failure mode is not bad output, but the system taking a valid action for the wrong reason. In this post, I break down three OWASP vulnerabilities that stem from loss of intent, explain how they show up in real systems, and outline some mitigations.

Agents often appear structured at the planning level, but at runtime their execution becomes increasingly non-deterministic once tools, retries, partial failures, and replanning are introduced. This can easily become an economic denial of service (EDoS) attack.

Web applications, especially single‑page applications (SPAs) rely heavily on client‑side JavaScript caching for performance and ensuring updates are seamless. Most JavaScript bundlers (vite, webpack, etc.) compile, optimize, and bundle source JavaScript into static assets that are served to the browser. These build pipelines append a hash to the filename of the bundled JS file for cache‑busting purposes. The hash is a unique identifier for the bundled JS file that is generated by the build pipeline.

Secure software refers to applications designed and developed with stringent security measures to protect against unauthorized access and vulnerabilities. It is foundational for maintaining customer trust, ensuring operational continuity, and mitigating financial and reputational risks. We need to look at this challenge as both top-down and bottom-up. In this blog we will explore the key aspects of building secure software, including metrics for tracking security, and the use of frameworks to enhance security.