What do you dislike about FortiGate-VM NGFW?
The biggest downside of FortiGate VM, in my experience, is performance. Without the dedicated ASICs (NP/CP chips) found in physical FortiGates, all packet processing is handled in software on the hypervisor’s CPU. That means throughput is ultimately constrained by the host’s available resources as well as the vCPU licensing tier you’re on. SSL inspection is especially impacted, since there’s no hardware crypto offload to absorb that workload.
Licensing is vCPU-based, which initially sounds flexible, but it can get expensive fast if you need additional cores to achieve the throughput you’re aiming for. In practice, scaling up this way can end up costing more over time than buying an equivalent physical appliance. Review collected by and hosted on G2.com.
Recommendations to others considering FortiGate-VM NGFW:
To maximize the benefits of FortiGate VM, consider the following recommendations:
1. **Resource Allocation**: Ensure that your hypervisor has sufficient resources to handle the expected traffic load, especially if SSL inspection is a priority.
2. **Licensing Strategy**: Plan your vCPU licensing carefully to avoid unexpected costs. Consider your current and future throughput needs.
3. **Hybrid Deployment**: Use FortiGate VM in conjunction with physical appliances to balance performance and flexibility.
4. **Regular Updates**: Keep your FortiGate VM updated with the latest firmware to benefit from security patches and new features.
5. **Monitoring and Management**: Utilize FortiManager and FortiAnalyzer for centralized management and monitoring to streamline operations across your network.
6. **Testing Environment**: Leverage the VM for testing configurations and updates before deploying them to production environments.
By following these recommendations, you can effectively leverage FortiGate VM to enhance your network security posture. Review collected by and hosted on G2.com.
What problems is FortiGate-VM NGFW solving and how is that benefiting you?
FortiGate VM addresses the challenge of extending consistent, enterprise-grade NGFW security into environments where physical hardware either can’t be deployed or simply doesn’t make sense.
For cloud coverage, there’s no rack to mount a box in, so VM firewalls can inspect traffic directly inside AWS/Azure/GCP VPCs. It also helps maintain consistency across hybrid infrastructure by keeping the same policies, logging, and FortiManager/FortiAnalyzer-based management across on-prem, colo, and multiple clouds, rather than juggling different tools in each environment.
Another big advantage is speed and elasticity: you can deploy in minutes instead of waiting weeks for hardware procurement, shipping, and racking. That’s especially useful for DR sites, temporary environments, M&A integration, or scaling up and down with demand. On the cost side, vCPU-based licensing provides flexibility to pay for what you actually need, instead of over-provisioning hardware for peak capacity—helpful when traffic is unpredictable or seasonal.
Finally, FortiGate VM supports east-west segmentation by inspecting traffic between VMs and microservices inside a virtual network, which a perimeter hardware appliance can’t effectively cover.
Overall, it delivers enterprise-grade firewalling that’s quick to deploy, consistent across environments, and elastic—ideal for places where physical hardware can’t go or isn’t practical. Review collected by and hosted on G2.com.