Objective. Students will demonstrate at least three containment techniques—network isolation, firewall rule insertion, and endpoint quarantine—without destroying forensic evidence.
This lesson, its worked examples and its practice questions has not yet been verified by an industry-certified professional or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.
VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.
When a security incident is confirmed, the instinct is to wipe the infected machine and move on. Resist that instinct. Rushing to eradicate malware before you contain the threat lets attackers spread laterally, exfiltrate more data, or destroy evidence you will need for forensics and legal proceedings. The NIST SP 800-61 incident response lifecycle places containment as a distinct phase that must happen before eradication or recovery. Your job in this phase is to stop the bleeding while keeping the patient alive—and keeping the evidence intact.
Network isolation cuts an infected host off from the rest of the network so malware cannot spread, receive new commands, or exfiltrate data. In a virtualized lab environment, you accomplish this by changing the virtual network adapter on the suspect VM from a bridged or NAT mode to host-only or a completely isolated internal network segment. This severs outside connectivity while leaving the VM powered on.
Critical evidence-preservation rule: Do not power off the machine before capturing a memory image. Volatile data—running processes, active network connections, encryption keys loaded in RAM—disappears the moment power is cut. Tools such as Magnet RAM Capture or FTK Imager can acquire a live memory dump while the VM remains running. Only after that dump is saved should you change network settings.
In physical environments, isolation may mean pulling a network cable, disabling a switch port via the management console (preferred because it avoids touching the machine), or moving the host to an isolated VLAN. Document every action with a timestamp.
Sometimes full isolation is too disruptive—a web server cannot go completely dark during business hours. In those cases you use targeted firewall rules to block only the malicious traffic while allowing legitimate traffic to continue. This is called partial containment.
On a Windows host, the built-in Windows Defender Firewall with Advanced Security lets you create outbound rules that block traffic to specific IP addresses or CIDR ranges. For example, if your threat intelligence identifies a command-and-control (C2) server at a known IP range, you insert an outbound block rule for that range. After adding the rule, verify it works: attempt a connection to the blocked IP (using `Test-NetConnection` in PowerShell or a similar tool) and confirm the connection fails. Log the verification result.
At the network perimeter, a firewall or router ACL can block the attacker's source IP inbound. On a pfSense firewall, you navigate to Firewall > Rules, select the appropriate interface, and add a block rule matching the attacker's source IP or range. Place the block rule above any permissive rules so it is evaluated first. Again, test and document.
Modern endpoint detection and response (EDR) platforms offer a quarantine function that isolates a host at the software level—blocking all network communication except the EDR management channel—without requiring physical access. This preserves your ability to continue collecting telemetry from the host. If your environment does not have an EDR tool, you can simulate quarantine in the lab by using host-based firewall rules to block all inbound and outbound traffic except a specific management IP, effectively achieving the same result.
Endpoint quarantine is especially useful when the suspect machine is a laptop that is off-site or a server in a remote data center where you cannot physically touch the hardware.
Every containment choice carries a trade-off. Full isolation stops all risk of spread but may take a critical service offline. Partial containment keeps the service running but leaves some attack surface open. You must document:
This documentation becomes part of the chain of custody and the after-action report. Regulators, legal counsel, and leadership will rely on it.
Cybersecurity lab work does not involve physical electrical hazards in the same way as electrical trades, but professional safety practices still apply:
CompTIA Security+ tests containment concepts under the Incident Response domain. CompTIA CySA+ goes deeper, requiring you to analyze threat indicators and select appropriate containment strategies based on evidence. ISC2 CC covers the importance of preserving evidence and following an IR process. All three credentials expect you to know that containment precedes eradication and that evidence integrity is non-negotiable.
Answer each question, then check it. Nothing is recorded; this is your own practice.
A free tech program — complimentary, as our commitment to get America working. Help us build VoTechWorks. Tell us what works, what doesn’t, and what you want to learn.