TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------
If you update to Service Release 1.1 for RealSecure network sensor 5.0, then
the TFN2000 false positives should be greatly reduced or eliminated for DNS.
Brian Fitch, IDS Escalation Engineer
Internet Security Systems, Inc.
404-236-2700 / 1-888-447-4861|[EMAIL PROTECTED]
-----Original Message-----
From: Brock, Eric [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 23, 2001 10:34 AM
To: [EMAIL PROTECTED]
Subject: TFN2000
TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any
problems!
----------------------------------------------------------------------------
Greetings,
I am seeing several TFN2000 events come across my RS network sensor ever
since it was installed. The source is our ISP's DNS server and the target is
our proxy server, which uses the DNS server for lookups. The source port is
DNS (53/udp), and the destination port is a random high port. This looks
like a normal response from the DNS server to a DNS request by the proxy
server. It seems to me that the network sensor should see the initial
request from the proxy server and then not be alarmed by the response from
the DNS server. Is that what is supposed to happen?
Also, what exactly does RS see in the packet that triggers the TFN2000
event? Is it a specific port or something else in the data portion of the
packet?
Thanks,
Eric Brock, CISSP
Information Security Team Lead - Mary Kay Inc.
[EMAIL PROTECTED]