Skip to content

Commit 69af3d5

Browse files
committed
Mention that spec authors can avoid id-based correlation.
1 parent 8d9a315 commit 69af3d5

File tree

1 file changed

+26
-13
lines changed

1 file changed

+26
-13
lines changed

index.html

Lines changed: 26 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -5300,22 +5300,32 @@ <h3>Personally Identifiable Information</h3>
53005300
<h3>Identifier-Based Correlation</h3>
53015301

53025302
<p>
5303-
[=Subjects=] of [=verifiable credentials=] are identified using the
5304-
`credential.credentialSubject.id` field. The identifiers used to
5305-
identify a [=subject=] create a greater risk of correlation when the
5306-
identifiers are long-lived or used across more than one web domain.
5303+
[=Subjects=] of [=verifiable credentials=] are identified using the `id`
5304+
property, as defined in Section [[[#identifiers]]], and are used in places such
5305+
as the `credentialSubject.id` property. The identifiers used to identify a
5306+
[=subject=] create a greater risk of correlation when the identifiers are
5307+
long-lived or used across more than one web domain.
53075308
</p>
53085309

53095310
<p>
5310-
Similarly, disclosing the [=credential=] identifier
5311-
(`credential.id`) leads to situations where multiple
5312-
[=verifiers=], or an [=issuer=] and a [=verifier=], can collude to
5313-
correlate the [=holder=]. If [=holders=] want to reduce correlation, they
5314-
should use [=verifiable credential=] schemes that allow hiding the
5315-
identifier during [=verifiable presentation=]. Such schemes expect the
5316-
[=holder=] to generate the identifier and might even allow hiding the
5317-
identifier from the [=issuer=], while still keeping the identifier embedded
5318-
and signed in the [=verifiable credential=].
5311+
Similarly, disclosing the [=credential=] identifier (such as in
5312+
[[[#example-usage-of-the-id-property]]]) leads to
5313+
situations where multiple [=verifiers=], or an [=issuer=] and a [=verifier=],
5314+
can collude to correlate the [=holder=]. If [=holders=] want to reduce
5315+
correlation, they are advised to use [=verifiable credentials=] from [=issuers=]
5316+
that allow selectively disclosing correlating identifiers in a [=verifiable
5317+
presentation=]. Such approaches expect the [=holder=] to generate the identifier
5318+
and might even allow hiding the identifier from the [=issuer=] through the use
5319+
of techniques like
5320+
<a href="https://en.wikipedia.org/wiki/Blind_signature">blind signatures</a>,
5321+
while still keeping the identifier embedded and signed in the [=verifiable
5322+
credential=].
5323+
</p>
5324+
5325+
<p>
5326+
Securing mechanism specification authors are advised to avoid enabling
5327+
identifier-based correlation by designing their technologies, when possible,
5328+
to avoid the use of correlating identifiers.
53195329
</p>
53205330

53215331
<p>
@@ -5326,6 +5336,9 @@ <h3>Identifier-Based Correlation</h3>
53265336

53275337
<ul>
53285338
<li>
5339+
Selectively disclosable
5340+
</li>
5341+
<li>
53295342
Bound to a single origin
53305343
</li>
53315344
<li>

0 commit comments

Comments
 (0)