<?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>Bug Bounty on After the Code</title><link>https://windshock.github.io/ko/tags/bug-bounty/</link><description>Recent content in Bug Bounty on After the Code</description><generator>Hugo -- 0.145.0</generator><language>ko-KR</language><lastBuildDate>Thu, 30 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://windshock.github.io/ko/tags/bug-bounty/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Slop의 역설: 취약점을 더 잘 찾는 시대에 triage가 더 어려워지는 이유</title><link>https://windshock.github.io/ko/post/2026-04-30-ai-slop-vulnerability-triage/</link><pubDate>Thu, 30 Apr 2026 00:00:00 +0000</pubDate><guid>https://windshock.github.io/ko/post/2026-04-30-ai-slop-vulnerability-triage/</guid><description>AI는 취약점 발견 비용을 낮추지만 동시에 저품질 후보와 중복 신고를 늘린다. AI slop 시대에 triage 기준이 왜 보안 운영의 핵심이 되는지 설명합니다.</description></item></channel></rss>