> Source: [sk120157](https://support.checkpoint.com/results/sk/sk120157)

# sk120157 - CloudGuard Network for Microsoft Azure Stack

| Property | Value |
|----------|-------|
| Solution ID | sk120157 |
| Date Created | 2017-08-23 |
| Last Modified | 2023-05-07 |
| Technical Level | General |
| Products | Cloud Firewall |
| Versions | R81 (EOS), R81.10 (EOS) |
| OS | Gaia |
| Platform | Azure |

## Solution

**Table of Contents:**

* Overview
* Prerequisites
* Network Diagram
* Management
* Deployment through the Azure Stack admin portal - using `*.azpkg`
* Setting up the route tables of the Frontend and Backend subnets
* Setting up backend subnets and their route tables
* Known Limitations and Issues
* Related documentation

### Overview {#Overview}

Microsoft [Azure Stack](https://azure.microsoft.com/en-us/overview/azure-stack/) is an extension of Microsoft [Azure](https://azure.microsoft.com/), bringing the agility and fast-paced innovation of cloud computing to on-premises environments. Only Azure Stack lets you deliver Azure services from your organization's datacenter, while balancing the right amount of flexibility and control-for truly-consistent hybrid cloud deployments.

Check Point CloudGuard Network for Microsoft Azure Stack extends advanced Threat Prevention security to protect customers' Azure Stack on-premises environments from malware and other sophisticated threats. As a Microsoft Azure Stack certified solution, CloudGuard Network enables you to easily and seamlessly secure your workloads, data and assets while providing secure connectivity across your cloud and on-premises environments.

This article will guide you in deploying a Check Point CloudGuard Network single Security Gateway or CloudGuard Network Standalone machine (Security Gateway and Security Management Server) in Microsoft Azure Stack.

### Prerequisites {#Prerequisites}

It is assumed that the reader is familiar with the following topics:

|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Vendor      | Topic                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
| Azure       | * [Virtual Networks](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-overview) * [Virtual Machines](https://docs.microsoft.com/en-us/azure/virtual-machines/linux/) * [Public IP addresses](https://docs.microsoft.com/en-us/rest/api/network/virtualnetwork/public-ip-addresses) * [User Defined Routes / Routing (UDR)](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-udr-overview) * [Role Based Access Control (RBAC)](https://docs.microsoft.com/en-us/azure/active-directory/role-based-access-control-what-is) * [Register Azure stack with Azure](https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-register#register-azure-stack-with-azure) |
| Check Point | * [Check Point R80.40](https://support.checkpoint.com/results/sk/sk160736) * [Check Point R81](https://support.checkpoint.com/results/sk/sk166715) * [Check Point R81.10](https://support.checkpoint.com/results/sk/sk170416) * [Check Point in Azure](https://www.checkpoint.com/products/vsec-microsoft-azure/)                                                                                                                                                                                                                                                                                                                                                                                                    |

You should have installed and configured Azure PowerShell version 1.0 or higher.  
For additional information on how to install it, refer to the [Install PowerShell for Azure Stack](https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-powershell-install) article.

You should have installed and configured the Azure AD PowerShell module.  
For additional information on how to install it, refer to the [Azure Active Directory PowerShell 1.0](https://msdn.microsoft.com/en-us/library/jj151815.aspx) article.

### Network Diagram {#Network Diagram}

*Example Network Diagram*:

[![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk120157/Network_Diagram.jpg)](https://sc1.checkpoint.com/sc/SolutionsStatics/sk120157/Network_Diagram.jpg "Click the image to see it in full size in a new tab/window")

In this architecture, the Azure Stack virtual network consists of four subnets:

* A CloudGuard Network Security Gateway frontend subnet
* A CloudGuard Network Security Gateway backend subnet
* Two backend subnets:  
  * A web tier subnet
  * An application tier subnet

This environment consists of two separate web applications. Each web application consists of:

* A separate public IP address, through which the web application can be accessed
* A web server on a web tier subnet
* An application server on an application tier subnet

The CloudGuard Network Security Gateway for Azure Stack inspects:

* Traffic arriving from the Internet to each of the web applications
* Traffic between the web and application tiers
* Traffic originating from the backend subnets to the Internet

### Management {#Management}

The CloudGuard Network Gateway for Azure Stack can be managed in several ways, including:

* A StandAlone configuration, in which the CloudGuard Network Gateway machine also acts as its own Management Server
* Centrally managed, where the Management Server is located on premises, outside the virtual network
* Centrally managed, where the Management Server is located in the same virtual network (support for this scenario is planned)

The CloudGuard Network Gateway for Azure Stack can be managed by a Security Management Server running R80.40 or higher.

### Deployment through the Azure Stack admin portal - using `*.azpkg` {#Deployment through the Azure Stack admin portal}

To deploy this solution through the Azure Stack portal, use the [Check Point CloudGuard Network](https://portal.azure.com/#create/checkpoint.vsecsingle) package:

1. Execute the [**`RegisterWithAzure.ps1`**](https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-register#register-azure-stack-with-azure) script, which lets you add images from Azure Marketplace Management to your on-premises environment.

2. Download the CloudGuard Network image from the [Marketplace Management](https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-download-azure-marketplace-item):

   1. Search for either ***check point*** or ***CloudGuard*** and click on the ***Check Point CloudGuard***image link.

      *Example* :  
      [![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk120157/Add_from_Azure.png)](https://sc1.checkpoint.com/sc/SolutionsStatics/sk120157/Add_from_Azure.png "Click the image to see it in full size in a new tab/window")
   2. Click on the ***Download*** button at the bottom.

      *Example* :  
      [![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk120157/Download_vSEC.png)](https://sc1.checkpoint.com/sc/SolutionsStatics/sk120157/Download_vSEC.png "Click the image to see it in full size in a new tab/window")
   3. Download the Azure Gallery Package `*.azpkg` to the environment using the following command in the PowerShell CLI:

      **`Add-AzsGalleryItem -GalleryItemUri https://chkpazurestack.blob.core.windows.net/azpkg-stack-single/checkpoint.CloudGuard-stack-single.1.0.4.azpkg -VERBOSE`**
      1. Example output of the "*Get-AzsGalleryItem \| select name*" command before adding the package:

         [![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk120157/Get-AzsGalleryItem__before_1709270325.png)](https://sc1.checkpoint.com/sc/SolutionsStatics/sk120157/Get-AzsGalleryItem__before_1709270325.png "Click the image to see it in full size in a new tab/window")
      2. Example output of the above "*Add-AzsGalleryItem ... checkpoint.CloudGuard-stack-single.1.0.4.azpkg ...*" command:

         [![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk120157/Add-AzsGalleryItem_1709270325.png)](https://sc1.checkpoint.com/sc/SolutionsStatics/sk120157/Add-AzsGalleryItem_1709270325.png "Click the image to see it in full size in a new tab/window")
      3. Example output of the "*Get-AzsGalleryItem \| select name*" command after adding the package:

         [![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk120157/Get-AzsGalleryItem__after_1709270325.png)](https://sc1.checkpoint.com/sc/SolutionsStatics/sk120157/Get-AzsGalleryItem__after_1709270325.png "Click the image to see it in full size in a new tab/window")
   4. In the left tree, click on the ***More services*** - click on the ***Security + Identity*** menu - you should see ***Check Point CloudGuard Single Gateway***.

      *Example* :  
      [![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk120157/Security_Identity.png)](https://sc1.checkpoint.com/sc/SolutionsStatics/sk120157/Security_Identity.png "Click the image to see it in full size in a new tab/window")

**Notes about the CloudGuard Network `*.azpkg` package:**

* This package deploys a single CloudGuard Network Security Gateway with 2 network interfaces.  
  After deployment, you should set up [User Defined Routes (UDR)](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-udr-overview) to route traffic through the CloudGuard Network Security Gateway.  
  This package can also be used in a Standalone (Security Gateway and Security Management Server) configuration.

* This package contains a template that can either create a new virtual network, or allow you to deploy into an existing virtual network.

* This package does not create the Web and App subnets - you should add these subnets by yourself.

* This template does not deploy any web or application VMs.

* VMs launched in the backend subnets, might require Internet access in order to finalize their provisioning.  
  You should launch these VMs only after you have applied NAT hide rules on the CloudGuard Network Security Gateway for Azure Stack to support this type of connectivity.

* After you deploy the template, the CloudGuard Network for Azure Stack will automatically execute the Check Point First Time Configuration Wizard based on the provided parameters. Once the First Time Configuration Wizard completes, the CloudGuard Network Security Gateway for Azure Stack has to be rebooted.

### Setting up the route tables of the Frontend and Backend subnets {#Setting up the route tables of the Frontend and Backend subnets}

This section shows how to ensure that the route tables associated with the CloudGuard Network Gateway frontend and backend subnets are set up correctly.

**Note:** Follow this section *only* if you have deployed the CloudGuard Network Gateway into an existing virtual network. If you have opted to let the template create a new virtual network, then you should *skip* this step.

To setup route table, visit the "Route Table" section of Azure Stack portal (refer to [Connect to Azure Stack](https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-connect-azure-stack) and [Using the administrator and user portals in Azure Stack](https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-manage-portals)).

For step by step instructions, refer to [User-defined routes and IP forwarding](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-udr-overview).

The route table associated with the frontend subnet should consist of the following routes:

Note: This is an example of a route table taken from Azure Stack portal "Route Tables" menu.

```
-  name: frontend-local
   address-prefix: frontend-subnet-prefix #e.g., 10.0.1.0/24
   next-hop-type: Virtual network
-  name: frontend-to-other-subnets
   address-prefix: Virtual Network address prefix #e.g., 10.0.0.0/16
   next-hop-type: Virtual Appliance
   next-hop-address: GATEWAY-EXTERNAL-ADDRESS #e.g., 10.0.1.10
```

The route table associated with the CloudGuard Network Security Gateway backend subnet should consist of the following routes:

Note: This is an example of a route table taken from Azure Stack portal "Route Tables" menu.

```
-  name: internal-default
   address-prefix: 0.0.0.0/0
   next-hop-type: Virtual Appliance
   next-hop-address: GATEWAY-INTERNAL-ADDRESS #e.g., 10.0.2.10
```

### Setting up backend subnets and their route tables {#Setting up backend subnets and their route tables}

Use either the [Azure portal](https://portal.azure.com/), or CLI to add backend subnets, such as the Web and App subnets to the virtual network.

For each such backend subnet, create an Azure routing table with the following [User Defined Routes (UDR)](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-udr-overview):

Note: This is an example of a route table taken from Azure Stack portal "Route Tables" menu.

```
-  name: SUBNET-NAME-local #e.g., web-local
   address-prefix: SUBNET-PREFIX #e.g., 10.0.3.0/24
   next-hop-type: Virtual network
-  name: SUBNET-NAME-to-other-subnets #e.g., web-to-other-subnets
   address-prefix: Virtual Network address prefix #e.g., 10.0.0.0/16
   next-hop-type: Virtual Appliance
   next-hop-address: GATEWAY-INTERNAL-ADDRESS #e.g., 10.0.2.10
-  name: SUBNET-NAME-default #e.g., web-default
   address-prefix: 0.0.0.0/0
   next-hop-type: Virtual Appliance
   next-hop-address: GATEWAY-INTERNAL-ADDRESS #e.g., 10.0.2.10
```

With reference to the example Network Diagram above, this is the example routing table that can be used by the Web subnet:

|-----------------------------|----------------|-----------------|
| NAME                        | ADDRESS PREFIX | NEXT HOP        |
| web-subnet-local            | 10.0.3.0/24    | Virtual network |
| web-subnet-to-other-subnets | 10.0.0.0/16    | 10.0.2.10       |
| web-subnet-default          | 0.0.0.0/0      | 10.0.2.10       |

Associate the newly created routing table with the subnet.

### Related documentation {#Related documentation}

* [Azure documentation](https://docs.microsoft.com/en-us/azure/)
* [Azure Stack documentation](https://docs.microsoft.com/en-us/azure/azure-stack/)

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content
