Let’s not beat around the bush – it’s the SPAN port. The use of SPAN has long been the cause of network security issues.
Moreover, the prevalent use of SPAN ports to capture data has led to the prevalence in security breaches and data loss.
Security starts and ends with network visibility. If you’re unaware of a breach because you don’t have complete data capture, you’re susceptible to great damage. In fact, the average time that passes before an organization is aware of a data breach is 170 days.
In the 1990s, companies were sold on the false marketing promise that SPAN ports were a sufficient means of capturing data. A component of a switch, the SPAN port is simply convenient and cost-effective to use.
Unsurprisingly, you’re not alone if you’re still utilizing SPAN.
For starters, it’s too easy to program a SPAN port incorrectly. If you mess up here, you risk having problems that you won’t be aware of until it’s too late. And because SPAN ports groom your data, you don’t have real-time access to critical information.
Switches and routers are also easily hacked, meaning that attackers are able to access and easily alter your SPAN port functions. In fact, savvy hackers break into networks and reprogram devices to alter your network visibility, and they remain undetected.
SPAN ports also demand production bandwidth in order to copy and resend traffic over your network. Ironically, you’re investing a great deal of money to set up your network, but the SPAN port hoards the resources needed to monitor your activity.
The coming surge of software-defined networking (SDN) is another key factor in the use of SPAN. As you move to more dynamic network control, network visibility becomes an even greater focal point.
Why? Because SDN actually hides your data plane.
Some organizations exploiting traditional networking are able to use SPAN ports to gather baseline statistical information for behavioral analysis purposes. But with SDN, a SPAN port won’t suffice even for this basic task.
There is only one way to ensure 100% network visibility and complete data capture, and that’s to leverage the network TAP. With any other device or method, you’re going to continue to expose yourself to further network security issues. Stop risking your data and ensure your visibility into your network.
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.