NSG Exposing Unintended Internal Ports to the Internet

Daniel_PDX

NSGs rely on NAT for inbound firewall rules. However NAT (Virtual Server) rules don't allow you select which protocal type you wan to use. For example: If I want to open TCP 443 only I can't do that with NSG. It opens UDP and TCP 443 (at least from what I can tell).

Please add the ability to select protocol type as part of the NAT rules. The absence of this feature is exposing internal surface area that doesn't need to be exposed to the internet.

Additionally, this will result in remediation flags for companies who have penetration tests run. The only problem... it can't be remeadiated in with currently NSG settings without disabling the whole rule.

Happy to clarify if needed.

Nebula_Bayardo

Hi Daniel, Welcome to our Nebula Community!

I have good news, the ability to select protocol (TCP/UPD/Any) for Virtual server rules will be added in the coming release by the end of this month, so it's a matter of time only ?

Thanks for your valuable input! ?

Nebula_Bayardo

Hi @Daniel_PDX

Just to update you, the new Nebula interface already supports the selection of TCP/UDP protocols in the Virtual server rules.

Feel free to check it out ?.