PHP web application security before SSEQ-LIB

There are lots of books and articles out there coping with web application security. What they have in common is they explain over and over again the different types of attacks and give some advice on how defend them. After reading, you are either a security expert and write down some stable code to fortify your application, or you rather are a bit confused about what to do now and actually do nothing at all.

Take a look at almost any web application you can download as open source: with an eye on security you'll find lots of security flaws. Is there nothing we can do about it?

Principles of SSEQ-LIB

There are lots of things you can do to secure a web application, without even changing the code. These things can be done with SSEQ-LIB in an incredible simple manner. Other things need some code to be changed inside the application. SSEQ-LIB comes with handy functions to manage these things too.

Imagine: your php web application gets secured against Session Hijacking and Session Fixation just the minute you include SSEQ-LIB with one line of code!

The near future with SSEQ-LIB

There is a vision behind SSEQ-LIB: that in the near future you will have to search hardly to find a web site or a web application with some obvious security flaw. And that helpers like SSEQ-LIB are pre-installed on any public web hoster to help their customers create secure web sites. And that any mature open source Blog or CMS or Guest book comes with SSEQ-LIB incuded, just in case there could be a flaw and to prevent it being exploited.