Back to overview

Session management 2

In general use the server or framework’s own session management controls, rather than creating custom code. The application should only recognize these session identifiers as valid, and the session identifier creation must always be done on a trusted system (e.g. server-side).

How to play?

William has control over the generation of session identifiers


Owasp ASVS (4.0): 3.7.1

Capec: 31 ,60 ,61

Owasp SCP: 58,59

Owasp Appsensor: SE2

Safecode: 28

ASVS (4.0) Cheatsheetseries Index

ASVS V3.7 - Defenses Against Session Management Exploits


Cross-Site Scripting (XSS)

Password Guessing/Brute Force Attacks

Session Fixation

Session Hijacking (Man-in-the-Middle)

Session Timeout Issues

Loading comments 0%

Github logo View source on GitHub

Provided by dotNET lab

This website is created, hosted and provided by dotNET lab. dotNET lab provides training and guidance on secure software development. Contact us to get in touch!

OWASP Cornucopia

OWASP Cornucopia is originally created by Colin Watson. It is open source and can be downloaded free of charge from the OWASP website. It is is free to use. It is licensed under the Creative Commons Attribution-ShareAlike 3.0 license, so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one. OWASP does not endorse or recommend commercial products or services. OWASP Cornucopia is licensed under the Creative Commons Attribution-ShareAlike 3.0 license and is © 2012-2016 OWASP Foundation.