<?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 Securosis</title><link>/tags/ransomware/</link><description>Recent content in Ransomware on Securosis</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 05 Sep 2023 09:23:37 -0400</lastBuildDate><atom:link href="/tags/ransomware/index.xml" rel="self" type="application/rss+xml"/><item><title>Deploying AWS Backup</title><link>/research/howto/awsbackup/</link><pubDate>Tue, 05 Sep 2023 09:23:37 -0400</pubDate><guid>/research/howto/awsbackup/</guid><description>&lt;p&gt;tl;dr - here is a &lt;a href="https://github.com/primeharbor/pht-awsbackup-management"&gt;link to the scripts&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="what-ransomware-in-aws-looks-like"&gt;What Ransomware in AWS looks like&lt;/h2&gt;
&lt;p&gt;In a typical ransomware attack, a threat actor will attempt to encrypt files on critical machines belonging to the victim. In exchange for a cryptocurrency payment, the threat actor will provide the decryption key and software to the victim, who then has to go through the arduous process of restoring their machines. The encrypted data is typically lost forever if the victim refuses to pay the ransom.&lt;/p&gt;</description></item></channel></rss>