https://fortinetcloudcse.github.io/ai-101/05security/index.htmlThis page covers the security model of agentic systems: why conventional defences miss agentic attacks, how a multi-step attack chain exploits each layer of the stack, and what defence-in-depth looks like when the executor is an LLM. The hands-on portion is in Lab 4. By the end of this page you should be able to explain: Why an LLM agent is a new class of threat surface, not just a new frontend How four separate vulnerabilities chain into a single data exfiltration attack What the confused deputy problem means in an agentic context Why observability is not optional for deployed agents Which OWASP LLM Top 10 categories cover agentic risk What “agentic” means here — and why it matters now Module 2 drew the line between an agent (a specific system) and agentic (a property any system can have). It is worth restating that distinction before discussing attacks, because the scope of agentic security is wider than most people expect.Hugoen-UShttps://fortinetcloudcse.github.io/ai-101/05security/1_lab.htmlMon, 01 Jan 0001 00:00:00 +0000https://fortinetcloudcse.github.io/ai-101/05security/1_lab.htmlLab 4 runs the full attack chain: prompt injection to SQL injection to data exfiltration, all through the agent’s legitimate tools. You will then see what the same attack looks like when observability is suppressed, and optionally trigger an MCP tool-poisoning attack via a modified tool description. Your path: Docker ComposeKubernetes / Helm Locked in — every lab page follows this choice. ​ Docker Compose Kubernetes / Helm Docker Compose — every command on this page runs on your own machine.