domains / families / security / detecting-cloud-threats-with-guardduty
detecting-cloud-threats-with-guardduty
separate
'Deploy and operationalize Amazon GuardDuty, covering protection plans
When to use
- When establishing continuous threat detection for new or existing AWS accounts
- When investigating GuardDuty findings related to compromised instances, credential abuse, or data exfiltration
- When building automated incident response playbooks triggered by GuardDuty findings
- When extending threat coverage to container workloads running on EKS, ECS, or Fargate
- When enabling malware scanning for EBS volumes attached to suspicious EC2 instances
When not to use
- Azure threat detection
- GCP threat detection
- static code analysis
- compliance posture monitoring
Skill page
Source