CloudLabBox
Try the free demo

JNCIA-SEC and JNCIS-SEC lab 13 of 16

Identity-aware policy

Write rules about people rather than addresses: fill the local authentication table, match roles and unknown users in policy, see names in the logs, and read how JIMS feeds the same machinery.

Run this lab

It needs Lite: its 3 nodes are set to 4 vCPU and 6,144 MB in total. That fits the free demo too.

In your workspace: Shared, then JNCIA-SEC and JNCIS-SEC SRX security guided labs, then 13 - Identity-aware policy

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Advanced
Time
About 60 minutes
Nodes need
4 vCPU, 6,144 MB
Smallest plan
Lite

The scenario

Addresses come from DHCP now, and Hartwell's auditors want rules about people: staff can use the supplier's stock console, contractors get the web only, and anyone the firewall can't identify gets nothing. On a real network, the firewall would learn who's where from Juniper Identity Management Service (JIMS). This lab has no Windows domain, so you'll feed the same machinery by hand, using the SRX's local authentication table.

DeviceInterfaceAddressZone or gateway
SRXge-0/0/0203.0.113.1/24zone untrust
SRXge-0/0/110.10.10.1/24zone trust
LAN-PCeth010.10.10.10/24gateway 10.10.10.1
OUTeth0203.0.113.10/24gateway 203.0.113.1
PersonAddress on LAN-PCRole
Alice10.10.10.10staff
Bob10.10.10.20contractor
A stranger10.10.10.30none

To act as one of them, use curl --interface, for example curl -m 8 --interface 10.10.10.20 http://203.0.113.10/. OUT runs a web server on port 80, and the stock console on port 8080. There are no policies yet.

What you’ll practise

  • Explain how JIMS gets user data to an SRX
  • Fill and read the local authentication table
  • Write policies with source-identity, roles and the authenticated and unauthenticated keywords
  • See what happens when a user moves
  • Read identity in flow logs

The tasks

  1. How identity reaches a firewall
  2. Fill the table
  3. Policies by identity
  4. People move
  5. What JIMS would look like

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.

Topology of Identity-aware policy3 nodes, 2 links. Every link is listed as text below the diagram.SRXLAN-PCOUTge-0/0/1eth0ge-0/0/0eth0
3 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • SRX ge-0/0/0 to OUT eth0
  • SRX ge-0/0/1 to LAN-PC eth0
Nodes in Identity-aware policy, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
SRXJuniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 4,096 MB
LAN-PCEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB
OUTEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder JNCIA-SEC and JNCIS-SEC SRX security guided labs.

  3. Open 13 - Identity-aware policy and 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.