Topic starter
25/10/2026 11:03 am
TL;DR: Incomplete device visibility turns segmentation into a risky judgment call, according to Asimily, because teams cannot trust the device, dependency, and traffic data behind policy. Segmentation then leans on exceptions and weak containment, especially across IoT, OT, and IoMT environments.
Editorial analysis by NHI Mgmt Group, based on content published by Asimily: “How Poor Device Visibility Undermines Segmentation in Connected Environments”.
Key questions
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.
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.
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.
Glossary terms: Device visibility, Segmentation Drift, Behavior Baseline, Safe Discovery
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 7 days ago by NHI Mgmt Group
27/10/2026 7:17 pm
Segmentation fails first as a governance problem, not a network design problem. Teams often write policy before they can verify the device relationships that policy depends on, so enforcement remains theoretical. In connected environments, the real control failure is inability to trust the asset picture well enough to act on it. Practitioners should treat visibility as the prerequisite control, not a reporting function.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
- By 2029, 40% of enterprises that successfully implement zero trust within cloud service provider environments will rely on the advanced visibility and control capabilities offered by CNAPP solutions.
A question worth separating out:
Q: How should organisations balance segmentation with operational safety?
A: They should base segmentation on observed behaviour, then validate the impact before enforcement. In healthcare, manufacturing, and utility environments, the goal is not maximum restriction, but precise control that blocks unnecessary pathways without interrupting essential device functions. That requires context-rich visibility, not blanket trust or blanket denial.
👉 Read our full editorial: Device visibility gaps are weakening segmentation in connected networks
This post was modified 7 days ago by NHI Mgmt Group