TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------
Hi Weike,
See my comments below...
-----Original Message-----
From: KW Pong [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 08, 2000 1:38 AM
To: [EMAIL PROTECTED]
Subject: ISS Realsecure 3.2 Console and Engines connection problem
TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any
problems!
----------------------------------------------------------------------------
Hi all,
My company is recently using Realsecure 3.2 to monitor our internet
link and internal subnet. The currently configuration is one engine is
connected to internet link to monitor all in/out traffic, and another
engine is connected to one of our internal subnets. As per the Starting
Guide mentioned, one console can monitor one or more engines at the same
time. When I trying to do this by add a detector and click the OK
button, the console always prompt that "you have exceeded the device
limit" and reject the request. I have put two iss.key files in the same
directory but still failure to do so. Now, I need to use two consoles to
monitor two engines, separately. Could anyone advice me how to
configurate the console so it can monitor two engines ?
<sheila>> This is typically due to a problem with your iss.key file. Just to
make sure, you should have iss.key loaded on the console under the default
directory of C:\Program Files\ISS\RealSecure 3.2...not on the detectors.
Now, open your console and go to
view->display key
look at the "device count" field to see how many detectors (devices) your
key allows the console to monitor. Then look at "current device" count field
to see how many the console thinks it is monitoring. If either of these is
incorrect, you should probably call tech support to get help. It could be a
console problem or it could be a problem with your key file. I believe there
was once a bug associated with this, but I can't remember the details and I
think it's been resolved. Tech support can help you there too.
Furthermore, I found the engine, which monitor the internet link, seem
to have problem. The preview report is alway showing source address
0.0.0.0 doing Syn_flood to various destinations. In the event inspector,
the info type is SPOOFEDSRC and Info Value is a IP address. I'm sure the
address 0.0.0.0 is not present, because I used the sniff to monitored
the internet link several days and none such address in the sniff logs.
Does someone could tell me what wrong in my engine setting or console
setting ?
<sheila> This is actually correct and does not represent a misconfiguration
at all. Quite often, Syn floods (and certain other attacks) are generated
with a spoofed source address or a source address that isn't too meaningful
initially. RealSecure puts the syn flood diagnosis into the source tree on
your console with a source of 0.0.0.0 to indicate that it is likely the
source address(es) are spoofed. The benefit of using one source address of
0.0.0.0 is that all the packets associated with that one syn flood diagnosis
show up in the same branch of the tree. I am almost positive (I'm not
anyplace that I can verify this right now) that if you drill down on that
event in the tree, you'll see all the actual source addresses. Just be aware
that it is likely that they are spoofed. You should also be aware of all the
possible false positives associated with Syn Floods in general. Our help
file is informative here. I don't usually do commercials, but Stephen
Northcutt's book (Network Intrusion Detection; An Analyst's Handbook) has
some good information on this also.
Best Regards,
weike Pong,
ITSC,
HKUST