Overview#OAuth 2.0 Threat Model and Security Configurations (RFC 6819) gives additional Security Considerations for OAuth 2.0 beyond those in the OAuth specification, based on a comprehensive threat model for the OAuth 2.0 protocol RFC 6749.
OAuth 2.0 Threat Model and Security Configurations contains the following content:
- Documents any assumptions and scope considered when creating the threat model.
- Describes the security features built into the OAuth 2.0 protocol and how they are intended to thwart attacks.
- Gives a comprehensive threat model for OAuth and describes the respective countermeasures to thwart those threats.
Threats include any intentional attacks on OAuth tokens and resources protected by OAuth tokens, as well as security risks introduced if the proper security measures are not put in place. Threats are structured along the lines of the protocol structure to help development teams implement each part of the protocol securely, for example, all threats for granting access, or all threats for a particular grant type, or all threats for protecting the resource server.
Note: This document cannot assess the probability or the risk associated with a particular threat because those aspects strongly depend on the particular application and deployment OAuth is used to protect. Similarly, impacts are given on a rather abstract level. But the information given here may serve as a foundation for deployment-specific threat models. Implementors may refine and detail the abstract threat model in order to account for the specific properties of their deployment and to come up with a risk analysis.
As OAuth 2.0 Threat Model and Security Configurations is based on the base OAuth 2.0 specification, it does not consider proposed extensions such as OAuth 2.0 Client Registration or OAuth 2.0 Authorization Server Metadata, many of which are still under discussion.