Rami McCarthy’s Post

View profile for Rami McCarthy, graphic

Security-at-Large

Is GuardDuty all you need for AWS threat detection? My friends over at Tracebit gave me a chance to do a deep dive on the topic, going beyond the marketing. My conclusions? * GuardDuty offers narrow coverage at an unpredictable cost with low signal * six Stratus Red Team techniques triggered zero GuardDuty findings * median detection latency was 15 minutes * Attackers could exfiltrate 100-2500GB of data from S3 before the first GuardDuty alert might fire All this shows that Canary Infrastructure can offer a strong compensating control, given it has broader coverage, predictable cost, deterministic alerting, and latency only bounded by Cloudtrail timing! https://lnkd.in/evGiRGJh

A hard look at GuardDuty shortcomings

A hard look at GuardDuty shortcomings

tracebit.com

h/t Christophe Tafani-Dereeper for Stratus Red Team Travis McPeak and team for a recent S3 exfiltration benchmark Chester Le Bron Jr. for his talk on operationalizing GuardDuty ☁️ Houston Hopkins ☁️and Nick Frichette for their coverage of S3 Streaming Copy Korstiaan S. for his previous benchmark of GuardDuty Corey Quinn for sharing his experience diving into unpredictable GuardDuty costs

Travis McPeak

Configure it right the first time

1mo

I don't know any big organizations that solely rely on GuardDuty. IMO, GuardDuty is great for a smaller company that wants *something* and doesn't want to have to buy/onboard/maintain a vendor.

William Bengtson and I have done a lot with this due to building our live fire training range. Multiple attacks rely on triggering GuardDuty and we are set up to run these across around 200 AWS accounts simultaneously. In my experience most detections are about 20-40 minutes, depending on what we are simulating. Some trigger consistently, some are REALLY HARD for me to trigger (SSH brute force from outside an account on an open 22, for example, even when I hardcode in the actual key as part of the simulation). I still always recommend GuardDuty for multiple reasons, but it's very cool to see more research on how it actually functions. Happy to play on our training range if you ever want more metrics since we can scale things and evaluate across accounts :)

Andre Rall

Cloud Security Leader

1mo

Yikes! It hasn’t improved in ~1.5 years. I ran almost all Pacu modules in an environment with GD enabled. Only one GD alert fired.

James Berthoty

Security Engineer Turned Analyst @ Latio Tech | AWS Community Builder

1mo

I was impressed with the eBPF detections recently, but otherwise totally agree. I view guard duty as the ultimate compliance box checker and better than nothing, but not great for much else!

Damien Wilson

Software Engineer, Security Specialist, Technical Mentor

1mo

It’s amazing how reliable a simple honeypot can be.

Korstiaan S.

Founder at Invictus Incident Response | SANS Instructor FOR509 | AWS Community Builder

1mo

Interesting research will read it when I have some time, I was hoping you found that we were completely wrong with our tests 😉

Jonathan Thompson

Information Security Consultant | vCISO | CISSP | CISM

1mo

This is outstanding work Rami McCarthy. I've been under the impression for a while now that GuardDuty is a little better than nothing and also checks some compliance boxes. This confirms my assumptions.

Bhavna Soman

Security Research | Machine Learning

1mo

Thanks for the great analysis and feedback Rami McCarthy

See more comments

To view or add a comment, sign in

Explore topics