Overview of CloudGuard Network for Azure VMSS
Use this guide to:
-
Deploy a new Check Point VMSS for Microsoft Azure.
-
Configure an existing Check Point VMSS for Microsoft Azure
Collection of integrated cloud services that developers and IT professionals use to build, deploy, and manage applications through a global network of data centers managed by Microsoft®., for templates 20180610 and above.
You can locate the template version on each CloudGuard instance in this file:
/etc/cloud-version
|
Note - For the list of supported versions, refer to the Support Life Cycle Policy. |
Licensing
Check Point CloudGuard Security Gateways and Check Point CloudGuard Security Management Server Dedicated Check Point server that runs Check Point software to manage the objects and policies in a Check Point environment within a single management Domain. Synonym: Single-Domain Security Management Server. must have a license.
There are two licensing options:
-
Pay As You Go (PAYG)
-
Bring Your Own License (BYOL)
Because the number of Security Gateways in VMSS can increase and decrease over time, we recommend that you use Security Gateways with the Pay As You Go (PAYG) license model. For the list of countries, see sk109360.
You can use the Check Point VMSS for Microsoft Azure solution template to launch BYOL Security Gateways.
To buy BYOL licenses, contact Check Point Sales.
For more information about licensing, see the CloudGuard Network Central License Management Utility guide.
|
Important - A VMSS with a mixture of BYOL and PAYG Security Gateways is not supported. All Security Gateways in a Scale Set must use the same payment plan, either PAYG or BYOL. |
Introduction to Virtual Machine Scale Sets (VMSS)
Virtual Machine Scale Sets (VMSS) are an Azure compute resource you can use to deploy and manage sets of identical Virtual Machines (VMs). The Scale Sets increase or decrease the number of Virtual Machines based on the current needs.
For example, multiple web servers server a web application. The web servers are deployed across multiple fault and update domains. A Load Balancer distributes network traffic across this group of web servers as needed.
In the current cyber-landscape, it is very important that you protect these environments from attackers with a security solution that is as scalable as the resources it protects. As the number of resources you protect scales up or down, the number of Security Gateways that provide protection has to scale as well.
Azure Autoscale is set up to increase or decrease the number of Check Point CloudGuard Network Security Gateways that protect your environment in the VMSS. A Check Point Security Management Server Check Point Single-Domain Security Management Server or a Multi-Domain Security Management Server. manages these Security Gateways. The Security Management Server can be located either in Azure, or on-premises.
See Azure documentation for information on the configuration of multiple Virtual Machines - Configure multiple virtual machines in an availability set for redundancy.
Prerequisites
Make sure you are familiar with these topics:
Vendor |
Topics |
---|---|
Microsoft Azure |
|
Check Point |
|
Components of the Check Point Deployed Solution
The diagram below depicts an Azure Virtual Network Environment of logically connected Virtual Machines. (VNET) with the Check Point solution deployed.
There are two backend subnets - WebApp1 and WebApp2.
WebApp1 and WebApp2 are each a user-deployed backend subnet. Each has its own load-balanced web server.
The Check Point deployed solution has these components:
-
Frontend subnet
-
Virtual Machine Scale Set (VMSS)
The number of instances that you can deploy in the Cloud is dynamic.
-
Internal Load Balancer
-
Backend subnet
-
External Load Balancer
-
Public IP address for each VMSS instance (optional)
-
You cannot deploy other VMs in the VMSS subnets
Load Balancers
In the diagram below you can see Load Balancers at three levels.

-
The Load Balancer at the first level is the External Load Balancer, where traffic comes in from the Internet.
-
The Load Balancer at the second level is the Internal Load Balancer of the Check Point deployed solution.
-
The Load Balancer at the third level (in this diagram there are two), is the Internal Load Balancer of the Web Servers.
Subnets with load balanced hosts (such as web servers), use the Load Balancers at the third level.

-
Standard - Both Load Balancers (this includes the ELB public IP address).
-
External Only - The Internal Load Balancer is not deployed.
-
Internal Only - The External Load Balancer (this includes its public IP) is not deployed. For outbound inspection, it is mandatory to deploy an External Load Balancer and, or instance level public IP addresses.
Network Diagram
|
Note - WebAppA and WebAppB routing tables have the same VNET address, but different subnet addresses. |

1 |
Example 1 |
Frontend WebAppA:80 |
Backend port 8081 |
|
Example 2 |
Frontend WebAppB:80 |
Backend port 8083 |

2 |
Destination 10.0.0.0/16 |
Nexthop None (Drop) |
|
10.0.1.0/24 |
Virtual Network |

3 |
Destination 0.0.0.0/0 |
Nexthop None (Drop) |

4 |
Frontend |
Nexthop |
|
10.0.0.0/16 -VNET address |
10.0.2.4 -IP address of the Internal Load Balancer |
|
0.0.0.0/0 |
10.0.2.4 -IP address of the Internal Load Balancer |
|
10.0.2.0/24 |
Virtual Network |
|
10.0.3.0/24 (WebApp1) - Subnet address |
Virtual Network |

5 |
Frontend |
Nexthop |
|
10.0.0.0/16 -VNET address |
10.0.2.4 -IP address of the Internal Load Balancer |
|
0.0.0.0/0 |
10.0.2.4 -IP address of the Internal Load Balancer |
|
10.0.2.0/24 |
Virtual Network |
|
10.0.4.0/24 (WebApp2) - Subnet address |
Virtual Network |

6 |
WebAppA (subnet) load balanced VMSS WebAppB (subnet) load balanced VMSS |
For Site-2-Site VPN configuration between Cluster Two or more Security Gateways that work together in a redundant configuration - High Availability, or Load Sharing. High Availability, see the Check Point CloudGuard Network High Availability for Azure Administration Guide.