Topic starter
25/10/2026 11:03 am
TL;DR: Segmentation efforts often stall because security teams cannot fully see the devices, dependencies, and traffic patterns they need to trust before enforcing policy, especially across IoT, OT, and IoMT environments, according to Asimily. The governance problem is not intent but decision quality: without reliable visibility, segmentation becomes guesswork and defaults to permissive controls.
Editorial analysis by NHI Mgmt Group, based on content published by Asimily: “How Poor Device Visibility Undermines Segmentation in Connected Environments”.
Key questions
Q: What breaks when device visibility is incomplete in segmented networks?
A: When visibility is incomplete, segmentation becomes a guess instead of a governed control.
Q: Why does poor visibility make segmentation projects fail so often?
A: Poor visibility means teams cannot see the traffic paths, device relationships, or policy exceptions they need to govern.
Q: What are the signs that segmentation is failing in a real environment?
A: Segmentation is failing when a compromise in one zone quickly reaches other networks, critical services, or shared infrastructure that should have been separated.
Practitioner guidance
- Implement continuous device discovery Replace static inventories with discovery that updates as authorised, transient, unmanaged, and rogue devices appear across IT, IoT, OT, and IoMT estates.
- Baseline device communications before enforcing rules Map normal traffic, protocol use, and dependency paths so segmentation policies reflect real device behaviour rather than assumptions.
- Simulate policy impact against observed traffic Test proposed segmentation changes against live communications and known exceptions before deploying them to NAC or firewall systems.
Bottom line: Incomplete device visibility turns segmentation into a risky judgement call instead of a reliable control.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →