<?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>AI Security on After the Code</title><link>https://windshock.github.io/en/tags/ai-security/</link><description>Recent content in AI Security on After the Code</description><generator>Hugo -- 0.145.0</generator><language>en-US</language><lastBuildDate>Fri, 01 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://windshock.github.io/en/tags/ai-security/index.xml" rel="self" type="application/rss+xml"/><item><title>Security Assessment Becomes a Development Process, Not an Outsourced Event</title><link>https://windshock.github.io/en/post/2026-05-01-security-assessment-as-development-process/</link><pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate><guid>https://windshock.github.io/en/post/2026-05-01-security-assessment-as-development-process/</guid><description>AI-era security assessment is not primarily about reducing outsourcing cost. It is about embedding repeatable verification into the development process while separating automation candidates from human judgment.</description></item><item><title>The AI Slop Paradox: Why Triage Gets Harder When Vulnerabilities Get Easier to Find</title><link>https://windshock.github.io/en/post/2026-04-30-ai-slop-vulnerability-triage/</link><pubDate>Thu, 30 Apr 2026 00:00:00 +0000</pubDate><guid>https://windshock.github.io/en/post/2026-04-30-ai-slop-vulnerability-triage/</guid><description>AI lowers the cost of finding vulnerability candidates, but it also increases low-quality reports, duplicates, and false positives. In the AI slop era, triage quality becomes the core security operation.</description></item><item><title>Beyond CVE Response: AI-Era Vulnerabilities Move Before They Get Numbers</title><link>https://windshock.github.io/en/post/2026-04-29-after-cve-response-ai-vulnerability/</link><pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate><guid>https://windshock.github.io/en/post/2026-04-29-after-cve-response-ai-vulnerability/</guid><description>AI-era vulnerability response cannot wait for a CVE number. Pre-CVE signals such as issues, commits, PoCs, write-ups, and patch traces now have to be mapped against internal exposure earlier.</description></item></channel></rss>