Aggregator

You must login to view this content

You must login to view this content

Author, Creator & Presenter: Joe Sullivan, CEO, Ukraine Friends And Joe Sullivan Security

Our thanks to [un]prompted for publishing their Creators, Authors and Presenter’s outstanding [un]prompted 2026 AI Security Practitioner content on the Organizations' YouTube Channel.

Permalink

The post [un]prompted 2026 – Al Notetakers: The Most Important Person In The Room appeared first on Security Boulevard.

Learn how to secure AI agents in the enterprise. Explore the IDC Spotlight report on why agentic AI requires session-centric Browser Security Platforms.

The post Why IDC Believes the Next Billion Users Aren’t Human (And How to Secure Them) – Blog | Menlo Security appeared first on Security Boulevard.

Series Note: This article is Part Three of our ongoing series on AI‑driven side‑channel attacks and the architectural shifts required to defend against them. If you missed Part Two, you can read it here. 

AI is changing the shape of enterprise infrastructure faster than any technology in decades. Models are larger, pipelines are more distributed, and inference is increasingly pushed to the edge. But while computing, storage, and orchestration have evolved to meet this moment, one layer has not: the network.

Most organizations still rely on VPNs, SDWAN, and IPsec tunnels which are technologies designed for a world of centralized applications, predictable traffic, and human-driven workflows. AI workloads break every one of those assumptions. And as a result, the secure networking stack that once felt “good enough” is now a structural liability.

This post explains why traditional secure networking fails AI systems, which risks that creates, and why a new transport architecture is required for the AI era.

Legacy secure networking was built around a simple model: a small number of users accessing a small number of applications over predictable paths. AI workloads are the opposite.

Training and inference pipelines move massive datasets across nodes. Even lightweight inference generates rapid, high-frequency traffic patterns. Traditional encrypted tunnels serialize this traffic through fixed paths, creating chokepoints that throttle throughput, amplify jitter, and enable cyber targeting by source and/or destination.

Modern AI spans edge sensors, GPU clusters, cloud regions, and on-premises environments. Traditional secure networking assumes stable, long-lived endpoints. AI introduces thousands of ephemeral ones and expects them to communicate securely, instantly, and continuously.

Inference timing matters. Model accuracy and operational reliability depend on consistent, low-latency transport. VPNs and IPsec tunnels introduce overhead that AI workloads simply cannot absorb. The result is predictable performance bottlenecks, instability, and degraded model behavior.

Even when encrypted, conventional tunnels expose metadata that adversaries can analyze. For AI systems, this becomes a risk for “side-channel” attacks.

A VPN or IPsec tunnel is a stable, discoverable conduit. Traffic volume, timing, directionality, source and destination are all visible, even if the payload is encrypted. For AI workloads, these patterns can reveal:

• When models are running
• How often inference occurs
• The size and sensitivity of data being processed
• Operational tempo and mission cadence
• Which traffic flows a cyber attacker might want to target

Attackers don’t need to break encryption. They just need to observe the tunnel.

SDWAN improves routing flexibility, but it still relies on exposed tunnels and centralized controllers. Those controllers become high-value targets, and the tunnels remain predictable.

AI workloads generate distinctive traffic signatures. A model running inference at the edge looks nothing like a user browsing the web. These signatures become fingerprints, and fingerprints become attack surfaces. Traditional secure networking doesn’t hide these fingerprints, it highlights them.

AI workloads don’t run in pristine networks. They run in the real world where latency, jitter, and packet loss are common.

When a packet is lost inside a tunnel, the entire encrypted frame often needs to be retransmitted. This compounds loss, increases latency, and destabilizes throughput.

If the path degrades, the workload degrades. AI inference pipelines can’t tolerate this.

Remote industrial sites, mobile networks, and cross-region cloud traffic all introduce latency. VPNs and IPsec tunnels struggle here, often reducing throughput by orders of magnitude. AI workloads don’t degrade gracefully. They fail abruptly.

AI introduces new threat vectors that legacy architectures were never meant to defend against.

Attackers can infer model behavior, data sensitivity, topical content, and/or operational tempo from traffic patterns, even when encrypted.

If an attacker can observe or disrupt data-in-motion, they can extract model outputs, training data, or inference results.

AI systems increasingly support critical operations. Disrupting inference timing or data flow can have real-world consequences. Traditional secure networking protects confidentiality. AI systems require protection of confidentiality, observability, and operational integrity. Legacy tools only solve one of the three.

Protecting AI workloads requires a fundamentally different approach, one that eliminates predictable paths, removes exposed tunnels, and makes data-in-motion unobservable. The architectural principles are clear:

Traffic must be split, scattered, and routed across multiple unpredictable paths to eliminate chokepoints, increase resiliency and throughput, and reduce observability.

Routes must continuously change to prevent pattern analysis and side-channel inference.

Endpoints should never be exposed. Access should be ephemeral, least-privilege, and continuously verified.

The network should be invisible to unauthorized observers (i.e., no discoverable tunnels, no exposed control planes, no predictable metadata).

AI systems require architectures that traditional secure networking architecture cannot provide. AI workloads must maintain throughput and stability even in high-latency or lossy environments.

AI is reshaping how organizations operate, compete, and defend themselves. But the secure networking architectures protecting these systems haven’t kept up. VPNs, SDWAN, and IPsec tunnels were built for a different era ... one with different traffic patterns, different threat models, and far lower stakes.

AI workloads demand secure transport that is fast, resilient, unobservable, and built for adversarial environments. Traditional secure networking can’t deliver that, and the gap is widening.

In the next post, we’ll explore what a stealth, multipath, Zero Trust transport layer looks like in practice and how it transforms the security and performance of AI systems from the edge to the cloud.

If you’re evaluating how to secure AI workloads, our team can walk you through what a modern transport layer looks like in practice. 

📞 Schedule a conversation with Dispersive: www.dispersive.io

Header image courtesy of StockSnap from Pixabay.

The post Why Traditional Secure Networking Can’t Protect AI Workloads appeared first on Security Boulevard.