Securing your web application with deep HTTP understanding

Securing your web application is not an easy job. In this blog post I will explain some of the challenges in protecting a web application and how F5 Application Security Manager (ASM) can help mitigate security risks.

HTTP is a flexible protocol that allows clients (browsers in this case) to communicate with servers (web applications) passing information back and forth. The information can be delivered in many ways, and it is up to the application developer to decide how it will be done. For example, information can be delivered by using:

  1. Quary based HTTP parameters
  2. Content based HTTP parameters (POST)
  3. Content based HTTP parameters (MulitPart data)
  4. XML content
  5. JSON content
  6. HTTP Header

From the application security point of view, looking at the HTTP request as one big chunk of data is not acceptable. Having a fine-tuned security policy should be the right approach due to the following reasons:

  1. Securing each HTTP data object separately and maintaining a unique profile for each object improves security by reducing the attack surface.
  2. It reduces false alarms without losing any security capabilities. For example, instead of entirely disabling an attack signature when it is matched, you can disable the signature on a specific HTTP object, therefore preserving attack signature security functionality for the rest of the application.


In the attached picture you can see an example of the ASM parameter properties screen. On this screen you can control all the HTTP parameter properties, for example:

  1. Allowed meta characters.
  2. Activate attack signatures.
  3. Parameter properties such as: parameter length, is the parameter allowed to appear more than once, and whether the parameter is allowed to contain an empty value.



Today’s web applications are usually the combination of different technologies developed by internal and third party software teams across the globe. Understanding and controlling these applications has become an almost impossible mission to those responsible for securing these applications.

The Attack surface of the web application is derived from the complexity of the HTTP protocol, without the understanding of the application data objects and their characteristics, and without the ability to secure each data object from the threats waiting to be exploited.

F5 Application Security Manager (ASM) parses the HTTP request to its most delicate parts allowing you to learn and manage security profiles to each of the HTTP objects and as a result harden web application security and improve your protection capabilities.

Published Oct 12, 2011
Version 1.0

Was this article helpful?

No CommentsBe the first to comment