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. |

| Subject: | WAF learning ability limitation? |
|---|---|
| Date: | Fri, 19 May 2006 18:04:25 +0100 |
Hi,
I listened to the recent London WAF mp3s. Thanks for those!
One thing I heard was that the WAFs worked in two main ways: 1. specific input parameters (input fields) policies to defend against particular vulnerabilities, and more generally they were 2. learning what users put into input boxes and could form their own dynamic reg exp protection.
Perhaps this is just a silly eccentric solution and never likely to be used in the real world.
matt
--form example (response 1)--
<form method="post"> <input type="text" name="input_KL23JgrtIsuqwKjh5cTgt" /> <input type="test" name="input_KNi5s4TgfR5GkUYdk09" /> <input type="submit" value="submit" /> </form>
--form example (reponse 2) - after page refresh/post--
<form method="post"> <input type="text" name="input_Ksdg3r5XI7u86Dwjhdscyjljgt" /> <input type="test" name="input_asfsdgyuXkl78dr54GdrfgdF09" /> <input type="submit" value="submit" /> </form>
etc...
------------------------------------------------------------------------- Sponsored by: Watchfire
https://www.watchfire.com/securearea/appscansix.aspx?id=701300000007t9c --------------------------------------------------------------------------
| Previous by Date: | Re: http/spnego connections, Adam Tuliper |
|---|---|
| Next by Date: | RE: Non SSL Bank Login Forms, James Strassburg |
| Previous by Thread: | RE: Comparison report on web app security scanners, Mark Curphey |
| Next by Thread: | Re: Comparison report on web app security scanners, solutions_PHP |
| Indexes: | [Date] [Thread] [Top] [All Lists] |