JNCIA-SEC and JNCIS-SEC lab 1 of 16
SRX first steps with zones and host-inbound traffic
Bring a blank SRX into service: address its interfaces, build trust, dmz and untrust zones, decide what may reach the firewall itself, write the first policy and read the session table.
Run this lab
It needs Lite: its 4 nodes are set to 5 vCPU and 7,168 MB in total. That fits the free demo too.
In your workspace: Shared, then JNCIA-SEC and JNCIS-SEC SRX security guided labs, then 01 - SRX first steps with zones and host-inbound traffic
- Level
- Beginner
- Time
- About 50 minutes
- Nodes need
- 5 vCPU, 7,168 MB
- Smallest plan
- Lite
The scenario
Hartwell Marine runs a boatyard at Poole. A new SRX firewall (a vSRX here) has just been racked between the office LAN, a small DMZ and the internet. It has a hostname and a login and nothing else. You'll bring it into service: learn what you're looking at, address the interfaces, build three security zones, decide what may talk to the firewall itself, and write the first policy.
| Device | Interface | Address | Zone or gateway |
|---|---|---|---|
| SRX | ge-0/0/0 | 203.0.113.1/24 | zone untrust |
| SRX | ge-0/0/1 | 10.10.10.1/24 | zone trust |
| SRX | ge-0/0/2 | 10.10.20.1/24 | zone dmz |
| LAN-PC | eth0 | 10.10.10.10/24 | gateway 10.10.10.1 |
| DMZ-WEB | eth0 | 10.10.20.10/24 | gateway 10.10.20.1 |
| OUT | eth0 | 203.0.113.10/24 | gateway 203.0.113.1 |
LAN-PC is a member of staff's desktop. DMZ-WEB and OUT each run a web server on port 80. All three already have their addresses and gateways.
What you’ll practise
- Explain flow-based forwarding and what a session is
- Configure interfaces, units and security zones
- Use host-inbound traffic to protect the firewall itself
- Write a first interzone policy and read the session table
- Enable J-Web from the trust zone
The tasks
- Look around
- Address the interfaces
- Build the zones
- Host-inbound traffic
- The first policy
- J-Web
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
- SRX
ge-0/0/0to OUTeth0 - SRX
ge-0/0/1to LAN-PCeth0 - SRX
ge-0/0/2to DMZ-WEBeth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| SRX | Juniper vSRX NextGen template | vsrxng-24.4R1.9 | 2 vCPU, 4,096 MB |
| LAN-PC | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
| DMZ-WEB | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
| OUT | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
JNCIA-SEC and JNCIS-SEC SRX security guided labs.Open
01 - SRX first steps with zones and host-inbound trafficand 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 JNCIA-SEC and JNCIS-SEC labs
All JNCIA-SEC and JNCIS-SEC labs
Related labs in other courses
CloudLabBox is independent of Cisco and Juniper Networks. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.