GuardDuty is on. Does it detect anything?
Most AWS teams switch on detections and assume they work. We run real attack techniques in a sandbox account and show you what was detected, what was only logged and what was missed. Then we help you close the gaps.
Switched on is not the same as working
In one published test, six data-theft techniques run against a real AWS account produced no GuardDuty alert at all. The findings that did fire took between 15 minutes and about an hour.
Posture scanners such as Prowler tell you what is misconfigured. They can't tell you what happens when someone actually attacks. The only way to know is to run the attack and look.
$ firedrill run starter --expected-account 111111111111 --confirm DETECTED aws.defense-evasion.cloudtrail-stop@us-east-1 LOGGED aws.persistence.iam-backdoor-user@us-east-1 LOGGED aws.exfiltration.ec2-share-ebs-snapshot@us-east-1 PREVENTED custom:s3-ssec-write@us-east-1
Five questions every AWS team should be able to answer
Does a detection fire?
Run the technique, then check GuardDuty, Security Hub or your SIEM for the finding, and time how long it took.
Does the alert reach a human?
A finding nobody sees is a log entry. Check that it actually lands in Slack, email or your pager.
Do your SCPs and RCPs really block it?
Run the attack step and pass only when AWS denies it.
Do harmless actions stay quiet?
Run a benign twin of each attack. Noisy alerts get muted, and muted alerts miss real attacks.
Did anything break since last week?
Compare every run with the previous ones and fail when a detection that worked stops working.
Answer them with cloud-firedrill →
Open source, runs in your own sandbox account, no telemetry, no commercial SIEM required.
When you'd rather have the gaps closed for you
Fixed scope, short engagements, and a fire drill at the end that proves the result.
AWS Security Baseline in 2 weeks
Detections, alert routing and guardrails set up and proven with fire drills, not just switched on.
AWS controls that pass SOC 2
Fix the AWS controls your auditor will test, and hand them evidence that the controls actually work.
Monthly fire drill
A recurring run against your accounts, a short report, and a fix for anything that stopped working.
Data, not opinions
What Public AWS Breaches Actually Teach Us
A decade of public AWS breaches shows attackers log in rather than break in: stolen keys, leaked secrets, IMDSv1. What that means for your priorities.
Your AWS KEV List: Why CVEs Miss Cloud Risk
CISA KEV is great for patching, but most AWS breaches never get a CVE. Where KEV fits in AWS, and nine exploited conditions to fix alongside it.
LLMjacking on Amazon Bedrock: How to Stop It
How stolen AWS keys run Amazon Bedrock on your bill, the SCP that blocks the payoff, and the CloudTrail signals that give LLMjacking away.