Difference between revisions of "Data Minimization"

From MgmtWiki
Jump to: navigation, search
(Created page with "==Full Title or Meme== For the purposes of Privacy it is generally a good idea to minimize the amount of data that is transmitted to that which is absolutely essential. =...")
(No difference)

Revision as of 14:41, 12 September 2022

Full Title or Meme

For the purposes of Privacy it is generally a good idea to minimize the amount of data that is transmitted to that which is absolutely essential.

Context

Solutions

Using Zero Knowledge Proofs

If you want to know more about the arguments against a ZK approach, perhaps talk to Dave Longley, who has articulated some principled concerns. If you want to know more about those who are doing things like this, perhaps talk to the Hyperledger Indy community. Both parties will be able to give you much more detailed info.

In some of our more recent security & privacy architecture work, we also looked at some of the ZK approaches (such as BBS+ proofs) but have elected to instead focus on elision & redaction by a hash-tree-based graph, and enveloped encryption approaches. In particular, we felt that it was important that holders could also withhold details, not just issuers.

Though our MVA (minimum viable architecture) does not conform with the current W3C efforts for DID 1.0 or VC 1.1 / 2.0 (though someday we might submit for VC 3.0), they are quite parallel, and you might find them useful ground for defining your own requirements.

References