<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Posts on Default Deny</title><link>https://defaultdeny.cloud/posts/</link><description>Recent content in Posts on Default Deny</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 21 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://defaultdeny.cloud/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>When Only Adaptation Moves: AI, Robots and Parsons' AGIL Scheme</title><link>https://defaultdeny.cloud/posts/agil/</link><pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate><guid>https://defaultdeny.cloud/posts/agil/</guid><description>Talcott Parsons&amp;#39; AGIL scheme shows why AI and robotics strain society: the economy adapts in months, while politics, law and values move in decades.</description></item><item><title>The Perfect Storm - How AI-Generated Code, Model Poisoning, and Supply Chain Attacks Converge</title><link>https://defaultdeny.cloud/posts/perfectstorm/</link><pubDate>Sun, 27 Sep 2026 03:17:49 +0200</pubDate><guid>https://defaultdeny.cloud/posts/perfectstorm/</guid><description>&lt;h2 id="tldr"&gt;TL;DR&lt;/h2&gt;
&lt;p&gt;AI-generated code is introducing security vulnerabilities at alarming scale—roughly 45% of AI-generated code fails OWASP Top 10 security tests, while supply chain attacks have increased 93% year-over-year. Three converging threats create a perfect storm: vulnerable code flowing through supply chains, poisoned AI models generating insecure patterns, and compromised training data embedding backdoors. Traditional security scanners miss ~80% of these LLM-specific issues. Organizations must shift from trusting AI outputs to continuous validation with human-in-the-loop review gates.&lt;/p&gt;</description></item><item><title>The Clock Is Ticking - Surviving Exploit Timelines</title><link>https://defaultdeny.cloud/posts/theclockisticking/</link><pubDate>Tue, 08 Sep 2026 03:17:49 +0200</pubDate><guid>https://defaultdeny.cloud/posts/theclockisticking/</guid><description>&lt;h1 id="tldr"&gt;TL;DR&lt;/h1&gt;
&lt;p&gt;AI has compressed the time between CVE disclosure and active exploitation from weeks to near real time.
Traditional patch cycles and CVSS-based triage can&amp;rsquo;t keep up anymore — low-severity vulnerabilities are now chainable at machine speed, and a single vulnerable container image across a cluster scales your attack surface horizontally.&lt;/p&gt;
&lt;p&gt;What to do about it:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Know what you have — Generate and sign SBOMs for every image. Maintain a real-time inventory of what&amp;rsquo;s running where.&lt;/li&gt;
&lt;li&gt;Automate patching in tiers — Fully automate base image updates, gate application dependency updates with tests, and reserve human-in-the-loop only for architectural changes.&lt;/li&gt;
&lt;li&gt;Control what you can&amp;rsquo;t patch — Strip unnecessary features at build time, isolate vulnerable services with default-deny network policies and L7-aware controls, and deploy runtime detection (Falco, Tetragon) to catch exploitation in progress.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The window between &amp;ldquo;vulnerable&amp;rdquo; and &amp;ldquo;exploited&amp;rdquo; is gone. Speed, visibility, and layered defense are the only viable response.&lt;/p&gt;</description></item></channel></rss>