views:

68

answers:

4

I am developing a site and i am using yslow to profile speed and stats, webdeveloper for html and css validation, etc.

What can i use to check for security mistakes?

+2  A: 

Review this list.

Obviously what is relevant is your server-side language (so you may want to scan from the WEB side and then an analysis of the server code as well).

This is a significant field of work and research. It's good that you want to perform this type of analysis, and enjoy reviewing and testing all the various available tools :)

Noon Silk
A: 

Depending on the size of your site you could possibly use a tool called Fortify. It will scan your code for security vulnerabilites. I am sure there are other tools which are similar.

Zaps
Sorry but fortify is not for web apps.
Rook
+2  A: 

For secuirty I recommend the open source wapiti or the commercial Acunetix. Acunetix will tell you about broken links, but it won't tell you if you have problem with HTML.

On a side note, html and css can really cause secuirty problems. Maybe if you have html links pointing to http content within https could be a problem and Acunetix will inform you of some of these problems.

Rook
what do you mean by "html and css can really cause security problems" ? Are you talking about allowing user html and css? i can see html causing a problem but not css.
acidzombie24
actually you can execute javascript within css, so that is still a problem. HTML isn't an issue but, `<script>` tags are. You can also use onload= and onmouseover= to do nasty things with other html tags. By in large filtering `<>` is a very good idea.
Rook
html can be a problem if you link to http resources from an https page. browsers will throw an warning and acuentix will detect this.
Rook
A: 

I assume you are familiar with OWASP Top 10 (http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project). You can try rat proxy (http://code.google.com/p/ratproxy/) - it is a security audit tool. Other http/https proxies such as paros also can to some extent detect injection and XSS flaws.

None of these is perfect and so with a good understanding of web application vulnerabilities you can supplement with some manual tests and code inspection.

mar