The system should use securely generated, stateless session tokens that are validated using digital signatures instead of static API secrets.
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.
This requirement is verified in following services
Plan | Supported |
---|---|
Essential | 🔴 |
Advanced | 🟢 |