Security, Identity, and Compliance
CoreAmazon GuardDuty
Explicit finding/report and remediation example.
Key points
- GuardDuty generates threat findings that should enter a scoped, evidence-based remediation workflow.
Best-known use cases
- D4.1, D4.2, and D5.1: investigate and remediate the named GuardDuty finding without widening unrelated access.
What candidates often confuse it with
- GuardDuty detects threat activity; Inspector finds supported vulnerabilities and Security Hub aggregates findings.
Key takeaway
Treat a GuardDuty finding as detector evidence, then validate resource scope and remediation through the originating service.
Related services
- AWS Certificate Manager (ACM)
- Amazon EC2 security groups
- Egress-only internet gateways
Relevant exam tasks
- D4.1 — Task 4.1: Implement and manage security and compliance tools and policies.
- 4.1.1 — Implement IAM features (for example, password policies, multi-factor authentication [MFA], roles, federated identity, resource policies, policy conditions).
- D4.2 — Task 4.2: Implement strategies to protect data and infrastructure.
- 4.2.1 — Implement and enforce a data classification scheme.
- D5.1 — Task 5.1: Implement and optimize networking features and connectivity.
- 5.1.1 — Configure a VPC (for example, subnets, route tables, network ACLs, security groups, NAT gateways, internet gateway, egress-only internet gateway).