While software-defined networking (SDN) is slowly working its way toward having a real impact on how network architects can keep up with increasing demands, SDN adoption is on a collision course with another key networking challenge—security.
At the height of SDN’s hype in 2013, software-centric networks were being praised by many for their potential to revolutionize network security. The hype may have died down in recent years, leaving us with a more realistic perspective of the advantages and disadvantages of SDN for network security.
If you’re thinking of starting the transition from a hardware-centric network to SDN, don’t forget to weight the pros and cons in terms of network security.
As the security stack becomes more complex at the edge of the network, it’s no wonder that network architects and security professionals are looking for new ways to approach network protection. When data breach volumes started to spike in 2013, it seemed like SDN was going to be the answer.
Software-defined networking didn’t revolutionize network security in 2013, but its potential to improve network defense still stands today and technology is catching up. The following are just a few of the ways that SDN could make a positive impact on network security moving forward:
There are many more potential use cases for SDN in network security, but the bottom line is this—effectively implementing a software-defined network means you can extend your defense capabilities from simply blocking specific attacks to proactively adapting to new threats.
With so many potential network security advantages from SDN, it might seem like an obvious choice to make the switch. However, there are some key challenges to keep in mind.
The main issue regarding SDN security is the fact that virtualizing every aspect of the network infrastructure and its management greatly increases your attack footprint.
Rather than attackers having specific virtualized instances in the public cloud to target, they could potentially compromise your central controller and gain complete control over your network. This is an extreme scenario, but it could become very real as SDN sees more widespread adoption.
Digging a little deeper, software-defined networks could experience greater vulnerability due to the separation of control and data planes. If there is any disruption in communication between the two planes, it could result in a major hole for attackers to compromise. We know that attackers are relentless in their research and preparation, so it would only be a matter of time before these disruptions were exposed.
Just like in today’s hardware-centric networks, ensuring visibility in your software-defined network is the key to maintaining security. Deploying a foundation of visibility with a network TAPs may not be a point security solution, but it is certainly necessary if you want to reap the benefits of SDN while avoiding potential security pitfalls.
Looking to add visibility to your SDN deployment, but not sure where to start? Join us for a brief network Design-IT consultation or demo. No obligation - it’s what we love to do!
If the inline security tool goes off-line, the TAP will bypass the tool and automatically keep the link flowing. The Bypass TAP does this by sending heartbeat packets to the inline security tool. As long as the inline security tool is on-line, the heartbeat packets will be returned to the TAP, and the link traffic will continue to flow through the inline security tool.
If the heartbeat packets are not returned to the TAP (indicating that the inline security tool has gone off-line), the TAP will automatically 'bypass' the inline security tool and keep the link traffic flowing. The TAP also removes the heartbeat packets before sending the network traffic back onto the critical link.
While the TAP is in bypass mode, it continues to send heartbeat packets out to the inline security tool so that once the tool is back on-line, it will begin returning the heartbeat packets back to the TAP indicating that the tool is ready to go back to work. The TAP will then direct the network traffic back through the inline security tool along with the heartbeat packets placing the tool back inline.
Some of you may have noticed a flaw in the logic behind this solution! You say, “What if the TAP should fail because it is also in-line? Then the link will also fail!” The TAP would now be considered a point of failure. That is a good catch – but in our blog on Bypass vs. Failsafe, I explained that if a TAP were to fail or lose power, it must provide failsafe protection to the link it is attached to. So our network TAP will go into Failsafe mode keeping the link flowing.
Single point of failure: a risk to an IT network if one part of the system brings down a larger part of the entire system.
Heartbeat packet: a soft detection technology that monitors the health of inline appliances. Read the heartbeat packet blog here.
Critical link: the connection between two or more network devices or appliances that if the connection fails then the network is disrupted.