Network+ lab 18 of 27
Secure remote management with SSH and a jump host
Take a router and a switch from Telnet with default passwords to hardened SSH management. You capture a Telnet password in clear text, enable SSH v2 with local accounts at two privilege levels, allow management only from an out-of-band jump host, and switch off services nobody uses.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 2,304 MB in total. That fits the free demo too.
In your workspace: Shared, then CompTIA Network Plus N10-009 guided labs, then 18 - Secure remote management with SSH and a jump host
- Level
- Intermediate
- Time
- About 60 minutes
- Nodes need
- 4 vCPU, 2,304 MB
- Smallest plan
- Lite
The scenario
An audit of the Harbour Logistics depot found the router and switch managed over Telnet with the factory-style password cisco, reachable from every user PC. Your job is to make management secure: encrypted, authenticated per person, limited to what each person needs, and possible only from the jump host on the separate out-of-band (OOB) management network.
| Device | Interface | Address | Network |
|---|---|---|---|
| R1 | Gi0/0 | 10.10.10.1/24 | user LAN (in-band) |
| R1 | Gi0/3 | 10.99.0.1/24 | OOB management |
| SW1 | Vlan99 (port Gi1/3) | 10.99.0.2/24 | OOB management |
| JUMP | eth0 | 10.99.0.10/24 | OOB management, the only admin entry point |
| H1 | eth0 | DHCP 10.10.10.100+ | an ordinary user PC |
Accounts to create (teaching values): admin / Harb0ur-Adm1n at privilege 15, helpdesk / Help-Desk1 at privilege 1, enable secret Harb0ur-Enable. Domain name harbour.lab.
What you’ll practise
- Explain in-band and out-of-band management, console access and jump hosts
- Show why Telnet is unsafe by capturing its credentials
- Enable SSH version 2 with RSA keys, local users and secrets
- Apply least privilege with privilege levels
- Restrict management access to a jump host with an access class
- Harden devices: remove default credentials, disable unused services, add banners and timeouts
The tasks
- Prepare the jump host
- See why Telnet must go
- Enable SSH v2 with local accounts
- Apply least privilege
- Allow management only from the jump host
- Switch off what nobody uses
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
- R1
Gi0/0to SW1Gi0/0 - SW1
Gi0/1to H1eth0 - R1
Gi0/3to OOB (network) - SW1
Gi1/3to OOB (network) - JUMP
eth0to OOB (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 MB |
| SW1 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 768 MB |
| H1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| JUMP | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
CompTIA Network Plus N10-009 guided labs.Open
18 - Secure remote management with SSH and a jump hostand 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 Network+ labs
Related labs in other courses
CloudLabBox is independent of CompTIA, Cisco and Netgate. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.