From 2d6ce1dd473be8fc26c71e62f8c7d61916a15192 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Thu, 5 Dec 2024 12:54:10 -0500 Subject: [PATCH] Add initial content to Security and Privacy Considerations sections. (#189) --- index.html | 236 +++++++++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 200 insertions(+), 36 deletions(-) diff --git a/index.html b/index.html index 4aa28d6..1bcfb14 100644 --- a/index.html +++ b/index.html @@ -433,48 +433,212 @@

Security Considerations

-

- This section is a work in progress as this document evolves. -

-

- The documents listed below outline initial security considerations for - Digital Credentials, both broadly and for presentation on the web. - Their contents will be integrated into this document gradually. -

- +
+

+ This section is a work in progress as this document evolves. +

+ +

+ The documents listed below outline initial security considerations for + Digital Credentials, both broadly and for presentation on the web. + Their contents will be integrated into this document gradually. +

+ +
+ +
+

Credential Protocols

+ +

+Explain that while the API provides security at the browser API level, that +security for the underlying credential issuance or presentation protocol is a +separate concern and that developers need to understand that layer of the stack +to get a total picture of the protections that are in place during any given +transaction. +

+
+ +
+

Cross-device Protocols

+ +

+Explain that cross-device issuance or presentation uses a separate protocol +that has its own security characteristics. +

+
+ +
+

Quishing

+ +

+Explain that the API is designed to avoid the problem of quishing +(phishing via QR Codes) and other QR Code and non-browser API-based attacks +and to be aware of exposure of QR Codes during digital credential interactions. +

+
+ +
+

Data Integrity

+ +

+Explain that the API does not provide data integrity on the digital +credential requests or responses and that responsibility is up to the +underlying protocol used for the request or response. +

+
+ +
+

Authentication

+ +

+Explain that authentication (such as a PIN code to unlock) to a particular app, +such as a digital wallet, that responds to an API request is crucial in +high-risk use cases. +

+
+ +
+

Cross-Site Scripting (XSS) and Cross-Site Request Forgery (CSRF)

+ +

+Explain what attacks are possible via XSS and CSRF, if any. +

+
+ +
+

Session Security

+ +

+Explain that once a secure session is established at a website using +credentials exchanged over this API, that the subsequent security is no +longer a function of the credential used or this API and is up to the +session management utilized on the website. +

+
+ +

Privacy Considerations

-

+

+

This section is a work in progress as this document evolves. -

-

- The documents listed below outline various privacy considerations for - Digital Credentials, both broadly and for presentation on the web. - Their contents will be integrated into this document gradually. -

- +

+

+ The documents listed below outline various privacy considerations for + Digital Credentials, both broadly and for presentation on the web. + Their contents will be integrated into this document gradually. +

+ +
+ +
+

Unnecessary Requests for Credentials

+ +

+Explain how the API could be used to unnecessarily request digital credentials +from individuals such as requesting a driver's license to log into a +movie rating website and how the ecosystem can mitigate this risk. +

+
+ +
+

Over Collection of Data

+ +

+Explain how the API could be used to request more data than necessary for +a transaction and how the ecosystem can mitigate that over collection. +

+
+ +
+

Individual Consent

+ +

+Explain how the API acquires an individual's consent to share a digital +credential and how digital wallets can also provide further consent when +sharing information. +

+
+ +
+

Data Retention

+ +

+Explain how verifiers might retain data and what the ecosystem does to +mitigate excessive data retention policies. +

+
+ +
+

Compliance with Privacy Regulations

+ +

+Explain to what extent the API complies with known privacy regulations (e.g., +consent) and what parts of those regulations are not possible to enforce via the +API (e.g., retention). +

+
+ +
+

Selective and Unlinkable Disclosure

+ +

+Explain how selective disclosure and unlinkable disclosure help preserve +privacy as well as their limitations in doing so. +

+
+ +
+

Phoning Home

+ +

+Explain how some systems might "phone home", the impact on privacy that +might have, and what the ecosystem provides to mitigate the risk. +

+
+ +
+

Transmission of Personally Identifiable Information

+ +

+Explain that the API does enable the transmission of personally identifiable +information and that it does its best to ensure there is informed consent +by the individual, but that the consent might be provided due to exhaustion +or not understanding what PII is being transmitted and how to mitigate those +concerns. +

+
+