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).
William has control over the generation of session identifiers
Owasp ASVS (4.0): 3.7.1
Owasp SCP: 58,59
Owasp Appsensor: SE2
Safecode: 28
ASVS V3.7 - Defenses Against Session Management Exploits
Password Guessing/Brute Force Attacks
Session Hijacking (Man-in-the-Middle)
Loading comments 0%