Thanks Joni Brennan Store it anywhere they want puts all of the responsibility on the individual and not the service or platform. What infrastructure, not app, needs to be in place on the part of the verifier and issuers, of identifiers and the derived credentials. How do you manage your credz? Who manages those keys? How do I audit the use of my credz in particular for any ongoing AuthZ? EIC in full swing....
“The credential doesn’t get issued to the wallet it gets issued to the holder. The holder can store it anyway they want. Of course we’d prefer a privacy enhancing approach with certification. The holder needs to choose or we’ll have wallet based silos.” Very interesting comment from Pramod Varma of EkStep Foundation regarding choice and full user-centric design. #EIC2024
The point was more about choices. I agree “store it anywhere” is extremely oversimplifed . Secure, privacy engancing… and auditable or certified for private sector. These would be my preferences.
Unfortunately, it is not so black and white. To a certain degree the issuer needs to have a say where the credential is stored and how. Example, device binding if you do not want, that the credential can be copied and used on multiple devices from different persons.
Add Dynamic Cognitive Biometric to ALL existing authentication systems will make it more robust imho
Indeed Salvatore (Sal) D'Agostino, we have a few ideas about these critical questions.
EX-CEO/Founder NimbusID.com
6moIMHO , although location and how the credentials matter , HOW a user can prove to the Auth server that he/she is the rightful possessor of the credz at point of use is crucial