Session Security: Cookies, Tokens and Session Fixation

Session Lifecycle

In Session Security testing, identity and authorization are two different questions: who is the client, and what are they allowed to perform on the resource. Roles, Claims, Session, Object ownership, and changes throughout the lifecycle are examined, not just whether the user is 'logged in'.

A test matrix includes an anonymous user, a regular user, an object owner, another user, and an administrator. For each action, the Response and server-side impact are compared. Changing an identifier or Header is only a testing means; the evidence is that the server approved or rejected an action contrary to policy.

Cookie attributes

The topic 'Cookie attributes' is a central part of working on Session Security testing. It is recommended to break it down into three questions: what is the input, what decision do we want to make, and what evidence is sufficient to justify it. These questions prevent automatic tool usage without understanding the purpose.

In practice, note Secure/HttpOnly/SameSite, rotation, expiration, revocation, fixation, compare to expected behavior, and define at least one Pivot. The result should be verifiable by another analyst, including limitations and next steps.

Rotation and Fixation

The topic 'Rotation and Fixation' is a central part of working on Session Security testing. It is recommended to break it down into three questions: what is the input, what decision do we want to make, and what evidence is sufficient to justify it. These questions prevent automatic tool usage without understanding the purpose.

In practice, note Secure/HttpOnly/SameSite, rotation, expiration, revocation, fixation, compare to expected behavior, and define at least one Pivot. The result should be verifiable by another analyst, including limitations and next steps.

Timeout and Logout

The topic 'Timeout and Logout' is a central part of working on Session Security testing. It is recommended to break it down into three questions: what is the input, what decision do we want to make, and what evidence is sufficient to justify it. These questions prevent automatic tool usage without understanding the purpose.

In practice, note Secure/HttpOnly/SameSite, rotation, expiration, revocation, fixation, compare to expected behavior, and define at least one Pivot. The result should be verifiable by another analyst, including limitations and next steps.

Tokens, Storage, and Retest

Professional Session Security testing begins with success and failure conditions. A positive case, a negative case, a boundary case, and similar legitimate activity are defined. This allows for identifying both False Negative and False Positive.

In an authorized environment, a minimal action that proves the claim without causing harm is used. Input, Output, time, and version are saved, and after remediation, a Retest is performed in the same scenario, and Regression on nearby functions is also checked.

Unique Testing Focus Areas

For this topic, it is recommended to build a focused evidence map in advance. The main testing focus areas are: Secure/HttpOnly/SameSite, rotation, expiration, revocation, fixation, CSRF context. The list is not an automatic Checklist; each item is chosen because it can link an entity, action, and time or explain legitimate behavior.

• Secure/HttpOnly/SameSite: Define the expected value, what would be considered an anomaly, and what additional source would verify the finding.
• rotation: Define the expected value, what would be considered an anomaly, and what additional source would verify the finding.
• expiration: Define the expected value, what would be considered an anomaly, and what additional source would verify the finding.
• revocation: Define the expected value, what would be considered an anomaly, and what additional source would verify the finding.
• fixation: Define the expected value, what would be considered an anomaly, and what additional source would verify the finding.
• CSRF context: Define the expected value, what would be considered an anomaly, and what additional source would verify the finding.

When one of the focus areas is unavailable, the gap should be documented, and an alternative selected. For example, if a Process identifier is unstable, time, Host, User, and Parent can be used; if a Payload is encrypted, Metadata, volume, frequency, and TLS/DNS context are used.

Recommended Workflow

1. Define a Scope and a single working question regarding Session Security testing.
2. Note the data sources and required evidence: Secure/HttpOnly/SameSite, rotation, expiration, revocation.
3. Create a short Baseline of normal behavior or an expected outcome.
4. Perform the minimal test in a lab environment and save time, input, and output.
5. Build a Timeline or comparison table and separate fact from interpretation.
6. Pivot to an additional source to confirm or refute the initial explanation.
7. Summarize the decision, limitations, recommended action, and Retest criterion.

Practical Scenario

The chosen scenario is comparing a Session before and after Login/Logout in a lab. The purpose of the exercise is not to demonstrate attack capability, but to practice safe collection, comparison, and documentation. Before starting, dummy data, a time window, and an expected outcome are defined.

At the end of the exercise, a deliverable should be submitted that another analyst or tester can review: a screenshot or export of the evidence, a short Timeline, an initial assumption, corroborating evidence, a limitation, and a recommendation. When there is insufficient evidence, the correct conclusion is that the scenario was not proven.

Practical Checklist

• ✓Check and document: Role and session.
• ✓Check and document: Endpoint and method.
• ✓Check and document: Request/Response.
• ✓Check and document: Object identifier.
• ✓Check and document: Server-side effect.
• ✓Check and document: Control expected and remediation.
• ✓Note Time zone, tool version, and collection time.
• ✓Save the raw data before filtering or modification.
• ✓Write what the finding proves and what is still unknown.
• ✓Define owner and next action with a deadline.

Common Mistakes

• Checking only Status code.
• Relying on Client-side changes.
• Using a dangerous Payload.
• Not checking different Roles.
• Ignoring business logic.
• Reporting without clean Request/Response.

Summary and CTA

Session Security: Cookies, Tokens, and Session Fixation is a topic that connects technical knowledge to work discipline. Start with a question, collect only relevant evidence, maintain context and time, and choose an action that can be justified and re-tested.

In HPI's Cybersecurity & AI program, these principles are practiced using systems, logs, and labs. A natural next step is to move on to the linked articles, perform the lab exercise, and save the deliverable as part of a professional portfolio.

FAQ