The external IP of our WiFi controller requires 443 to be open to the internet, so we have this open on our inbound rule>external IP of the controller. 443 needs to be open but we don't want this to be accessible via a web browser - as currently this rule allows the external IP to be accessed via https. Is there a way of stopping this behavior? Many thanks.
I don't think there's an easy way to do this.
You could decrypt the traffic and do a pattern match on all the different User-Agent strings that you can find in the header information. You can identify different browsers that way and block traffic accordingly ... but the list will be enormous and hard to keep updated.
An old example :
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!