How the concept is used

Different frameworks measure different things. NIST distinguishes confidence in identity proofing from the strength of subsequent authentication. eIDAS has its own framework for electronic identification schemes. A number or a label such as “high” is therefore not a self-explanatory quality score. A business needs to know who makes the assessment, which requirements apply and which stages of the journey are covered.

A practical example

A supplier may describe a login as strong because it uses multiple factors. That says something about access to the account, but does not necessarily explain how the person’s identity was checked when the account was created. Conversely, thorough initial identity proofing can be undermined by weak recovery later. Requirements should consider enrolment, ordinary use and recovery together.

Important distinctions

A NIST level should not simply be renamed as an equivalent eIDAS level without evidence. Any assurance claim also needs to identify the specific method and configuration. For an online shop, start with the failure you need to prevent: the wrong person, the wrong age or unauthorised account access. Then choose documented controls suited to that risk, rather than assuming the highest available number is always the correct requirement.

Sources

  1. NIST: NIST SP 800-63A-4: Identity Proofing and Enrollment Checked
  2. NIST: NIST SP 800-63B-4: Authentication and Authenticator Management Checked
  3. EUR-Lex: Regulation (EU) No 910/2014 Checked

These explanations were prepared with AI assistance and draw on the sources listed.