CloudLabBox
Try the free demo

JNCIA-SEC and JNCIS-SEC lab 12 of 16

SSL forward proxy with a lab CA

Make the SRX a forward proxy: build a private CA, load upstream trust, find out why a proxy on its own does nothing, deploy the CA to a client, and stop an attack hidden inside HTTPS.

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 12 - SSL forward proxy with a lab CA

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 80 minutes
Nodes need
4 vCPU, 6,144 MB
Smallest plan
Lite

The scenario

Most of what crosses Hartwell's firewall is now TLS, so its IDP rules see nothing but ciphertext. You'll make the SRX a forward proxy for outbound web traffic: it decrypts, inspects and re-encrypts. You'll build a small private CA on the SRX, teach staff PCs to trust it, and prove that an attack hidden inside HTTPS gets stopped.

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
On OUTAddressCertificate
shop.example203.0.113.10Issued by Example Public CA, with the CA file at http://203.0.113.10/public-ca.pem
bank.example203.0.113.20The same

LAN-PC already resolves both names through /etc/hosts. Policies TLS-OUT (HTTPS) and WEB-OUT (HTTP) permit trust to untrust.

What you’ll practise

  • Explain client and server protection
  • Generate a CA on the SRX and load upstream CA certificates
  • Configure an SSL proxy profile and apply it with an interested service
  • Deploy the CA to a client and verify the re-signed certificate
  • Exempt a destination from decryption

The tasks

  1. The baseline
  2. A private CA on the SRX
  3. Tell the SRX which server CAs to trust
  4. The proxy profile
  5. Give it something to inspect
  6. Deploy the CA to the client
  7. Inspection, proved
  8. Leave the bank alone

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 SSL forward proxy with a lab CA3 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 SSL forward proxy with a lab CA, 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 12 - SSL forward proxy with a lab CA 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.