+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.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. Apžvalga

Pavadinimas Standartas
V9.2.1 Verify that, if a validity time span is present in the token data, the token and its content are …

Verify that, if a validity time span is present in the token data, the token and its content are accepted only if the verification time is within this validity time span. For example, for JWTs, the claims 'nbf' and 'exp' must be verified.

V9.2.2 Verify that the service receiving a token validates the token to be the correct type and is meant …

Verify that the service receiving a token validates the token to be the correct type and is meant for the intended purpose before accepting the token's contents. For example, only access tokens can be accepted for authorization decisions and only ID Tokens can be used for proving user authentication.

V9.2.3 Verify that the service only accepts tokens which are intended for use with that service …

Verify that the service only accepts tokens which are intended for use with that service (audience). For JWTs, this can be achieved by validating the 'aud' claim against an allowlist defined in the service.

V9.2.4 Verify that, if a token issuer uses the same private key for issuing tokens to different audiences …

Verify that, if a token issuer uses the same private key for issuing tokens to different audiences, the issued tokens contain an audience restriction that uniquely identifies the intended audiences. This will prevent a token from being reused with an unintended audience. If the audience identifier is dynamically provisioned, the token issuer must validate these audiences in order to make sure that they do not result in audience impersonation.

1.1 Nuorodos

1.2 Nustatyti reikalavimai

1.3 Susiję teisės aktai

2. Nustatyti reikalavimai

Reikalavimai
Šaltinis Reikalavimas

3. Susiję teisės aktai

Teisės aktai
Šaltinis Reguliavimas
  • 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.