Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security ISSForum
[Top] [All Lists]

[ISSForum] XXP_Port_Scan

Subject: [ISSForum] XXP_Port_Scan
Date: Mon, 15 May 2006 18:03:23 +0400
Hi, List

Sometimes there is no :intruder-port in (TCP|UDP)_Port_Scan signature
details and without :reason too. Why?
As I mentioned before, I faced with a great number of false positives (I
think so) with HTTP replies from Web-sites: all highly-loaded
web-servers scan my HTTP-proxy. It's easy to investigate if
:intruder-port and :reason are shown in details, but when they didn't
present... So, my question is why sometimes we see :intruder-port and
:reason and sometimes not?
Is it because sometimes :intruder-port is one and it could be specified
in details and sometimes :intruder-port is different for different
probes, so it can't be specified? How can I influence on appearance of
:intruder-port ? Can I somehow correlate :intruder-port with
XXP_Port_Scan triggering (i.e. if  :intruder-port is 80 and tere is no
:reason, port scan signature is not triggering) ?

Tanks.
---
Best regards, Sergey V. Soldatov.
Information security department.


_______________________________________________
ISSForum mailing list
ISSForum@iss.net

TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to 
https://atla-mm1.iss.net/mailman/listinfo/issforum

To contact the ISSForum Moderator, send email to mod-issforum@iss.net

The ISSForum mailing list is hosted and managed by Internet Security Systems, 
6303 Barfield Road, Atlanta, Georgia, USA 30328.

<Prev in Thread] Current Thread [Next in Thread>
  • [ISSForum] XXP_Port_Scan, Soldatov, Sergey V. <=