Market Brief

Security Implications of Moving From Hub-and-Spoke to MPLS

Download Market Brief

MPLS delivers many benefits, including reduced congestion due to added flow path control, easier creation of VPN tunnels, Quality of Service and reduced network complexity. However, enterprises are struggling with many network security repercussions from migrating to MPLS networks.

Traffic Flow on a Hub and Spoke Network

hub and spokePrior to MPLS, a cost-effective Intrusion Detection System (IDS) deployment may have required security devices at the hubs only of a hub and spoke network. In order for traffic to travel from the Seattle, WA facility to the Denver, CO facility, it first must pass through the Atlanta, GA Data Center, as depicted by the orange arrows in Figure 1. With this network model, the IDS in the Atlanta Data Center inspects all traffic passing between facilities. It is important to realize, however, that this security “visibility” can only be maintained as long as traffic reliably passes through the hub.




Traffic Flow on a MPLS NetworkMPLS network

MPLS introduces the potential for the “spokes” to communicate directly with one another, bypassing the “hubs” and security devices resident within. As depicted by the orange arrow in Figure 2, traffic can now travel from the Seattle, WA facility to the Denver, CO facility without first going through the Atlanta hub. Consequently, all facilities can communicate with and infect one another without the protection of an IDS at the hub, which loses visibility into this “inter-facility” network traffic.



Is There a Cost-Effective Solution?

Enterprises considering MPLS migrations should evaluate a more cost-effective and complementary method of monitoring traffic that transits the MPLS cloud. By choosing a NetFlow™ or sFlow® StealthWatch® solution instead of deploying IDS sensors at each MPLS-enabled site, Lancope customers saved both upfront expenses and ongoing administrative costs associated with deploying, tuning and upgrading scores of extra IDS sensors. In addition, StealthWatch enabled them to:

  • regain network visibility into all host behaviors and all network traffic during and after the move to MPLS with a centralized deployment of StealthWatch
  •  increase confidence in security personnel workflow prioritization to immediately identify compromised hosts and dramatically limit the impact of network incidents
  • monitor the network, identifying incidents that may affect network and application availability

stealthwatch and mplsHow StealthWatch Works

At each MPLS-enabled WAN location, NetFlow or sFlow technology is enabled at the remote locations’ router(s). Detailed information about the traffic flowing from site to site is transmitted across the MPLS cloud to a central StealthWatch flow collector appliance. As the flows arrive at the centralized collector, StealthWatch performs behavior analysis to reveal network congestion issues, policy violations, worm outbreaks and other security-related incidents.