<?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>Security Testing as Code on After the Code</title><link>https://windshock.github.io/en/tags/security-testing-as-code/</link><description>Recent content in Security Testing as Code 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/security-testing-as-code/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></channel></rss>