You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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:
eidasMeansLoa
(eIDAS identification means level of assurance)low | substantial | high
as per 2015/1502And one field for NIST:
nistAal
(authenticator assurance level)1 | 2 | 3
as per SP 800-63BThe text was updated successfully, but these errors were encountered: