TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED]  Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------



-----Mensaje original-----
De:     [EMAIL PROTECTED]  [SMTP:[EMAIL PROTECTED] ]
Enviado el:     Wednesday, February 09, 2000 7:48 PM
Para:   [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Asunto: Re: ISS Realsecure 3.2 Console and Engines connection problem

From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Date: Wed, 9 Feb 2000 10:48:58 -0800
Subject: Re: ISS Realsecure 3.2 Console and Engines connection problem
Message-Id: <[EMAIL PROTECTED]>
Sender: [EMAIL PROTECTED]


TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED]  Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------

The console can only use one key at a time, so your key defines how many
engines or sensors a console can manage.  If you have licensed 2 engines,
then make sure your key allows you to manage both engines.  Take a look at
the key file, it tells you how many engines you can manage at once.   If
you have 2 separate keys, ask ISS to combine the keys for you.  To change
the key, in the console, select the menu: view, options, General Tab: click
on browse - select the key (licensed for multiple engines - in your case,
2), Click ok.

Here's a whole discussion on the Syn Flood attack signature and why you're
probably receiving some false positives.

RealSecure tracks all SYN's as you theorize. It keeps a table of SYN's that
have been seen which have not been followed by ACK packets traveling in the
same direction to the same connection. Once a following ACK (presumably the
ACK that completes the three way handshake, but it can be *ANY* ACK packet
in the subsequent connection) is seen, the SYN is removed from the "half
open connections" table. This goes on for all SYN's and ACK's that
RealSecure sees.

It also, of course, processes any FIN's or RST's it sees appropriately, so
for instance if a SYN is seen going to a non-open port, and a RST comes
back off that port, it will not be considered as a half-open connection.
If, for a given listening port, the number of half open connections in the
table exceeds a certain number (which is configurable by the user in their
policy file), RealSecure decides a SYNFlood has occurred. It will then
(optionally, only if the user has the RSKILL action enabled) send a RST
packet to the listening host to close the half-open connection on the
server side. This mitigates the effect of the flood.

As a flood proceeds, the RST packets are sent for every contributing SYN.
However, to keep from creating a subsidiary flood at the console, actual
SYNFLOOD events are only generated every "Nth" SYN, N again being
configurable in the users policy file.

If RealSecure sees an ACK packet which completes the three-way handshake,
that SYN is removed from the table and does not contribute to the SYNFLOOD
determination. Therefore, a properly operating RealSecure network engine
will not consider completed connections in SYNFLOOD.

explanation of why you see 0.0.0.0 in the reports. Of particular note is
your mention of the danger of maintaining state in the RealSecure engine
and why we might not want to do this. That was very astute. As it happens,
we ARE maintaining state information, but a very small amount. This does
have its limitations which result in some false positive situations.

There are a number of reasons these false positives can occur. Here are a few:
(0) Your tuning parameters for SYNFLOOD in your policy file are set too low
for your network. Look for "HighWaterMark" and "PacketsPerEvent" under the
Advanced button for SYNFLOOD in the Policy editor for RealSecure 3.2 or
higher. Experiment with raising these numbers and see what effect it has on
the reports. However, don't go crazy with these values (for instance,
increasing them by several orders of magnitude all at once).
(1) You have asymmetric routes on your network near the RealSecure sensor.
In this case, RST and FIN packets that are coming back off the target
server cannot be seen by the same RealSecure engine that saw the SYN's.
Thus connections which are being legitimately closed (or were never opened
in the first place) are not being closed out of the half-open table in
RealSecure's memory and contribute to SYNFLOOD determinations.
(2) Due to packet bursts or sustained loading, your RealSecure Network
Engine may be dropping packets, and therefore missing the ACK's that
correspond to some SYN's, again contributing to false SYNFLOOD determinations.

As it happens, in all of the known cases where SYNFlood false positives,
the RST packet we send will end up being ignored by the target host because
it either (a) doesn't correspond to an open port or (b) doesn't match the
current window of an actual open TCP connection. Thus it is pretty safe to
leave RSKILL turned *ON* for SYNFLOOD, even though false positives do occur!

Here is the rule of thumb: if you have a real SYNFLOOD on your hands, you
will see multiple, repeated, regular reports of SYNFLOOD aimed at the same
IP and port. It will be like a "heartbeat" on your RealSecure console. In
other words, you will see SYNFLOOD over and over and over, on intervals on
the order of a few seconds or minutes, and the destination IP/Port will be
a critical server on your network. This type of report is real and should
be reacted to.

If you see SYNFLOOD other than this, such as a single SYNFLOOD event, or on
the order of one every hour or less, then this is clearly a false positive
and can be safely ignored. Of particular note are low-volume SYNFLOOD
reports that appear to be aimed at IP/PORT combinations that do not
actually exist on your network (these are often caused by case (1) above),
or low-volume SYNFLOOD reports that correspond to legitimate traffic to
very high volume servers on your network.

At 03:37 PM 2/8/00 +0800, KW Pong wrote:

>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 ?
>
>   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  ?
>
>
>Best Regards,
>weike Pong,
>ITSC,
>HKUST

================================================
Audra N. Eng
Technical Product Manager
Internet Security Systems

Office: 415-379-3566
FAX: 415-831-4780
E-Mail: [EMAIL PROTECTED]
==============================================

*******************************************************************
ISS CONNECT 2000
International User Group and Information Security Summit
March 19-24, 2000 http://connect.iss.net
REGISTER TODAY!
*******************************************************************


Reply via email to