<?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>Incident-Response on danilchenko.dev</title><link>https://www.danilchenko.dev/tags/incident-response/</link><description>Recent content in Incident-Response on danilchenko.dev</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 19 Apr 2026 18:30:00 +0000</lastBuildDate><atom:link href="https://www.danilchenko.dev/tags/incident-response/index.xml" rel="self" type="application/rss+xml"/><item><title>Vercel's April 2026 Security Incident: What We Know, What to Rotate</title><link>https://www.danilchenko.dev/posts/vercel-2026-breach/</link><pubDate>Sun, 19 Apr 2026 18:30:00 +0000</pubDate><guid>https://www.danilchenko.dev/posts/vercel-2026-breach/</guid><description>Vercel disclosed unauthorized access to internal systems on April 19, 2026. Here&amp;#39;s what&amp;#39;s confirmed, what&amp;#39;s still murky, and which secrets to rotate today.</description></item></channel></rss>