Skip to main content

Six Simple rules to make your application hard to hack

I was going through an interesting post on ACE team's blog. I was really impressed the way they have listed few rules to prevent bad guys to check into your application.It is very comprehensive and detailed.

The main rules they are talking are:

Rule no. 1:Implement a Secure Development Lifecycle in your organisation.

Rule no. 2:Implement a centralised input validation system (CIVS) in your organisation.

Rule no. 3:Implement input/output encoding for all externally supplied values.

Rule no. 4:Abandon Dynamic SQL- This is very contentious issue. The 'Abandon' word has generated a lot of comments supporting and opposing it on the blog.

Rule no. 5: Properly architect your applications for scalability and failover

Rule no. 6:Always check the configuration of your production servers.

For more details please go to:


Popular posts from this blog

File Upload through Null Byte Injection

Sometimes, during file upload we come across situation wherein there would be check on the file extension at the client side as well as server side too. If the application does allow only .jpeg extension to be uploaded, the client side java script checks for the extension of the file before passing the request. We all know that how easily this can be defeated.
Some applications, checks for the extension at the server side also. That's not easy to bypass. However there are some ways with which it still can be bypassed. Most of server side scripts are written in high level languages such as Php, Java etc who still use some C/C++ libraries to read the file name and contents. That leads to the problem. In C/C++ a line ends with /00 or which is called Null Byte. So whenever the interpreter sees a null byte at the end of the a string, it stops reading thinking it has reached at the end of the string.
This can be used for the bypass. It works for many servers, specially php servers. Th…

SQL Injection in search field

Earlier I had written about performing SQL injection in search field and how to do a DoS attack and privilege escalation using 'Like' operators. Now another SQLi exploitation I came across recently. That too in the search field. This becomes important as lots of people don't pay much attention on the search forms/ fields in the application. My aim is to show that a search form can also be exploited with SQL Injection. The following queries are based on a real world exploitation. The steps and data are for just illustration purpose only. Suppose, the search form provides the details of users who have accessed the application some time and their login time details etc, we just need to provide their name in the search box provided. All the data were being going as Post request. So, to just fingerprint the database, I provide, 'nil'+'esh' in the search field and it successfully gives me the results. That means the database behind the application is concatenat…

Insecure protocols

Some basic insecure protocols and risk associated with them: