FCP_ZCS_AD-7.4 FCP - Azure Cloud Security 7.4 Administrator Questions and Answers

Azure does not allow the deployment of virtual machines (VMs) in a gateway subnet. The gateway subnet is specifically reserved for Azure VPN Gateway or ExpressRoute Gateway instances, and deploying other resources in it can cause gateway deployment or operation failures.

Since port 80 traffic is reaching the FortiGate (as shown in the sniffer output) but port 22 traffic is not, the issue lies before the FortiGate, at the Azure Load Balancer level. Azure Load Balancers require an Inbound NAT rule to forward specific ports (like SSH on port 22) to a specific backend VM. Creating a new Inbound NAT rule for port 22 will allow SSH traffic to be properly routed to the FortiGate VM.

Azure does not allow you to view an existing client secret’s value after creation for security reasons. If you did not save the client secret when it was first generated, the quickest and only option is to create a new client secret under the existing app registration and use the new value in your FortiGate configuration.

Using FortiGate at both ends of a site-to-site IPsec VPN tunnel provides the advantage of applying consistent security policies, configurations, and management tools across both the on-premises and Azure environments. This simplifies policy enforcement, improves operational efficiency, and ensures uniform threat protection.

In a FortiGate active-active HA deployment in Azure, synchronization between instances is achieved using:

FortiGate Clustering Protocol (FGCP) – This is the primary protocol used to synchronize configuration and session information between HA peers.

Heartbeat interfaces – These interfaces are specifically configured to exchange HA state and sync data between the FortiGate VMs, ensuring cluster consistency.

Infrastructure-as-a-Service (IaaS) allows you to deploy FortiWeb as a virtual machine in Azure, giving you granular control over vCPU and memory allocation. This model provides full flexibility over the compute resources and network configuration, which is essential for deploying and scaling security appliances like FortiWeb.

The Linux server in the spoke VNet cannot directly peer BGP with the Azure Route Server, as it is not a BGP-enabled device. Instead, Azure propagates routes to VMs through the effective route tables associated with their network interfaces (NICs). Therefore, to diagnose why BGP routes are not reaching the Linux VM, you should monitor the effective routes on the NIC to verify if the routes from the FortiGate (via the Route Server) are being injected properly.