Azure Bootcamp Lab Guide v5 Final
Azure Bootcamp Lab Guide v5 Final
BOOTCAMP
Azure lab training guide
@Igor Freidin
Cyber Security Products Expert
This document will guide you through the steps required to get familiar with the AWS
platform and how to deploy a basic day-to-day scenario with CloudGuard in place. You will
understand and simulate a real-life use case to grasp the ease of deploying automated
advanced security protection within the AWS cloud.
We prepared simples exercises to illustrate the benefits of having security integrated into
a virtual networking platform. The exercises are incremental - they start from a basic
setup and progress to more advanced scenarios.
Good Luck!
IP address
Management server 10.0.0.4 (can be different - autoassigned by Azure)
CloudGuard GW - frontend 10.0.0.5 (can be different - autoassigned by Azure)
CloudGuard GW - backend 10.0.1.4 (can be different - autoassigned by Azure)
Web server 10.0.2.x (can be different - autoassigned by Azure)
6
4. An email will be sent to you to start the lab. Open the email and click 'Launch Lab' to go to
the starting page of the lab.
7
6. Your on-demand lab session has started and will be active for several hours.
The web page shows your Azure credentials for this session and the sign-in link.
You will be emailed the same information.
7. Click on the login to Microsoft Azure link for the on-demand lab, use the provided credentials.
8. Click on the portal menu icon and click on 'All services’.
10. Search and hover over each of the services below. Click on start to add it to the favorites list.
8
a) Route tables
b) Subscriptions
c) Public IP addresses
d) Network security group
e) Network interfaces
9
Exercise 1 - Build your Azure environment
Goal
Creating basic Azure environment with vNET and subnets
1. On the top search bar of the Azure portal search for and click on 'Virtual networks’.
2. At the bottom of the window that appears click on 'Create virtual network'.
3. In the window that appears fill in the info per details below. Click on 'Next: IP Addresses’.
Setting Value
Name myVNET
Subscription Leave subscription as is
Resource group Resource Group that ends with -01 (the first one)
10
4. Make sure that your IPv4 address space listed is in the 10.0.0.0/16 range. Click on the 'default' subnet and
change its 'Subnet name' to 'Frontend'. Check whether the subnet address range is 10.0.0.0/24.
Click ‘Save'.
11
5. Click on "Add subnet". Name the new subnet as 'Backend' and give it the 10.0.1.0/24 address range.
Click on Add.
12
7. Verify validation is passed and click on Create
13
8. You should see the created vNET on the Virtual networks service.
14
Exercise 2 - Deploy Check Point R80.x Management Server
Goal
Deploying the Check Point management server using an Azure marketplace template
2. Change the plan to 'Check Point Security Management' and click Create.
15
Step 2. deploy Security Management
1. Fill in the info per the details below. Click on 'Next: Check Point Security Management Server
settings’.
Setting Value
16
2. Fill in the info per the details below. Click on 'Next : Network Settings’.
Setting Value
Check Point R81
CloudGuard version
License type Bring Your Own License
Virtual machine size Leave as is (or choose a smaller one if instructed to do so)
Installation type Management
Allowed GUI clients 0.0.0.0/0
3. Under the Virtual network choose the 'myVNET' that we created in exercise 1, and for
Management subnet choose the network named 'Frontend'.
Click on ‘Next : Review + Create >‘.
4. Verify whether you passed the validation. You can click on 'Download a template for
automation' for feature deployments.
Click on 'Create'.
17
18
19
Step 3. connect to Security Management and start the CloudGuard service
1. Click on the 'CPmng' virtual machine and connect to the GAIA portal by browsing the listed
public IP address https://<public IP address>.
*Wait at least 10 minutes after Azure deployment for Security Management is finished
before connecting GAIA portal*
The username is 'admin' and the password the one you configured before.
20
2. Verify whether the System Uptime is over 5 minutes to have all backend resources
created and ready.
4. Connect to the Security Management server public IP address with an SSH session. Use the
same credentials as you did for the GAIA web portal.
21
Step 4. connect to the Security Management
1. Open the R81 SmartConsole GUI and connect to the Security Management server public IP
address. Use the same credentials as you did for the GAIA web portal.
2. Wander around the GUI and make yourself familiar with its options.
22
Exercise 3 - Deploy CloudGuard Gateway
Goal
Deploying the Check Point CloudGuard gateway using an Azure Resource Manager template
23
Step two: deploy Security Management
1. Fill in the info per the details below. Click on 'Next: Check Point CloudGuard settings’.
Setting Value
2. Fill in the info per the details below. Click on 'Next : Network Settings’.
Setting Value
Check Point R81
CloudGuard version
License type Bring Your Own License
Virtual machine size Leave as is (or choose a smaller one if instructed to
do so)
Installation type Gateway only
24
3. Under the Virtual network choose the 'myVNET' that we created in exercise 1. For Frontend
subnet choose the network named ‘Frontend'. For Backend subnet choose the network
named 'Backend'.
Click on ‘Next : Review + Create >’.
4. Verify whether you passed the validation. You can click on 'Download a template for
automation' for feature deployments.
Click on 'Create'.
Deployment of the R81 CloudGuard gateway takes less than five minutes.
25
26
27
Step 3. create a CloudGuard gateway object in Security Management
1. Log in to the R81 management server and configure the cluster object
Detailed instructions are in sk109360 .
2. Click GATEWAYS & SERVERS on the left menu.
Click on New wizard -> Gateway.
28
Setting Value
Gateway name CGIGW
Gateway platform CloudGuard IaaS
4. Fill in the one-time password that you configured in step 1 and click Next.
2. Verify whether you see two network interfaces in the Topology Results window. Click Close.
Uncheck the 'Edit Gateway properties ….' and click Finish.
29
Step 4. create a security policy
1. Navigate to the 'Security Policies' section, change the Access Control cleanup rule action from
'Drop' to 'Accept', and set Track to 'Log'.
30
3. Click 'Publish & Install'.
31
4. Navigate to the 'Logs & Monitor' section - the Logs tab. Refresh the view and see logs
originating from the CGIGW gateway.
32
Exercise 4 - Deploying a web server
Goal
Provision the Web Server instance from Azure Marketplace and protect it by CloudGuard gateway
33
3. Click on the '+ Subnet'. Add the subnet named 'Web' with the subnet address range of
10.0.2.0/24.
Step 2. create UDRs and associate them with the newly created subnet
1. Search the Azure portal for the 'Route tables' service and click on 'Create route table'.
34
2. Fill in the details as described below and click 'Next : Tags'.
Setting Value
Name myVNETroutes
Resource Group Choose the resource group that ends with -01 (the 1st on the list)
3. Skip the tags creation, click on 'Next : Review + Create'. See the validation passed and click on
Create.
35
4. Click on the 'Go to resource' link.
36
6. Fill in the details as described below and click 'OK'.
Setting Value
Route name Intra_VNET
Address prefix 10.0.0.0/16
Next hop type Virtual appliance
Next hop address 10.0.1.4 , use the private IP of CGIGW GW eth1. You can see it at
Azure portal -> Virtual machines -> CGIGW -> Networking ->
CGIGW-eth1 -> NIC Private IP
This will create a route entry, which will direct all VNET related traffic to CloudGuard gateway.
This includes traffic between subnets as well as traffic between instances in the same subnet,
effectively inserting macro as well as micro segmentation.
37
7. Repeat step 6 and add a new route with the details below:
Setting Value
This will create a route entry, which will direct all Internet related traffic to CloudGuard.
8. Repeat step 6 and add a new route with the details below:
Traffic between subnets as well as traffic between instances in the same subnet,
effectively inserting macro as well as microsegmentation.
Setting Value
This will create a route entry, which will direct all Internet related traffic to CloudGuard.
38
9. The created routes stay ineffective until associated with some subnet so that the subnet will
enforce the configured routes. Navigate to the 'Route tables' service -> myVNETroutes and
click on Subnets.
10. Click on 'Associate'. Select 'myVNET' for virtual network and 'Web' for subnet. Click OK.
39
Step 3. Provision the Web Server instance from the Azure Marketplace
1. Connect to the Azure portal, click on the portal menu icon -> 'Create a resource'.
Search for 'nginx open source' and select NGINX Open Source packaged by Bitnami virtual
machine
40
2. Click on 'Create'.
3. Fill in the info per the details below. Click on 'Next : Disks’.
41
Setting Value
Resource Group The one ending with '01'
Virtual machine name web
Subscription leave as is
Region use the same location as in exercise 1
Size Click ’See all sizes’ and manually choose ‘Standard_A1_v2’
Authentication type Password
User name webadmin
Password Choose your own
4. Click on 'Next: Networking>'.
5. Fill in the info per the details below. Click on 'Next : Disks'.
Click on 'Review + Create'.
Setting Value
42
6. Validate the virtual machine details and click 'Create' to start deployment.
Note: there is no way to set the virtual machine private IP address at that stage, Azure will provide
auto-assigned with an IP (DHCP), and you are able to change it later on (after deployment).
43
Step 4. creation of security policy
1. Login to the R81 management server.
2. Navigate to the 'Gateway & Servers' tab and doubleclick on CGIGW object.
3. Select Network Management -> eth0 -> Modify and uncheck the 'Perform Anti-Spoofing'
selection.
4. Click 'OK' twice and repeat the previous step for eth1.
5. Doubleclick eth1. Click on General -> Modify -> Override -> Specific -> New -> Network.
Create a new network object.
Name: All_myVNET
Network address: 10.0.0.0
Net mask: 255.255.0.0
44
6. Click OK four times until all windows are closed, and you are back to the main view.
7. Navigate to the 'Security Policies' tab and click on 'Add rule above' icon.
45
8. Add rule allowing HTTP traffic to the Web server from the internet:
a. Name: Traffic to Web server
b. Source: Any
c. Destination: click on the + sign -> New -> Host.
Name the object 'CGIGW_Frontend IPv4' and assign it IP 10.0.05, the private IP address of
CGIGW in the Frontend network.
Click OK to acknowledge the 'Multiple Object…' warning.
d. Services & Applications: click on the + sign, search for HTTP, and click the + sign again.
e. Action: change to Accept
f. Track: change to Log
9. Mark the rule you have just created and click on the 'Add rule below' icon.
46
10. Create another rule for administration and troubleshooting of the lab.
a. Name: SSH to Everywhere
b. Source: Any
c. Destination: Any
d. Services & Applications: click on the + sign, search for ssh, and click the + sign again.
e. Action: Accept
f. Track: Log
11. Verify whether your ruleset looks like this:
2. Create the following NAT rule to protect the connections to the web server.
a. Original Source: All_Internet
b. Original Destination: CGIGW_Frontend IPv4
c. Original Service: HTTP
d. Translated Source: Original
e. Translated Destination: click on the + sign -> New -> Host.
Create a host named 'myWeb' and IP 10.0.2.4, the private IP address of the 'web'
virtual machine in the Azure portal.
f. Service: Original
The NAT rule should look like this:
47
3. On the Install the access control policy on CloudGuard gateway
1. Verify connectivity to the web server by browsing to the CloudGuard gateway public IP
address web site below.
48
Exercise 5 - Configuring the CloudGuard Controller
Goal
Configure Azure's service principal name (SPN) to allow Check Point security management to access
Azure API
49
3. Doubleclick the CGIGW object -> General Properties -> Identity Awareness.
4. A window will open. Select the Terminal Servers and uncheck the AD Query. Click 'Next'.
5. Select the option: "I don't want to configure Active Directory at this time" and click
Next -> Finish -> OK.
50
6. Change to the Identity Awareness section, uncheck the Terminal Servers, and check the
'Identity Web API'. Click Settings.
51
7. In the new window click the green + sign on the right. Click the green + sign on the right.
Locate and choose a host called 'Localhost'.
52
8. Click 'OK' twice to close the CGICW object editing.
9. Click 'Yes' for the platform administration web portal warning.
10. Install access policy on the CGICW gateway.
53
Step 2: Connect CloudGuard Controller to the Azure account
1. We will create a trusted connection between the CloudGuard Controller and the
Azure account. Open SmartConsole, click on Objects -> More object types ->
Cloud -> Data Center -> New AWS.
2. Name the Azure object and use the Application ID, Secret key (as for Application Key field) and Tenant
ID (as for Directory ID field) you got in the registration email. Click on 'Test Connection' to see a
Connected status.
54
3. Publish the policy.
55
3. You can import objects from the Azure cloud in 3 ways:
1. Subscriptions view to import Azure vNETs, Subnets, or virtual machines to your
Security Policy
2. Security Groups view to import all virtual machines from the same security group
3. Tags view Security to import all virtual machines that have a specific Tag Key
56
Exercise 6 - Advanced scenarios
Goal
Explore additional features in the Azure environment.
Test scenarios:
1. Initiate 'fw monitor' on the gateway and inspect traffic traversing the gateway. See sk30583
for more details.
2. Activate Threat Protection blades (Anti-Virus, Anti-Bot, URL filtering, Application control) on
the gateway, inspect the logs, and check which traffic is hitting our environment (can you
identify malicious traffic targeting our environment)?
4. Verify whether traffic between two servers on the same subnet does not traverse through the
firewall (there is no microsegmentation or East - West protection). It can be verified in logs or
using the fw monitor on the gateway.
b. Verify whether traffic between two servers on the subnets traverses through the firewall
(there is microsegmentation or aka East - West protection). It can be verified in logs or using
the fw monitor on the gateway.