SESSION MANAGEMENT (SM5)
John can predict or guess session identifiers because they are not changed when the user's role alters (e.g. pre and post authentication) and when switching between non-encrypted and encrypted communications, or are not sufficiently long and random, or are not changed periodically
John can predict or guess session identifiers because they are not changed when the user's role alters (e.g. pre and post authentication) and when switching between non-encrypted and encrypted communications, or are not sufficiently long and random, or are not changed periodically
OWASP SCP
60,62,66,67,71,72
OWASP ASVS
3.2.1,3.2.2,3.2.4,3.3.1
OWASP AppSensor
SE4,SE5,SE6
CAPEC
-
SAFECODE
28
Ensure the following occur:
Ensure sufficiently long and random session identifiers are used Generate a new session identifier: If a session was established before login, and successful login has occurred When changing from HTTP to HTTPS When re-authenticating Periodically otherwise. See SM 7 for session termination on logging out.
Mappings
OWASP ASVS (4.0): 3.2.1 ,3.2.2 ,3.2.4 ,3.3.1
Capec: 31
OWASP SCP: 60,62,66,67,71,72
OWASP Appsensor: SE4,SE5,SE6
Safecode: 28
ASVS (4.0) Cheatsheetseries Index
ASVS V3.2 - Session Binding Requirements
ASVS V3.3 - Session Logout and Timeout Requirements
No suitable mappings were found.
