<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Raci on it-learn.io | IT, Networking &amp; Cybersecurity Blog</title><link>https://blog.it-learn.io/tags/raci/</link><description>Recent content in Raci on it-learn.io | IT, Networking &amp; Cybersecurity Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 06 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.it-learn.io/tags/raci/index.xml" rel="self" type="application/rss+xml"/><item><title>Building an Incident Response Playbook from Zero</title><link>https://blog.it-learn.io/posts/2026-06-06-building-incident-response-playbook-from-zero/</link><pubDate>Sat, 06 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.it-learn.io/posts/2026-06-06-building-incident-response-playbook-from-zero/</guid><description>&lt;p&gt;The IR plan is the document the auditor wants to see. The IR playbook is the document the on-call analyst actually opens at 02:43 AM when the EDR is screaming and they have to make decisions while half-asleep.&lt;/p&gt;
&lt;p&gt;Most organizations have the plan and not the playbooks. Or they have a playbook that is 47 pages of policy language with no actionable steps. Or they have great playbooks for the wrong incident types — a beautiful APT-attribution playbook and nothing for the ransomware they actually got hit with.&lt;/p&gt;</description></item></channel></rss>