<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ransomware on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/ransomware/</link>
    <description>Recent content in Ransomware on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 20 Nov 2026 10:45:33 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/ransomware/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Ransomware recovery: why you should archive pre‑incident snapshots</title>
      <link>https://linuxeries.org/post/2026-11-20-ransomware-recovery-why-you-should-archive-pr/</link>
      <pubDate>Fri, 20 Nov 2026 10:45:33 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-11-20-ransomware-recovery-why-you-should-archive-pr/</guid>
      <description>&lt;p&gt;When a ransomware wave hits a production environment, the first instinct is to restore from backups. That’s a good rule of thumb, but it only works if the backups are clean. In practice, many organisations restore from the same storage that the malware infected, ending up with the same encrypted data. Archiving &lt;em&gt;pre‑incident&lt;/em&gt; snapshots—immutable, signed copies of the system state taken before the attack—provides a clean slate that is often overlooked.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
