<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blue-Team on it-learn.io | IT, Networking &amp; Cybersecurity Blog</title><link>https://blog.it-learn.io/tags/blue-team/</link><description>Recent content in Blue-Team on it-learn.io | IT, Networking &amp; Cybersecurity Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 04 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.it-learn.io/tags/blue-team/index.xml" rel="self" type="application/rss+xml"/><item><title>The NIST 800-61 Incident Response Lifecycle — Plain English</title><link>https://blog.it-learn.io/posts/2026-06-04-nist-800-61-incident-response-lifecycle-plain-english/</link><pubDate>Thu, 04 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.it-learn.io/posts/2026-06-04-nist-800-61-incident-response-lifecycle-plain-english/</guid><description>&lt;p&gt;Every incident response program in the world traces back to a single document: NIST Special Publication 800-61. If you have ever worked a SOC ticket, sat for ECIH or CySA+, or read a post-mortem, you have used the NIST lifecycle whether you knew it or not.&lt;/p&gt;
&lt;p&gt;The problem is the document itself is 80 pages of federal-government English and most summaries online either gloss over the parts that matter or repeat the four phase names without explaining what actually happens inside them. This post is the plain-English version — what each phase actually means at a keyboard, where teams get them wrong, and how the phases feed into each other so the same incident does not happen twice.&lt;/p&gt;</description></item></channel></rss>