How do you integrate AWS GuardDuty into CI/CD without slowing delivery to a crawl?

The usual failure mode is a security gate so slow or noisy that teams bypass it. For AWS GuardDuty, the practical levers are: scan only what changed on pull requests and keep the exhaustive scan for a nightly or pre-release run; cache whatever database or ruleset the tool downloads so CI is not re-fetching it every job; and parallelise across services rather than scanning a monorepo serially.

Severity policy matters as much as speed. Blocking on every finding trains people to add blanket suppressions. A workable policy blocks on Critical (and often High) with a documented, time-boxed exception process, while everything lower is tracked as a ticket rather than a hard stop.

For this tool specifically, tune ML/threat-intel detection over CloudTrail, VPC Flow Logs and DNS logs, EKS and Malware Protection add-ons, finding types and severities, suppression rules to cut noise, and automated response via EventBridge and Lambda. Finally, make the gate honest: auto-isolating an instance on a high-severity finding. A gate that warns but never blocks is documentation, not a control.