This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/anti-abuse-wg@ripe.net/
[anti-abuse-wg] New Abuse Information on RIPE NCC Website
- Previous message (by thread): [anti-abuse-wg] New Abuse Information on RIPE NCC Website
- Next message (by thread): [anti-abuse-wg] New Abuse Information on RIPE NCC Website
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Suresh Ramasubramanian
ops.lists at gmail.com
Fri Jun 21 16:24:17 CEST 2013
On Friday, June 21, 2013, Frank Gadegast wrote: > Suresh Ramasubramanian wrote: > > >> and yes, outbound mail scanning is a widely recognized best practice >> > > But this is in some countries or under some other regulations no option. Which is a pity of course. However it remains a best practice and even in Germany there are ISPs who do filter outbound mail. There is a much easier way of finding botted PCs dialing into your own > network without having to scan outgoing mail. This wasn't anything about botted PCs ON that network. It was about C2 for various bots running on collocated IP space leased by botmasters. As for the rest of it - there's RFC 6561 besides a ton of best practice documents on how to detect botted PCs on a network. --srs -- --srs (iPad) -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/anti-abuse-wg/attachments/20130621/498adf24/attachment.html>
- Previous message (by thread): [anti-abuse-wg] New Abuse Information on RIPE NCC Website
- Next message (by thread): [anti-abuse-wg] New Abuse Information on RIPE NCC Website
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]