Re: Blocking unauthorized remote access
- From: Mike Dorn <mrdorn@xxxxxxxx>
- Date: Sun, 24 Sep 2006 03:53:25 -0500
Volker Birk wrote:
Mike Dorn <mrdorn@xxxxxxxx> wrote:Obviously, but this is more of a tool for the serious "hacker" type. We're more worried about commercial sites that just sell a "click here to use" service, as any dummy can install them without knowing how it works or investing any serious effort to set it up.
Has anybody seen a comprehensive list of addresses used by the various "services" that allow unauthorized users to remote into their work computers from home, bypassing corporate security? These things work by making an outbound connection from the target PC to a fixed external site. The user then contacts the external site from their home PC or traveling laptop, and the site uses the previously-opened connection to create a remote session for them. It's not caught by normal firewall config, because the outbound ssl connection appears to be legal.
http://www.agroman.net/corkscrew/
With such a tool, any site on the outside can be used.
Aren't all admin problems really social problems? Unfortunately, with hundreds of users spread thru multiple sites and a complex 7x24 operation, we can't just look for open sockets during "non-working hours". What we can do, however, is look for traffic to specific addresses, once they are known.
I think, you have a social problem, not a technical one. Try to detect
open sockets or reconnecting sockets after working time and talk to the
people who are installing such things.
Yours,
VB.
.
- Follow-Ups:
- Re: Blocking unauthorized remote access
- From: Moe Trin
- Re: Blocking unauthorized remote access
- References:
- Blocking unauthorized remote access
- From: Mike Dorn
- Re: Blocking unauthorized remote access
- From: Volker Birk
- Blocking unauthorized remote access
- Prev by Date: Re: Enable / disable internet access in selected classrooms
- Next by Date: Re: Cisco 501 PIX port forwarding (outside DHCP)
- Previous by thread: Re: Blocking unauthorized remote access
- Next by thread: Re: Blocking unauthorized remote access
- Index(es):
Relevant Pages
|