What best mitigates a legacy IoT OS vulnerability quickly?
A newly identified network access vulnerability has been found in the OS of legacy IoT devices. Which of the following would best mitigate this vulnerability quickly?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests whether you know that legacy/unsupported IoT devices usually cannot be patched, so the fastest mitigation is network segmentation rather than patching or replacement.
A newly identified network access vulnerability in the OS of legacy IoT devices cannot be patched if the devices are unsupported. This SY0-701 study page establishes segmentation (C) as the fastest mitigation, isolating the vulnerable IoT devices from the rest of the enterprise network.
Many candidates pick patching (B) because it is the textbook fix for a software vulnerability, but legacy IoT devices typically no longer receive OS updates, so patching is neither available nor quick.
Community Discussion (12 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Network segmentation (C) is correct because it is a compensating control that can be applied immediately without waiting on the device vendor. By placing the legacy IoT devices in an isolated VLAN or restricted subnet with strict access control lists, the enterprise limits the network access an attacker could abuse through the OS vulnerability. This matches the stem's demand for the fastest mitigation, since it does not require a patch that may not exist or a hardware refresh cycle. Segmentation also buys time to monitor, contain, and later replace or upgrade the devices on a planned schedule.Why the Other Options Are Wrong
Insurance (A) transfers financial risk rather than mitigating the technical vulnerability; it does nothing to stop exploitation. Patching (B) is the normal remediation for a software flaw, but legacy IoT devices are typically past end-of-support, so no vendor patch exists and constrained hardware or firmware may not support updates. Replacement (D) is the most permanent fix, but it is not the quickest: procurement, compatibility testing, OT/IT integration, and downtime make it a slow, planned project.Community Comment Notes
Community consensus strongly favors segmentation. KrazyMonkey noted, "I've not heard of patching legacy devices," and CyberSecurity24 explained that "patches may no longer be provided" for legacy devices, making patching unsuitable as a quick mitigation. AutoroTink openly retracted an earlier patching answer, while dbrowndiver emphasized that legacy IoT devices often cannot be quickly patched or replaced due to operational constraints. ProudFather argued for replacement, but that view overlooks the question's emphasis on speed.Exam Strategy
When a question says 'legacy' or 'unsupported,' eliminate patching immediately unless a patch source is stated. Look for the control that delivers the fastest risk reduction—usually segmentation or another compensating control—while treating replacement as the durable but slower option.
Frequently Asked Questions
Why isn't patching the fastest fix for a legacy IoT OS vulnerability?
Legacy IoT devices usually no longer receive vendor OS updates, and constrained hardware can make patch deployment impractical, so patching is not a quick mitigation.
Why doesn't replacement beat segmentation for the legacy IoT devices?
Replacement fixes the root cause permanently but requires procurement, compatibility testing, and operational downtime, so it is slower than isolating the devices with segmentation.
Related Analysis
Practice All SY0-701 Questions
Access 100 questions with complete answers and detailed explanations.
View Full SY0-701 Practice Test →