Check Point CCSE lab 6 of 10
Identity Awareness: Web API and access roles
Make two DMZ services depend on who is using a PC, not which PC it is. Enable the Identity Web API, build two access roles, rewrite the rules around them, and push identities from an external system. Watch one user replace another on the same address, and check the result on the PDP, the PEP and the API.
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 06 - Identity Awareness - Web API and access roles
- Level
- Advanced
- Time
- About 90 minutes
- Nodes need
- 10 vCPU, 15,872 MB
- Smallest plan
- Standard
The scenario
HQ-PC is shared. Today the rule DMZ administration lets anyone at that PC use SSH on DMZ-WEB, because the rule names the PC. Auditors want the rules to name people:
| Who | Role | May use |
|---|---|---|
| alice | DMZ-Admins | SSH to DMZ-WEB |
| bob | Web-Readers | the staff site, TCP 8080 on DMZ-WEB |
| nobody identified | none | neither |
Northgate's network access system already knows who signs in where, and it can call a web API. So the gateway will learn identities from that, through the Identity Web API. In this lab, the SMS plays that system.
This lab has no directory server. The requests therefore name the role themselves. With a directory, the gateway would work out the role from the user's groups.
What you’ll practise
- Explain the PDP and PEP, and where an identity lives
- Enable the Identity Web API and authorise a client
- Build access roles and use them as rule sources
- Add, show and delete identities with the Web API
- Verify identities with pdp monitor, pep show and show-identity
The tasks
- Check the starting point
- Enable the Identity Web API
- Access roles and rules
- Alice signs in
- Bob takes over
- Look inside the PDP and PEP
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
06 - Identity Awareness - Web API and access rolesand 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.