Protego field desk
Threat Detection and Incident Response · 14% of exam

L14. Amazon GuardDuty: Threat Detection Fundamentals

Video generating

Check back soon for the video lesson on Amazon GuardDuty: Threat Detection Fundamentals

Course outlineLesson 14 of 18
AWS Security Specialty Exam Prep: course overview

Distinguish GuardDuty foundational log-based threat detection from optional protection plans, including agent-based Runtime Monitoring and malware scanning.

Exam scope: Use the current SCS-C03 guide linked below; this lesson covers the topic rather than the complete exam syllabus.

Foundational Detection and Optional Coverage

Amazon GuardDuty continuously analyzes independent streams of AWS CloudTrail management events, VPC flow data, and DNS query data. You do not need to create a trail or enable VPC Flow Logs yourself for these foundational sources. This log-based detection needs no workload agent.

Additional protection plans extend the data analyzed. Enable and verify the relevant coverage rather than treating every feature as part of the foundational detector.

Findings and Severity

GuardDuty combines threat intelligence, machine learning, and anomaly detection. Findings have Low, Medium, High, or Critical severity. Critical findings can represent a correlated attack sequence. Use finding details and affected resources to drive triage rather than treating severity as proof of compromise.

Centralized Organization Management

Designate a delegated administrator in AWS Organizations and configure automatic enablement for existing and new accounts. GuardDuty is Regional: configure organization settings and coverage in each required Region.

Protection Plans

CapabilityCoverage and deployment distinction
S3 ProtectionS3 data-event analysis for suspicious object access
EKS ProtectionKubernetes audit-log analysis
Runtime MonitoringRuntime behavior on supported EKS, ECS on Fargate, and EC2 resources; requires the GuardDuty security agent
RDS ProtectionLogin activity for supported database engines
Lambda ProtectionLambda network activity
Malware Protection for EC2Agentless scanning of supported attached EBS volumes, initiated by eligible GuardDuty findings or an on-demand scan
Malware Protection for S3Scans objects in configured S3 buckets for malware; distinct from S3 data-event threat analysis
EKS audit-log detection and Runtime Monitoring are separate capabilities. Runtime Monitoring does not support EKS on Fargate. Malware Protection for EC2 is not a continuous scan of every disk, and an on-demand scan does not require a preceding GuardDuty finding.

Responding to Findings

Route findings through Amazon EventBridge to notifications or a controlled Lambda, Step Functions, or Systems Manager Automation response. Scope remediation permissions, handle repeated events safely, and verify the result before closing the finding. Exam tip: Agentless foundational detection and agent-based Runtime Monitoring are different requirements. Use delegated administration plus per-Region coverage checks for an organization-wide rollout.

References

Continue Learning

Exam Focus Points
  • ✓GuardDuty foundational detection analyzes CloudTrail management events, VPC flow data, and DNS data without a workload agent or customer-created log delivery
  • ✓Finding severities include Low, Medium, High, and Critical; investigate the evidence and resource context
  • ✓A delegated administrator configures organization-wide GuardDuty coverage separately in each required Region
  • ✓EKS audit-log protection is separate from Runtime Monitoring, which requires a GuardDuty security agent on supported resources
  • ✓Malware Protection for EC2 supports GuardDuty-initiated and on-demand EBS scans; Malware Protection for S3 is a separate capability
Knowledge Check

1. A company wants threat detection across multiple AWS accounts without deploying any agents to EC2 instances. Which service fits this requirement?

2. How should a company with a multi-account AWS Organization enable GuardDuty consistently across all current and future member accounts?

3. GuardDuty generates a high-severity finding that an EC2 instance is likely compromised and communicating with a known command-and-control IP. Which GuardDuty protection plan would additionally scan that instance's attached EBS volumes for malware?