|
ClearRoute Online Help Latest Update: 8/03/2003 3:07 PM
|
|
Top Virus Alerts! |
|
|
|
Before reporting attacks it is necessary to determine the level of threat to your system the attack poses. The reporting of attacks could have been more automated, however, the choice not to do so is a very conscious one on my part for a very good common sense reason. It is imperative that good old human judgment be used in determining what attacks should actually be reported. Do NOT report attacks from the Shields Up web site as these are not actual attacks! Thanks, |
|
|
| Step 1.
Configuration Go to Options, point to the Security.log file in the \Program Files\WinRoute Pro\Logs folder. Enter the path to your favorite WhoIs trace utility. ClearRoute ships with an interface to SmartWhoIs called SWLAUNCHER.EXE. It will also work with NeoTrace from NeoWorx. Click OK to save the Options
settings. |
|
|
|
Step 2. Importing the WinRoute
Log file |
|
|
| Step 3. Analyzing the data
Go to the Browse Menu and select
WinRoute Interceptions to see the imported data. NOTE: Clicking on the column heading for
TIME will sort the records by time, but the display of the data may NOT be
what you expect. The proper way to sort on the TIME column is to use the
Date & Time TAB. This index is purposely set to display
the data in the format of most recent attack first. |
|
|
|
Step 4. Reporting the Attacks - Quickstart instructions
Highlight any of the attacks in the browse and click on the WhoIs button. If you have entered the path to the executable of your favorite WhoIs utility it will be launched and the IP address of the highlighted attack will be appended to the command line. Make note of the email address to send your comments regarding the network. Usually, you can send abuse reports to abuse@domain but this is not in all cases. NOTE: I have included SWLAUNCHER.EXE with ClearRoute in order to provide an interface to SmartWhoIs. So far, this is the only WhoIs utility I have found that will take an IP address on the command line. I will be working on my own utility for this but it will take some time to get completed. In order for the WhoIs button to be activated you MUST have the path to the executable file of your WhoIs utility in the Options screen. If you would like to purchase SmartWhoIs, use the following link Purchase SmartWhois. WhoIs Query NEW! (v 1.3) You can now do a WhoIs query from within the program itself. If you are not using any of the third-party WhoIs utilities mentioned above the internal WhoIs will be used. In order to use any of the third-party utilities, you must go to the Options screen and select the External WhoIs checkbox. Then you can enter the path and filename of the utility you would like to use. Highlight any of the attacks and the "Email
Attack" button will allow you to copy the attack details to the
clipboard so you can email them to the attacker's
ISP. If you would like more details regarding
the reporting of attacks, click HERE! |
|
|
| Version History:
ClearRoute Pro 3.1 Released August 3, 2003 ClearRoute Pro 3.0 Released May 9, 2002 Special Edition - 2.1 Released April 2, 2001 Special Edition - 2.0 Released March 26, 2001 1.7 1.6 1.5 1.4 1.2 1.1 1.0 |
|
|
|
A
Deeper Explaination of reporting attacks
If you have an attack that you want to report, highlight it in the
browse list and press the WhoIs Trace button.
Depending on whether or not you are using an external WhoIs query
tool such as SmartWhoIs or NeoTrace or the internal WhoIs
query you will get somewhat different results. I will explain this
using the internal Whois query.
The IP addreess of the intruder is "controlled" by the ISP.
The WhoIs query results will usually show you what organization controls
the address in question, but sometimes it takes a little more digging
and sometimes an educated guess depending on what results you get.
The main information you want to see is what the DOMAIN is for the IP
address. The best place to look for this information is the email
address of the domain co-ordinator (if that is shown in the query
results) This will show up as something like (but not exactly, these are
just examples) admin@sprint.net or
<some name>@aol.com or admin@earthlink.net
to name a few.
Once you have the domain name, then you have to determine what the email
address is to send the actual report in order to report the attack. Most
ISPs use 'abuse@<domain.org>'
as the recipient for emails concerning abuse of their service. This is
not always the case. Sometimes you will send an email and get a
bounce back telling you that was not the proper address. In which case
you should then send it to 'admin@<domain.org>'
So now you have the email address. The next step is to collect the
attack information into the Windows clipboard. You do this by pressing
the "Email Attack" button. The details of the attack get
copied to the clipboard and then you get a message instructing you to
start a new email message and paste the contents of the clipboard into
the body of the email message.
To do this, start your email program, Outlook Express, AOL, Netscape, Pegasus, etc... and compose a new message. Address it to the email address that you found by researching the WhoIs information.
Put your cursor in the body of the email message and do a CTRL-V
or a right-click on the mouse and select PASTE from the
popup menu. (I find CTRL-V easier). Put a subject on the message, I
ususally use "Suspicious activity by your subscriber" in the
subject line and then press Send.
When you have completed this, you will see a little green ball beside
the entry in the Browse on the attack that has just been reported to let
you know that you have taken some action on that particular attack.
Now all you will have to do is wait for some sort of response from the
ISP regarding the message. Some will send you an auto-responder and some
will actually be from a person that is investigating the attack.
There are a few ISPs that tend not to respond (Bellsouth comes to mind)
but I am sure that if you press the issue you can get some sort of
response. If sending it to abuse@ doesn't work, then send it over
their heads to the administrator.
|
|
|