Elastio × AWS GuardDuty — Automated scans triggered by GuardDuty malware findings
Author
Anshuman Biswas
Date Published

GuardDuty’s release of malware scanning on AWS Backup is an important enhancement to the AWS ecosystem, reflecting growing industry recognition that inspecting backup data has become a core pillar of cyber resilience.
But real-world incidents show that ransomware often leaves no malware behind, making broader detection capabilities for encryption and zero-day attacks increasingly essential.
Across industries, there are countless examples of enterprises with premium security stacks in place - EDR/XDR, antivirus scanners, IAM controls - still suffering extended downtime after an attack because teams couldn’t reliably identify an uncompromised recovery point when it mattered most. That’s because ransomware increasingly employs fileless techniques, polymorphic behavior, living-off-the-land tactics, and slow, stealthy encryption. These campaigns often reach backup and
replicated copies unnoticed, putting recovery at risk at the very moment organizations depend
on it.
As Gartner puts it:
Modern ransomware tactics bypass traditional malware scanners, meaning backups may appear ‘clean’ during scans but prove unusable when restored. Equip your recovery environment with advanced capabilities that analyze backup data using content-level analytics and data integrity validation.”
— Gartner, Enhance Ransomware Cyber Resilience With A Secure Recovery Environment, 2025
This is the visibility gap Elastio was designed to close.
In this post, we walk through how Elastio’s data integrity validation works alongside AWS GuardDuty to support security and infrastructure teams through threat detection all the way to recovery confidence and why integrity validation has become essential in the age of identity-based and fileless attacks.
What is AWS GuardDuty?
AWS GuardDuty is a managed threat detection service that continuously monitors AWS environments for malicious or suspicious activity. It analyzes signals across AWS services, including CloudTrail, VPC Flow Logs, DNS logs, and malware protection scans, and produces structured security findings.
GuardDuty integrates natively with Amazon EventBridge, which means every finding can be consumed programmatically and routed to downstream systems for automated response.
For this integration, we focus on GuardDuty malware findings, including:
- Malicious file findings in S3
- Malware detections in EC2 environments
These findings are high-confidence triggers that indicate potential compromise and warrant immediate validation of recovery data.
Why a GuardDuty Finding Should Trigger Recovery Validation
Malware detection is important, but it is no longer sufficient to validate data recoverability.
Identity-based attacks dominate cloud breaches
Today’s attackers increasingly rely on stolen credentials rather than exploits. With valid identities, they can:
- Use legitimate AWS APIs
- Access data without dropping malware
- Blend into normal operational behavior
In these scenarios, there may be nothing malicious to scan, yet encryption or tampering can still occur.
Fileless and polymorphic ransomware evade signatures
Many ransomware families:
- Run entirely in memory
- Continuously mutate their payloads
- Avoid writing recognizable artifacts to disk
Signature-based scanners may report “clean,” even as encryption spreads.
Zero-day ransomware has no signatures
By definition, zero-day ransomware cannot be detected by known signatures until after it has already caused damage - often widespread damage.
The result is a dangerous failure mode: backups that scan clean but restore encrypted or corrupted data.
Why Integrity Validation Changes the Outcome
Elastio approaches ransomware from the impact side.
Instead of asking only “is malware present?”, Elastio validates:
- Whether encryption has occurred
- What data was impacted
- When encryption started
- Which recovery points are still safe to restore
The timeline above reflects a common real-world pattern:
- Initial access occurs quietly
- Encryption begins days or weeks later
- Backups continue, unknowingly capturing encrypted data
- The attack is only discovered at ransom time
Without integrity validation, teams cannot know with confidence that their backups will work when they need them. This intelligence transforms a GuardDuty finding from an alert into an actionable recovery decision.
Using GuardDuty as the Trigger for Recovery Validation
Elastio’s new GuardDuty integration automatically initiates data integrity scans when GuardDuty detects suspicious or malicious activity.
Instead of stopping at alerts, the integration immediately answers the implied next question: Did this incident affect our data, and can we recover safely?
By validating backups and recovery assets in response to GuardDuty findings, Elastio reduces response time, limits attacker leverage, and enables faster, more confident recovery decisions.
Architecture Overview

