Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Firewalls
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: Blocking IM

from [Robert Hajime Lanning] Network Security [Permanent Link]
Subject: Re: Blocking IM
Date: Tue, 6 Dec 2005 17:34:00 -0800 
On 12/6/05, Morales, David (Seta) <David_Morales@onr.navy.mil> wrote:

We are blocking IM at the Firewall (juniper 5200) and through Surf-control
(Web Filtering product, but we are still able to connect to Yahoo IM. Has
anyone been able to do this successfully? And, does anyone have a list of
ports to block so we cannot get to this IM?


Alot of the clients scan through the firewall and pick the first port
available to use.
The IM server is listening on all ports.

The only real way to catch things like this a device that scans the
layer 7 protocol
and applies the policy to the protocol, not the port.

Something like the Packeteer PacketShaper.  Which is what we use for choking
streaming media.  (Which is mostly just a measured rate HTTP GET on
different ports.)

--
And, did Guloka think the Ulus were too ugly to save?
                                         -Centauri
[More with this subject...]




<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: Blocking IM, Devdas Bhagat
Next by Date:  RE: Tool for to test firewall, DavidMZendzian
Previous by Thread:  Re: Blocking IM, Devdas Bhagat
Next by Thread:  Re: Blocking IM, Yoshiro M Aoki
Indexes:  [Date] [Thread] [Top] [All Lists]