AWS Threat Detection and Incident Response
Investigate, detect and respond with the evidence AWS records
Five weeks of an AWS organization under attack, read the way investigators read it: with SQL, from CloudTrail and the sources around it. Every query runs in the page, every number is checked, and nothing assumes you have worked in AWS before.
What you'll be able to do
Course Syllabus
Every module and every lesson. The first three modules are open; the rest open on a click.
Download the full syllabus (PDF)
Orientation
AWS Threat Detection and Incident Response: investigating attacks in AWS from the evidence AWS records, taught with Athena SQL against five weeks of an engineering company's AWS accounts with six real attacks in them.
Show 8 lessonsHide lessons
- 0.10.1 What This Course TeachesPreview
- 0.20.2 How Investigation Works in AWSPreview
- 0.30.3 Organization TrailsPreview
- 0.40.4 Data and Network Activity EventsPreview
- 0.50.5 Retention, Integrity and the Log ArchivePreview
- 0.60.6 GuardDuty and Security Hub Across an OrganizationPreview
- 0.70.7 The Investigator's AccessPreview
- 0.80.8 Assessing Investigation ReadinessPreview
Foundation
Module 1 of AWS Threat Detection and Incident Response: how CloudTrail records reach Athena, the CloudTrail table and its columns, selecting and filtering, the identity block, management and data events, time windows, and reads, writes and errors.
Show 9 lessonsHide lessons
- 1.11.1 How CloudTrail Reaches Athena
- 1.21.2 The CloudTrail Table and Its Columns
- 1.31.3 Selecting the Columns That Answer a Question
- 1.41.4 Filtering with WHERE
- 1.51.5 Reading the Identity Block
- 1.61.6 Management and Data Events
- 1.71.7 Working in Time Windows
- 1.81.8 Reads, Writes and Errors
- 1.9Module Summary and Knowledge Check
Module 2 of AWS Threat Detection and Incident Response: combining conditions, matching text and patterns, extracting values from JSON, arrays and UNNEST, counting and grouping, filtering groups with HAVING, ranking and top-N, and building a timeline.
Show 9 lessonsHide lessons
Module 3 of AWS Threat Detection and Incident Response: IAM users, access keys and the root user; roles and AssumeRole; joining a session to its source; cross-account access; federation and Identity Center sign-in; service-linked roles and service principals; common table expressions; attributing an action to a person.
Show 9 lessonsHide lessons
- 3.13.1 IAM Users, Access Keys and the Root User
- 3.23.2 Roles and AssumeRole
- 3.33.3 Joining a Session to Its Source
- 3.43.4 Cross-Account Access
- 3.53.5 Federation and Identity Center Sign-In
- 3.63.6 Service-Linked Roles and Service Principals
- 3.73.7 Common Table Expressions for Investigations
- 3.83.8 Attributing an Action to a Person
- 3.9Module Summary and Knowledge Check
Intermediate
Module 4 of AWS Threat Detection and Incident Response: how credentials leak, detecting use of a leaked key, console sign-in and MFA evidence, root user activity, reading GuardDuty findings, discovery after access, baselines and first-seen analysis, and scoping a compromised credential.
Show 9 lessonsHide lessons
- 4.14.1 How Credentials Leak
- 4.24.2 Detecting Use of a Leaked Key
- 4.34.3 Console Sign-In and MFA Evidence
- 4.44.4 Root User Activity
- 4.54.5 Reading GuardDuty Findings
- 4.64.6 Discovery After Access
- 4.74.7 Baselines and First-Seen Analysis
- 4.84.8 Scoping a Compromised Credential
- 4.9Module Summary and Knowledge Check
Module 5 of AWS Threat Detection and Incident Response: escalation paths in IAM, policy versions and inline policies, PassRole through compute services, trust policy changes, new users, keys and login profiles, configuration history with AWS Config, window functions for change sequences, and proving what an identity could do.
Show 9 lessonsHide lessons
- 5.15.1 Escalation Paths in IAM
- 5.25.2 Policy Versions and Inline Policies
- 5.35.3 PassRole Through Compute Services
- 5.45.4 Trust Policy Changes
- 5.55.5 New Users, Keys and Login Profiles
- 5.65.6 Configuration History with AWS Config
- 5.75.7 Window Functions for Change Sequences
- 5.85.8 Proving What an Identity Could Do
- 5.9Module Summary and Knowledge Check
Module 6 of AWS Threat Detection and Incident Response: bucket access control and Block Public Access, public exposure and who used it, data events for object access, S3 server access logs, measuring what left, the KMS witness, ransom with customer-provided keys, and scoping a data theft.
Show 9 lessonsHide lessons
Advanced
Module 7 of AWS Threat Detection and Incident Response: the instance metadata service, instance credentials used elsewhere, VPC Flow Logs, DNS query logs, load balancer logs and SSRF, Lambda abuse, joining network and API evidence, and reconstructing a host's activity.
Show 9 lessonsHide lessons
Module 8 of AWS Threat Detection and Incident Response: stopping and deleting trails, changing what a trail records, disabling GuardDuty, Config and Security Hub, Region and account evasion, anonymized infrastructure, gaps in the record, proving logging was intact, and evasion in a timeline.
Show 9 lessonsHide lessons
- 8.18.1 Stopping and Deleting Trails
- 8.28.2 Changing What a Trail Records
- 8.38.3 Disabling GuardDuty, Config and Security Hub
- 8.48.4 Region and Account Evasion
- 8.58.5 Anonymized Infrastructure
- 8.68.6 Gaps in the Record
- 8.78.7 Proving Logging Was Intact
- 8.88.8 Evasion in a Timeline
- 8.9Module Summary and Knowledge Check
Module 9 of AWS Threat Detection and Incident Response: triaging GuardDuty findings, attack sequence findings, Security Hub in both formats, suppression and trusted lists, detections from CloudTrail queries, testing a detection against the sample period, tuning false positives, and writing a detection specification.
Show 9 lessonsHide lessons
- 9.19.1 Triaging GuardDuty Findings
- 9.29.2 Attack Sequence Findings
- 9.39.3 Security Hub in Both Formats
- 9.49.4 Suppression and Trusted Lists
- 9.59.5 Detections from CloudTrail Queries
- 9.69.6 Testing a Detection Against the Corpus
- 9.79.7 Tuning False Positives
- 9.89.8 Writing a Detection Specification
- 9.9Module Summary and Knowledge Check
Mastery
Module 10 of AWS Threat Detection and Incident Response: the AWS incident response process and AWS's role in it, triaging and declaring an incident, containing compromised identities and resources, organization-level containment with SCPs and RCPs, preserving evidence, eradication and recovery, and post-incident review.
Show 9 lessonsHide lessons
- 10.110.1 The AWS Incident Response Process
- 10.210.2 Triaging and Declaring an Incident
- 10.310.3 Containing a Compromised Identity
- 10.410.4 Containing Compromised Resources
- 10.510.5 Organization-Level Containment
- 10.610.6 Preserving Evidence
- 10.710.7 Eradication and Recovery
- 10.810.8 Post-Incident Review
- 10.9Module Summary and Knowledge Check
Phase 0: Course Resources
Athena queries by investigation area, each with the console path, the fields that carry the decision, and what the answer does not establish.
Seven procedures an AWS responder repeats: triaging a finding, scoping a leaked credential, following an identity chain, establishing what data left, and preserving evidence before eradication.
Building an AWS account that produces the evidence this course investigates, with the cost guardrails in place before anything is switched on.
Six queries from the course that ran cleanly and answered wrongly, each taken step by step to the right answer: a Region filter, a writes-only timeline, a role's empty user name, a sign-in's missing error, an anonymous reader and an alert's time.
Seven response playbooks keyed to what actually fires in AWS, each with a pre-flight, a sequence, escalation tiers and the false positives that live in that domain.
Where to practice AWS investigation and use it at work: query drills against the course corpus, your own account, the detection library, and the reference pages worth keeping open.
Every query, field and command from AWS Threat Detection and Incident Response in one place, organized by the task in front of you and linked back to the lesson that explains it.
Show 1 lessonHide lessons
AWS service documentation, security guidance, frameworks, and threat-intelligence sources used throughout the AWS Threat Detection and Incident Response course.
Project
The AWS Threat Detection and Incident Response project: a readiness assessment of an AWS account, five detections tested and specified to Module 9's standard, and an investigation report on a prepared case none of the modules teaches, written to Module 10's standard. No submission, no grading.
Show 1 lessonHide lessons
Course Completion
AWS Threat Detection and Incident Response practical exam: twenty tasks, two per teaching module, each answered by writing Athena SQL against Northgate's record and checked on the server.
Show 1 lessonHide lessons
Course overview
In AWS almost everything that matters happens through an API call, and AWS records the calls. This course teaches you to read that record: who made a call, with which credentials, from where, and what it changed, and then to use it to investigate attacks, detect them sooner and decide what to do about them.
It is taught against five weeks of Northgate Engineering's AWS organization, four accounts whose record holds ordinary work and six attacks: a leaked CI key, a password spray, a stolen session, an escalation to administrator, backups stolen and held to ransom, and instance credentials taken through a web application, with an attempt to stop the logging along the way.
How this course works
Every query runs in the page. A SQL engine built into each lesson holds the record in ten tables, from CloudTrail and VPC flow logs to GuardDuty, Security Hub and AWS Config, and behaves as Athena does on them. Change a query, run it, and see what changed.
Predict, then run. Queries ask for your prediction before they show their result, so every query is a small test of your understanding.
Exercises, audits and decisions. Lessons carry graded exercises that complete, fix and write queries. Module 0 has you audit real configurations, and Module 10 has you commit to response decisions in writing before reading where they lead. Each module ends with a knowledge check and a challenge set.
Check every answer. The course treats an empty result, a single Region and an alert's timestamp as things to verify before anyone relies on them, and says plainly what the record cannot show.
What you will learn
Who this course is for
Anyone who needs to investigate or detect attacks in AWS: SOC analysts, incident responders, detection engineers and cloud engineers, and people moving into those roles. No experience with AWS or SQL is assumed; every service, field and clause is explained where it is first used.
Readers who already work in AWS will find the later modules go well past the basics, and the Course Fit Check in the free Module 0 shows where you sit.
What you will build
What this course does not cover
Disk and memory forensics of a compromised instance, Kubernetes and container investigation, and AWS security architecture each sit outside this course; the platform's forensics and architecture courses cover them. This course is about the AWS layer: every identity and API call, and the evidence AWS keeps of them.
Things you need to know
What are the prerequisites?
None. The course explains AWS and SQL from first principles, and the free Module 0 sets out how AWS evidence works and what an organization must record before the first query.
What do I need to run the queries?
A device with a modern browser. Every query in the course runs in the SQL engine built into the page. For the Project you can work in an AWS account of your own; the lab setup pages explain how to turn on the evidence safely and what it costs.
How is the course assessed?
By a practical exam: twenty tasks, two per teaching module, each answered by writing SQL against Northgate's record and checked on the server. Passing at 70 earns the AWS Threat Detection and Incident Response certificate with CPE credit.
Usage rights and disclaimer
Course materials: Licensed for individual professional development. You may use the queries you write in your own environment. You may not redistribute course content or share account credentials.
Fictional environment: All scenarios use Northgate Engineering. Any resemblance to real organizations is coincidental.
End of Course Exam
Complete the course, then write the queries: twenty tasks answered against Northgate's record, no time limit. Pass mark: 70. Earn your certificate with CPE credits.
Answers are checked on the server. Certificate issued on pass.