What does High Assurance mean?

[tlodderstedt]

resolves #189

[tlodderstedt]

I considered adding a bullet that the profile also give the holder (some) assurance about the identity of the verifier she discloses her credential data to.

Any thought?

[andprian]

There are many concepts in the description here that I do not see in the HAIP profiles. Where are the requirements mentioned about:

• Policies and procedures
• Holder authentication / Holder binding
• Claim authenticity

[tlodderstedt]

HAIP defines on a technically level how holder authentication can be proved and claim authenticity is protected by way of requiring certain protocol and credential format features.
Out of scope are concrete holder authentication mechanisms (which ensure the holder can only sign the presentation) and policies and procedures (as this is a technical interop profile and not a policy definition).
Shall we add this?

[tlodderstedt]

added suggest text to the PR
@andprian please review

[andprian]

@tlodderstedt There is currently some confusion in the EU on the link between the HAIP profiles and the LoA High attainment. Could you clarify that while HAIP provides a good basis, it is not sufficient and extra elements that are out of scope would be needed for LoA High

[Sakurann]

WG discussion: @andprian to propose a text that high assurance here is not EU LoA High

[andprian]

WG discussion: @andprian to propose a text that high assurance here is not EU LoA High

@tlodderstedt , I suggest the following additional note:

Note: This specification does not correspond to the "High" Level of Assurance (LoA) as defined in the eIDAS Regulation. While this profile defines features intended for scenarios targeting a high level of security, these measures alone are not sufficient to achieve LoA High compliance. Meeting LoA High requires additional measures outside the scope of HAIP.

[jogu]

Seems reasonable @andprian - I might suggest rewording the first sentence a little as it someone could read it as "HAIP is not suitable for LoA High":

Note: This specification fulfils some, but not all, of the requirements to meet the "High" Level of Assurance (LoA) as defined in the eIDAS Regulation. While this profile defines features intended for scenarios targeting a high level of security, these measures alone are not sufficient to achieve LoA High compliance. Meeting LoA High requires additional measures outside the scope of HAIP.

[andprian]

Seems reasonable @andprian - I might suggest rewording the first sentence a little as it someone could read it as "HAIP is not suitable for LoA High":

Note: This specification fulfils some, but not all, of the requirements to meet the "High" Level of Assurance (LoA) as defined in the eIDAS Regulation. While this profile defines features intended for scenarios targeting a high level of security, these measures alone are not sufficient to achieve LoA High compliance. Meeting LoA High requires additional measures outside the scope of HAIP.

Looks good

[tlodderstedt]

@andprian @jogu updated PR to incorporate your proposals. I combined the 2nd and 3rd sentence to make the text more concise.

[jogu]

"defined" feels a bit awkward. Possibly this is slightly less awkward:

Suggested change

	The level of security and privacy defined in this profile includes the following assurance:
	This profile aims to achieve a level of security and privacy that includes the following properties:

[Sakurann]

@andprian @jogu updated PR to incorporate your proposals. I combined the 2nd and 3rd sentence to make the text more concise.

@andprian would be great if you could approve the PR before the WG call. if not, i would take your thumbs up on the Torsten's comment as an approval :)

[c2bo]

I agree with @jogu's proposed rewording.

[c2bo]

Suggested change

* Authenticity of claims: There is strong assurance that the claims within a Credential are valid and bound to the correct Holder. This involves the policies and procedures used to collect and maintain the claims, the authentication of the Holder during issuance, and the protection of claim authenticity both at rest (in the wallet) and during presentation. The scope for this profile is: security of the issuance process, protection of issued credentials, and mechanisms for the Verifiers to access trustworthy information about the Issuer.

* Authenticity of claims: There is strong assurance that the claims within a Credential or Presentation are valid and bound to the correct Holder. This involves the policies and procedures used to collect and maintain the claims, the authentication of the Holder during issuance, and the protection of claim authenticity both at rest (in the wallet) and during presentation. The scope for this profile is: security of the issuance process, protection of issued credentials, and mechanisms for the Verifiers to access trustworthy information about the Issuer.