Tackling the recent Kong ingress controller security incident with ARMO's behavioral CADR
Imagine this situation: you recently updated one of your infrastructure software components. A few weeks later, you notice your AWS bill has gone up and you’re not sure why. After some digging, you find that the auto-scaler for this component is constantly scaled to the maximum. It takes days to realize that this change in behavior started right after the software update. You start asking around to see if anyone else is having the same issue with this new version.