Introduction

By now, you should be asking yourself Is there anything else that I can do to secure my Web applications against malicious hackers? We have stepped back from the developer s chair and looked at development as a hacker would see it. We have looked at CGI Bin scripts and the vulnerabilities that are associated with them. We have had a chance to examine Java and Java Applets, XML, ActiveX, ColdFusion, and Mobile Code. We have addressed almost every topic relevant to Hack Proofing your Web Applications. This last chapter deals with not only tying all of the previously discussed methods together, but also introducing a security plan. Very often, simple common sense will assist you greatly.

As hard as you try, chances are good that your Web site still will not be secure enough to protect your organization from all attacks by malicious hackers. At the very least, you need a well-rounded balance of security. By now you realize that security does not happen at just the application level or only at the network level. Security should happen everywhere. The more security that is in place, the more successful you will be at thwarting attacks.

As a developer, you should look deep within the work that you are doing as well as the work your co-workers are doing and check your own code for security holes. Examine your operations and review the code from cradle to grave, understanding that vulnerabilities probably exist. How exploitable is your code? That is the question...