+V9 Self-contained Tokens
---+V9.1 Token source and integrity
------+V9.1.1 Verify that self-contained tokens are validated using their digital signature or MAC to protect …
------+V9.1.2 Verify that only algorithms on an allowlist can be used to create and verify self-contained tokens …
------+V9.1.3 Verify that key material that is used to validate self-contained tokens is from trusted …
---+V9.2 Token content
------+V9.2.1 Verify that, if a validity time span is present in the token data, the token and its content are …
------+V9.2.2 Verify that the service receiving a token validates the token to be the correct type and is meant …
------+V9.2.3 Verify that the service only accepts tokens which are intended for use with that service …
------+V9.2.4 Verify that, if a token issuer uses the same private key for issuing tokens to different audiences …

V9 Self-contained Tokens

Control Objective

The concept of a self-contained token is mentioned in the original RFC 6749 OAuth 2.0 from 2012. It refers to a token containing data or claims on which a receiving service will rely to make security decisions. This should be differentiated from a simple token containing only an identifier, which a receiving service uses to look up data locally. The most common examples of self-contained tokens are JSON Web Tokens (JWTs) and SAML assertions.

The use of self-contained tokens has become very widespread, even outside of OAuth and OIDC. At the same time, the security of this mechanism relies on the ability to validate the integrity of the token and to ensure that the token is valid for a particular context. There are many pitfalls with this process, and this chapter provides specific details of the mechanisms that applications should have in place to prevent them.

References

For more information, see also:

1. Επισκόπηση

Τίτλος Πρότυπο
V9.1 Token source and integrity

This section includes requirements to ensure that the token has been produced by a trusted party and has not been tampered with.

V9.2 Token content

Before making security decisions based on the content of a self-contained token, it is necessary to validate that the token has been presented within its validity period and that it is intended for use by the receiving service and for the purpose for which it was presented. This helps avoid insecure cross-usage between different services or with different token types from the same issuer.

Specific requirements for OAuth and OIDC are covered in the dedicated chapter.

1.1 Παραπομπές

1.2 Εντοπισμένες απαιτήσεις

1.3 Σχετικοί κανονισμοί

2. Εντοπισμένες απαιτήσεις

Απαιτήσεις
Πηγή Απαίτηση

3. Σχετικοί κανονισμοί

Κανονισμοί
Πηγή Κανονισμός
  • OWASP -

    EN: Publications of the OWASP Foundation, https://owasp.org/. OWASP® is a registered trademark of the OWASP Foundation, Inc.; GRCA is not affiliated with, nor endorsed by, the OWASP Foundation. Only the versions published by OWASP are authoritative.

    DE: Veröffentlichungen der OWASP Foundation, https://owasp.org/. OWASP® ist eine eingetragene Marke der OWASP Foundation, Inc.; GRCA steht in keiner Verbindung zur OWASP Foundation und wird von ihr nicht unterstützt. Maßgeblich sind allein die von OWASP veröffentlichten Fassungen.