Skip to content

Add section addressing PII in schemas #168

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

Merged
merged 3 commits into from
Jun 22, 2023
Merged

Add section addressing PII in schemas #168

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5c3c97e
add section on pii
Jun 20, 2023
6be3ff1
Update index.html
decentralgabe Jun 20, 2023
87647ae
Update index.html
decentralgabe Jun 21, 2023
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
27 changes: 24 additions & 3 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -777,7 +777,28 @@ <h2>Privacy Considerations</h2>
This section details the general privacy considerations and specific privacy
implications of deploying this specification into production environments.
</p>
<section class="informative">
<section>
<h3>Personally Identifiable Information</h3>
<p>
Data associated with schemas and <a>verifiable credentials</a> are susceptible
to privacy violations when shared. Personally identifying data, such as a
government-issued identifier, address, or name, can be used to track and correlate
entities. Even less overt personal data such as a birthdate or postal code has
the ability to result in correlation and de-anonymization.
</p>
<p>
Implementers are strongly advised to avoid constructing schemas with any personally
identifiable information (PII).
</p>
<p>
If such personally identifiable information is necessary in a schema, or a credential
schema, implementers are strongly advised to use mechanisms while storing and
transporting <a>verifiable credentials</a> that protect the data from those who should
not access it such as Transportation Layer Security (TLS) or other means of encrypting
the data whether in transit or at rest.
</p>
</section>
<section>
<h3>Verifier Caching</h3>
<p>
Since schemas are immutable, they are highly cachable.
Expand All @@ -788,7 +809,7 @@ <h3>Verifier Caching</h3>
<a>verifier</a>-based access patterns on the schema.
</p>
</section>
<section class="informative">
<section>
<h3>Content Distribution Networks</h3>
<p>
The use of content distribution networks by <a>issuers</a> can increase the
Expand All @@ -808,7 +829,7 @@ <h2>Security Considerations</h2>
not understanding the implications of this section can result in
security vulnerabilities.
</p>
<section class="informative">
<section>
<h3>Issuer Impersonation</h3>
<p>
It is possible for a schema to become authoritative, such as schemas
Expand Down