Article View: comp.protocols.tcp-ip
Article #15461Re: Where should I report port scans?
From: Lawrence Baldwin
Date: Tue, 10 Apr 2001 23:33
Date: Tue, 10 Apr 2001 23:33
46 lines
3854 bytes
3854 bytes
Dark, I have found that even using a threshold of *2* "victims" reporting the same attacker to be highly effective in identifying those with malice intent, while at the same time filtering out false positives. This policy could easily trigger on your non-malicious scan activity if you became "curious" about more than one host within a several day period. I use port scanning myself but ONLY for back- tracing purposes...e.g. when sites don't bother to provide DNS SOA and Whois records...then I'll scan for 25, 80, 21 to see if I get a banner that identifies the site so I can drop them an email. However, even using a threshold of 2 victims results in filtering a *lot* of scans that I'm sure ARE malicious and/or are indications of a compromised host. For example, one scan from a host for 515 (LprNG) or 111 (RPC) is pretty much a giveaway that the host has been rooted. For this reason, I think we all have to be extremely responsible about scan activity...if we get too casual about it, then we'll have to raise the threshold and this will mean that many more compromised hosts will go unreported for a longer time. The other solution is getting more agents reporting the attacks, so it's a lot easier to have 3,4,5++ victims reporting the same attacker...but I'm workin on that....should have >format- independent< log uploader done in about a week...this will add the much awaited Zone Alarm support (currently myNetWatchman Agent for Windows only supports BlackICE) AND all uploads will be real- time via HTTP (vs. delayed FTP). lb. In article <B6F8472D.B0F7%nan-ae@nospam.nospam.porterfield.net.foo>, nan- ae@nospam.nospam.porterfield.net.foo says... > Out of curiosity, what do people feel is a reportable margin for protscans? > > I have portscanned without the slightest element of malicious intent, just > to see what is running on a system. Does this make me a cracker? Am I a > cracker for telneting into an SMTP server (on port 25) and attempting to > VRFY or RCPT TO an address? > > I am not suggesting that one not LART legitimate attemtps at system > intrusion, but I am curious as to where people reading this thread draw > their lines. > > -- Lawrence Baldwin Baseline your FastAccess Connection: http://www.mynetwatchman.com/perfwatch/beta.htm Automatic Port Scan Reporting: http://www.mynetwatchman.com/vision.htm
Technical Details
Message-ID:
<MPG.153d623dfe50249b9896a1@news2.mia.bellsouth.net>Path:
arc1-ca.pugleaf.net!supernews.google.com!sn-xit-03!supernews.com!newsswitch.lcs.mit.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.atl.bellsouth.net.MISMATCH!newsfeed.atl!news2.mia.POSTED!not-for-mailReferences:
<3A9C3710.7F2E86F8@mynetwatchman.com> <96gk79.khf.ln@linux.abbitt.org> <wJOy6.3081$Rv.131064@news1.atl> <MPG.15369849667cdc0c989685@news2.mia.bellsouth.net> <xF6z6.315$U4.11027@burlma1-snr2> <MPG.153b74cbe7ab82a8989695@news2.mia.bellsouth.net> <9asm06$pvu$1@new-usenet.uk.sun.com> <B6F8472D.B0F7%nan-ae@nospam.nospam.porterfield.net.foo>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10090f,64b87d735e5bf97e X-Google-Attributes: gid10090f,public X-Google-Thread: 104f05,64b87d735e5bf97e X-Google-Attributes: gid104f05,public X-Google-Thread: f9325,5fddf9b17d575149 X-Google-Attributes: gidf9325,public X-Google-ArrivalTime: 2001-04-10 16:36:01 PST Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-03!supernews.com!newsswitch.lcs.mit.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.atl.bellsouth.net.MISMATCH!newsfeed.atl!news2.mia.POSTED!not-for-mail From: Lawrence Baldwin <baldwinl@mynetwatchman.com> Newsgroups: comp.protocols.tcp-ip,bellsouth.net.security,news.admin.net-abuse.email Subject: Re: Where should I report port scans? Message-ID: <MPG.153d623dfe50249b9896a1@news2.mia.bellsouth.net> References: <3A9C3710.7F2E86F8@mynetwatchman.com> <96gk79.khf.ln@linux.abbitt.org> <wJOy6.3081$Rv.131064@news1.atl> <MPG.15369849667cdc0c989685@news2.mia.bellsouth.net> <xF6z6.315$U4.11027@burlma1-snr2> <MPG.153b74cbe7ab82a8989695@news2.mia.bellsouth.net> <9asm06$pvu$1@new-usenet.uk.sun.com> <B6F8472D.B0F7%nan-ae@nospam.nospam.porterfield.net.foo> Organization: System Management Technologies, Inc. X-Newsreader: MicroPlanet Gravity v2.50 Lines: 46 Date: Tue, 10 Apr 2001 19:33:10 -0400 NNTP-Posting-Host: 208.62.250.249 X-Trace: news2.mia 986945607 208.62.250.249 (Tue, 10 Apr 2001 19:33:27 EDT) NNTP-Posting-Date: Tue, 10 Apr 2001 19:33:27 EDT