Comments for good code, secure software http://mikeware.us/goodcode It's time to start being less reactive and more proactive Sat, 19 May 2012 22:38:34 +0000 http://wordpress.org/?v=2.6.3 Comment on OWASP XSS cheat sheet by romain http://mikeware.us/goodcode/?p=194#comment-87 romain Fri, 03 Apr 2009 18:33:55 +0000 http://mikeware.us/goodcode/?p=194#comment-87 Actually, this makes me think that we should have this kind of information, for developers, at Cigital. Let's say, developers are using a given platform/framework/language combination and we would be allow to give them best practices related to their technology stack, not only general description (or publicizing a particular API like ESAPI/OWASP does)... Actually, this makes me think that we should have this kind of information, for developers, at Cigital.
Let’s say, developers are using a given platform/framework/language combination and we would be allow to give them best practices related to their technology stack, not only general description (or publicizing a particular API like ESAPI/OWASP does)…

]]> Comment on OWASP XSS cheat sheet by mikeware http://mikeware.us/goodcode/?p=194#comment-81 mikeware Fri, 03 Apr 2009 03:03:48 +0000 http://mikeware.us/goodcode/?p=194#comment-81 Romain: excellent, I didn't know about it. Romain: excellent, I didn’t know about it.

]]> Comment on OWASP XSS cheat sheet by romain http://mikeware.us/goodcode/?p=194#comment-80 romain Fri, 03 Apr 2009 02:14:45 +0000 http://mikeware.us/goodcode/?p=194#comment-80 They also have the SQL Injection prevention cheat sheet now: http://www.owasp.org/index.php/SQL_Injection_Prevention_Cheat_Sheet Fairly complete now I believe... They also have the SQL Injection prevention cheat sheet now:
http://www.owasp.org/index.php/SQL_Injection_Prevention_Cheat_Sheet

Fairly complete now I believe…

]]>