In our new infographic, The Evolution of Network Visibility, we took a trip down melody lane to show readers the events and innovations that sparked the rise of network visibility.
Relax and rewind to some rock from the 2000’s, when networking gained in complexity and keeping secure become tougher than ever before.
As soon as we and rang in the new century, network complexity exploded like a Bugs Bunny cigar. Networks were no longer dedicated to hardwiring desktop PCs, and tying offices together and reaching out to the Internet.
Networks encompassed wireless, remote users and partners, and ran rich new apps—video and web conferencing, Cloud applications, and social media. The networks to support it all got faster, and complexity multiplied. Two problems—it was harder to manage and understand this complexity, and there was a much larger and more intricate field of attack vectors.
It may sound Korn-y, but network managers couldn’t just TAP dance around these issues. They took charge of their networks with more monitoring, management and security appliances. However, the appliances themselves became a problem. They were just one more layer to connect, monitor and protect.
In the early 2000’s a few things were hot—including Green Day and Korn. But with all this mess, network managers had their own favorite tune—network TAPs!
Like Billy Joe Armstrong, in the 2000’s hackers got better with age and their attacks became more advanced, widespread and persistent.
The B side of that was network pros demanded deeper visibility into connections and traffic. Network monitoring was part of that, but so was the complete picture only a TAP can create. But a TAP is no one hit wonder. Smart IT has TAPs tied in to aggregate traffic data from an array of network devices, offering broad and deep visibility across all the tracks.
IT had some other requests for network players—give us deep visibility into Web firewalls, and help make sure there is no network downtime.
In the first decade of the new century, network TAPs came to the rescue like a Wall Street bailout and helped hunt down hackers when they come around.
In our Evolution of Network Visibility infographic, we cover the chain of events that have led us to the current state of network visibility. Just as the favorite rock bands of the decades have emerged and evolved, so too have network TAPs and security appliances.
Rock on and discover how each decade came to grips with the growing need for network visibility.
Tweet and tell us where your visibility story began #NetworkFlashback.
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.