Anyone who watches The Wire and other police dramas knows that obtaining an admissible wiretap starts with detectives making a case against a suspected criminal and getting judicial buy-in. Once they collect the evidence, prosecutors go to court and move for a conviction.
Of course there’s more to it in the real world.
Now that defense attorneys have wised up to the principles behind networking, the technology used to obtain evidence is being called into question to debunk cases. To ensure quality of evidence, the Commission on Accreditation for Law Enforcement Agencies (CALEA) has outlined standards for electronic surveillance once a Title III surveillance application is approved:
Smart defense attorneys are well versed in exploring all possible Title III wiretapping violations – from Forth Amendment abuses to technical issues that could make it seems as if the data was incomplete, altered or unrelated to the defendant. When motions to suppress are upheld, all evidence obtained is considered fruit of the poison tree and is no longer admissible in court.
All good defense attorneys thoroughly interrogate law enforcement on their evidence gathering methods. When it originates with an electronic surveillance program, they look to impeach the data collection process by discovering possible:
For example, organizations often connect intercept devices to SPAN ports on network switches to get a copy of all traffic traveling over the network. Unfortunately, this configuration will invalidate the evidence obtained – when traffic spikes there is not enough capacity within the switch to copy the data so the switch just drops it. Cisco, a leading switch provider, recognizes this fact and even warned users that their switch treats SPAN data with a lower priority than regular port-to-port data.
After having major cases dismissed due to technicalities and dropped packets within the intercept process, the FBI sought a better approach. Today, their lawful intercept initiatives are anchored by a network TAP featuring link speed synchronization. These purpose built hardware devices were originally designed to ensure that mission-critical IT security and monitoring applications can always see 100% of the traffic flowing through the network. This approach eliminates many of the reasons for having evidence suppressed by ensuring that:
Building a case is difficult enough – having key evidence suppressed for technical reasons makes it all that harder to prosecute. Therefore it’s important to ensure that electronic surveillance solutions keep pace with the evolving technologies they are tasked with monitoring. Because network TAPs automatically mitigate issues between networks and intercept devices, they help law enforcement agencies eliminate many of technicalities that can compromise their work.
Need more information on designing protocols for lawful intercept programs? Let our network designers show you how to create highly defensible surveillance solutions. Contact us today.
Read more about lawful intercept in our free white paper, What's Your Network Missing: 7 Tools to TAP
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.