I posted this on the news section on UGN Security
and thought it was really intresting so i am gonna post it in the news forum
What u guys think about the story ?
Using a honeypot to detect and surveil computer intruders might put you on the working end of federal wiretapping beef, or even get you sued by the next hacker that sticks his nose in the trap, a Justice Department attorney warned Wednesday.
"There are some legal issues here, and they are not necessarily trivial, and they're not necessarily easy," said Richard Salgado, senior counsel for the Department of Justice's computer crime unit, speaking at the RSA Conference here Wednesday.
An increasingly popular technique for detecting would-be intruders, a honeypot is a type of hacker flypaper: a system that sits on an organization's network for no other purpose than to be hacked, in theory diverting attackers away from genuinely valuable targets and putting them in an closely monitored environment where every keystroke can be analyzed.
But that monitoring is what federal criminal law calls "interception of communications," said Salgado, a felony that carries up to five years in prison. Fortunately for honeypot operators, there are exemptions to the Federal Wiretap Act that could be applied to some honeypot configurations, but they still leave many hacker traps in a legal danger zone.
One exemption permits interception of a communication if one of the parties consents to it the monitoring. To that end, Salgado suggested that honeypots display a banner message warning that use of the computer is monitored. "You can banner your honeypot... and you've got the argument that they saw the banner, continued using the system, and consented to monitoring," he said. But most hackers don't penetrate a system through the front door -- telneting in or surfing to a web page -- and if they never see the banner, they haven't consented to monitoring. "It's not the silver bullet."
The consent exemption might apply without a banner if a court determines that the honeypot itself is one of the "parties" to the communication, Salgado said. But that goes out the window -- or at least becomes more legally complicated -- the moment the hacker uses the honeypot to connect to another machine, or sets up a chat system on the box. Now the honeypot operator is intercepting communications between two or more parties. "Those kinds of situation become problematic."
Another relevant exemption passed in the USA-PATRIOT Act in October 2001, but only applies to cases where the government steps in to do the spying. The so-called "computer trespasser exemption" allows the government to intercept the communications of a computer intruder at the invitation of the victim. "Everyone coming into that honeypot is a trespasser... So this exception may work very nicely with honeypots when the government is coming in to do the monitoring," said Salgado. "But it has to be relevant to an ongoing investigation."
Can a Hacker Sue You?
That leaves a third "provider exemption" as the most promising for honeypot fans. This allows the operator of a system to eavesdrop for the purpose of protecting their property or services from attack. But even that exemption probably wouldn't apply to a system that's designed to be hacked, Salgado said. "The very purpose of your honeypot is to be attacked... so it's a little odd to say we're doing our monitoring of this computer to prevent it from being attacked."
Instead, Salgado favors configurations where a hacker is invisibly rerouted to a honeypot after beginning an attack on a production machine. "The closer the honeypot is to the production server, the less likely that it's going to have some of the legal issues that we're talking about," he said, because the monitoring becomes part of the normal process of protecting the production machine.
Despite the legal issues, Salgado praised honeypots as a valuable tool. But he cautioned attendees to consult with their company's legal department before deploying them. In addition to the danger of criminal liability, and myriad state laws that may be more restrictive than the federal statutes, Salgado warned that honeypot operators might get sued if they become an unwitting conduit to an attack on another victim.
And because the Federal Wiretap Act has civil provisions, as well as criminal, there's even a chance that a hacker could file a lawsuit against a honeypot operator that doesn't have their legal ducks in a row.
That's not as incredible as it sounds, the lawyer said, in an interview after the presentation. "It would take chutzpah," said Salgado. "But there's a case where an accused kidnapper who was using a cloned cell phone sued for the interception of the cell phone conversations... And he won."
In contrast, he said he's not aware of anyone being prosecuted for hacking a honeypot, which, after all, is meant to be hacked. "What I can tell you is that under the federal hacking laws, an attempt to hack can constitute a felony... The fact that it turned out to be a honeypot may not change the legality, but I haven't seen a court case yet."