Preventing Session Hijacking: Secure Your Web Application Sessions
Learn about session hijacking, the risks, prevention methods, and why session identifiers should be unique, secure, and managed properly. Discover best practices and the importance of maintaining client-side and server-side security.
Preventing Session Hijacking: Secure Your Web Application Sessions
E N D
Presentation Transcript
Session Hijacking Tarun Lall
What is Session Hijacking • TCP Connection Takeover • Takeover of a Web Application Session
State Management • HTTP is Stateless • Web Applications need state • User Logins • Shopping Carts
State Management, Cont’d • Client Side • Server Side • Golden Rule of Web Application Security • Cookies and Hidden Fields
Reasons for Session Hijacking • No Standards for Maintaining State • Session Tracking and State information at Client
How to Prevent Session Hijacking • Session Identifiers Should Be Unique • Session Identifiers Should Not be Guessable • Session Identifiers Should Be Independent • Session Identifiers Should be Mapped with Client-Side Connections
References • Web hacking Attacks and Defense by Stuart McClure, Saumil Shah, Shreeraj Shah • http://www.ftponline.com/javapro/2004_01/magazine/columns/proshop/default_pf.aspx • http://www.iss.net/security_center/advice/Exploits/TCP/session_hijacking/default.htm • http://staff.washington.edu/dittrich/talks/qsm-sec/script.html