Draft for Recognized Entities Threat Model v1.0

Based on the feedback at the VCWG F2F meeting, I've updated the base
recognized entities threat model and have raised a PR for it here:

https://github.com/w3c/vc-recognized-entities/pull/83

There is a HTML preview attached to the initial PR comment:

https://github.com/user-attachments/files/28690000/NOTE-vc-recognized-entities-20260608.html

Changes since the F2F include a bespoke, artisanal threat model
diagram on the two major data flows we expect to be used in
production: 1) holder delivers recognized entity credential, and 2)
verifier downloads recognized entity credential list as a part of
administrative configuration. I'm fairly happy with the DFD for the
first cut at this point in time:

https://github.com/w3c/vc-recognized-entities/blob/ab11a9bd45e66c2fa9b6f971925de8edb0065204/threat-model/diagrams/dfd.png

I went through every threat we had in the spec already, all the ones
we brainstormed, and merged as many as I could without losing
important detail. We're at around 18 threats documented, but could
probably reduce it down to 12-15. This includes both the security and
privacy threats, with tags for each. I also included one market
competition threat to try out a new threat class and to see what it
would look like in the threat model.

I think this constitutes something we could submit for horizontal
review to both SING and PING if the group feels like it's complete
enough. Looking for high-level feedback on the direction. I expect
we'll have to significant editorial passes, but hope that the main
"bones" of the threat model is there now and is repeatable for the
other specs we have yet to threat model at this level of detail.

-- manu

-- 
Manu Sporny - https://www.linkedin.com/in/manusporny/
Founder/CEO - Digital Bazaar, Inc.
https://www.digitalbazaar.com/

Received on Monday, 8 June 2026 00:50:58 UTC