<?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/ko/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>ko-KR</language><lastBuildDate>Fri, 01 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://windshock.github.io/ko/tags/security-testing-as-code/index.xml" rel="self" type="application/rss+xml"/><item><title>보안진단은 외주 업무가 아니라 개발 공정이 된다</title><link>https://windshock.github.io/ko/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/ko/post/2026-05-01-security-assessment-as-development-process/</guid><description>AI 시대의 보안진단은 외주비 절감 문제가 아니라 개발 프로세스 안에 반복 검증을 내재화하는 문제다. 공정별 자동화 가능성과 사람 판단이 남는 영역을 나눠 봅니다.</description></item></channel></rss>