CNAPP recommendations for a small team on EKS?
We're a 4-person security team supporting about 20 EKS clusters across two AWS accounts, plus a handful of standalone ECS services. Right now we're stitching together GuardDuty, native ECR scanning, and a pile of Trivy output in CI. It technically works but nobody has time to actually triage any of it, and the vuln backlog is somewhere north of a thousand "criticals" that nobody trusts.
Renewal on our current scanner is up in about six weeks and I don't want to just re-sign out of inertia. What I actually want is something that tells me which of those criticals are reachable at runtime so we can stop treating every CVE in a base image like it's on fire. Half our findings are in packages that never get loaded.
I've been reading up on CNAPPs and the pitch is always the same: full posture, runtime, IaC, the works. For a team our size I'm worried about buying a giant platform we deploy 10% of and still drown in.
So for anyone running one on EKS at a similar scale: did the runtime context actually cut your noise, or did you just swap one dashboard of alerts for another? How painful was the agent/sensor rollout across a lot of clusters? And is there anything that's genuinely workable for a small team, or is this all built for 30-person security orgs?
[link] [comments]