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

Add identification means / authenticator assurance level #34

Open
sander opened this issue Mar 4, 2024 · 1 comment
Open

Add identification means / authenticator assurance level #34

sander opened this issue Mar 4, 2024 · 1 comment
Labels
TBD we can not solve this right now, but maybe in the future

Comments

@sander
Copy link
Contributor

sander commented Mar 4, 2024

For some use cases it is important to know the security strength of the wallet/agent when applied to present credentials.

Common assessment criteria are available: (EU) 2015/1502 lists requirements for identification means characteristics and design for eIDAS LoA Low/Substantial/High, where LoA High will be required for the EUDI Wallet. Peer review feedback and related Guidance documents provide common interpretations. NIST SP 800-63B specifies Authenticator Assurance Levels (AALs) in more concrete detail.

For example, the EUDI Wallet will require eIDAS LoA High, while webshop coupon issuers may find AAL1 sufficient.

I suggest to add one field for eIDAS:

  • ID: eidasMeansLoa (eIDAS identification means level of assurance)
  • Type: low | substantial | high as per 2015/1502

And one field for NIST:

  • ID: nistAal (authenticator assurance level)
  • Type: 1 | 2 | 3 as per SP 800-63B
@maaikevanleuken maaikevanleuken added the TBD we can not solve this right now, but maybe in the future label Mar 21, 2024
@maaikevanleuken
Copy link
Contributor

It might be good to discuss this at DICE and/or IIW, or in the SIG call.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TBD we can not solve this right now, but maybe in the future
Projects
None yet
Development

No branches or pull requests

2 participants