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 Web-App-Sec
[Top] [All Lists]

Re: AJAX and Web application scanners

Subject: Re: AJAX and Web application scanners
Date: Thu, 30 Mar 2006 00:26:13 +1100
Yes, but this is actually really hard; most scanners are completely unaware of the security aspects of Javascript:

* Client side validation
* DOM injection
* XSS etc

Until scanners become more competent, a well written Manual of Style which encourages / mandates how validation works and variables are named is more desirable. Look at Chris Shifflett's approach for PHP:

$clean = array();
$clean['foo'] = someValidation($_POST['foo']);

That sort of naming scheme can truncate audits by literally days and days on bigger apps. There's no reason not to encourage it in JS as well.

thanks,
Andrew


On 30/03/2006, at 12:04 AM, Jeff Robertson wrote:

Side question:

If you find yourself in the position to influence the design of a new
application, would you encourage the people coding it to optimize it for
"scannability" so as to make your own job easier?

Attachment: smime.p7s
Description: S/MIME cryptographic signature

<Prev in Thread] Current Thread [Next in Thread>