The tool's security features need to improve. It needs also to include a monitoring system for logs. It is also complicated to find a query on the Azure firewall.
There should be a simple one-click deployment for a firewall, rather than a set of setup instructions that include steps such as the DNS configuration, et cetera. It should be a friendly one-click process that is easy for non-technical or business people to do. By bringing in an autonomous or semi-autonomous system, we would not have to supply several different parameters. Alternatively, if it were a query-based configuration then it would still be a benefit on top of what they have now. Microsoft was unable to fully solve the problem with email phishing and spamming. Irrespective of whatever endpoint security solution you bring in from a third party, it requires constant AI and learning. This is something that is missing, and it is one place where you are forced to use a third party.
With Azure Firewall, the problem is that the NAT-ing still has to be improved. They need reverse network address translation (NAT) capabilities. We cannot get the same NAT-ing capability as what we had in the on-premise deployment, where we could have multiple sources of IP coming in and could be NAT-ed to a specific IP. Similarly, we couldn't use the reverse NAT-ing of the scenario. We could do only one-way NAT-ing, where the traffic comes from outside to internal, to Azure, which is fine. However, when we actually do NAT-ed traffic to hit the firewall, that way is not working.
CIT at a tech services company with 51-200 employees
Real User
2021-06-15T13:04:00Z
Jun 15, 2021
When we initially started using the solution around five years ago there was no wizard for setting things up, although now there is a very nice one. When it comes to configuration, a few steps is all it takes. However, beforehand, there was a need to enter and understand everything that was necessary for configuring the firewall. There is no additional documentation or training required. When we first started using the product there was a need to enter everything on one's own and the initial setup was not easy. Now, after a few clicks, everything is fine.
Find out what your peers are saying about Microsoft, Amazon Web Services (AWS), Palo Alto Networks and others in Firewall Security Management. Updated: April 2024.
What is firewall security management software? Firewall management is the group of actions and practices used for configuring and monitoring a firewall with the goal of maintaining network security. Firewalls are key elements used for protecting private networks.
Organizations may use multiple firewalls to protect devices and networks, and these can prove difficult to manage. That’s where firewall security management comes in. Firewall security management (FSM) software monitors and...
The solution can improve the integration with open-source tools.
The tool's security features need to improve. It needs also to include a monitoring system for logs. It is also complicated to find a query on the Azure firewall.
There should be a simple one-click deployment for a firewall, rather than a set of setup instructions that include steps such as the DNS configuration, et cetera. It should be a friendly one-click process that is easy for non-technical or business people to do. By bringing in an autonomous or semi-autonomous system, we would not have to supply several different parameters. Alternatively, if it were a query-based configuration then it would still be a benefit on top of what they have now. Microsoft was unable to fully solve the problem with email phishing and spamming. Irrespective of whatever endpoint security solution you bring in from a third party, it requires constant AI and learning. This is something that is missing, and it is one place where you are forced to use a third party.
With Azure Firewall, the problem is that the NAT-ing still has to be improved. They need reverse network address translation (NAT) capabilities. We cannot get the same NAT-ing capability as what we had in the on-premise deployment, where we could have multiple sources of IP coming in and could be NAT-ed to a specific IP. Similarly, we couldn't use the reverse NAT-ing of the scenario. We could do only one-way NAT-ing, where the traffic comes from outside to internal, to Azure, which is fine. However, when we actually do NAT-ed traffic to hit the firewall, that way is not working.
When we initially started using the solution around five years ago there was no wizard for setting things up, although now there is a very nice one. When it comes to configuration, a few steps is all it takes. However, beforehand, there was a need to enter and understand everything that was necessary for configuring the firewall. There is no additional documentation or training required. When we first started using the product there was a need to enter everything on one's own and the initial setup was not easy. Now, after a few clicks, everything is fine.