skip to content

In a security practice lab, why does a deliberately vulnerable machine not belong on the same network as everyday office devices?

level: juniorimportance: must knowfreq 62%

answer

  1. a place where nothing real is at stake
  2. weak on purpose, so assume hostile
  3. attached to the office means reachable
  4. no route in and no route out

basics

~20 s

A lab is where every system is yours, so mistakes cost nothing outside it. A deliberately vulnerable machine is weak by design, so on the office network it is an exposed host. It needs a segment with no route in or out.

solid answer

~50 s

A practice lab is a place where every system is yours or was provided for the purpose, so an action that goes wrong, or that nobody scoped, costs nothing outside it. A deliberately vulnerable machine is weak on purpose, so you treat it as already hostile. Attached to the office network, directly or through a virtual machine that joins the physical network, it becomes an exposed host that colleagues' devices can reach and that can reach them. So the lab sits on its own segment with no route to the everyday network and no inbound path from it, and outbound traffic from the targets is denied until you open something deliberately. The office's network defences typically do not see traffic between a guest and its host, so the lab has to carry its own boundaries. The cost is convenience: updates and downloads happen outside the lab, not from the targets.

go deeper

for a junior

Say what a lab is for and why a machine that is weak by design must not share a network with everyday devices.

for a middle

Check three properties together: what a target can reach, what can reach it, and what is inside it. Explain why a guest joined to the physical network breaks the first two.

for a senior

Turn it into an incident: work out how the image was attached, what could reach it, and what must be treated as exposed, rather than declaring the matter harmless.

for a principal

Decide how the standard makes the safe arrangement the easy one, so isolation does not depend on each analyst remembering it.

## What a practice lab is for A **practice lab** is an environment where every system is yours, or was provided to you for the purpose of being practised on. That single property is the whole point. When you try something, misjudge it or leave it half finished, the effects stay inside a space that nobody else depends on. Contrast that with the real world, where an action against a system you do not own or have written permission to test is a different kind of act altogether. A lab removes the question of scope from your practice, because nothing outside it is touched. A **deliberately vulnerable machine** is the usual lab target: a system built to contain weaknesses so that you can study them. Weak by design means it behaves like an already compromised host. It may run outdated services, accept trivial credentials or expose functions no sensible system would. The right mental model is that every target is hostile from the moment you start it. ## Why it cannot share the office network If such a machine joins the everyday network, three things go wrong at once: - **Colleagues' devices can reach it.** It is a weak host sitting among machines that hold real data, and anything on that network can talk to it. - **It can reach them.** A compromised or simply careless target can probe, send traffic to and fetch from everything its network allows. - **It inherits the office's trust.** Printers, file shares and monitoring all treat addresses on the office network as friendly. The virtualization hosting the machine does not change this. A virtual machine attached in a mode that exchanges packets directly through the host's physical network card is a participant of that physical network (a desktop hypervisor's manual describes direct bridged networking this way). The isolation a hypervisor provides, which the NIST guidance on full virtualization describes as limiting what each guest can reach among other guests, the hypervisor and the host, is about the host's resources. It says nothing that makes the surrounding network safe for a hostile guest. ## Check three properties together For any lab arrangement, ask all three questions. A setup is called isolated only when all of them have a good answer. 1. **What can each target reach?** Only the other lab machines it is meant to meet, and nothing outbound unless someone opened it on purpose. 2. **What can reach each target?** Only the operator machine, and no path from the everyday network. 3. **What is inside each target?** Nothing real: no production credential, no real data, no password you use elsewhere. | Arrangement | Reachable from office devices? | Can reach office devices? | Verdict | |---|---|---|---| | Guest joins the physical network directly | Yes | Yes | Not a lab, an exposure | | Guest behind address translation | No, by default | Yes, outbound to the office and internet | Fails outbound-denied by default | | Network shared with the host only | No | Can reach the host | Host must be treated as exposed to it | | Network visible only to selected guests | No | No | Fits the purpose | The table names properties rather than menu entries, because the mechanics of each mode belong with the virtualization material. The names matter less than the questions. ## The office's defences do not cover the lab The NIST guidance on full virtualization notes that under typical configurations traffic between guests, or between a guest and its host, does not pass through network-based security controls, so host-based controls have to monitor it. The practical consequence is that you cannot lean on the office firewall or its sensors to catch a misbehaving target. The lab brings its own boundaries and its own watchfulness. ## What it costs, and the usual slips The price of isolation is convenience. A target that cannot reach the internet cannot download an update, and that is intended: fetching tools or packages happens on a different, trusted machine, and files cross into the lab deliberately. Typical slips include: - Plugging the lab into the office wireless network "just for today". - Treating a patched laptop as sufficient protection for the network it sits on. - Reusing a real credential inside a target because it is easier to remember. - Forgetting that the host running the lab is itself a machine on the everyday network, and has to stay patched even though its guests do not. If a team learns that someone has run such an image on the office network, the right response is to find out how it was attached, for how long, and what could reach it, and to treat reachable devices as possibly exposed until the facts say otherwise.

  • An analyst says they ran a downloaded vulnerable image on a laptop attached to the office wireless network last week. What do you do first?
    Stop it, then establish how it was attached, for how long, and which devices could reach it. Treat the laptop and anything reachable as possibly exposed until those facts say otherwise, and do not accept 'nothing happened' as an answer. Afterwards, rebuild the lab arrangement so the safe setup is the default.
  • Isn't the hypervisor's isolation enough to make this safe?
    No. The isolation the NIST guidance describes limits what a guest can reach among other guests, the hypervisor and the host. It does not make the network the guest is attached to safe. A guest placed on the physical network is a participant of it, whatever sandboxing surrounds it.
  • Why can't the office's existing network monitoring watch the lab for you?
    Under typical configurations, traffic between a guest and its host does not pass through network-based controls, so the NIST guidance says host-based controls should monitor it instead. The lab therefore needs its own boundaries and its own watching, not borrowed coverage.

A chemistry bench with its own extraction and no door to the corridor: a spill has nowhere to go, and nobody walks through it on the way to lunch. The protection runs both ways.

  • It is only a test machine, so the office network is fine
  • Running it in a virtual machine makes the surrounding network irrelevant
  • A fully patched laptop is protection enough for the network it joins
  • The office firewall already protects anything plugged into the office network
  • Good intentions make the exposure acceptable