Skip to main content

Use stateless session tokens

Summary​

The system should use securely generated, stateless session tokens that are validated using digital signatures instead of static API secrets.

Description​

This approach is aligned with security best practices by emphasizing the use of cryptography for securing session tokens. Digital signatures provide a robust mechanism for ensuring the authenticity and integrity of tokens. Static API secrets, such as hardcoded keys or long-lived secrets, present security risks if compromised. The general recommendation is to avoid using static secrets and instead rely on dynamically generated session tokens secured with digital signatures.

Supported In​

This requirement is verified in following services

PlanSupported
Essential🔴
Advanced🟢

References​

Vulnerabilities​

free trial

Search for vulnerabilities in your apps for free with Fluid Attacks' automated security testing! Start your 21-day free trial and discover the benefits of the Continuous Hacking Essential plan. If you prefer the Advanced plan, which includes the expertise of Fluid Attacks' hacking team, fill out this contact form.