<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on TechMonk</title><link>https://techmonk.red/categories/security/</link><description>Recent content in Security on TechMonk</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://techmonk.red/categories/security/feed.xml" rel="self" type="application/rss+xml"/><item><title>The AI Patch Wave Is Here, and Your Patching Process Is the Bottleneck</title><link>https://techmonk.red/posts/ai-patch-wave-security-process/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://techmonk.red/posts/ai-patch-wave-security-process/</guid><description>The AI patch wave isn&amp;rsquo;t coming. It&amp;rsquo;s already here. NCSC warns of industrial-scale vulnerability discovery. Your patching process is the real bottleneck.</description></item><item><title>Cal.com closed its code over AI security fears. Open source doesn't work that way.</title><link>https://techmonk.red/posts/open-source-security-ai-cal-com/</link><pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate><guid>https://techmonk.red/posts/open-source-security-ai-cal-com/</guid><description>Cal.com went proprietary citing AI security threats. Open source security doesn&amp;rsquo;t survive by hiding code — it&amp;rsquo;s never worked that way, and AI makes it worse.</description></item><item><title>AI Code Is Not Disposable: It Is Security Debt</title><link>https://techmonk.red/posts/ai-generated-code-security/</link><pubDate>Thu, 23 Apr 2026 00:00:00 +0000</pubDate><guid>https://techmonk.red/posts/ai-generated-code-security/</guid><description>Schneier imagines a future where AI tilts the balance toward defenders. But LLM-generated code is already in production, remains in systems, and risks becoming security debt.</description></item></channel></rss>