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


There's a good question. I've seen similar with a couple of other alerts,
where the characteristic simply seems to be
the use of a specific high port.
It seems the only way to find out the answer to such questions is to
contact ISS. The knowledgebase is far to sparse.

Oliver




"Brock, Eric" <[EMAIL PROTECTED]>@iss.net on 24/05/2001 00:34:05

Sent by:  [EMAIL PROTECTED]


To:   [EMAIL PROTECTED]
cc:
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]






Reply via email to