How do I validate resources that have 443 publicly exposed have a WAF ?


Changes to the LIVEcommunity experience are coming soon... Here's what you need to know.

L2 Linker

How do I validate resources that have 443 publicly exposed have a WAF ?

If you have an AWS EC2 instance with 443 exposed to the internet, you would get an alert but what would be a good way to validate that a particular instance has a WAF protecting it?  One thing I was thinking of would be to do a joins looking at the EC2 security group API and the AWS WAF API but is there some other way we can look through a cloud config that would look for this?  I understand you can't run joins across network and config queries but the use case is pretty valid when you have large cloud teams that are constantly doing testing and making things exposed publicly exposed with a compensating control.  In this example I wouldn't have access to the actual resource to deploy a Defender and use the WAAS which is part of the reason we need to look for the cloud native WAF in say AWS or Azure.  Thanks in advance.

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!