--- title: How Breach-Focused Microsegmentation Could Have... description: AWS suffered outages in 2024-2025 caused by an internal AI agent ('Kiro') that deleted and recreated production environments due to over-permissioned access... canonical: https://daily.dev/posts/how-breach-focused-microsegmentation-could-have-contained-aws-s-ai-agent-outages-juxphnymn twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: How Breach-Focused Microsegmentation Could Have Contained AWS’s AI Agent Outages | daily.dev og:description: AWS suffered outages in 2024-2025 caused by an internal AI agent ('Kiro') that deleted and recreated production environments due to over-permissioned access... og:url: https://daily.dev/posts/how-breach-focused-microsegmentation-could-have-contained-aws-s-ai-agent-outages-juxphnymn og:image: https://api.daily.dev/og/posts/juXphnymN.png og:image:alt: How Breach-Focused Microsegmentation Could Have Contained AWS’s AI Agent Outages og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # How Breach-Focused Microsegmentation Could Have Contained AWS’s AI Agent Outages **[Security Boulevard](https://daily.dev/sources/securityboulevard)** · 14 min read · 0 upvotes · 0 comments ## Summary AWS suffered outages in 2024-2025 caused by an internal AI agent ('Kiro') that deleted and recreated production environments due to over-permissioned access and lack of containment. The core failure was granting AI agents broad production-level permissions without network-level guardrails. Breach-focused microsegmentation, as offered by ColorTokens Xshield, could have limited the blast radius by enforcing strict environment-level zoning (sandbox, staging, production), applying least-privilege network policies to non-human identities, and blocking direct AI agent access to production control planes. The post outlines four key failure modes and how microsegmentation addresses each, while acknowledging it cannot fix broken IAM design alone. CIOs and CISOs are urged to treat AI agents as high-risk non-human identities, mandate segmentation plans before deploying AI systems, and set a 12-month goal of no unconstrained AI agents in production. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Similar posts on daily.dev - [An AI-Powered Poly-Crisis Is Here, and It Is Rewriting Cyber Postures. Are You Breach Ready Yet?](https://daily.dev/posts/an-ai-powered-poly-crisis-is-here-and-it-is-rewriting-cyber-postures-are-you-breach-ready-yet--8qxodh1eq) · Security Boulevard · 0 upvotes · 0 comments - [The AI Vulnerability Storm Is Here. Is Your Security Program Breach Ready?](https://daily.dev/posts/the-ai-vulnerability-storm-is-here-is-your-security-program-breach-ready--3vrthvsgk) · Security Boulevard · 0 upvotes · 0 comments - [AI Coding Agent Horror Stories: The 13-Hour AWS Outage](https://daily.dev/posts/ai-coding-agent-horror-stories-the-13-hour-aws-outage-zosxjzyng) · Docker · 17 upvotes · 5 comments - [IEEE Cloud Summit 2026: The Tunnels No One Mapped](https://daily.dev/posts/ieee-cloud-summit-2026-the-tunnels-no-one-mapped-livjy4s3b) · GitGuardian · 1 upvotes · 0 comments - [Why agentic systems need microsegmentation](https://daily.dev/posts/why-agentic-systems-need-microsegmentation-vlltbxt2l) · InfoWorld · 0 upvotes · 0 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#aws](https://daily.dev/tags/aws), [#security](https://daily.dev/tags/security) [View this post on daily.dev](https://daily.dev/posts/how-breach-focused-microsegmentation-could-have-contained-aws-s-ai-agent-outages-juxphnymn) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"How Breach-Focused Microsegmentation Could Have Contained AWS’s AI Agent Outages","url":"https://daily.dev/posts/how-breach-focused-microsegmentation-could-have-contained-aws-s-ai-agent-outages-juxphnymn","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/how-breach-focused-microsegmentation-could-have-contained-aws-s-ai-agent-outages-juxphnymn"},"datePublished":"2026-03-13T10:28:20.652Z","dateModified":"2026-03-15T03:38:14.620Z","description":"AWS suffered outages in 2024-2025 caused by an internal AI agent ('Kiro') that deleted and recreated production environments due to over-permissioned access...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8fe9eeb967de205fd6743e2535f16178?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8fe9eeb967de205fd6743e2535f16178?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Security Boulevard","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Security Boulevard","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/3613c832180040de8d85bb29f74395be","url":"https://daily.dev/sources/securityboulevard"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/how-breach-focused-microsegmentation-could-have-contained-aws-s-ai-agent-outages-juxphnymn","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,aws,security","timeRequired":"PT14M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Security Boulevard","item":"https://daily.dev/sources/securityboulevard"},{"@type":"ListItem","position":3,"name":"How Breach-Focused Microsegmentation Could Have Contained AWS’s AI Agent Outages"}]} ```