Security Considerations: Secure Context #426
Draft
+96
−71
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Security properties and mitigations - Secure Context For more context, please refer to the [Google Doc](https://docs.google.com/document/d/1BpBBiv7GgkGi1_Y7NvyD3Mkalj0g857Qw-aan3NqYwU/edit?tab=t.dilz864boly) containing the Threat Model (which will be published as separate Notes) and the complete Section.
TallTed
reviewed
Jan 13, 2026
| behavior only when mediating credential presentation and issuance. | ||
| </p> | ||
| <p> | ||
| Other security properties that depend on protocols, Wallet |
Contributor
There was a problem hiding this comment.
Suggested change
| Other security properties that depend on protocols, Wallet | |
| Other security properties that depend on protocols, wallet |
TallTed
reviewed
Jan 13, 2026
| ecosystem level for Decentralized Identities), the Threat Model for | ||
| the Web (at the web ecosystem level), RFC 3552 (at the internet | ||
| level), and the FIDO Security Reference, since the FIDO's Client to | ||
| Authenticator Protocol (CTAP) protocol is used for cross-device flow. |
Contributor
There was a problem hiding this comment.
Suggested change
| Authenticator Protocol (CTAP) protocol is used for cross-device flow. | |
| Authenticator Protocol (CTAP) is used for cross-device flow. |
TallTed
reviewed
Jan 13, 2026
| <a href= | ||
| "https://github.com/w3c-cg/threat-modeling/blob/main/models/decentralized-identities.md"> | ||
| Threat Model for Decentralized Identities</a> | ||
| <li>Out-of-Scope threats handled by protocols, Wallets, OS platform |
Contributor
There was a problem hiding this comment.
Suggested change
| <li>Out-of-Scope threats handled by protocols, Wallets, OS platform | |
| <li>Out-of-scope threats handled by protocols, wallets, OS platform |
TallTed
reviewed
Jan 13, 2026
| mediation role: | ||
| </p> | ||
| <ul> | ||
| <li><strong>T1</strong>: Presentation Request Modification (Tampering) — A malicious script or compromised page attempts to alter a DigitalCredentialGetRequest before processing.</li> |
Contributor
There was a problem hiding this comment.
Suggested change
| <li><strong>T1</strong>: Presentation Request Modification (Tampering) — A malicious script or compromised page attempts to alter a DigitalCredentialGetRequest before processing.</li> | |
| <li><strong>T1</strong>: Presentation Request Modification (Tampering) — | |
| A malicious script or compromised page attempts to alter a | |
| DigitalCredentialGetRequest before processing.</li> |
TallTed
reviewed
Jan 13, 2026
| "https://github.com/w3c-cg/threat-modeling/blob/main/models/decentralized-identities.md"> | ||
| Threat Model for Decentralized Identities</a> | ||
| <li>Out-of-Scope threats handled by protocols, Wallets, OS platform | ||
| security, or transport layers. Even if Out-of-Scope, they are |
Contributor
There was a problem hiding this comment.
Suggested change
| security, or transport layers. Even if Out-of-Scope, they are | |
| security, or transport layers. Even if out-of-scope, they are |
TallTed
reviewed
Jan 13, 2026
| </p> | ||
| <section> | ||
| <h4>Secure Context</h4> | ||
| <p>WebIDL [=interfaces=] of the Digital Credential API are only exposed in a Secure Context, thus reducing [=tampering=].</p> |
Contributor
There was a problem hiding this comment.
Suggested change
| <p>WebIDL [=interfaces=] of the Digital Credential API are only exposed in a Secure Context, thus reducing [=tampering=].</p> | |
| <p>WebIDL [=interfaces=] of the Digital Credential API are only exposed in a | |
| Secure Context, thus reducing [=tampering=].</p> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Secure Context
For more context, please refer to the Google Doc containing the Threat Model (which will be published as separate Notes) and the complete Section.
Closes #???
The following tasks have been completed:
Implementation commitment:
Documentation and checks
Preview | Diff