<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kenza In The Cloud on Medium]]></title>
        <description><![CDATA[Stories by Kenza In The Cloud on Medium]]></description>
        <link>https://medium.com/@Kenza.In.The.Cloud?source=rss-c5cca0a05490------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FHWQtPwoNi6_Cz9eD6NzKw.gif</url>
            <title>Stories by Kenza In The Cloud on Medium</title>
            <link>https://medium.com/@Kenza.In.The.Cloud?source=rss-c5cca0a05490------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:26:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Kenza.In.The.Cloud/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[☠️ Ransomware on AWS: Break It Down. Detect It Fast. ]]></title>
            <link>https://infosecwriteups.com/aws-cloud-ransomware-anatomy-of-a-digital-hostage-crisis-4805ded3ff81?source=rss-c5cca0a05490------2</link>
            <guid isPermaLink="false">https://medium.com/p/4805ded3ff81</guid>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[ransomware]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Kenza In The Cloud]]></dc:creator>
            <pubDate>Mon, 07 Apr 2025 11:03:26 GMT</pubDate>
            <atom:updated>2026-10-19T12:28:06.254Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1cKD_cQyGj4v6gsLYrysZA.png" /></figure><p>Picture this : It’s a sunny day, you walk into the office, open your laptop… and then, disaster strikes 💥. All your files are <strong>encrypted</strong>, your databases are <strong>locked</strong>, and <strong>a cold message pops up</strong>: “<em>Pay 50 bitcoins within 72 hours, or say goodbye to your data 🚮.</em>”</p><p>A nightmare? <em>No, it’s still a reality in 2025.</em></p><h4>💡 Did you know?</h4><p>🔹 In 2024, 65% of companies in the financial sector reported being hit by a ransomware attack.<br>🔹 The number of active ransomware groups increased by 56% in just the first six months of 2024.<br>🔹 By 2027, the annual cost of cybercrime will exceed $23 trillion.<br><a href="https://www.sangfor.com/blog/cybersecurity/ransomware-attacks-2024-top-ransomware-headlines">➡️ Link here.</a></p><blockquote>Now that I’ve put you into this (unfortunately real) disaster scenario, let’s dive into how cloud ransomware works. Because it’s better to know what we’re up against. <em>⚔️</em></blockquote><blockquote>💡 <strong>TL;DR</strong> : Scroll to the bottom for a futuristic recap that’ll blow your mind!</blockquote><h3>🔐 Ransomware Decoded: The Dark Playbook of Cybercriminals</h3><p><em>Wannacry, Lockbit, BlackCat, C10p, MalasLocker, 8BASE, Akira</em>… Sound familiar? I bet at least one of these names rings a bell. And for good reason: these ransomware groups are spreading at an alarming rate, as you can see below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jSWtK8JUez_OGjIAMvRmUA.png" /><figcaption><a href="https://www.withsecure.com/en/whats-new/pressroom/ransomware-driving-professionalization-of-cyber-crime">Source</a></figcaption></figure><h4>→ So, what exactly is ransomware and how does it work?</h4><p>Basically, it’s malicious software that encrypts your data and demands a ransom to unlock it.</p><p><em>*Picture a digital burglar breaking into your house, changing all the locks, and demanding money to give you the new keys.*</em> Not very cool, right?</p><h4>➩ 💰 Who’s behind these attacks?</h4><p>Behind these ransomware attacks, you’ll find cybercriminals driven by <strong>money, politically motivated groups, and sometimes even malicious insiders </strong>(yep, the infamous insiders).</p><h4><strong>➩ 🔎 Their favorite targets?</strong></h4><p>The <strong>legal, industrial, financial, and healthcare sectors, </strong>along <strong>with small businesses </strong>that don’t always have the resources to defend themselves properly.</p><h4>➩ 💥 And how does it work in the cloud?</h4><p>Unlike attacks on traditional infrastructure, cloud ransomware takes advantage of <strong>specific vulnerabilities:</strong></p><p>🚨 Poorly configured IAM access 👤🔑<br>🚨 Exposed APIs 💀<br>🚨 Unprotected backups and snapshots 📂🚨</p><blockquote>Attackers are targeting any cloud providers architectures... And then what? Well, that’s a game changer.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w8-WK5MRO69Huf_VTu3GOA.png" /><figcaption>Here’s a bit of how the steps work in the Cloud and this isn’t just about AWS, by the way. <a href="https://blog.eclecticiq.com/ransomware-in-the-cloud-scattered-spider-targeting-insurance-and-financial-industries">Link here for more info.</a></figcaption></figure><h3>🛡️ Key Cloud Ransomware Techniques (MITRE ATT&amp;CK)</h3><p><strong>In the cloud, the attack evolves and becomes even more stealthy.</strong> Here’s an overview of the techniques used on AWS, based on the MITRE ATT&amp;CK framework:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zCUYdj5A4V6hHX-YXv4V4w.png" /></figure><blockquote><em>💡</em> Of course, there are many more techniques! But here’s a structured look at a cloud ransomware attack. To dive deeper, check out the MITRE ATT&amp;CK site.</blockquote><blockquote>🔒 The end goal remains the same: Block access to data and demand a ransom. But in the cloud, the method evolves with more stealthy and destructive attacks.</blockquote><h3>🚀 The other faces of a Cloud Ransomware attack</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xdyVL0dVmF823cay2lzwsg.png" /><figcaption><strong>Ransomware isn’t just about encrypting files on a hard drive anymore…</strong> In AWS, attackers exploit the cloud’s native mechanisms to lock up data in much more devious ways.</figcaption></figure><h4>🛡️ Protect yourself now!</h4><p>✅ Enable AWS Backup to ensure secure copies.<br>✅ Monitor CloudTrail for suspicious actions.<br>✅ Strengthen your KMS policies to prevent unauthorized access to encryption keys.</p><p>☛ And because nothing beats a real-world case, let’s now dive into the Codefinger attack, which perfectly showcases the tactics used in cloud ransomware… 🍿</p><h3>💥 Anatomy of a Cyberraid: How Codefinger Shatters AWS Security</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dMToFHWK9DQlgLDmaD0oAQ.png" /></figure><p>I could talk about Wannacry, Lockbit, BlackCat all day long… but I think we’ve covered that enough. No, today, I want to tell you about CodeFinger. Ever heard of them? Let me explain 🍿</p><h4>🕵️‍♂️ Attack Timeline: A Dive into the Mind of a Hacker</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p7VStW6N1kQekNdQoFkrkQ.png" /></figure><p>⥬ <em>As of today, the full scope and details of this attack remain unclear, this is </em>how Codefinger <em>is believed to have operated.</em></p><blockquote>⥭ Here, I’m simulating the attack flow to give you an idea of how it might have unfolded. :</blockquote><h4><strong>1️⃣ Recon - Midight 00:00</strong></h4><ul><li>Cybercriminals start by scanning public GitHub repositories for exposed credentials. a common tactic. They eventually get their hands on a valid AWS key… jackpot!</li></ul><h4><strong>2️⃣ Initial Compromise - 01:30</strong></h4><ul><li>They test the compromised key on S3. Bingo: they get write access to S3 objects.</li></ul><h4><strong>3️⃣ Mass Encryption - 02:00</strong></h4><ul><li>The attackers enable SSE-C (customer-provided encryption keys) to encrypt all files on S3. <br>It’s <strong>fast</strong>, <strong>discreet</strong>, and most importantly, <strong>irreversible </strong>without the key they hold.</li></ul><h4><strong>4️⃣ Ransom Message - 02:15</strong></h4><ul><li>A ransom note is dropped into the bucket, typically named something like READ_ME.txt. <em>(Catchy enough to grab someone’s attention)</em><br><strong> The message? Crystal clear</strong>: <em>“Pay or lose everything.”</em></li></ul><h4><strong>5️⃣ Scheduled Deletion - 02:30</strong></h4><ul><li>The attacker sets up an S3 Lifecycle Policy to delete all the data in 7 days. <strong>Safe to say, there’s no room for hope.</strong></li></ul><blockquote>☞ Done.</blockquote><h4>⇰🔥 Attack Process Summary :</h4><p>⓵<strong> Initial Access</strong> → The attacker tests the permissions of the compromised key.<br>⓶ <strong>Exploitation </strong>→ They encrypt S3 files with SSE-C and a secret key.<br>⓷ <strong>Extortion </strong>→ They leave a ransom note and enable automatic deletion within 7 days.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*Lw6Nl7bTl7nrf0Y6HXKPyA.png" /><figcaption><a href="https://www.vectra.ai/blog/defending-against-codefinger-ransomware-in-aws-s3">Source from Vector.ai</a></figcaption></figure><h4>⇰ Why is this attack so dangerous?</h4><ul><li>Abuse of a legitimate AWS feature → Hard to detect.</li><li>No malware → Just using IAM permissions, which makes detection trickier.</li><li><strong>No recovery possible</strong> → AWS doesn’t store SSE-C keys.</li></ul><blockquote><em>➡️ Want more info about this type of attack ?</em><a href="https://www.infoguard.ch/en/blog/aws-ransomware-and-whats-really-behind-it"><em> Here</em></a><em>.</em></blockquote><p>📌 Users will get a message like this when they try to access the files encrypted with SSE-C:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RCYEMbZfxnY6QTv7C701DQ.png" /><figcaption>Source PaloAltoNetworks</figcaption></figure><h4>🛑 Conclusion: The Codefinger Attack, a Wake-Up Call</h4><p>The Codefinger attack highlights how easily cybercriminals can exploit legitimate AWS features. This kind of cloud ransomware is on the rise and will keep evolving…<br> How would you react if this happened in your own cloud environment?</p><blockquote><em>In the face of an attack like this, paying the ransom might seem tempting, but it’s a false good idea, and I’m about to show you why below.</em></blockquote><h3>💸 Why Paying a Ransom After a Ransomware Attack is a Bad Idea</h3><p>Paying the ransom after a ransomware attack might seem like a quick fix, but the risks are huge:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SdCYKQweucHvf5AZkkPY_g.png" /><figcaption>credit Stage2data</figcaption></figure><blockquote>Scary Stats: Up to 94% of businesses that suffer severe data loss never fully recover.</blockquote><h4>Here’s why paying is a bad idea:</h4><p>🚨 No guarantee of recovery<br>🚨 Funding organized crime<br>🚨 Risk of double extortion<br>🚨 Huge financial cost<br>🚨 No security strategy can replace prevention</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*HXW-YvfCm-VUyDcG.jpg" /><figcaption><strong>They’ll try to pressure you, playing on the sense of urgency, but stay calm and don’t give in!</strong></figcaption></figure><blockquote><em>💡 Conclusion: Don’t give in to the temptation to pay! It’s far better to invest in solid backups, an effective incident response, and flawless cyber hygiene. Prevention is always better than cure.</em></blockquote><h4>⇰ Now that you know it’s not a good idea, I’ll help you spot the signals and know what to do if you ever fall victim to ransomware on your AWS cloud.</h4><h3>🛡️ Your Anti-Ransomware Arsenal: Ultimate Defense Strategies :</h3><p>Instead of waiting to pay the ransom, <strong>it’s better to detect the attack before it escalates.</strong> Here are the <strong>warning signs</strong> that should immediately raise your suspicions!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0h4E5oeWCPUd5HH0H_7CsQ.png" /></figure><h4>1.🕵️ Attack Profiling: The Red Flags You Can’t Miss</h4><p>⟾ <strong>Pay attention to these behaviors:</strong><br>• 🔍 <strong>Unusual activity:</strong> Access at odd hours or from suspicious locations.<br>• ⚠️ <strong>Increased errors: </strong>Files that won’t open, applications crashing.<br>• 🚨 <strong>Security alerts:</strong> Notifications from monitoring tools about strange behaviors.</p><p>⟾ <strong>AWS-Specific Things to Watch:</strong><br>• 🔐 IAM Changes: Monitor changes in roles and permissions via CloudTrail.<br>• 📊 <strong>Unusual behaviors in CloudTrail logs:</strong> Suspicious API calls or modified configurations.<br>• 🛠️ <strong>Access to unused services:</strong> Check for access to rarely used services like Lambda or SQS.<br>• 🧑‍💻 <strong>Root permissions: </strong>Monitor connections with elevated privileges or from unexpected regions.<br>• 🛑 <strong>Attempts to disable security</strong>: Any attempt to disable services like GuardDuty or WAF should raise an alarm.</p><blockquote><em>💡 These indicators, combined with proactive monitoring, will help you spot an attack before it gets out of hand.</em></blockquote><h4>2.🔥 Metrics to Watch in CloudTrail:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SKGIvniwthvXKDSVm0pHMA.png" /><figcaption><a href="https://gist.github.com/invictus-ir/2e892e19aad49eafe449fae91b2ff25b#file-cloudtrail-csv">Link from Github</a></figcaption></figure><h3>📡 CloudTrail Logs: Your Anti-Ransomware Radar</h3><p>An attack always leaves traces… but you need to know where to look! 👣</p><blockquote><strong><em>💡</em></strong> I gathered for you the <strong>key CloudTrail events to monitor to spot suspicious</strong> <strong>activity</strong> before it turns catastrophic.</blockquote><h4>Phase 1: Early Stage - Attack Begins</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E0gk6dJ9wBzWcTtyp1w_gA.png" /><figcaption>These early signs act as a warning: something’s brewing!</figcaption></figure><h4>Phase 2: Persistence - Ongoing Attack (Maintaining Access)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cxH3_3QqkjEQj2Ysa9PE4Q.png" /><figcaption>The attacker isn’t stopping here ; they’re preparing to dominate your environment.</figcaption></figure><h4>Phase 3: Defense Evasion - Ghost mode : Activated.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wqmsXpmJUwubohoPp8NfYg.png" /><figcaption>The attacker is erasing all traces to avoid detection.</figcaption></figure><h4>Phase 4: Impact - Final Phase (Data Destruction)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QQsUo1KWQCDOH5saKl3ESw.png" /><figcaption>This is when the attacks hit hard, and the damage becomes visible.</figcaption></figure><h3>🚨 Key Takeaways:</h3><p><strong>CloudTrail logs are your eyes and ears in the cloud. </strong>Keep an eye on these events and be ready to act before the attack escalates. <strong><em>Anticipating and detecting</em></strong> in time ensures the security of your data and infrastructure. 🛡️<br>See? <strong><em>A little vigilance and a sharp radar are all you need to stop the attack before it spreads. 🚀</em></strong></p><blockquote>☛ Looking for more info on what to monitor ? <a href="https://www.paloaltonetworks.com/blog/cloud-security/ransomware-data-protection-cloud/">Here</a>.</blockquote><h3>📌 How to Protect Yourself:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oC4M7v0AvIud1WBQfRFx-g.jpeg" /></figure><p>As a Cloud Security Engineer, here’s how I recommend mitigating ransomware risks:<br> • 💠 <strong>Limit SSE-C</strong>: Prefer SSE-KMS for centralized key management.<br> • 💠 <strong>IAM Least Privilege</strong>: Use the principle of least privilege with IAM roles, Security token service (STS), <br> • 💠 <strong>AWS Config Rules:</strong> Block unauthorized use of SSE-C.<br> • 💠 <strong>Surveillance</strong>: Enable GuardDuty and CloudTrail to detect abnormal access.<br> • 💠 <strong>Automation</strong>: Set up automatic responses using Lambda and EventBridge.<br> • 💠 <strong>Immutable Backups:</strong> Enable S3 Object Lock or S3 Versioning + MFA Delete.<br> • 💠 <strong>Mandatory MFA</strong>: Always enable multi-factor authentication.<br> • 💠 <strong>Regular Backups</strong>: Create copies of your critical data.<br> • 💠 <strong>Updates and Patches:</strong> Use AWS Systems Manager to maintain security.<br> • 💠 <strong>Awareness</strong>: Train your team on cybersecurity best practices.<br> • 💠 <strong>Disaster Recovery:</strong> Implement a plan with AWS Backup and Vault Lock.</p><blockquote><em>💡</em> Focus on SSE-C vs SSE-KMS:<br> •<strong> SSE-C (Server-Side Encryption with Customer-Provided Keys)</strong>: You manage the encryption key entirely.<br> ○ <strong><em>Risk</em></strong>: If you lose the key, your data is unrecoverable.</blockquote><blockquote>• <strong>SSE-KMS (Server-Side Encryption with AWS Key Management Service)</strong>: AWS manages the key centrally.<br> ○ <strong><em>Advantage</em></strong>: CloudTrail tracking, granular IAM policies, automatic key rotation.</blockquote><p>➠ By applying these strategies, you’re building a robust defense to prevent ransomware from ever reaching your data. 🛡️</p><blockquote>➡️ Among all these defenses, two stand out for their effectiveness against ransomware: <strong><em>AWS Backup Vault Lock and S3 Object Lock. </em></strong>Let’s dive deeper into how to set them up.</blockquote><h3>🔐 Quick Focus on AWS Backup Vault Lock &amp; S3 Object Lock</h3><p><strong>➡️ AWS Backup Vault Lock = you lock down a backup vault.</strong></p><p>It comes in 2 modes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jw1cLXFtvnDb39gEV4tnTQ.png" /><figcaption>In AWS Backup, a <strong>vault</strong> is a secure storage container for your backups, and a <strong>vault lock</strong> is a mechanism that prevents deletion or modification of those backups, even during an attack.</figcaption></figure><blockquote><em>⚠️</em> <em>Compliance mode is designed for strict immutability. Once grace period ends, the vault is untouchable if it contains recovery points.</em></blockquote><p>📌 Looking for more info about AWS BackUp ? <a href="https://docs.aws.amazon.com/aws-backup/latest/devguide/vault-lock.html">Here</a>.</p><h4>➔ CLI example for Compliance Mode:</h4><pre>aws backup put-backup-vault-lock-configuration \<br>  --backup-vault-name my_vault_to_lock \<br>  --changeable-for-days 3 \<br>  --min-retention-days 7 \<br>  --max-retention-days 30</pre><p>➡️ What does this code do?<br> • This code prevents the deletion of backups for 7 to 30 days, with a 3-day delay before a permanent lock is applied.</p><h4>➔ CLI example for Governance Mode:</h4><pre>aws backup put-backup-vault-lock-configuration \<br>  --backup-vault-name my_vault_to_lock \<br>  --min-retention-days 7 \<br>  --max-retention-days 30</pre><p>➡️ What does this code do?<br> • Same as the previous code, except it applies an immediate lock, preventing any modification or deletion of backups.</p><h4>➔ 💠 S3 Object Lock: Why use it?</h4><pre>aws s3api create-bucket - bucket amzn-s3-demo-bucket1 - object-lock-enabled-for-bucket</pre><p>➡️ What does this code do?<br> • This code creates an S3 bucket named “amzn-s3-demo-bucket1” with Object Lock enabled, allowing the application of retention or WORM (Write Once Read Many) mode on objects to prevent their deletion or modification.</p><p>📌 Looking for more info on S3 Object Lock ? <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock.html">Here</a>.</p><blockquote>➻ But Kenza.. What’s the difference between S3 Object Lock &amp; AWS Backup Vault lock ?</blockquote><p>➡📦 S3 Object Lock: Protects each file individually. “Don’t touch my files!”<br>➡ 🗄️ Backup Vault Lock: Protects the entire backup vault. “Nobody opens this vault without my permission! ”</p><p>Hope that makes things clearer!</p><blockquote><em>➥ 💡Even with the best protections, there’s no such thing as zero risk in the digital world. If the worst happens despite everything, here’s your step-by-step action plan.</em></blockquote><h3>🚨 Your Survival Plan</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aAXKVSgAqNrwRwLi6g7dtw.png" /></figure><p>If you find yourself the victim of an attack, follow these steps:<br>1️⃣ Isolate infected systems: Immediately disconnect compromised machines to stop the spread.<br>2️⃣ Assess the damage: Identify impacted data and check for available backups.<br>3️⃣ Inform stakeholders: Notify internal teams, clients, and relevant authorities if needed.<br>4️⃣ Restore data: Restore systems from backups to minimize the impact.<br>5️⃣ Analyze and strengthen security: Identify the exploited vulnerability and implement measures to prevent recurrence.<br>6️⃣ Contact AWS services and/or government agency : Don’t go it alone, reach out to AWS/Gov agency experts for a fast, efficient response.</p><p>⤏ Beyond immediate responses, the cybersecurity world is constantly evolving, with increasingly sophisticated attacks. I’ve put together a little analysis of emerging ransomware trends to keep an eye on!</p><h3>🌐 Cyber-War 2.0: The New Invisible Weapons of Cloud Hackers</h3><p>As you’ve probably figured out, attacks are going to become not only more frequent but also increasingly sophisticated. <br>Cybersecurity Ventures made an estimate, and here’s what came out of it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GCqDwJ2CBkWv_qOr9aUknA.png" /><figcaption>Source Back Cell &amp; Cybersecurity Ventures</figcaption></figure><h4>🤖 Emerging Defense Technologies :</h4><p>• Artificial Intelligence: Predictive detection of abnormal behaviors<br>• Zero Trust: Continuous verification of every access ➡️ “Never Trust, Always Verify”.<br>• Intelligent Containerization: Isolation and self-healing of systems.<br>• Blockchain: Tamper-proof traceability of security events.<br>• Quantum Encryption: Post-quantum cryptography resistant to future attacks.<br>• Cloud-Native Security Platforms (CNSP): Native integration of security into the cloud infrastructure (Detection + real-time correction).</p><blockquote><strong>📌💥 New Attack Vectors:</strong><br>In October 2024, researcher H. Varagiya revealed how an attacker could encrypt your AWS files with customer-managed keys. Result: impossible to recover your data without their key. Solution? Block the API kms:CreateCustomKeyStore using Service Control Policies (SCP). <a href="https://medium.com/@harsh8v/redefining-ransomware-attacks-on-aws-using-aws-kms-xks-dea668633802">Link</a>. 🔗</blockquote><blockquote>💡 Key to Resilience: The best defense will be one that combines human technology and artificial intelligence, staying constantly adaptive.</blockquote><blockquote>These technologies are impressive, but let’s talk numbers for a second. What’s the financial impact of ransomware and cybersecurity in general?</blockquote><h3>💸 The Financial Toll: These Ransomware Stats Will Blow Your Mind</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vs7TIa1wGj4K1hCF8joz2A.jpeg" /></figure><p><strong>➡️ The stats are pretty wild </strong><a href="https://keepnetlabs.com/blog/171-cyber-security-statistics-2024-s-updated-trends-and-data"><strong>(Link here)</strong></a><strong> but in nutshell :</strong></p><p>💥 Attacks every 11 seconds (UNODC)<br>💥Estimated damage costs of $30 billion in 2024 (Cybersecurity Ventures)<br>💥 Healthcare sector: average cost of a data breach, $10.93 million (IBM)<br>💥 Average loss of $8,500/hour due to ransomware (Egnyte)</p><blockquote>➡ Makes you think, right? The best defense? Combine technology and AI, staying ready to adapt. Because in cybersecurity, responsiveness makes all the difference.</blockquote><h3>⚒️ Your Anti-Ransomware Defense Strategy: The Essentials to Remember</h3><p>Ransomware in the cloud is an omnipresent, ever-evolving threat. Ignoring this danger puts your data and business at serious risk. But the good news is: you can anticipate and protect yourself.<br>Integrate these services to combat ransomware and boost your protection:</p><p>✅ AWS Backup with Vault Lock → clean recovery following the WORM model (write-once, read-many).<br>✅ S3 Object Lock → storage immutability.<br>✅ DRS → fast VM or server recovery.<br>✅ <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/getting-started-reduce-permissions.html">Restrictive IAM</a> + <a href="https://docs.aws.amazon.com/cli/latest/reference/guardduty/">GuardDuty</a>+ <a href="https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-settingup.html">Security Hub</a> + CloudTrail → detection and prevention.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*VmE1ItblbQmPP0cUhJjDXQ.gif" /></figure><p>By anticipating threats and responding effectively, you turn this threat into an opportunity. Cybersecurity isn’t just tech ; it’s a mindset. Stay ahead and secure your digital future! 🚀</p><h3>My Networks:</h3><p>💬 <a href="https://www.linkedin.com/in/kenza-in-the-cloud">LinkedIn : Let’s Connect!</a><br>👾 <a href="https://discord.com/users/kzax01">Discord</a><br>🧪 <a href="https://github.com/Kzax01">GitHub : AWS Security Projects straight from 2065.</a></p><blockquote><em>DISCLAIMER<br></em>This article is for educational purposes only. Its goal is to help cybersecurity professionals understand and anticipate threats in an AWS environment. Any malicious use of the information presented is strictly prohibited.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4805ded3ff81" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/aws-cloud-ransomware-anatomy-of-a-digital-hostage-crisis-4805ded3ff81">☠️ Ransomware on AWS: Break It Down. Detect It Fast. 🚨</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cryptojacking: When Hackers Hijack Your Cloud to Mine Money‍☠️]]></title>
            <link>https://infosecwriteups.com/cryptojacking-when-hackers-hijack-your-cloud-to-mine-money-%EF%B8%8F-fd0f316154cb?source=rss-c5cca0a05490------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd0f316154cb</guid>
            <category><![CDATA[cryptojacking]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[crypto-mining]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Kenza In The Cloud]]></dc:creator>
            <pubDate>Tue, 11 Mar 2025 10:57:28 GMT</pubDate>
            <atom:updated>2026-03-19T14:56:26.470Z</atom:updated>
            <content:encoded><![CDATA[<h3>💰<strong>Cryptojacking: When Attackers Hijack Your Cloud to Mine Money</strong>🏴‍☠️</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2XuZXTgN05R_v6VI5UKJSQ.png" /></figure><p>Imagine this: 7AM still tired, you open your AWS dashboard, coffee in hand, and then… BOOOOM!!! 💥 A $15,000 bill instead of the usual $300. You check your account, refresh the page (just in case hehe)… but no, it’s real, you’re well awake!! 😱</p><p>No, it’s not a billing mistake. Congratulations! You’ve just become the unwilling bankroller of a cybercriminal gang that hijacked your infrastructure to mine crypto : on YOUR dime, yay! 🎉</p><p>&gt; No worries.. you’re not alone in this nightmare. Cryptojacking attacks surged by <strong>75% in 2023</strong>, according to Sysdig. Campaigns like <strong>AmberSquid</strong> 🦑 even exploit <strong>lesser-known AWS services</strong> to stay under the radar.</p><h4>☞ But as always, no worries! I got you! Let’s see how we can prevent this from happening &amp; what to do if it’s the case.</h4><blockquote>💡TL;DR -<em>Go at the bottom of the page, a cool recap awaits you!</em></blockquote><h3>📖 Kenza.. sorry but w<strong>hat Exactly is Cryptojacking?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hxaw7vRcnHq8x1VvsoZgOw.png" /></figure><p>Good question! Cryptojacking is all about <strong>mining crypto at someone else’s expense</strong>. Instead of investing in hardware and paying for electricity, attackers squat on your cloud infrastructure. That’s the laziest attack lol.</p><p>Back in the day, they simply launched EC2 instances loaded with mining software. But that became too easy to detect.</p><p>➞ Now, they’re targeting <strong>less-monitored AWS services</strong>, such as:</p><ul><li>🚀 <strong>AWS Amplify</strong></li><li>🛳 <strong>AWS Fargate</strong></li><li>🤖 <strong>SageMaker</strong></li></ul><p>More subtle, more profitable, and much harder to catch. 🕵️‍♂️</p><blockquote><em>💡 </em><strong>Think of it like this:</strong> Someone is siphoning gas from your car without you noticing. The only difference? The thief doesn’t leave you a thank-you note.</blockquote><p>As technology evolves, attackers up their game too. Let’s dive into their arsenal…</p><h3>🏴‍☠️ <strong>The 3 Types of Cryptojacking: How attackers Drain Your Resources :</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z2yqGRl1qBiOxzM8yjxTpA.png" /><figcaption>Behind these attacks are <strong>highly organized groups</strong> with tactics straight out of a spy movie…</figcaption></figure><blockquote><em>💡 </em>Now that you know how threat actors exploit different methods to hijack your resources, let’s look at a real-world example of how they target AWS services that often fly under the radar.</blockquote><h3>🏴‍☠️ <strong>The Key Players in Cryptojacking: TeamTNT, Silent Bob &amp; AmberSquid</strong></h3><p>Everyone’s heard of <strong>TeamTNT</strong> and the <strong>Silent Bob</strong> campaign, but today, I want to focus on <strong>AmberSquid</strong>, which made waves in 2023.</p><p>Silent Bob primarily attacks <strong>misconfigured Docker APIs</strong> and exposed <strong>JupyterLab</strong> instances. Check out AquaSec’s full analysis here: <a href="https://www.aquasec.com/blog/threat-alert-anatomy-of-silentbobs-cloud-attack/">Silent Bob Cloud Attack</a>.</p><blockquote>➡️ But <strong>AmberSquid</strong>? That’s a whole different story.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/1*fS67YqdeGQZ2ieJY3PH4EA.png" /><figcaption>credit hackmetrix</figcaption></figure><h3>🦑 <strong>AmberSquid: When Cryptojacking Targets AWS Services in the Shadows</strong></h3><p>Discovered by Sysdig, <strong>AmberSquid</strong> struck where it hurts :AWS services that aren’t closely monitored ; allowing attackers to mine crypto undetected.</p><p>➞ While most cryptojacking campaigns focus on <strong>EC2</strong>, AmberSquid shifts its attention to:</p><ul><li><strong>AWS Amplify</strong></li><li><strong>AWS Fargate</strong></li><li><strong>Amazon SageMaker</strong></li><li><strong>Amazon Elastic Container Service (ECS)</strong></li><li><strong>AWS CloudFormation</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bOBw93mOP8hI_RS6BKmlkQ.jpeg" /></figure><p>These services often <strong>lack strong security oversight</strong>, but for victims, the <strong>costs can skyrocket to over $10,000 per day</strong> <em>(Sysdig Threat Research Team)</em>.</p><h4>💭 Imagine…</h4><p>Picture this : Peter, the CTO of a small innovative startup. One morning, as he checks his AWS bill, he notices an unexpected charge of $20,000. At first, he thinks it’s a mistake, but as he digs deeper, he realizes that resource usage exploded overnight… even though no new applications were deployed.</p><p>&gt; His heart skips a beat.. A mistake? He keeps digging… and discovers that a cryptocurrency miner has quietly set up shop on AWS Fargate and SageMaker. What seemed like a regular day quickly turns into a full-blown financial nightmare…</p><blockquote>And it can escalate <em>really</em> fast!</blockquote><p><em>Now that you’ve got the big picture of the AmberSquid campaign through Peter’s eyes, let’s take a closer look at how attackers successfully deployed malicious scripts to mine cryptocurrencies on seemingly harmless AWS services.</em></p><h4>🎯 <strong>Targets: Less Common, Yet Strategic Services</strong></h4><p>By choosing lesser-known services like Amplify, Fargate, and SageMaker, the attackers flew under the radar of traditional security mechanisms.</p><p>➞This made detection and intervention much more complex, highlighting the importance of monitoring the entire infrastructure ; even the services that seem harmless.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IM87MryDcbrD5h0ySu5NbQ.jpeg" /></figure><h3>🔍 <strong>AmberSquid Attack Methodology:</strong></h3><p>⓵ <strong>Attackers used AWS CodeCommit</strong> to create a private repository containing the code for an AWS Amplify app.</p><p>⓶ <strong>From this repo, shell scripts</strong> were executed to deploy a web app on AWS Amplify, which secretly launched a crypto miner.</p><p>⓷ <strong>Similar techniques</strong> were used to exploit Fargate and SageMaker, spinning up cloud resources for mining.</p><p><strong><em>➡ Here’s a breakdown of the AWS services used in this attack:</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gulFf2MPZk-oswe4kTMHbg.png" /></figure><h3><strong>💡 Key Lessons from the AmberSquid Attack</strong></h3><p>The <strong>AmberSquid</strong> attack highlights <strong>several critical takeaways</strong>:</p><p>🔹 <strong>Exploitation of less-monitored services</strong> → Services like Fargate and SageMaker, not typically associated with cryptojacking, were used to mine crypto. This proves the importance of <strong>monitoring all cloud services</strong>, not just EC2.</p><p>🔹 <strong>Code pipeline security</strong> → Attackers used <strong>CodeCommit</strong> to store malicious scripts. This underscores the need to <strong>secure your entire CI/CD pipeline</strong>, including AWS Amplify.</p><p>🔹 <strong>Visibility gaps</strong> → Services like <strong>Fargate</strong> offer <strong>limited real-time visibility</strong>, making it harder to detect cryptojacking activities.</p><p>🔹 <strong>Risk of shell scripts</strong> → Attackers deployed crypto miners <strong>via scripts</strong> on services like <strong>Lambda</strong> and <strong>SageMaker</strong>, emphasizing the need for <strong>strict execution permissions</strong>.</p><p>🔹 <strong>Unexpected costs</strong> → AWS’s <strong>pay-as-you-go</strong> pricing makes <strong>cryptojacking profitable for attackers</strong> while remaining unnoticed until you get a massive bill.</p><blockquote>These insights show that <strong>attackers are getting stealthier</strong>, favoring <strong>low-profile techniques that evade detection</strong>. This makes <strong>proactive cloud security a must</strong>.</blockquote><h3><strong>💸 The Real Cost of that Incident :</strong></h3><p>➞ Once <strong>attackers infiltrate your AWS account</strong> and launch crypto miners, your <strong>costs skyrocket within hours</strong>.</p><h4>💰 <strong>Here’s a daily cost estimate based on real-world attacks:</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/1*fHFwfNLeVrCfgOmfiaT0rg.png" /><figcaption><strong>Threat actors now target overlooked cloud services, exploiting automation and high-performance resources to launch cryptojacking campaigns. The result? Sky-high bills and hard-to-detect damages.</strong></figcaption></figure><p>➡️ <strong>For more details, check out </strong>🔗 <a href="https://sysdig.com/blog/ambersquid/">Sysdig Blog: AmberSquid Analysis</a>.</p><blockquote>Cryptojacking isn’t just <strong>stealing your compute power</strong> ; it’s draining your <strong>budget, resources, and security posture</strong>. Time to <strong>fight back</strong>. 🛡️🚀</blockquote><h3>💰 <strong>How Does an AWS Account Fall Victim to Cryptojacking?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6VZUQrDd3lPkLf2ki1yCGg.jpeg" /></figure><h4>Attackers don’t mine just any cryptocurrency. They focus on:</h4><ul><li><strong>Monero (XMR)</strong> → <strong>Anonymous</strong>, easy to mine on CPU. The <strong>#1 choice</strong> for cryptojacking.</li><li><strong>Ethereum (ETH)</strong> → Used to be <strong>profitable before Proof-of-Stake</strong>, but was a major target.</li><li><strong>Zcash (ZEC)</strong> → <strong>Highly valued</strong> for its <strong>private transactions</strong>.</li><li><strong>Bitcoin (BTC)</strong> → <strong>Rare in cryptojacking</strong> (too resource-intensive).</li></ul><h3>🚨 <strong>How do they Infiltrate Your AWS Account ?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/780/1*nbDBPgpXcuQKZMaoRVz50Q.png" /></figure><h4>Cybercriminals <strong>gain access to AWS accounts in multiple ways</strong>:</h4><p>1️⃣ <strong>Leaked credentials</strong> → If your <strong>AWS keys leak on GitHub</strong>, you’re an easy target. <strong>80% of cloud compromises</strong> start with exposed credentials. (<a href="https://unit42.paloaltonetworks.com/malicious-operations-of-exposed-iam-keys-cryptojacking/">Unit 42, Oct 2023).</a></p><p>2️⃣ <strong>No MFA</strong> → No <strong>Multi-Factor Authentication</strong>? They can easily use stolen credentials.</p><p>3️⃣ <strong>Privilege escalation</strong> → Once inside, attackers <strong>escalate privileges</strong>, targeting <strong>admin accounts or overly permissive IAM roles</strong>.</p><p>4️⃣ <strong>Subscription hijacking</strong> → They <strong>move your resources to another tenant</strong>, making detection even harder.</p><h3><strong>⚡ Rapid Setup: From AWS Account to Crypto Mining Farm :</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*80gQtsc3g5tyYrfjw-3pmQ.jpeg" /></figure><p>Once inside, <strong>attackers waste no time</strong>. Their goal? <strong>Turn your cloud into a mining farm within minutes</strong>.</p><p>If <strong>GPUs are available</strong>, they deploy <strong>NVIDIA GPU drivers</strong> to <strong>maximize computing power</strong>.</p><h4>🔍 <strong>Signs of Cryptojacking Activity:</strong></h4><p>➞ Sudden, <strong>massive deployment of GPU drivers.<br></strong>➞ Unknown accounts installing <strong>GPU extensions</strong> for no reason.<br>➞ <strong>Connections to known mining pools</strong></p><p>➥️ <strong>More details in this research: “</strong><a href="https://arxiv.org/pdf/2408.14554"><strong>Behavior-Based Detection of GPU Cryptojacking” (Ural Federal Univ, Aug 2024)</strong></a></p><h3><strong>🧐 Why Is Cryptojacking So Popular Among Attackers ?</strong></h3><p>Because it’s the <strong>perfect scam</strong>:</p><p>✅ <strong>Zero investment</strong> → No hardware costs, no electricity bills, no personal risk. <em>( Told you, the laziest attack..)</em><br>✅ <strong>Guaranteed profit</strong> → <strong>Your cloud infrastructure</strong> becomes their <strong>cash factory</strong>.<br>✅ <strong>Maximum stealth</strong> → Miners <strong>run silently in the background</strong>, undetected for weeks.</p><blockquote>With <strong>skyrocketing electricity costs</strong> and the increasing <strong>difficulty of traditional mining</strong>, <strong>cryptojacking has become a highly profitable business</strong>.</blockquote><h3><strong>🚨 The Hidden Costs to You and Your Business </strong>💸</h3><h4>➞ <strong>For You, the AWS Customer:</strong></h4><ul><li><strong>Skyrocketing AWS bills</strong> (up to $<strong>50,000+ in a few days</strong>).</li><li><strong>Slower applications</strong> or <strong>random crashes</strong> affecting your services.</li><li><strong>Increased attack surface</strong>, opening doors for <strong>more security breaches</strong>.</li></ul><h4>➞ <strong>For Your Business:</strong></h4><ul><li><strong>Significant financial losses</strong> due to unauthorized compute usage.</li><li><strong>Legal &amp; compliance risks</strong>, especially if <strong>sensitive data is compromised</strong>.</li><li><strong>Wasted resources</strong> on <strong>incident response and mitigation</strong>.</li></ul><h3>⚖️ <strong>The Legal Risks You Can’t Ignore :</strong></h3><p>Regulations like <strong>GDPR</strong> (EU) and <strong>CCPA</strong> (California) enforce <strong>strict compliance rules</strong>. If your <strong>AWS infrastructure is compromised</strong>, you could face <strong>severe consequences</strong>:</p><p>➤ <strong>Mandatory breach notification</strong> (72 hours under GDPR).<br>➤ <strong>Your company is liable</strong>, even if an external attack caused the breach.<br>➤ <strong>Fines up to 4% of global revenue</strong> or <strong>€20M</strong> (whichever is higher).<br>➤ <strong>You must prove</strong> that proper <strong>security measures</strong> were in place.</p><blockquote>💬 <em>“Cryptojacking is often seen as simple resource theft, but it frequently leads to serious data breaches.”</em></blockquote><h3><strong>🔎 How to Detect a Cryptojacking Attack?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*P78tKyiT3B7t0u8stWVm9A.jpeg" /></figure><h4>Look for these <strong>key warning signs</strong> in your AWS environment:</h4><p>➩ 📊 <strong>Unusual CPU/GPU consumption</strong> (spikes in compute usage).<br>➩ 💰 <strong>Unexplained AWS bill increase</strong> (sudden cost surges).<br>➩ 🔍 <strong>Suspicious connections</strong> to your cloud resources.<br>➩ 🌐 <strong>Outbound traffic to known mining pools</strong>.<br>➩ 🛠️ <strong>Use AWS security tools</strong> (CloudTrail, GuardDuty, SIEM logs).<br>➩ 🍯 <strong>Deploy honeypots</strong> to <strong>trap and analyze attackers</strong> before they cause damage. (<a href="https://kth.diva-portal.org/smash/record.jsf?pid=diva2%3A1887935&amp;dswid=8558">KTH Research Paper</a>)</p><h3><strong>🌍 Monitor for Mining Pool Connections</strong></h3><p>☞ As you know by now, cryptojackers hijack computing power to mine cryptocurrency, often relying on <strong>mining pools ; </strong>platforms where miners collaborate and share rewards. <br>☞ Monitoring these connections can help you detect unauthorized mining activity.</p><h4>⛏️ <strong>Common mining pool domains to watch out for:</strong></h4><ul><li><strong>nanopool.org</strong></li><li><strong>nicehash.com</strong></li><li><strong>supportxmr.com</strong></li><li><strong>hashvault.pro</strong></li><li><strong>zpool.ca</strong></li><li><strong>herominers.com</strong></li><li><strong>f2pool.com</strong></li><li><strong>minexmr.com</strong></li><li><strong>moneroocean.stream</strong></li><li><strong>miner.rocks</strong></li></ul><p>➥<em>️ </em><strong><em>Source: </em></strong><a href="https://www.microsoft.com/en-us/security/blog/2023/07/25/cryptojacking-understanding-and-defending-against-cloud-compute-resource-abuse/"><em>Microsoft Security Blog, 2023</em></a></p><h3><strong>🛠️ AWS Tools to Detect Cryptojacking</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zf9VWmUI3kAZf6wjOI6VTA.png" /></figure><blockquote>Now that you <strong>understand the threat</strong>, it’s time to <strong>secure your AWS environment</strong>… <em>🚀</em></blockquote><h3><strong>🛡️ How to Protect Your AWS Account from Cryptojacking</strong></h3><h4>🔐 <strong>Best practices to strengthen your cloud security:</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xhRBETvplqwRLy4TlBcnaw.png" /><figcaption>You should be good to go now!</figcaption></figure><p>📌 <strong>Reference: </strong><a href="https://attack.mitre.org/techniques/T1496/">MITRE ATT&amp;CK, Oct 2024</a></p><h3><strong>🚨 </strong>But.. Kenza, what should I do if my AWS Account is compromised ?</h3><p>➞ <strong>Revoke compromised IAM keys &amp; tokens</strong> to block attacker access.</p><p>➞ <strong>Stop all suspicious instances immediately</strong>.</p><p>➞ <strong>Analyze CloudTrail logs</strong> to track the attack’s origin.</p><p>➞ <strong>Rotate all exposed credentials</strong> and <strong>review IAM permissions</strong>.</p><p>➞ <strong>Contact AWS Support</strong> → They can help mitigate <strong>financial impact</strong>.</p><blockquote><strong><em>⚠️ Every second counts! The faster you respond, the lower the cost. ⚠️</em></strong></blockquote><h3><strong>🔮 Future of Cryptojacking: Emerging Trends</strong></h3><p>Threat actors are constantly evolving. Here’s what’s coming next:</p><blockquote><em>🧠 </em><strong><em>AI-powered cryptojacking :</em></strong></blockquote><ul><li>Uses <strong>AI to optimize mining operations</strong> while avoiding detection.</li><li><strong>Dynamically alters malware signatures</strong> to bypass security tools.<br> ➡️ <strong>Source:</strong> <a href="https://datagroupit.com/navigating-the-cybersecurity-horizon-check-points-projections-for-2024/">Datagroup, 2024</a></li></ul><h3><strong>📋 Ultimate Anti-Cryptojacking Checklist</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/1*gi6eBQjENcisgg_v3P13EQ.png" /><figcaption>Last table..I promise.</figcaption></figure><h3><strong>🎯 Final Thoughts: Secure Your Cloud Before malicious people turn it into a Gold Mine!</strong></h3><p>Cryptojacking is <strong>getting more sophisticated</strong> ; but <strong>with the right security measures, you can fight back</strong>.</p><p>🛡️ <strong>It’s an invisible heist. Only a well-locked system can protect you.<br></strong>So… are you ready to <strong>secure your AWS infrastructure?</strong> 🚀</p><p>Thanks for taking the time to read! Looking forward to reading your feedback as always!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*pFQwFXw0o_BgIuuwXS1UmQ.gif" /></figure><h3><strong>My Networks:</strong></h3><p>💬 <a href="https://www.linkedin.com/in/kenza-in-the-cloud">LinkedIn -Let’s Connect!</a></p><p>👾 <a href="https://discord.com/users/kzax01">Discord</a></p><p>🧪 <a href="https://github.com/Kzax01">GitHub -AWS Security Projects straight from 2065.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd0f316154cb" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/cryptojacking-when-hackers-hijack-your-cloud-to-mine-money-%EF%B8%8F-fd0f316154cb">💰Cryptojacking: When Hackers Hijack Your Cloud to Mine Money🏴‍☠️</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ DDoS Attacks in AWS Cloud: When Your Server Drowns Under Requests ]]></title>
            <link>https://awstip.com/ddos-attacks-in-aws-cloud-when-your-server-drowns-under-requests-825c3b265016?source=rss-c5cca0a05490------2</link>
            <guid isPermaLink="false">https://medium.com/p/825c3b265016</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ddos-attack]]></category>
            <dc:creator><![CDATA[Kenza In The Cloud]]></dc:creator>
            <pubDate>Mon, 03 Mar 2025 16:08:08 GMT</pubDate>
            <atom:updated>2026-10-19T12:36:03.031Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fQbLgwUhMMAbrRdINZR8YA.png" /></figure><p>Imagine: everything’s running smoothly on your AWS infrastructure. Your services are ticking like clockwork, your users are happy, and your business is thriving. Until… BOOM🚨 ! Your site slows down... Then it lags... Then it crashes. A DDoS attack is underway!! It’s like a tsunami of requests coming from everywhere, it engulfs your server in minutes.</p><p>In 2023, the average DDoS attack lasted 68 minutes, costing businesses an eye-watering <strong>$408,000 per attack</strong>. With organizations unprotected, the damage can add up fast. ( <a href="https://www.zayo.com/newsroom/average-ddos-attack-cost-businesses-nearly-half-a-million-dollars-in-2023-according-to-new-zayo-data/">Zayo Group, 2024</a>)</p><p>Let’s dive into this crucial topic together, shall we ? 🍵</p><blockquote>💡TL;DR: Go at the bottom of the page, a cool recap awaits you!</blockquote><h3><strong>📊 DoS vs DDoS: One Adversary or an Entire Army?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/770/1*alGtotfyJUGV5M3EY4n4PQ.jpeg" /><figcaption>DoS VS DDoS : FIGHT !</figcaption></figure><ul><li><strong>DoS (Denial of Service)</strong>: A single source sends a massive volume of requests to saturate a target. One individual blocks the entrance to your store.</li><li><strong>DDoS (Distributed Denial of Service)</strong>: Multiple sources (often a botnet with thousands of compromised devices) coordinate a massive attack. It’s like an entire crowd invading your store at once.</li></ul><p>In a cloud environment, the distributed nature of DDoS complicates defense because the traffic appears to come from legitimate clients.</p><blockquote><em>👉 Now that we’ve laid the theoretical groundwork, let’s get to the heart of the matter to</em> <strong><em>concretely understand how these attacks work in the AWS ecosystem.</em></strong></blockquote><h3><strong>🔍 Anatomy of an Attack: How Hackers Drown Your AWS</strong></h3><p>Let’s forget theoretical presentations and get practical. A DDoS attack is like thousands of people suddenly deciding to enter your store without buying anything, blocking access to real customers.</p><p>🎯 Three major categories of DDoS attacks:</p><ol><li><strong>Volumetric attacks</strong>:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/619/1*sM74lH2w87IAo_XjHCNr8g.png" /><figcaption>Imagine a tsunami of data completely drowning your bandwidth. On AWS, they often target Elastic IP addresses or your entry points: UDP/ICMP/ IPSec Floods.</figcaption></figure><p>2. <strong>Protocol-level attacks</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*vZ_sjbyO0Nf4qxpZ1lHkWA.png" /><figcaption>They exhaust server resources by abusing TCP/IP protocols : like the famous SYN floods, Ping Of Death (PoD), Smurf DDoS or Border Gateway Protocol (BGP)</figcaption></figure><p>3. <strong>Application-level attacks (Layer 7)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/555/1*haeiTvA4E69qUgAcoq1EHg.png" /><figcaption>More vicious, they target specific weaknesses in your application, such as massive HTTP GET/POST requests on a sensitive endpoint of your API Gateway or Application Load Balancer; or SlowLoris, RUDY (R-U-DEAD-YET?)</figcaption></figure><blockquote>Knowing the enemy is one thing, but how do you know if you’re currently under attack? <br><strong><em>Let’s look at the signs that should trigger your alarms.</em></strong></blockquote><h3><strong>🚨 Your Server Is Suffocating: Symptoms of an Ongoing Attack</strong></h3><p>Warning signs:</p><ul><li>📈 Sudden traffic spike</li><li>⚠️ Explosion of 5xx errors</li><li>🔥 CPU and latency spikes</li><li>❌ Massive increase in HTTP requests without apparent reason</li></ul><h4>🔍 Specific metrics to monitor 🔍</h4><ul><li>NetworkIn &gt; 2x the usual average for more than 5 minutes (CloudWatch)</li><li>RequestCount in CloudFront increasing by 300% for no reason</li><li>5xx Error Rate above 10% for more than 2 minutes (CloudWatch Logs / Elastic Load Balancer)</li><li>TargetResponseTime going from milliseconds to seconds (Elastic Load Balancer)</li><li>Requests abnormally concentrated on a geographic region (CloudFront)</li></ul><p><a href="https://docs.aws.amazon.com/whitepapers/latest/aws-best-practices-ddos-resiliency/metrics-and-alarms.html">→ More Info here</a>.</p><blockquote><strong><em>Now that you know how to detect an attack, let’s move on to the weapons AWS provides to defend yourself effectively.</em></strong></blockquote><h3><strong>🛡️ The Anti-Tsunami Arsenal: Your AWS Shield Against DDoS</strong></h3><p>AWS offers you a complete arsenal against DDoS attacks. Here’s what you need to know at a glance:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qF8yzyb_o5JSGEl9QpY88w.png" /></figure><h4>→ <strong>Free and Premium Protection :</strong></h4><p><strong>🔒 AWS Shield Standard ; Basic protection, free and automatic for everyone :</strong><br>- Included by default in all your AWS services.<br>- Protects against the most common DDoS attacks.<br>- No configuration needed.</p><p><strong>🛡️AWS Shield Advanced ; For critical applications ($3000/month):</strong><br>- Enhanced protection against all types of attacks.<br>- 24/7 support with dedicated DDoS experts.<br>- Reimbursement of costs related to spikes during attacks.</p><h4>→ <strong>Intelligent Traffic Filtering :</strong></h4><p><strong>🛑 AWS WAF ; Your web application firewall : <br>- </strong>Create rules to block attackers.<br>- Limit requests per IP.<br>- Filter suspicious behaviors. <br>- Block OWASP Top 10 threats.</p><h4>→ <strong>Storm-Resistant Architecture</strong></h4><p>Instead of listing all services separately, opt for this layered approach:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s3u2rAncb9dMkr7--virTg.png" /><figcaption>This architecture leverages multiple AWS services to protect against DDoS attacks, including AWS Shield, AWS WAF, CloudFront, Route 53, API Gateway, VPC, Elastic Load Balancer, and EC2, creating a multi-layered defense that filters and mitigates various attack types before reaching the application.</figcaption></figure><blockquote>Tools are essential, but nothing beats a concrete example to understand their effectiveness. <br><strong><em>Let’s examine how AWS handled one of the largest DDoS attacks in recent history.</em></strong></blockquote><h3><strong>🦈 When AWS Tamed the Monster: The 2.3 Tbps Mega-Attack</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p2uqwxFogzSAnGF-35HMPg.jpeg" /></figure><p>In February 2020, AWS had to face the largest DDoS attack ever recorded at the time: 2.3 terabits per second! To give you an idea, that’s equivalent to downloading 580 HD movies every second.</p><p>The attack exploited the CLDAP protocol as an amplifier, sending requests with spoofed IPs to vulnerable servers, which responded with an intensity multiplied by 70.</p><blockquote>→ AWS’s response? Shield Advanced detected and diverted malicious traffic, avoiding any service interruption for the targeted customer.</blockquote><blockquote>Lesson: With the right strategy, even a record attack can’t bring you down.</blockquote><p>→<a href="https://www.a10networks.com/blog/aws-hit-by-largest-reported-ddos-attack-of-2-3-tbps/">More info here.</a></p><blockquote><em>💡</em> This case study illustrates the effectiveness of protections, but what about the consequences if you neglected to equip yourself?<br> <strong><em>Let’s now talk about the real risks and associated costs.</em></strong></blockquote><h3><strong>💰 The Price of Inaction: What a DDoS Attack Will Really Cost You</strong></h3><p>⚠️ <strong>Operational impact</strong>: Your services are offline, your customers flee.<br>⚠️ <strong>Financial impact</strong>: Loss of revenue, infrastructure costs explode.<br>⚠️ <strong>Reputational impact</strong>: Once trust is broken, it’s hard to regain.</p><h4><strong>🔐 Protecting Without Breaking the Bank :</strong></h4><p>AWS offers several shields:</p><p>🛡️ <strong>Shield Standard</strong> → Free, it offers basic protection against the most common attacks. A must-have.</p><p>🛡️ <strong>Shield Advanced</strong> → $3,000/year, but essential for critical applications. It reduces mitigation costs and includes 24/7 response.</p><p>🛡️ <strong>WAF</strong> → Starting at $5/month to block malicious requests before they reach your backend.</p><blockquote><strong><em>💡 Do the math: investing in protection costs less than downtime that ruins your reputation and revenue.</em></strong></blockquote><h3><strong>📜 The Legal Weight of an Incident</strong></h3><p>If your service falls under a prolonged DDoS, expect legal obligations:</p><ul><li>Documentation of the incident to prove your diligence.</li><li>Notification to regulators (GDPR, CCPA) in case of impact on users.</li><li>Response plan compliant with ISO/NIST standards to avoid sanctions.</li></ul><blockquote>Knowing the risks is essential, but knowing how to react in the middle of a storm is just as important. <strong><em>Let’s imagine an attack scenario and detail step by step the appropriate response.</em></strong></blockquote><h3>🔴 <strong>Code Red: Action Plan for a DDoS Attack</strong></h3><p>Midnight… All is quiet… 🌆<br>Then suddenly, your CloudWatch dashboard goes crazy: abnormal traffic detected. In seconds, your servers are suffocating under the load…It’s a DDoS attack!! <br> Don’t panic, I got you. Here’s how to react effectively :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7kUeiwjWw7AaWNPLNb_PCw.png" /></figure><blockquote><em>💡 </em><strong><em>In a nutshell</em></strong><em>: Have a cup of coffee ☕, Detect quickly, react with protections and adjust infrastructure, then coordinate communication with the team and customers, and seek AWS support if needed.</em></blockquote><p>Reacting during an attack is crucial, but the real victory is prepared well before. Let’s now look at practices that can significantly strengthen your resilience to DDoS attacks.</p><h3><strong>🔒 The Impregnable Fortress: Best Practices That Really Make a Difference</strong></h3><p>These recommendations are based on real experiences:</p><p><strong>✅ Multi-AZ Architecture</strong>: Distribute your resources across at least three availability zones.</p><p><strong>✅ Aggressive Caching</strong>: Configure CloudFront to minimize calls to your origin.</p><p><strong>✅ Protection of Sensitive Resources</strong>: Place your databases in private subnets.</p><p><strong>✅ Regular Testing</strong>: Simulate controlled DDoS attacks during off-peak hours.</p><p><strong>✅ Automated Responses</strong>: Create Lambda functions that automatically react to alerts.</p><p><strong>✅ Strict ACLs and Security Groups</strong>: Limit authorized communications.</p><h3><strong>📋 Preparation Checklist (Are You Really Ready?) 📋</strong></h3><p>Being well prepared today is important, but anticipating tomorrow’s threats is just as crucial. Let’s examine emerging trends and how defenses are evolving to face them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*-IRYUeKIE7RPIpPd2nSjbw.gif" /></figure><h3><strong>👾 The Future of Threats: Tomorrow’s DDoS Attacks Are Already Coming</strong></h3><p>DDoS attacks are constantly evolving:</p><ul><li><strong>DDoS-as-a-Service</strong>: Attack services available for purchase on the dark web, making these attacks accessible even to non-experts.</li><li><strong>Smarter Attacks</strong>: Increasing use of AI to bypass traditional defenses and adapt to countermeasures.</li><li><strong>AWS Innovates in Response</strong>: Shield and WAF continuously improve their detection and filtering algorithms.</li></ul><h4><strong>🤖 The Army of Connected Objects: The Growing Threat of IoT Botnets</strong></h4><p>The explosion of connected devices creates a new playground for attackers:</p><ul><li><strong>Power</strong>: Attacks reaching 1 Tbps with only 100,000 IoT devices</li><li><strong>Detection Difficulties</strong>: Traffic comes from legitimate devices</li><li><strong>Sophistication</strong>: New botnets use advanced evasion techniques</li></ul><blockquote>Facing these constantly evolving threats, it’s important to understand where AWS’s responsibility ends and yours begins.<strong><em> <br>Let’s clarify this crucial point that is often misunderstood.</em></strong></blockquote><h3><strong>🤝 Who Does What? The Shared Anti-DDoS Responsibility Model</strong></h3><p>Careful, AWS isn’t responsible for everything! Here’s how anti-DDoS protection is divided:</p><h4><strong>🛡️ AWS Responsibilities:</strong></h4><ul><li>Protection of the underlying infrastructure</li><li>Global network and absorption capacity</li><li>Automatic detection of volumetric attacks</li><li>Basic tools like Shield Standard</li></ul><h4><strong>🔐 Your Responsibilities:</strong></h4><ul><li>Correct configuration of security services</li><li>Implementation of security groups and ACLs</li><li>Custom monitoring and alerts</li><li>Activation and configuration of advanced protections</li><li>Training your teams on emergency procedures</li></ul><p>All this technical jargon can seem intimidating for beginners. Let’s take a break to clarify the key terms that every AWS professional should know.</p><h3><strong>📚 Talk Like a Pro: The Anti-DDoS Dictionary for Beginners</strong></h3><p>To help you understand all these technical terms:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C3ScwdKKIP1Y2z4MQmxekg.png" /><figcaption>Hope it helps.</figcaption></figure><h3><strong>🔰 SOS Beginners: 7 Steps for Immediate Protection</strong></h3><p>If you’re new to the subject, here’s where to start:</p><p>1️⃣ <strong>Step 1</strong>: Activate AWS Shield Standard (it’s free and automatic).<br>2️⃣ <strong>Step 2</strong>: Put CloudFront in front of your public web applications.<br>3️⃣ <strong>Step 3</strong>: Configure security groups to limit open ports.<br>4️⃣ <strong>Step 4</strong>: Activate basic logging on CloudTrail.<br>5️⃣ <strong>Step 5</strong>: Create simple alerts in CloudWatch to detect traffic spikes.<br>6️⃣ <strong>Step 6</strong>: Learn to use AWS WAF for basic rules.<br>7️⃣ <strong>Step 7</strong>: Prepare a simple document with “who to contact” in case of an attack.</p><h3><strong>🎯 Conclusion: Be Ready Rather Than Sorry</strong></h3><p>DDoS attacks in the AWS cloud are no longer a question of “if” but “when”. The good news? With the combination of dedicated AWS services and a well-thought-out architecture, you can create an incredibly resilient environment.</p><p>Remember: every layer of protection counts. Start with the basics (Shield Standard, good architectural practices), then evaluate if more advanced protections are necessary for your specific use case.</p><p>So, is your AWS stack ready to face the next wave of DDoS attacks? If you have questions or experiences to share on this topic, don’t hesitate to share! I love discussing cybersecurity among cloud enthusiasts! 🚀</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*bTbhxH144AtsjDqGJUg8yA.gif" /></figure><p>Thanks for taking the time to read! 💖<br><strong>Sources and Resources 📚<br>- </strong><a href="https://www.akamai.com/site/en/documents/white-paper/akamai-8-steps-to-a-ddos-mitigation-plan-white-paper.pdf">Akamai : Making a DDoS Proection Plan</a><br>- A<a href="https://docs.aws.amazon.com/whitepapers/latest/aws-best-practices-ddos-resiliency/protecting-api-endpoints-bp4.html">WS Best Practices for DDoS Resiliency : AWS Whitepaper</a><br>- <a href="https://www.cloudflare.com/fr-fr/learning/ddos/what-is-a-ddos-attack/">CloudFare</a><br><a href="https://www.cisa.gov/sites/default/files/2024-03/understanding-and-responding-to-distributed-denial-of-service-attacks_508c.pdf">- MS-ISAC</a><br>- <a href="https://www.imperva.com/blog/with-slas-for-ddos-mitigation-the-devil-is-in-the-details/">Imperva</a></p><h3>My networks:</h3><p>💬 <a href="https://www.linkedin.com/in/kenza-in-the-cloud">LinkedIn : Let’s Connect! </a><br>👾<a href="https://discord.com/users/kzax01"> Discord </a><br>🧪 <a href="https://github.com/Kzax01">GitHub : AWS Security Projects straight from 2065.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=825c3b265016" width="1" height="1" alt=""><hr><p><a href="https://awstip.com/ddos-attacks-in-aws-cloud-when-your-server-drowns-under-requests-825c3b265016">🌊 DDoS Attacks in AWS Cloud: When Your Server Drowns Under Requests 💥</a> was originally published in <a href="https://awstip.com/">AWS Tip</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ 70% of Cloud Breaches Start Here: The Misconfiguration Attack Explained ⚙️]]></title>
            <link>https://awstip.com/70-of-cloud-breaches-start-here-the-misconfiguration-attack-explained-%EF%B8%8F-3b7403559432?source=rss-c5cca0a05490------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b7403559432</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-security]]></category>
            <category><![CDATA[misconfiguration]]></category>
            <dc:creator><![CDATA[Kenza In The Cloud]]></dc:creator>
            <pubDate>Tue, 25 Feb 2025 16:41:56 GMT</pubDate>
            <atom:updated>2026-10-19T12:46:57.472Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>🚨70% of Cloud Breaches Start Here: The Misconfiguration Attack Explained ⚙️</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tgsjV9vHPZ7cpBlnM7cP1w.png" /></figure><p>Everyone’s talking about the cloud these days. AWS, Azure, Google Cloud… It’s like the <strong><em>Avengers of modern computing</em></strong>. But even superheroes have their <strong>weaknesses</strong>. And in the cloud, one of the most dangerous ones is <strong>misconfiguration ⚡</strong>.</p><p>You might be thinking: <em>“Okay, it’s just a settings issue, nothing to freak out about.”</em> <strong>Wrong!</strong> Misconfigurations are exactly what open the door to the worst cyberattacks. And trust me, this happens way more often than you’d think.</p><blockquote>👉 <strong>Fun fact</strong>: According to a recent study from <a href="https://www.cloudwize.io/blog/cloud-data-breaches-in-2024-a-year-in-review/">Cloud Wize</a>, <strong>70% of cloud data breaches are caused by misconfigurations</strong>. And the scariest part? The <strong>average cost of a data breach hit $4.35 million in 2022</strong>. ( <a href="https://www.ibm.com/reports/data-breach">IBM</a>, 2024)<strong><em>💰</em></strong></blockquote><blockquote>💡TL;DR : Go at the bottom of the page, a cool recap awaits you!</blockquote><h3>→ <strong>Misconfigurations: Not Just About S3 📁</strong></h3><blockquote>“A single mistake can turn your cloud environment into an all-you-can-eat buffet for hackers” <em>- Kenza 2025 ✨</em>.</blockquote><blockquote>Some of the most common misconfigurations include:</blockquote><ul><li><strong>Misconfigured S3 buckets</strong> → Like leaving a safe wide open with a “help yourself” sign.</li><li><strong>Exposed EBS snapshots</strong> → Making copies of your sensitive data available for the world to see.</li><li><strong>Publicly accessible RDS databases</strong> → Like displaying your company’s financial records on a public billboard.</li><li><strong>Overly permissive EC2 security groups</strong> → Leaving all your windows open and letting anyone walk in.</li><li><strong>Misconfigured API Gateway</strong> → Handing out universal access keys to just about anyone.</li></ul><p>&gt; Each of these can lead to data leaks, regulatory fines, and a shredded reputation.</p><h4>↓ <strong>But what happens when these misconfigurations are exploited in the real world? Let’s look at a high-profile example. </strong>↓</h4><h3>→ <strong>Let Me Tell You a Story… Tesla, 2018 🚗</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*PUb14Vg5GQ8sbjRBRA-DNA.jpeg" /></figure><p>In 2018, Tesla nearly fell victim to a massive attack due to a <strong>misconfiguration</strong>. It all started with an <strong>IAM permissions issue</strong> (those little settings that control who has access to what).</p><p>A hacker managed to gain control over parts of Tesla’s cloud network… and guess what? <strong>They stole sensitive data.</strong> 🚨</p><p>➠ The outcome? <strong>Millions of dollars</strong> in response costs, plus some <strong>very bad PR aka </strong><em>Public Relations.</em></p><p>And all of this <strong>because of one poorly configured setting</strong>. See, just a tiny error can trigger <strong>a massive disaster</strong>.</p><h3>→ <strong>W</strong>hy a <strong>misconfiguration</strong> can be a <strong>disaster</strong> 🚨</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4BHYvMBE0M5uOBcJ8ypdDw.jpeg" /><figcaption>Most Common impacts due to a misconfig in AWS..</figcaption></figure><p>A poor configuration can lead to <strong>devastating</strong> consequences for both your clients and your business. Here’s how:</p><h4><strong>💥 Client &amp; Business Impact :</strong></h4><ul><li><strong>Exposure of sensitive client data</strong> → <strong>Their</strong> data in the wrong hands = A nightmare for them.</li><li><strong>Loss of trust</strong> → A data breach is a <strong>reputation in freefall</strong>.</li><li><strong>Financial loss</strong> → Fines, compensations, and incident costs… it can get <strong>expensive</strong>.</li><li><strong>Hidden costs</strong> → Investigation, higher insurance rates, business interruption… plus the potential loss of certifications.</li></ul><h4><strong>⚖️ And what about the law?</strong></h4><p>The <strong>legal consequences</strong> can be <strong>severe</strong>:</p><ul><li><strong>GDPR</strong>: Failing to report a breach within <strong>72 hours</strong> could lead to fines.</li><li><strong>PCI DSS</strong>: A breach involving credit card data can result in <strong>heavy penalties</strong>.</li><li><strong>HIPAA</strong>: In healthcare, a breach could cause you to <strong>lose your license</strong>.</li><li><strong>SOX</strong>: For publicly traded companies, poor management = <strong>legal action</strong>.</li></ul><blockquote>In short: A cloud misconfiguration is a legal, financial, and reputational risk that can have serious consequences. <br><strong>So how do you know if you’re under attack because of a misconfiguration?</strong></blockquote><h3>→<strong> How to Spot an Attack? 🕵️</strong></h3><p>If you spot these signs, it’s time to raise the alarm 🚨:</p><ul><li><strong>Unusual access to your S3 buckets or other cloud resources?</strong> Suspicious.</li><li><strong>A sudden spike in API requests?</strong> Someone’s poking around.</li><li><strong>Strange changes in IAM permissions (like a user giving themselves admin access)?</strong> Bad news.</li><li><strong>New IAM users appearing out of nowhere?</strong> Magic or a security breach.</li><li><strong>Logs mysteriously disappearing?</strong> Someone’s covering their tracks.</li><li><strong>Weird network traffic heading to unknown destinations?</strong> Time to investigate.</li></ul><p>Luckily, <strong>AWS provides some powerful tools to detect these threats</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HBn4iGsEUY1hXZRUJmyLJw.png" /><figcaption><em>💡 Think of these </em><strong><em>like an insurance policy</em></strong><em> </em><strong><em>far cheaper than a data breach!</em></strong></figcaption></figure><h4>Now that you know how to detect an attack, let’s focus on prevention aka the best form of protection.</h4><h3>→<strong> How to Protect Yourself? 🛡️</strong></h3><p>Here’s the ultimate <strong>security checklist</strong> to avoid sleepless nights:</p><h4>➥ <strong>The Basics (but non-negotiable)</strong>:</h4><p>✔️ <strong>Strict IAM policies</strong> → Always follow the <strong>principle of least privilege</strong>.<br>✔️ <strong>Encryption everywhere</strong> → <strong>At rest, in transit no exceptions.<br></strong>✔️ <strong>Mandatory MFA</strong> → This is NOT optional!<br>✔️ <strong>Private S3 buckets by default</strong> → <strong>Don’t let your data be publicly accessible.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9ZF9G8XAxTIzQmOvmm2ApQ.jpeg" /><figcaption><em>Best Practices for S3 buckets.</em></figcaption></figure><h3>⚡ <strong>For Advanced Security:</strong></h3><p>✔️<strong>AWS Organizations</strong> → Properly <strong>segregate</strong> accounts.<br>✔️ <strong>Service Control Policies (SCPs)</strong> → <strong>Enforce strict guardrails.<br></strong>✔️ <strong>Infrastructure as Code (IaC)</strong> → Use <strong>Terraform or CloudFormation</strong> to prevent manual mistakes.<br>✔️ <strong>Key rotation automation</strong> → <strong>Change access keys regularly</strong>, like you would with your house locks.</p><h4>But even the best technical controls won’t help if your team doesn’t know how to use them properly.</h4><h3>→ Train Your Teams: Security’s Secret Weapon! 👨‍💻</h3><p>A secure setup means nothing if your team isn’t <strong>trained</strong> to maintain it.</p><ul><li><strong>Continuous training</strong> → Even top engineers need regular security refreshers.</li><li><strong>Clear, up-to-date documentation</strong> → A well-maintained <strong>Notion page</strong> beats sticky notes any day.</li><li><strong>Incident simulations</strong> → Just like fire drills but for cyberattacks.</li><li><strong>Security monitoring &amp; threat intelligence</strong> → Because <strong>hackers never sleep</strong>.</li></ul><h4>Despite our best efforts, breaches can still happen. When they do, you need to act quickly and decisively.</h4><h3>→<strong> What If a Breach Happens? 🚨</strong></h3><p>Don’t panic and follow this <strong>battle plan</strong>:</p><p>✅ <strong>Identify the breach</strong> → Find the entry point <strong>ASAP</strong>.</p><p>✅ <strong>Mitigate the impact</strong> → Cut off access, change keys, stop the bleeding.</p><p>✅ <strong>Notify the right people</strong> → Customers, authorities… <em>(Reminder: GDPR gives you 72 hours.)</em></p><p>✅ <strong>Fix it and learn</strong> → One mistake is fine. <strong>Repeating it? Not okay.</strong></p><h3>→ <strong>Some Eye-Opening Stats You Should Know :</strong></h3><p><em>Just to put things in perspective:</em></p><ul><li><strong>50,000 DDoS attacks per day</strong> target cloud infrastructure. <em>(</em><a href="https://blog.cloudflare.com/ddos-threat-report-for-2024-q2/"><em>Cloudflare</em></a><em>, 2024)</em></li><li><strong>204 days</strong> on average to detect a data breach. <em>(</em><a href="https://ediscoverytoday.com/2024/08/08/2024-cost-of-a-data-breach-report-by-ibm-cybersecurity-trends/"><em>IBM</em></a><em>, 2024)</em></li><li><strong>82% of cloud misconfigurations come from human error, not software flaws. </strong><em>(</em><a href="https://www.sentinelone.com/cybersecurity-101/cloud-security/cloud-security-statistics/"><em>SentinelOne</em></a><em>, 2024)</em></li></ul><blockquote><strong>➡️🚨 Most targeted industries? Finance, healthcare, and retail. <em>(</em></strong><a href="https://www.cnil.fr/fr/violations-massives-de-donnees-en-2024-quels-sont-les-principaux-enseignements-mesures-a-prendre"><strong><em>CNIL</em></strong></a><strong><em>, France)</em></strong></blockquote><p>Annnnd that’s a wrap!!! Big thanks for sticking with me till the end! Hope you picked up some useful tips to secure your cloud.</p><p><strong>Now, tell me : Have you ever seen a wild misconfiguration in production? </strong>Drop your craziest stories in the comments! 👇</p><p>Cloud security is like learning to ride a bike ; it feels complicated at first, but with the right habits, it becomes second nature.</p><blockquote>Stay vigilant, keep your configs clean, and <strong>train your teams</strong>. And remember: <strong>the most dangerous attack is the one you didn’t see coming.</strong></blockquote><p>Now go secure that cloud and <strong>may the (secure) cloud force be with you!</strong> 💪☁️</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*3Bb4WRqB7noQ5UOV8xP8dw.gif" /></figure><h3>My networks:</h3><p>💬 <a href="https://www.linkedin.com/in/kenza-in-the-cloud">LinkedIn : Let’s Connect! </a><br>👾<a href="https://discord.com/users/kzax01"> Discord </a><br>🧪 <a href="https://github.com/Kzax01">GitHub : AWS Security Projects straight from 2065.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b7403559432" width="1" height="1" alt=""><hr><p><a href="https://awstip.com/70-of-cloud-breaches-start-here-the-misconfiguration-attack-explained-%EF%B8%8F-3b7403559432">🚨 70% of Cloud Breaches Start Here: The Misconfiguration Attack Explained ⚙️</a> was originally published in <a href="https://awstip.com/">AWS Tip</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ AWS & Exposed Credentials: The Mistake That Can Ruin You (And How To Avoid It -  I got you!)]]></title>
            <link>https://awstip.com/aws-exposed-credentials-the-mistake-that-can-ruin-you-and-how-to-avoid-it-i-got-you-722c464a0575?source=rss-c5cca0a05490------2</link>
            <guid isPermaLink="false">https://medium.com/p/722c464a0575</guid>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[cyberattack]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Kenza In The Cloud]]></dc:creator>
            <pubDate>Mon, 17 Feb 2025 17:30:57 GMT</pubDate>
            <atom:updated>2026-10-19T12:47:59.635Z</atom:updated>
            <content:encoded><![CDATA[<h3>🚨 AWS &amp; Exposed Credentials: The Mistake That Can Ruin You (And How To Avoid It - I got you!)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u6FW01qn-ycdtgCOKdgx7Q.png" /></figure><p>Okay, imagine this. You’re chilling, setting up your cloud server on AWS, and bam! A few days later, you find out your sensitive data got stolen because someone accessed your credentials… This has actually happened to a ton of companies.</p><p>In fact, over <strong>70%</strong> of cloud data breaches are caused by poor credential management. Yep, you heard that right, <strong>credentials</strong>!</p><p>You’re wondering, Why does this matter? Because a simple password mistake can open the door to massive damage, like a snowball effect… ⛄️</p><p>Alright, grab your coffee ☕️, and let’s dive into why credential compromise is a nightmare for your security.</p><blockquote>💡TL;DR : Go at the bottom of the page, a cool recap awaits you!</blockquote><h3>🗝️ It’s Not Just About Passwords</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wju4P4TjABdPneks5PsISw.jpeg" /><figcaption>credit : Varonis</figcaption></figure><p>Okay, so let’s say you’ve got a killer password for your AWS account, but… is it <em>really</em> that killer?<br>If your password is ‘1234’, ‘password’, or ‘Admin123’, it’s like leaving the key under the doormat. You feel me?</p><p>➠ But hold on ⏸ , passwords aren’t the only credentials you need to protect!<br>In the cloud, you’ve got a whole arsenal of credentials to handle:</p><ul><li><strong>API Keys</strong>: These little keys let your apps talk to each other. You use them to automate processes, but if they fall into the wrong hands…</li><li><strong>SSL/TLS Certificates</strong>: To secure your web connections. A breach here and a hacker can intercept all your data in a “Man In the Middle” style, you know what I mean?</li><li><strong>Authentication Tokens</strong>: These temporary tokens prove your identity for a certain period. What happens if someone steals them?</li><li><strong>Federated Identities</strong>: When you log in to other services with your Google or GitHub account. Seems super convenient, but it’s risky if you don’t manage the permissions well.</li></ul><blockquote>So yeah, credential compromise is when a hacker gets their hands on one of these precious keys and logs into your cloud resources. And once they’re in… it can all go downhill. <strong><em>😬</em></strong></blockquote><h3><strong>➡️ Capital One, 2019:</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MiaOhFqu3kRnjActyLoQlg.jpeg" /><figcaption>Remember the Capital One breach in 2019?</figcaption></figure><p>Spoiler alert: A poorly secured S3 bucket + unprotected access = 100M data stolen ; see what a misconfig can do..<br>Second spoiler alert (<em>I know, I’m on fire today!</em>): Big stuff coming on this topic, Stay tuned! 🔥</p><h3><strong>⚠️ Unsecured Cloud? Here’s What You’re REALLY Risking! ⚠️</strong></h3><h4>The consequences can be <em>devastating</em>:</h4><ul><li><strong>Exposure of Personal Data</strong>: Hackers can steal sensitive info like names, addresses, credit card numbers… It can even ruin someone’s life..</li><li><strong>Loss of Trust &amp; Reputation</strong>: When your clients find out you left the door wide open, their trust in you takes a hit.</li><li><strong>Financial Loss</strong>: Fines, incident response costs, and system recovery can get <em>real</em> expensive. Not to mention the legal risks if you violate regulations like GDPR.</li><li><strong>Shadow IT</strong>: If your employees create cloud resources without supervision, it’s like an open door to vulnerabilities. A misconfigured, exposed S3 bucket? <em>Classic Shadow IT move.</em></li><li><strong>Cryptojacking</strong>: Hackers can use your resources to mine cryptocurrencies, and guess who’s paying the bill? <em>You!</em> 🎉</li></ul><h3><strong>⚖️What About the Law? ⚖️</strong></h3><p>Brace yourself, ’cause the legal side is no joke:</p><ul><li><strong>GDPR in Europe</strong>: Up to 4% of global revenue in fines.</li><li><strong>PCI DSS for Card Data</strong>: Mandatory audits and hefty penalties.</li><li><strong>HIPAA</strong>: Criminal penalties possible for health data breaches.</li></ul><p>And don’t forget the notification obligations! In many countries, you must notify both authorities AND the affected individuals within 72 hours. Let’s just say… you’re not going to get much sleep.</p><h3><strong>🔐 Managing Secrets: Your New Best Friend 🔐</strong></h3><p>Let’s talk about how to handle all these secrets the right way:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKFzUqardeyjTt5zqo5hcg.png" /><figcaption>AWS Secrets Manager allows you to manage, retrieve, and rotate database credentials, API keys, and other secrets throughout their lifecycle.</figcaption></figure><ul><li>Use a dedicated secrets manager (AWS Secrets Manager, HashiCorp Vault ; <a href="https://docs.aws.amazon.com/prescriptive-guidance/latest/secure-sensitive-data-secrets-manager-terraform/introduction.html">more info here</a>). <br>Set up automatic key rotation policies to make sure they don’t stay too long in your system.</li><li>Set up automatic secret rotation (every 30–90 days). This reduces the lifespan of any compromised secrets.</li><li><strong>Encrypt ALL</strong> your secrets, even the ones that don’t seem important. A breach on a small secret and everything can go south.</li><li>Audit who has access to what. Yes, even Bob from marketing! It’s easy to neglect non-technical accounts, but that’s where vulnerabilities often lie.</li></ul><h3><strong>🚨 Warning Signs You Shouldn’t Ignore 🚨</strong></h3><ul><li><strong>Suspicious logins</strong>: A login at 3 AM from Antarctica 🤔? 🚩🚩🚩</li><li><strong>Excessive API requests</strong>: A bot might be scanning your infra.</li><li><strong>Cloud bill skyrocketing</strong>: Is someone mining crypto without your knowledge? 🏴‍☠️</li><li><strong>Unauthorized IAM changes</strong>: Someone might be trying to give themselves admin access…</li></ul><h3>🛠️ Your Toolbox 🛠️</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/949/1*iWODjnSzoQvTCq_VoU85Lw.png" /><figcaption>I found it easier to read it that way</figcaption></figure><h3><strong>🛡️ 6 Foolproof Tactics to Secure Your Cloud🛡️</strong></h3><p>Here are the key strategies to protect your cloud like a pro:</p><ul><li><strong>Zero Trust Architecture (ZTA)</strong>: Trust no one, verify everyone, even inside your own network.</li><li><strong>Biometric Authentication</strong>: Secure access with solutions like Okta or Microsoft Entra ID using biometrics (fingerprints, facial recognition).</li><li><strong>MFA + Strong Passwords</strong>: Enable MFA on AWS IAM or Okta to secure access to your sensitive resources. 🔑</li><li><strong>Principle of Least Privilege</strong>: Use AWS IAM policies to give only the permissions each user actually needs, reducing risks.</li><li><strong>WAF &amp; CASB Solutions</strong>: Protect your web apps with AWS WAF or Cloudflare WAF, and use AWS Macie to control access to sensitive data (S3 buckets) and ensure compliance.</li><li><strong>AI &amp; Machine Learning</strong>: Detect real-time attacks with tools like Darktrace and CrowdStrike, which analyze user behavior to prevent threats.</li></ul><blockquote><strong>💡 Pro Tip</strong>: Automate threat detection and access management with Identity Threat Detection &amp; Response (ITDR) to get ahead of attacks before they even happen.</blockquote><p><strong>🚨 What to Do If It Happens? 🚨</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*26k7IGP59p8W4-Wg_Sp8Zw.gif" /><figcaption>There you go!</figcaption></figure><blockquote>🔹 Tip: Set up an incident playbook and automate some responses with AWS Lambda and Amazon EventBridge to minimize the damage.</blockquote><p>Annnnd that’s a wrap!!! Big thanks for sticking with me till the end! Hope you picked up some useful tips to secure your cloud.</p><p>Cloud security is kinda like a sport: it takes practice and constant awareness. But with the right tools, you can protect your resources and avoid costly mistakes. 🚀</p><p>If you want to level up and secure your AWS environment like a pro, stay tuned! And feel free to share your thoughts ; I’m always open to feedback. ✨</p><p>Don’t forget to subscribe so you don’t miss out, tons of articles are coming to help you level up your cloud security game even more. 💪</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*NOSe800cA4jK5WoiTBy7MQ.gif" /></figure><h3>My networks:</h3><p>💬 <a href="https://www.linkedin.com/in/kenza-in-the-cloud">LinkedIn : Let’s Connect! </a><br>👾<a href="https://discord.com/users/kzax01"> Discord </a><br>🧪 <a href="https://github.com/Kzax01">GitHub : AWS Security Projects straight from 2065.</a></p><blockquote>Sources and Resources 📚</blockquote><blockquote>- AWS Security Best Practices<br>- Verizon Data Breach Investigations Report 2024<br>- NIST Guide on Identity Management<br>- CrowdStrike Cloud Threat Reports</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=722c464a0575" width="1" height="1" alt=""><hr><p><a href="https://awstip.com/aws-exposed-credentials-the-mistake-that-can-ruin-you-and-how-to-avoid-it-i-got-you-722c464a0575">🚨 AWS &amp; Exposed Credentials: The Mistake That Can Ruin You (And How To Avoid It -  I got you!)</a> was originally published in <a href="https://awstip.com/">AWS Tip</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>