Which compliance frameworks require ensure guardduty has malware protection enabled?

This security check is required by the following compliance frameworks: SOC 2, PCI-DSS, NIST 800-53.

MEDIUM

Ensure GuardDuty has Malware Protection enabled

GuardDuty Malware Protection scans EBS volumes for malware when threats are detected.

Security Impact

Without Malware Protection, malware on EC2 instances may not be detected.

How to Remediate

Enable Malware Protection for EC2 in GuardDuty detector settings.

Affected Resources

AWS::GuardDuty::Detector

Compliance Frameworks

SOC 2PCI-DSSNIST 800-53

How TigerGate Helps

TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:

Continuous Scanning
Automatically scans all Amazon GuardDuty resources across your AWS accounts every hour
Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
Compliance Evidence
Automatically collect audit evidence for SOC 2, PCI-DSS, NIST 800-53 compliance
Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation