Check Point CCSA lab 5 of 14
Ordered layers: an Application Control layer after the firewall layer
Add a second, ordered policy layer for Application Control and URL Filtering after the Network layer, block a forbidden site with a custom Application/Site object, and learn why each ordered layer must explicitly accept the traffic it should not stop.
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 CCSA guided labs, then 05 - Ordered layers - an Application Control layer after the firewall layer
- Level
- Intermediate
- Time
- About 60 minutes
- Nodes need
- 10 vCPU, 15,872 MB
- Smallest plan
- Standard
The scenario
HR has asked that staff can no longer reach a betting site, which in this lab lives at http://198.51.100.10. The web team wants its own policy layer for this kind of rule, separate from the firewall team's Network layer, so that each team edits only its own rules. You will add an ordered layer called Web Control after Network.
What you’ll practise
- Explain how ordered layers are evaluated and why traffic must be accepted in every layer
- Enable Application Control and URL Filtering on a gateway
- Create an ordered layer with the Applications & URL Filtering blade and add it to a policy package
- Block a site with a custom Application/Site object
- Read logs that show the layer and rule that dropped a connection
The tasks
- Prove the site works today
- Turn on the blades
- The ordered layer
- Spot the trap
- Fix the layer
- Read the logs
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 CCSA guided labs.Open
05 - Ordered layers - an Application Control layer after the firewall layerand 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 CCSA 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.