The system should use securely generated, stateless session tokens that are validated using digital signatures instead of static API secrets.
CWE-290: Authentication Bypass by Spoofing. This attack-focused weakness is caused by improperly implemented authentication schemes that are subject to spoofing attacks.
CWE-345: Insufficient Verification of Data Authenticity. The software does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
CWE-798: Use of Hard-coded Credentials. The software contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data.
OWASP Top 10 A2:2017-Broken Authentication. Application functions related to authentication and session management are often implemented incorrectly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users' identities temporarily or permanently.
OWASP-ASVS v4.0.1 V3.2 Session Binding Requirements.(3.2.2) Verify that session tokens possess at least 64 bits of entropy.
OWASP-ASVS v4.0.1 V3.5 Token-based Session Management.(3.5.1) Verify the application does not treat OAuth and refresh tokens — on their own — as the presence of the subscriber and allows users to terminate trust relationships with linked applications.
OWASP-ASVS v4.0.1 V3.5 Token-based Session Management.(3.5.2) Verify the application uses session tokens rather than static API secrets and keys, except with legacy implementations.
OWASP-ASVS v4.0.1 V3.5 Token-based Session Management.(3.5.3) Verify that stateless session tokens use digital signatures, encryption, and other countermeasures to protect against tampering, enveloping, replay, null cipher, and key substitution attacks.
PCI DSS v3.2.1 - Requirement 6.5.10 Address common coding vulnerabilities in software-development processes such as broken authentication and session management.