🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.protocols.tcp-ip
Article #15465

Where should I report port scans?

#15465
From: Lawrence Baldwin
Date: Wed, 28 Feb 2001 17:50
54 lines
3439 bytes
Stanislav,

Could not agree with you more...blind escalation of individual port scan
events is NOT productive as there is no conclusive way to determine
whether the activity is bogus or real attack.  Doing so is just going to
overwhelm ISP abuse departments that are already knee deep in SPAM
complaints.

This is why myself (and other aggregators: e.g. Dshield.org) have
developed are building an aggregation network which allows one to
achieve "collective awareness".

Using collective awareness you can't identify all real attacks, but you
CAN apply business rules that identify those that most likely real
attacks.  We ask that agents esclate ALL attack events to us so that we
can apply our rules against completely unfiltered data.  From this raw
data, we do massive filtering and throw out anything that we can't
conclusively identify as an attack...only the remaining few incidents do
we escalate to the source ISP.

To give you an idea on how much we filter see:

http://www.mynetwatchman.com/listincidentsummary.asp

As you can see our Escalation Rate is somewhere around 10%...thus we are
filtering 90%.

Our false-positive rate is remarkably low...in the last 30 days we have
only had ONE incident where the source provider indicated that the
attack was really their load-balancing servers sending DNS queries to
determine RTT and best route.

> The fact that somebody portscanned you or even, gosh, tried a
> well-known exploit blindly and went away is not a reason to bother
> remote admins unless you suspect that they may have an intruder in
> their systems.

Absolutely, but we're finding that 80-90% of the escalations we send the
source system ARE compromised hosts!  See:
http://www.mynetwatchman.com/mynetwatchman/hotclosed.asp


This makes sense since even script kiddies are not stupid enought to
launch direct scans. (Well most of them aren't)

IMHO, reporting port scans (with proper aggregation) can dramatically
reduce the number of compromised hosts on the Internet...this is a good
thing.

-------------------------
Lawrence Baldwin
Protocol Scientist
678-624-0924
http://www.mynetwatchman.com/about.htm - I'm under attack, now what?
Technical Details
Message-ID: <3A9D3A6B.F5CC6176@mynetwatchman.com>
Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!supernews.com!news.tele.dk!128.230.129.106!news.maxwell.syr.edu!newsfeed.atl.bellsouth.net.MISMATCH!newsfeed.atl!news1.atl.POSTED!not-for-mail
References: <3A9C3710.7F2E86F8@mynetwatchman.com> <87zof7k7hx.fsf@cain.internet2.edu>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f9325,5fddf9b17d575149
X-Google-Attributes: gidf9325,public
X-Google-Thread: 10090f,64b87d735e5bf97e,start
X-Google-Attributes: gid10090f,public
X-Google-Thread: 104f05,64b87d735e5bf97e,start
X-Google-Attributes: gid104f05,public
X-Google-ArrivalTime: 2001-02-28 09:55:55 PST
Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!supernews.com!news.tele.dk!128.230.129.106!news.maxwell.syr.edu!newsfeed.atl.bellsouth.net.MISMATCH!newsfeed.atl!news1.atl.POSTED!not-for-mail
Message-ID: <3A9D3A6B.F5CC6176@mynetwatchman.com>
From: Lawrence Baldwin <baldwinlSPAMMENOT@mynetwatchman.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.protocols.tcp-ip,bellsouth.net.security,news.admin.net-abuse.email
Subject: Where should I report port scans?
References: <3A9C3710.7F2E86F8@mynetwatchman.com> <87zof7k7hx.fsf@cain.internet2.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 54
Date: Wed, 28 Feb 2001 12:50:35 -0500
NNTP-Posting-Host: 209.214.36.176
X-Trace: news1.atl 983382636 209.214.36.176 (Wed, 28 Feb 2001 12:50:36 EST)
NNTP-Posting-Date: Wed, 28 Feb 2001 12:50:36 EST