About FortiGate-VM for Azure
By combining stateful inspection with a comprehensive suite of powerful security features, FortiGate next generation firewall technology delivers complete content and network protection. This solution is available for deployment on Microsoft Azure.
In addition to advanced features such as an extreme threat database, vulnerability management, and flow-based inspection, features including application control, firewall, antivirus, IPS, web filter, and VPN work in concert to identify and mitigate the latest complex security threats.
FortiGate-VM for Azure supports active/passive high availability (HA) configuration with FortiGate-native unicast HA synchronization between the primary and secondary nodes. When the FortiGate-VM detects a failure, the passive firewall instance becomes active and uses Azure API calls to configure its interfaces/ports.
FortiGate-VM also supports active/active HA using Azure load balancer.
Highlights of FortiGate-VM for Azure include the following:
- Delivers complete content and network protection by combining stateful inspection with a comprehensive suite of powerful security features.
- IPS technology protects against current and emerging network-level threats. In addition to signature-based threat detection, IPS performs anomaly-based detection, which alerts users to any traffic that matches attack behavior profiles.
- Docker application control signatures protect your container environments from newly emerged security threats. See FortiGate-VM on a Docker environment.
|
FortiOS 7.6 supports backing up FortiGate Azure VMs using Azure's enhanced backup policy. See the Microsoft documentation. |
|
When deploying Fortinet products on a cloud platform, it is critical to understand that you are responsible for all costs incurred from the resources you use. This includes but is not limited to the following: CPU, memory, storage volumes, snapshots, data transfers, and network bandwidth. Once your deployment is live, services may automatically generate temporary files, system logs, or additional volumes and snapshots. These can consume disk space and lead to unexpected charges. To avoid surprise costs, it is your responsibility to do the following:
|