Do I need a Firewall and WAF for Website HTTPS traffic only

New Contributor

Hello Azure Community,


I'm looking for some advice or feedback around the need to deploy a Firewall and WAF for Website only solution that uses HTTPS and Websockets on a IaaS platform leveraging Windows Server, IIS and SQL Server.


I've had a couple of comments/suggestions that I should be deploying a Firewall as well, suggesting that a WAF isn't sufficient enough to prevent attacks such as sql injection.


Given that adding a firewall to the solution adds substantial dollars to the monthly bill , I'm looking for any other feedback in terms of how secure a WAF is for layer 7 traffic or what others are deploying for website only traffic. i.e., WAF only or FW and WAF?


To be clear, this isn't necessarily about the dollars but rather is a client throwing money out the door with the addition of the FW when a WAF will do?


Thanks in advance,


6 Replies



How would adding a firewall add significantly to your monthly bill?


I would think adding strategically placed Network Security Groups to your solution would give you additional adequate protection without significant cost.

I have a helped deploy a similar solution. If you apply IP restrictions for the use of the site just to your customer's IP sets and other other protocol restrictions at the NSG level then along with WAF and SSL it works pretty nicely. 



Hi there Darrick,


Thanks for your response.


The Firewall appears to be just over $900 US converted to Canadian that's close to $1,200 per month.


The 2 WAF costs $280 CDN per month (have to deploy 2).


The rest of the solution uses a couple of front end and back ends subnets (with NSGs) and couple of  burstable VMs in each subnet which are also quite cheap. 


Looks like the FW alone costs more per month then rest of this light weight 2-tiered web app total solution.


So if WAF does the job, seems like adding the FW will more than double the costs but not sure it's adding equivalent value (as we're only using HTTPS).




Hi Abhishek,


Yes that was my thinking as well, however one my clients seems determined to add FW into the mix as well.  Perhaps once I tell them how much it will cost, they may change their minds.


So it sounds like neither you nor Darrick see the need for additional FW?





After more research, I understand the differences between Azure Firewall and NSGs: I wrongly assumed they were one in the same.


NSGs are good for network layer traffic filtering to resources within VNETs in each subscription.

A firewall is stateful and provides centralized service that can be applied to both network and application layer protection across subscriptions and networks:


The Azure Firewall complements NSGs, providing defense-in-depth protection.


Question: Does your web service warrant the more granular protections provided by Azure Firewall?





Hi Darrick,


Sure no worries.  Yes, NSGs provide network layer protection which helps but additional security is needed for sure from a web application perspective.


So yes, I could use a FW however from my investigation, FW provide protection from layer 3-7 however they still fall short re: the latest security attacks such sql injection and cross-site scripting.  So Microsoft and other vendors have been deploying "Application Gateway with Web App Firewall" aka WAFs to address this higher layer 7 traffic.  WAFs only deal with HTTP/S and Websockets (both over HTTP using ports 80/443)


So if we only allow layer 7 protocols do I really need the FW when the WAF handles that?  I believe WAFs also provide that defense in depth and work in conjunction with the NSGs I have setup for front end and back end subnets.


Re: your final question, if we're only dealing with HTTP traffic and the WAF is handling that, does the FW actually provide any other value re: protection.


I'm just trying to find anyone out there who has a web application that is implementing both a FW and WAF.  Seems to be one or the other but it seems WAFs have been developed to specifically address layer 7 traffic only.