Testing for Session Management

Session Management Testing
At the core of any web-based application is the way in which it maintains state and thereby controls user-interaction with the site. Session Management broadly covers all controls on a user from authentication to leaving the application. HTTP is a stateless protocol, meaning web servers respond to client requests without linking them to each other. Even simple application logic requires a user's multiple requests to be associated with each other across a "session”. This necessitates third party solutions – through either Off-The-Shelf (OTS) middleware and web-server solutions, or bespoke developer implementations.  Most popular web application environments, such as ASP and PHP, provide developers with built in session handling routines. Some kind of identification token will typically be issued, which will be referred to as “Session IDs” or Cookies. There are a number of ways a web-application may interact with a user.  Each is dependant upon the nature of the site, the security and availability requirements of the application. Whilst there are accepted best practices for application development, such as those outlined in the OWASP Guide to Building Secure Web Applications, it is important that application security is considered within the context of the provider’s requirements and expectations. In this chapter is described how to analyse a Session Management Schema and how to test the secuiry of session Token issued to the Client. Then is described how to test for Session Riding and HTTP Exploit.

4.5.1 Analysis of the Session Management Schema 4.5.1 Cookie and Session Token Manipulation 4.5.2 Weak Session Tokens (TO ELIMINATE) 4.5.2 Exposed Session Variables 4.5.3 Session Riding 4.5.4 HTTP Exploit

Session token transport security and reuse of session tokens from HTTP to HTTPS [][Completed]Javier Fernandez-Sanguino

OWASP Testing Guide v2 Table of Contents