At a high level:
- GuardDuty generates a malware finding
- The finding is delivered to EventBridge
- EventBridge routes the event into a trusted sender EventBus
- Elastio’s receiver EventBus accepts events only from that sender
- Elastio processes the finding and starts a targeted scan
- Teams receive recovery-grade intelligence
Including:
Ransomware detection results
File- and asset-level impact
Last known clean recovery point
Optional forwarding to SIEM or Security Hub
The critical design constraint: trusted senders
Each Elastio customer has a dedicated Receiver EventBus. For security reasons, that receiver only accepts events from a single allowlisted Sender EventBus ARN.
This design ensures:
- Strong tenant isolation
- No event spoofing
- Clear security boundaries
To support scale, customers can route many GuardDuty sources (multiple accounts, regions, or security setups) into that single sender bus. Elastio enforces trust at the receiver boundary.
End-to-End Flow

Step 1: GuardDuty detects malware
GuardDuty identifies a malicious file or suspicious activity in S3 or EC2 and emits a finding.
Step 2: EventBridge routes the finding
Native EventBridge integration allows customers to filter and forward only relevant findings.
Step 3: Sender EventBus enforces trust
All GuardDuty findings flow through the designated sender EventBus, which represents the customer’s trusted identity.
Step 4: Elastio receives and buffers events
The Elastio Receiver EventBus routes events into an internal queue for resilience and burst handling.
Step 5: Elastio validates recovery data
Elastio maps the finding to impacted assets and initiates scans that analyze both malware indicators and ransomware encryption signals.
Step 6: Recovery-grade results
Teams receive actionable results:
- Ransomware detection
- File-level impact
- Last known clean recovery point
- Optional forwarding to SIEM or Security Hub
What This Enables for Security and Recovery Teams
By combining GuardDuty and Elastio, organizations gain:
- Faster response triggered by high-signal findings
- Early detection of ransomware encryption inside backups
- Reduced downtime and data loss
- Confidence that restores will actually work
- Audit-ready evidence for regulators, insurers, and leadership
Supported Today
- S3 malware findings
- EC2 malware findings
EBS-specific handling is in progress and will be added as it becomes available.
Why This Matters in Practice
In most ransomware incidents, the challenge isn’t identifying a security signal - it’s understanding whether that signal corresponds to meaningful data impact, and what it implies for recovery.
Security and infrastructure teams often find themselves piecing together information across multiple tools to assess whether encryption or corruption has reached backups or replicated data. That assessment takes time, and during that window, recovery decisions are delayed or made conservatively.
By using GuardDuty findings as a trigger for integrity validation, customers introduce earlier visibility into potential data impact. When suspicious activity is detected, Elastio provides additional context around whether recovery assets show signs of encryption or corruption, and which recovery points appear viable.
This doesn’t replace incident response processes or recovery testing, but it helps teams make better-informed decisions sooner, particularly in environments where fileless techniques and identity-based attacks limit the effectiveness of traditional malware scanning.
Extending GuardDuty From Detection Toward Recovery Readiness
GuardDuty plays a critical role in surfacing high-confidence security findings. Elastio extends that signal into the recovery domain by validating the integrity of data organizations may ultimately depend on to restore operations.
Together, they help teams bridge the gap between knowing an incident may have occurred and assessing recovery readiness, with supporting evidence that can be shared across security, infrastructure, and leadership teams.
For organizations already using GuardDuty, this integration provides a practical way to connect detection workflows with recovery validation without changing existing security controls or response ownership.
Watch our discussion: Understanding Elastio & AWS GuardDuty Malware Scanning for AWS Backup
An open conversation designed to answer customer questions directly and help teams understand how these technologies work together to strengthen recovery posture.
- How signature-based malware detection compares to data integrity validation
- Real-world scenarios where behavioral and encryption-based detection matters
- How Elastio extends visibility, detection, and recovery assurance across AWS, Azure, and on-prem environments
- An early look at Elastio’s new integration launching at AWS re:Invent
Recover With Certainty
See how Elastio validates every backup across clouds and platforms to recover faster, cut downtime by 90%, and achieve 25x ROI.
Related Articles

Elastio and AWS recently hosted a joint webinar, “Modern Ransomware Targets Recovery: Here’s What You Can Do to Stay Safe.” The session brought together experts to unpack how ransomware tactics are evolving and what organizations need to do differently to stay resilient. A clear theme emerged. Attackers are no longer focused on disruption alone. They are deliberately sabotaging recovery. Ransomware Has Shifted From Disruption to Recovery Sabotage Modern ransomware no longer relies on fast, obvious encryption of production systems. Instead, attackers often gain access months in advance. They quietly study the environment, including backup architectures, replication paths, and retention windows. Encryption happens slowly and deliberately, staying below detection thresholds while corrupted data propagates into snapshots, replicas, and backups. By the time the attack is triggered and ransom is demanded, recovery options are already compromised. This represents a fundamental shift in risk. Backups are no longer just a safety net. They are a primary target. Ransomware Risk Is Unquantifiable Without Proven Clean Recovery Points Ransomware risk becomes impossible to quantify when organizations cannot prove their recovery data is clean. Boards, regulators, and insurers are no longer reassured by the mere existence of backups. They want to know how quickly recovery can happen, which recovery point will be used, and how its integrity is verified. Most organizations cannot answer these questions with confidence because backup validation is not continuous. The consequences are real. Extended downtime, board-level exposure, insurance gaps, and growing regulatory pressure under frameworks such as DORA, NYDFS, and PRA. Without proven clean recovery points, ransomware becomes an unbounded business risk rather than a technical one. The Three Pillars of Ransomware Recovery Assurance The webinar emphasized that real ransomware resilience depends on three pillars working together. Immutability and isolation ensure backups are tamper-proof and stored separately, protected by independent encryption keys. AWS capabilities such as logically air-gapped vaults support this foundation.Availability focuses on whether recovery can happen fast enough to meet business expectations, particularly when identity systems are compromised. Clean-account restores and multi-party approval become critical.Integrity, the most overlooked pillar, ensures backups are continuously validated to detect encryption, corruption, malware, and fileless attacks, and to clearly identify the last known clean recovery point. If any pillar fails, recovery fails. For more information: Resilience by design: Building an effective ransomware recovery strategy | AWS Storage Blog Malware Scanning Is Not Ransomware Detection The speakers drew a clear distinction between traditional malware scanning and what is required to defend against modern ransomware. Signature-based tools look for known binaries, but today’s attacks often run in memory, use polymorphic techniques, and encrypt data without leaving a detectable payload. In these cases, the absence of malware does not mean the absence of damage. Effective ransomware defense requires detecting the impact on data itself, including encryption, corruption, and abnormal change patterns, not just the presence of malicious code. Validation Enables Faster, Safer Recovery Without Paying Ransom A real-world case study illustrated the value of recovery validation. Attackers encrypted data gradually over several days, allowing compromised data to flow into backups that appeared intact but were unsafe to restore. Through targeted threat hunting, Elastio identified a clean recovery point from roughly six days earlier, enabling the company to restore operations without paying the ransom. With downtime costs often reaching millions per day, even small reductions in recovery time have outsized financial impact. The takeaway was simple. Knowing where to recover from matters more than recovering quickly from the wrong place. Key Takeaways Ransomware now targets recovery, not just production.Attackers gain access early, encrypt data slowly, and ensure corruption spreads into replicas and backups before triggering an attack. By the time ransom is demanded, recovery paths are often already compromised.Backups alone are not proof of recoverability.Without continuous validation, organizations cannot confidently identify a clean recovery point, making ransomware risk impossible to quantify.True ransomware resilience depends on three pillars.Immutability and isolation protect backups from tampering, availability ensures recovery meets business expectations, and integrity validation confirms recovery data is usable. If integrity fails, recovery fails.Malware detection is not ransomware detection.Fileless and polymorphic attacks often evade signature-based tools. Detecting the impact on data, such as encryption and corruption, is critical.Provable recovery changes the economics of ransomware.Validated recovery points reduce downtime, avoid reinfection, and can eliminate the need to pay ransom, delivering measurable operational and financial impact. Additional Resources AWS ReInvent: How Motability Operations built a ransomware-ready backup strategy with AWS Backup & Elastio AWS re:Invent 2025 - Motability Operations' unified backup strategy: From fragmented to fortified

In early 2026, U.S. authorities issued a cyber threat alert warning organizations about evolving tactics used by North Korean state-sponsored cyber actors. The advisory highlights how the Democratic People’s Republic of Korea (DPRK) continues to refine its cyber operations to conduct espionage, gain persistent access to networks, and generate revenue to support state objectives. This activity underscores a broader reality: DPRK cyber operations are no longer niche or experimental. They are mature, adaptive, and increasingly effective against both public- and private-sector targets. Evolving Tradecraft: From Phishing to QR Code Attacks A key focus of the alert is the growing use of malicious QR codes embedded in phishing emails, a technique often referred to as “quishing.” Instead of directing victims to malicious links, attackers embed QR codes that prompt users to scan them with mobile devices. This approach allows attackers to bypass traditional email security controls and exploit weaker defenses on mobile platforms. Once scanned, these QR codes redirect victims to attacker-controlled pages that closely mimic legitimate login portals, such as enterprise email or remote access services. Victims who enter their credentials unknowingly hand over access to their accounts, enabling attackers to move laterally, conduct follow-on phishing campaigns, or establish long-term persistence. Kimsuky and Targeted Espionage The activity described in the alert is attributed to a DPRK-linked cyber group commonly referred to as Kimsuky. This group has a long history of targeting policy experts, think tanks, academic institutions, and government entities, particularly those involved in foreign policy and national security issues related to the Korean Peninsula. What distinguishes recent campaigns is the subtlety of the lures and the deliberate exploitation of user trust. Emails are crafted to appear routine or administrative, and QR codes are presented as harmless conveniences. This increases the likelihood of successful compromise, even in security-aware environments. Cybercrime as Statecraft DPRK cyber operations should not be viewed solely through the lens of traditional espionage. North Korea has repeatedly demonstrated its willingness to use cybercrime as a strategic tool. In parallel with intelligence collection, DPRK-linked actors have conducted financially motivated attacks, including cryptocurrency theft, financial fraud, and illicit remote employment schemes. These activities serve a dual purpose: generating revenue to circumvent international sanctions and providing operational cover for broader intelligence objectives. In many cases, what appears to be simple fraud is ultimately tied to state-directed priorities. Why This Matters Now The techniques outlined in the 2026 alert highlight how DPRK cyber actors are adapting faster than many defensive programs. By shifting attacks to mobile devices, exploiting human behavior, and blending espionage with financial crime, they reduce the effectiveness of traditional security controls. For organizations, this means that technical defenses alone are no longer sufficient. User awareness, mobile security posture, identity protection, and anomaly detection all play a critical role in mitigating risk. Key Takeaways for Organizations Organizations should assume that DPRK cyber activity will continue to evolve and expand in scope. Practical steps include updating security awareness training to address QR code–based attacks, monitoring for anomalous authentication behavior, limiting credential reuse, and treating identity compromise as a high-impact security incident. Most importantly, leaders should recognize that DPRK cyber operations are persistent, well-resourced, and strategically motivated. Understanding this threat is essential not only for government and policy organizations, but for any enterprise operating in an increasingly interconnected and geopolitically influenced digital environment.

Detonation Point is where cyber risk stops being an abstract headline and becomes an operational reality. In a recent episode presented by Elastio, host Matt O’Neill sat down with cloud security expert Costas Kourmpoglou at Spike Reply UK to unpack a hard truth many organizations only learn after an incident: Ransomware doesn’t succeed because attackers are smarter; it succeeds because recovery fails. Ransomware Is an Industry Early ransomware operations were vertically integrated. The same group wrote the malware, gained access, deployed it, negotiated payment, and laundered funds. That model is gone. Today’s ransomware ecosystem resembles a supply chain: Developers build ransomware toolingInitial access brokers sell credentialsAffiliates deploy attacksNegotiators manage extortionSeparate actors handle payments and laundering This “Ransomware-as-a-Service” model lowers the barrier to entry and scales attacks globally. No one really needs expert technical skills. They just need access and opportunity. How Daily Mistakes Set Ransomware in Motion Ransomware became dominant for a straightforward reason: it pays. Despite headlines about zero-day exploits, most ransomware campaigns still begin with mundane failures: Reused credentialsPhishing emailsThird-party access The uncomfortable reality is that most organizations already assume breaches, yet design security as if prevention is enough. In this Detonation Point podcast, Costas noted, “Many teams over-invest in stopping the first mistake and under-invest in what happens after that mistake inevitably occurs.” Attackers don’t rush. Once inside, they: Observe quietly and use native tools to blend in (“living off the land”)Map systems and privilegesIdentify backups and recovery paths Ransomware often detonates months after initial access and long after backups have quietly captured infected data. But Why Paying the Ransom Rarely Works Ransomware payments are often justified as the “cheapest option.” But data tells a different story: Recovery success after payment is worse than a coin flipPayments may violate sanctions lawsData is often not fully restored or released anyway As Costas put it, “If you’re willing to gamble on paying the ransom, you might as well invest that money in resilience, where the odds are actually in your favor.” One of the most critical insights from the conversation was this: If your business cannot operate, that is not just a cybersecurity failure, it’s a business failure. If your plan assumes everything else still works, it’s not a plan. And, if ransomware detonated tonight, do you know which recovery path would save you, and which ones would make things worse? Because when ransomware stops being theoretical, only validated recovery determines the outcome. This blog is adapted from the Detonation Point podcast presented by Elastio.