Check Point CCSE lab 3 of 10
Advanced NAT and policy layers
Go beyond automatic NAT: publish a service on another port, translate source and destination together for a partner, give one host its own hide address, then watch each translation happen at the gateway's inspection points with fw monitor. Finally, tidy the policy with an inline layer for the DMZ and an ordered layer for web control.
Run this lab
It needs Standard: its 6 nodes are set to 10 vCPU and 15,872 MB in total.
In your workspace: Shared, then Check Point CCSE guided labs, then 03 - Advanced NAT and policy layers
- Level
- Advanced
- Time
- About 110 minutes
- Nodes need
- 10 vCPU, 15,872 MB
- Smallest plan
- Standard
The scenario
Northgate has automatic NAT and a simple rule base. Four requests have arrived from the business, and automatic NAT can't meet any of them:
| Request | Address | What it needs |
|---|---|---|
| A test site on DMZ-WEB, on port 80, reachable from outside on 8080 | 67.83.0.121 | port forward |
| A partner portal on DMZ-WEB port 8081. The partner connects from 67.83.0.113, and the application must see requests from the gateway's DMZ address, 10.0.2.111 | 67.83.0.122 | twice NAT |
| HQ-PC must reach the internet server from an address of its own, for the provider's allow list | 67.83.0.123 | dedicated hide address |
| The rule base is growing: move the DMZ rules into a layer of their own, and add web control as a separate step | inline and ordered layers |
What you’ll practise
- Write manual NAT rules: port forward, twice NAT and a dedicated hide address
- Explain NAT rule order and why twice NAT needs a specific source
- Publish manual NAT addresses with proxy ARP
- Trace a translation through the i, I, o and O inspection points with fw monitor
- Combine an inline layer and an ordered layer, and say which rule decides
The tasks
- Read the starting point
- A port forward
- Twice NAT for the partner
- A dedicated hide address
- Publish the addresses and install
- Watch the translation
- An inline layer for the DMZ
- An ordered layer for web control
The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.
Topology and devices
The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.
Every link, as text
- SMS
eth0to HQ-LAN (network) - HQ-GW
eth0to HQ-LAN (network) - HQ-GW
eth1to Internet (network) - HQ-PC
eth0to HQ-LAN (network) - ADMIN-PC
eth0to HQ-LAN (network) - ISP
Gi0/0to Internet (network) - HQ-GW
eth2to DMZ-WEBeth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| SMS | Check Point Security Management Server | cpsms-R81.20-Licensed | 4 vCPU, 8,192 MB |
| HQ-GW | Check Point Security Gateway VE (cpsg template) | cpsg-R81.20-Licensed | 2 vCPU, 4,096 MB |
| ISP | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 MB |
| HQ-PC | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| DMZ-WEB | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| ADMIN-PC | EVE-NG Firefox browser (Docker) | eve-firefox:latest | 1 vCPU, 2,048 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
Check Point CCSE guided labs.Open
03 - Advanced NAT and policy layersand start its nodes, then open Lab Tasks for the scenario and the steps.
The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.
More Check Point CCSE labs
Related labs in other courses
CloudLabBox is independent of Check Point and Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.