Benchmark: GuardDuty
Description
This section contains recommendations for configuring GuardDuty resources.
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-aws-complianceStart the Powerpipe server:
steampipe service startpowerpipe serverOpen http://localhost:9033 in your browser and select GuardDuty.
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.all_controls_guarddutySnapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.all_controls_guardduty --shareControls
- GuardDuty Detector should be centrally configured
- GuardDuty Malware protection for EC2 should be enabled
- GuardDuty EC2 runtime monitoring should be enabled
- GuardDuty ECS runtime monitoring should be enabled
- GuardDuty EKS audit log monitoring should be enabled
- GuardDuty EKS runtime monitoring should be enabled
- GuardDuty Lambda protection should be enabled
- GuardDuty RDS protection should be enabled
- GuardDuty runtime monitoring should be enabled
- GuardDuty S3 protection should be enabled
- GuardDuty should be enabled
- GuardDuty findings should be archived
- GuardDuty Detector should not have high severity findings