Scott Fulton, Chief Product & Technology Officer at BlueCat.
Over the years, the networking industry sought to unify monitoring, troubleshooting, management, security and automation in one dashboard. Dashboards improved visibility, but they failed to reduce complexity and improve operational efficiency.
Teams see more than ever but still struggle to act on the information. A recent Enterprise Management Associates’ survey of 300 IT professionals from December 2025 to January 2026 found that 48% of organizations are fully confident they have visibility into all network assets. The report was commissioned by my company.
One of the biggest reasons is that dashboards never resolved the fragmentation underneath. As data volumes ballooned, the problem only intensified. Data exists across DNS, DHCP, IP address management (IPAM), cloud platforms and security tools, but it remains disconnected. Fragmented environments contribute to outages and security risks tied to the mismanagement of core network services.
The next step is for the industry to look beyond the dashboard to the data layer.
When Visibility Doesn’t Equal Coordination
Most enterprise environments remain collections of loosely integrated systems. Monitoring tools track performance. Security platforms detect threats. IPAM systems manage device identity. Each operates with its own data model and context.
During an incident, teams must manually correlate data across systems to determine which devices are affected, who owns them and what policies apply. Teams get trapped in analysis.
This is not an edge case. The Uptime Institute’s industry analysis shows that misconfigurations of core network services lead to performance problems and downtime. In financial services, where downtime exceeds $2.2 million per hour, delays chip away at the bottom line.
As a technology leader working in core network services—specifically DNS, DHCP and IPAM, which underpin how devices connect and communicate across modern environments—I see this challenge across enterprises.
It’s not specific to any one platform. Most organizations operate across hybrid and multicloud environments with overlapping systems and only partial integration, making unified operations difficult to achieve.
The Limits Of AI On Fragmented Systems
Many organizations want AI to close this gap. They want AI to detect anomalies, prioritize incidents and recommend actions. But its effectiveness depends on context.
When systems remain disconnected, AI has limited visibility into the full picture. It may identify unusual traffic patterns, but without shared data on device identity, ownership or policy, it cannot accurately assess risk or determine appropriate action.
AI acts differently with a unified data foundation. Instead of isolated anomalies, it can trace activity across identity, telemetry and policy. Imagine latency issues halting activity on a trading floor. With a unified data foundation, the network team can trace the issue from the DNS request through the network path to the device and its policies in seconds.
Why The Data Layer Matters
The issue is architectural. Networks generate vast amounts of telemetry. That data is distributed across systems that do not operate as a unified whole.
Core services such as DNS, DHCP and IPAM sit at a foundational layer of this architecture. They define identity, addressing and connectivity. When these systems operate in isolation from security, cloud and observability platforms, the organization lacks a consistent understanding of what is happening across the network.
Making The Shift: From Fragmentation To Coordination
The outcome changes when the data is unified. Organizations that make progress here tend to see improvements in resilience, security posture and operational efficiency.
For technology leaders, the transition to a more integrated model is incremental. It involves aligning data, systems and operating practices rather than replacing any single tool:
• Start with complete visibility, not just dashboards. Many organizations still lack a reliable, unified view of IP space, DNS infrastructure and cloud resources. Establishing that foundation is a prerequisite for integration.
• Establish a consistent source of network identity. A shared understanding of device identity—linking IP addresses, DNS records, ownership and policy—is critical. Without it, correlation remains manual and slow.
• Integrate across environments, not just tools. Integration efforts need to extend across multiple clouds and legacy systems, which often involves APIs, shared data models and consistent governance.
• Prioritize automation where fragmentation creates risk. Manual processes still dominate in areas like compliance checks, network discovery and failover testing. Automation in these domains can reduce both operational burden and risk.
• Align teams as well as technology. Organizational silos between network, cloud and security teams remain a primary barrier. Without shared ownership, even well-integrated systems struggle to deliver coordinated outcomes.
Architecture Before Autonomy
Dashboards are evolving. Rather than acting as the primary point of convergence, they will reflect an already integrated system.
Their value will shift from aggregating disconnected signals to presenting coordinated insights derived from shared data. In that context, dashboards support decision-making rather than compensating for fragmentation.
The industry’s trajectory points toward more responsive, intelligent networks. But autonomy will not only emerge from better interfaces.
It depends on architectures where identity, policy and telemetry are inherently connected. Organizations that align these foundational elements can move from visibility to coordinated action.
Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?
