Enable GuardDuty Malware Protection
Specification & Description
Enable Amazon GuardDuty Malware Protection for EC2 (EBS_MALWARE_PROTECTION)
across all AWS Organizations member accounts to run agentless EBS volume
scans when GuardDuty detects suspicious instance or container activity.
Technical Specifications
GuardDuty Malware Protection automatically creates temporary replica snapshots of attached EBS volumes (both encrypted and unencrypted) when behavioral findings indicate potential EC2 instance or container compromise, scanning them agentlessly without impacting production workload performance.
1. Organization-Wide Activation and Service-Linked Role
- Enable
EBS_MALWARE_PROTECTIONwithAutoEnable = ALLfrom the GuardDuty delegated administrator account. - GuardDuty requires the service-linked role
AWSServiceRoleForAmazonGuardDutyMalwareProtection(malware-protection.guardduty.amazonaws.com) in member accounts to create and scan replica snapshots.
2. Snapshot Retention and Tag Filtering
- Configure
EbsSnapshotPreservation(RETENTION_WITH_FINDINGorNO_RETENTION) so snapshots are preserved for forensic investigation when malware is detected. - Use
ScanResourceCriteriainclude or exclude tags where cost control or compliance boundaries require selective scanning.
Security Rationale
Signature-based endpoint agents can be disabled by an attacker or miss fileless or post-exploitation payloads on EC2 instances. Agentless, event-triggered EBS scanning provides independent forensic visibility from outside the guest operating system.
Business & Security Impact
Without GuardDuty Malware Protection, responders lack automated payload identification on compromised EC2 instances and must perform manual snapshot acquisition and offline malware analysis, slowing containment.
Operational & Implementation Notes
If SCPs restrict IAM role creation in member accounts, explicitly allow iam:CreateServiceLinkedRole for malware-protection.guardduty.amazonaws.com so GuardDuty can create AWSServiceRoleForAmazonGuardDutyMalwareProtection. Use tag-based ScanResourceCriteria exclusions in non-production accounts if scan volume requires cost containment.
Related Controls & Guardrails (2)
Official References
Compliance Framework Mappings (5)
Regulatory baselines and industry standards mapped to this control specification.
| Framework / Standard | Mapped Requirements & Controls | Controls |
|---|---|---|
NIST 800-53 Rev 5NIST 800-53 | SI-3SI-4 | 2 |
ISO 27001:2022ISO 27001 | A.8.7A.8.16 | 2 |
PCI DSS v4.0PCI DSS | 5.2.111.5.1 | 2 |
SOC 2SOC 2 | CC6.8CC7.2 | 2 |
AWS Foundational Security Best PracticesAWS FSBP | GuardDuty.8 | 1 |
* Compliance framework mappings are provided for informational architectural reference. Always verify control alignment against your organization's formal audit requirements.
Automated Detection & Rule Logic
Detection Engine: aws-api • Automated: Yes
Query the GuardDuty delegated administrator detector, organization
configuration, and malware scan settings to confirm EBS_MALWARE_PROTECTION
is ENABLED, organization AutoEnable is ALL, and snapshot preservation
matches organizational forensic policy.
Preventative Enforcement Policies
Remediation Guide & Automation
In the GuardDuty delegated administrator (Security) account, enable the `EBS_MALWARE_PROTECTION` feature on the administrator detector, set organization auto-enablement to `ALL`, and configure snapshot preservation via `RETENTION_WITH_FINDING`.
Step-by-Step Instructions
- In the GuardDuty delegated administrator (Security) account, enable EBS_MALWARE_PROTECTION on the administrator detector.
- Update the GuardDuty organization configuration with EBS_MALWARE_PROTECTION AutoEnable set to ALL for existing and new member accounts.
- Set EbsSnapshotPreservation to RETENTION_WITH_FINDING (and optionally configure ScanResourceCriteria tag filters) to retain evidence for malware findings.
- Integrate GuardDuty malware findings with Security Hub and automated EC2 isolation playbooks.