cybersecurity

64 readers

1 users here now

An umbrella community for all things cybersecurity / infosec. News, research, questions, are all welcome!

Community Rules

Be kind
Limit promotional activities
Non-cybersecurity posts should be redirected to other communities within infosec.pub.

Enjoy!

founded 1 year ago

MODERATORS

shellsharks@infosec.pub

tweedge@infosec.pub

What are You Working on Wednesday (infosec.pub)

submitted 11 months ago by shellsharks@infosec.pub to c/cybersecurity@infosec.pub

7 comments fedilink hide all child comments

Weekly thread to discuss whatever you’re working on, big or small, at work or in your free time.

you are viewing a single comment's thread
view the rest of the comments

[–] starneld@infosec.pub 3 points 11 months ago (1 children)

Trying to find a suitable WAF for AWS EKS. Any suggestions?

One of the teams has a cluster built with the nginx ingress which uses classic load balancers. Shifting them to the AWS ingress (which uses ALBs enabling our AWS WAF to apply) looks like it’ll be massively expensive due to the blow out in load balancer costs - but it gets us a WAF we already use across everything else. Other option is to find a WAF specifically for EKS and shift all clusters to that.

[–] shellsharks@infosec.pub 2 points 11 months ago (1 children)

So native AWS WAF isn’t viable because of costs?

[–] starneld@infosec.pub 2 points 11 months ago

My preference is for the native AWS WAF as we already use it. The rub comes from how the cluster is architected which would mean we’d have an ALB ingress per application - the prohibitive cost is purely the extra ALBs that would be created. Though I literally just heard it’s not going to be as bad as initially forecast so ¯_(ツ)_/¯

My original curiosity was if any of the K8s specific WAFs are any good, for example Prophaze.