<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>事故响应 on PlumePHP</title><link>https://plumephp.com/tags/%E4%BA%8B%E6%95%85%E5%93%8D%E5%BA%94/</link><description>Recent content in 事故响应 on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Thu, 22 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://plumephp.com/tags/%E4%BA%8B%E6%95%85%E5%93%8D%E5%BA%94/index.xml" rel="self" type="application/rss+xml"/><item><title>事故响应：被盗、被封、被停机、域名劫持的 72 小时</title><link>https://plumephp.com/indie-resilience-09-incident-response-72h/</link><pubDate>Thu, 22 Oct 2026 14:00:00 +0800</pubDate><guid>https://plumephp.com/indie-resilience-09-incident-response-72h/</guid><description>真出事时，顺序比技术更重要。本篇给出 P0–P3 事故分级、0–1 小时止血、1–6 小时取证、6–24 小时恢复、24–72 小时沟通的处置表，附联系卡、证据清单与三份对外模板。</description></item></channel></rss>