Re: Blocking p2p traffic

[David Curry <david.curry () NEWSCHOOL EDU>]

Just one. It was an off-list reply, so I'll leave it to the author to chime
in if he/she wants.

But the gist of the response was that they had used a PacketShaper to limit
(not block) P2P on the network, allowing it to have more bandwidth during
less busy times. They got rid of it a couple of years ago and spent the
money on more bandwidth instead. They get about the same number of DMCA
notices, but they have more bandwidth.

--Dave


--

*DAVID A. CURRY, CISSP* • DIRECTOR OF INFORMATION SECURITY

*THE NEW SCHOOL* • 55 W. 13TH STREET • NEW YORK, NY 10011

+1 212 229-5300 x4728 • david.curry () newschool edu



On Tue, May 7, 2013 at 3:57 PM, Leo Song <song () uoguelph ca> wrote:

> David.
>
> How many responses you received which mentioned "Add more bandwidth
> instead of trying to block"? That will be very helpful. thanks.
>
>
> Leo Song
> Senior Analyst, Network and Security
> Computing and Communications Services (CCS)
>
> 519-824-4120 Ext53181
> song () uoguelph ca
> www.uoguelph.ca/ccs
> Room008, Animal Science and Nutrition Building
> Guelph, Ontario, N1G 2W1
>
> ------------------------------
> *From: *"David Curry" <david.curry () NEWSCHOOL EDU>
> *To: *SECURITY () LISTSERV EDUCAUSE EDU
> *Sent: *Tuesday, May 7, 2013 2:23:39 PM
>
> *Subject: *Re: [SECURITY] Blocking p2p traffic
>
> I did promise a summary once the responses died down, so here it is. The
> following solutions were mentioned:
>
>    - Add more bandwidth instead of trying to block
>    - Procera
>    - NetEqualizer
>    - Exinda
>    - TippingPoint IPS
>    - SourceFire IPS
>    - Fortinet
>    - Cisco SCE
>
> Exinda was mentioned by two people; all the others were mentioned by one
> person each. Everybody seems to be generally happy with their solutions;
> Procera and NetEqualizer received perhaps somewhat more enthusiastic
> "likes" than the others, but that's my subjective reaction.
>
> Thanks to all who responded.
>
>
> --Dave
>
>
> --
>
> *DAVID A. CURRY, CISSP* • DIRECTOR OF INFORMATION SECURITY
>
> *THE NEW SCHOOL* • 55 W. 13TH STREET • NEW YORK, NY 10011
>
> +1 212 229-5300 x4728 • david.curry () newschool edu
>
>
>
> On Thu, May 2, 2013 at 4:31 PM, David Curry <david.curry () newschool edu>wrote:
>
> > We currently have an aging Packeteer whose sole remaining purpose in life
> > is to "shape" peer-to-peer file sharing traffic (BitTorrent and friends)
> > down to zero, thus keeping us from receiving DMCA takedown requests. It's
> > worked well at this for several years, but now we're starting to max it out
> > as far as licensed bandwidth goes, and we're not inclined to spend more
> > money on such an old device.
> >
> > So... we're in the market for something new, and thought we'd ask what
> > other schools are using. From a bit of research it looks like Procera and
> > Exinda are still in that space; A10 has a product on their website still,
> > but it doesn't look like there's much focus on it anymore (maybe we're
> > wrong). Juniper SRX firewalls (which we own) have some capabilities in this
> > space via their AppID stuff; we'd be interested in hearing from anyone
> > using them for that purpose. And yes, we know that Palo Alto firewalls can
> > do it -- but we don't have Palo Altos and have no plans to purchase them
> > anytime soon, so that's not really an option for us.
> >
> > If you're using something OTHER THAN a Palo Alto firewall to
> > block/limit/reduce peer-to-peer traffic:
> >
> >    - What product are you using?
> >    - What are you doing with peer-to-peer (blocking, limiting, etc.)
> >    - How well is it working?
> >    - Do you like it?
> >
> > After responses taper off, I'll summarize back to the list.
> >
> > Thanks,
> > --Dave
> >
> >
> >
> > --
> >
> > *DAVID A. CURRY, CISSP* • DIRECTOR OF INFORMATION SECURITY
> >
> > *THE NEW SCHOOL* • 55 W. 13TH STREET • NEW YORK, NY 10011
> >
> > +1 212 229-5300 x4728 • david.curry () newschool edu