> For clean Markdown of this page, append .md to its URL. For the complete documentation index, see https://www.superagent.sh/llms.txt.


Check session invalidation after logout and whether workspace removal or API key revocation ends access in your application.

# Session and access revocation testing


[← Back to attack scenarios](https://www.superagent.sh/docs/products/red-teaming/attack-scenarios)

Logout should end the user's session. Removing someone from a workspace should end their access to that workspace even if their account stays active. Revoking an API key should end the access granted to that key. This scenario covers whichever of those events your application supports.

Session invalidation after logout applies to apps with persistent sign-in sessions. The same revocation question comes up in apps with team memberships, delegated access, or API credentials.

A finding shows which revocation event took place and what access remained afterward. The report can show the affected account or credential type and the data or action that was still available.

The app lists this scenario as **Retain access after logout, removal, or key revocation** (`APP-07`) in [Application Red Teaming](https://www.superagent.sh/docs/products/red-teaming/applications).

## Standards and guidance

[CWE-1464 Improper Session Invalidation](https://cwe.mitre.org/data/definitions/1464.html) · [CWE-1465 Improper Session Invalidation after User Logout](https://cwe.mitre.org/data/definitions/1465.html)

---
Source: https://www.superagent.sh/docs/products/red-teaming/attack-scenarios/application-session-revocation
Index: https://www.superagent.sh/llms.txt
