15 Rules to follow for safer web applications

After a small research and in conclusion I (try to) follow these rules…
(don’t mind the order!)

1. Display custom errors pages.
2. Remove unwanted files and folders.
3. Remove backup, unused or obsolete files (.bak, .inc, .old etc). For include files, carefully choose the suffix to prevent information disclosure.
4. Remove default document files (default.aspx, index.php, index.asp, main.jsp etc).
5. Validate properly all parameters against expected data length, data type, data format (dd-mm-yyyy etc) and data range (10-79 etc).
6. Use SANITIZE functions (custom made).
7. Disable directory browsing. If this is required, make sure the listed files does not induce risks.
8. Remove the private IP address from the HTTP response body. For comments, use jsp/asp comment instead of HTML/javascript comment which can be seen by client browsers.
9. For secure content, put session ID in cookie ,use a combination of cookie and URL rewrite, bind the Session ID to the IP address of the client who owns the session and put timeout mechanisms for the Session IDs against Replay Attacks.
10. Turn off AUTOCOMPLETE attribute in form or individual input elements containing password by using AUTOCOMPLETE=’OFF’.
11. Secure page can be cached in browser. Cache control is not set in HTTP header nor HTML header. Sensitive content can be recovered from browser storage. The best way is to set HTTP header with: ‘Pragma: No-cache’ and ‘Cache-control: No-cache’. Alternatively, this can be set in the HTML header but some browsers may have problem using this method.
12. Do not trust client side input and enforce tight check in the server side. Disable server side include. Use least privilege to run your web server or application server. For Apache, disable the following:
Options Indexes FollowSymLinks Includes
AddType application/x-httpd-cgi .cgi AddType text/x-server-parsed-html .html
13. Do not trust client side input even if there is client side validation. In general,

* If the input string is numeric, type check it.
* If the application used JDBC, use Prepared Statement or Callable Statement with parameters passed by ?
* If the application used ASP, use ADO Command Objects with strong type checking and parameterized query.
* If stored procedure or bind variables can be used, use it for parameter passing into query. Do not just concatenate string into query in the stored procedure!
* Do not create dynamic SQL query by simple string concatenation.
* Use minimum database user privilege for the application. This does not eliminate SQL injection but minimize its damage. E.g. if the application requires reading one table only, grant such access to the application. Avoid using sa or db-owner or root.

14. Do not try to work with invalid data. Display custom error page when data does not pass validation.
15. Use white list validation wherever possible!

Looking forward for your comments… […]

Read More… from 15 Rules to follow for safer web applications

Microsoft Tech-Ed Europe 2009 | 9-13 November 2009, Berlin, Germany

Here are the top 3 reasons you should join Tech·Ed Europe 2009.

More networking, more knowledge – Tech·Ed Europe 2009 an intensive learning experience and a great opportunity to expand our network of IT contacts.

Practical skills – Together, we can cover more ground by going to more sessions and more labs. Then we can start applying our new skills right away to build, deploy, secure, mobilise and manage solutions.

Competitive Advantage – Tech·Ed Europe 2009 can give us all the chance to experience emerging technologies and share ideas. That’s the perfect way for all of us to get a competitive edge in the future.

Sound good? Let’s do it! To learn all about Tech·Ed Europe 2009, just click here. […]

Read More… from Microsoft Tech-Ed Europe 2009 | 9-13 November 2009, Berlin, Germany

SQL Injection Cheat Sheet by ferruh mavituna

Currently only for MySQL and Microsoft SQL Server, some ORACLE and some PostgreSQL. Most of samples are not correct for every single situation. Most of the real world environments may change because of parenthesis, different code bases and unexpected, strange SQL sentences. […]

Read More… from SQL Injection Cheat Sheet by ferruh mavituna