r/aws
Is guardDuty runtime monitoring enough for EKS + Lambda, or do you still need a cnapp on top?
- upvotes
- 30
- comments
- 22
Post
Highlighted: the lines this signal was extracted from
We're about 70 engineers, all AWS, two orgs worth of accounts (prod and everything else). Workloads are mostly EKS with a long tail of lambda and a few ECS services nobody wants to touch. Security is me plus one contractor. Right now we have guardduty runtime monitoring turned on for EKS, security hub aggregating, and inspector scanning ECR. Leadership saw a few CNAPP demos at re:Invent last year (upwind and wiz mainly; wiz's felt like mostly a pretty graph) and the question i've been handed is basically "why are we paying for guardduty AND looking at another tool". My honest problem is that the AWS-native stack gives me findings but not much context. Inspector says a container has 400 criticals, guardduty tells me a pod made a weird DNS call, and connecting those two into "this exposed service is running a vulnerable package that's actually loaded" is me in athena on a friday night. what im trying to figure out: -For people who stayed aws-native, whtat did you build to get the correlation, and was it worth it? -For people who added a cnapp, did you turn guardduty runtime off afterwards or keep both? -Where does lambda coverage actually land with the third-party tools? that's when im least sure. not looking for a vendor pitch, just what it looks like six months in..
Also quoted as evidence
[comment u/Comfortable-Way-6271] wiz was alright too but flagged alot of lambda "risks" that were really jst unused layers, the real difference was with eks tho thats wher