Skip to content
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.

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

Pillar 2: Security - Presentation Protocols #45

Open
tlodderstedt opened this issue Aug 28, 2024 · 2 comments
Open

Pillar 2: Security - Presentation Protocols #45

tlodderstedt opened this issue Aug 28, 2024 · 2 comments

Comments

@tlodderstedt
Copy link

tlodderstedt commented Aug 28, 2024

I would argue bullets i-iv & vi describe requirements for the implementation of a wallet while only v is about the protocol between wallet and verifier. I suggest to add the following requirements:

  • protocols shall ensure the integrity of the exchange, e.g. prevent injection, phishing, and session fixation attacks
  • protocols shall ensure confidentiality of the exchange, e.g. prevent credentials from leakage
  • protocols shall prevent replay of credential presentations being exchange, e.g. through binding of the presentation to a transaction specific nonce and an audience
  • protocols shall enable the holder to reliably authenticate the verifier (as a basis for informed consent and potential follow-up actions, such as complaints)
@tlodderstedt
Copy link
Author

I would also encourage you to add a similar section on issuance protocols.

@andy-tobin
Copy link

andy-tobin commented Sep 3, 2024

I think these four additions are valid and useful additions, thanks @tlodderstedt. The first three are fairly generic for issuance and presentation (and other bidirectional interactions).

Would you mind submitting a pull request to this effect, but leave out the words in brackets on the last bullet point (as we don't want to specify particular follow-on actions).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@tlodderstedt @andy-tobin and others