I am looking for the current, state of the art, coding standards for web development (mostly PHP). Since I do not want to reinvent the wheel I would like to reuse libraries written by people much clever than I am.

I know about OWASP which is a wonderful source of best practices and brilliant information. Their web site is however quite unorganized when it comes to libraries.

  • On the one hand there is OWASP ESAPI with pointers to libraries.
  • On the other hand there is OWASP AntiSamy, which also has libraries. It in turn points to HTMLPurifier or the MS Anti-XSS library.

I did not find any links between these different solutions.

Is there currently a consensus on the most recommendable libraries to use in order to mitigate the major security risks?

Thank you

closed as off-topic by amon, user40980, Bart van Ingen Schenau, Dan Pichelman, GlenH7 Dec 19 '14 at 20:09

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions asking us to recommend a tool, library or favorite off-site resource are off-topic for Programmers as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it." – amon, Community, Bart van Ingen Schenau, Dan Pichelman, GlenH7
If this question can be reworded to fit the rules in the help center, please edit the question.


You will need to add static code analysis to your testing. Many Cross-site scripting (XSS) problems are very difficult for the human eye to pick out. Automated code analysis finds them easily.


(Hey, I know that Bruce Ediger character! ;) Seriously, you did not mention what exactly you were looking for, but ESAPI is not a "coding style", but rather a library of various security controls. There is an 'ESAPI for PHP'. OTOH, AntiSamy only exists for Java and .NET, so if you are looking for something to help defend against XSS in PHP, ESAPI should get the nod.

However, Bruce is correct...to a degree. Unless you are doing a green-field approach on some brand new project, static or dynamic analysis is a definite plus, especially if you are working on a large code base. These tools will have you identify places within your code where you need to insert the ESAPI's security controls.

Finally, you might find this book useful (note: I have not read it at all, but based on its title and TOC, it would seem to fit the bill): Pro PHP Security: From Application Security Principles to the Implementation of XSS Defenses, Second Edition by Chris Snyder, Thomas Myer and Michael Southwell. It's published by Apress. I'll let you look it up on your favorite online bookstore, etc.

  • Thanks. I should have been more clear with my question. What I actually meant is that there are several libraries which get a recommendation from OWASP and they are not mentionned as "you can use ESAPI or AntiSamy" but rather get independednt sections without any cross links or comments. Anyway I will have both tested to see which one will be easiest to implement in a PHP environment (since both cover PHP). – WoJ Sep 2 '11 at 6:49

Not the answer you're looking for? Browse other questions tagged or ask your own question.