Skip to content

Mention security analysis in the specification #694

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dpostnikov wants to merge 4 commits into
base: main
Choose a base branch
from
+28 −1
Open

Mention security analysis in the specification #694

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6f38f8f
Add security analysis comment
dpostnikov Feb 11, 2026
6064815
Applicable to different sections of the document
dpostnikov Feb 11, 2026
01c7b44
reference typo
dpostnikov Feb 11, 2026
75aeba6
Apply suggestions from code review
Sakurann Mar 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 28 additions & 1 deletion openid-4-verifiable-presentations-1_0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1769,6 +1769,10 @@ While breaking changes to the specifications referenced in this specification ar

# Security Considerations {#security_considerations}

## Formal Security Analysis

The security properties of the OpenID for Verifiable Credentials family of specifications have been formally analyzed, see [@secanalysis.openid4vc].

## Preventing Replay of Verifiable Presentations {#preventing-replay}

An attacker could try to inject Presentations obtained from (for example) a previous Authorization Response into another Authorization Response, thus impersonating the End-User that originally presented the respective Verifiable Presentation. Holder Binding aims to prevent such attacks.
Expand Down Expand Up @@ -2367,6 +2371,27 @@ Ecosystems intending to use trusted authority mechanisms SHOULD ensure that the
</front>
</reference>

<reference anchor="secanalysis.openid4vp.dc" target="https://openid.net/wp-content/uploads/2025/08/Report-Deliverable-A_1_B_.pdf">
<front>
<title>Formal Security Analysis of the OpenID for Verifiable Presentations Specification (with DC API)</title>
<author fullname="Fabian Hauck"></author>
<author fullname="Pedram Hosseyni"></author>
<author fullname="Ralf Küsters"></author>
<author fullname="Tim Würtele"></author>
<date day="15" month="July" year="2025"/>
</front>
</reference>

<reference anchor="secanalysis.openid4vc" target="https://elib.uni-stuttgart.de/items/07055a8e-a85e-42b9-98b5-11f046d5fb91">
<front>
<title>OpenID for Verifiable Credentials: Formal Security Analysis using the Web Infrastructure Model</title>
<author fullname="Fabian Hauck">
</author>
<date day="2" month="October" year="2023"/>
</front>
</reference>


# OpenID4VP over the Digital Credentials API {#dc_api}

This section defines how to use OpenID4VP with the Digital Credentials API.
Expand Down Expand Up @@ -2544,13 +2569,15 @@ The audience for the response (for example, the `aud` value in a Key Binding JWT

## Security Considerations {#dc_api_security_considerations}

The security properties of the OpenID4VP protocol, when used in conjunction with the Digital Credentials API (DC API) [@!W3C.Digital_Credentials_API], have been formally analyzed, see [@secanalysis.openid4vp.dc].

The following security considerations from OpenID4VP apply:

* Preventing Replay of Verifiable Presentations as described in (#preventing-replay), with the difference that the origin is used instead of the Client Identifier to bind the response to the Client.
* End-User Authentication using Credentials as described in (#end-user-authentication-using-credentials).
* Encrypting an Unsigned Response as described in (#encrypting_unsigned_response).
* TLS Requirements as described in (#tls-requirements).
* Always Use the Full Client Identifier as described in (#full-client-identifier) for signed requests.
* Always use the Full Client Identifier as described in (#full-client-identifier) for signed requests.
* Security Checks on the Returned Credentials and Presentations as described in (#dcql_query_security).
* DCQL Value Matching as described in (#dcql-value-matching).

Expand Down