Difference between revisions of "Authenticator"

From MgmtWiki
Jump to: navigation, search
(Table of Authenticators)
(Solution)
 
(14 intermediate revisions by the same user not shown)
Line 13: Line 13:
 
* The page [[One-Time Password Authenticator]] has a description of one type of [[Authenticator]].
 
* The page [[One-Time Password Authenticator]] has a description of one type of [[Authenticator]].
 
* [https://w3c.github.io/webauthn/#authentication-assertion Web Authentication Authenticator]. A cryptographic entity, existing in hardware or software, that can register a user with a given Relying Party and later assert possession of the registered public key credential, and optionally verify the user, when requested by the Relying Party. [[Authenticator]]s can report information regarding their type and security characteristics via attestation during registration. A WebAuthn Authenticator could be a roaming Authenticator, a dedicated hardware subsystem integrated into the client device, or a software component of the client or client device.
 
* [https://w3c.github.io/webauthn/#authentication-assertion Web Authentication Authenticator]. A cryptographic entity, existing in hardware or software, that can register a user with a given Relying Party and later assert possession of the registered public key credential, and optionally verify the user, when requested by the Relying Party. [[Authenticator]]s can report information regarding their type and security characteristics via attestation during registration. A WebAuthn Authenticator could be a roaming Authenticator, a dedicated hardware subsystem integrated into the client device, or a software component of the client or client device.
* Authentication Assertion = The cryptographically signed AuthenticatorAssertionResponse object returned by an Authenticator as the result of an authenticatorGetAssertion operation.
+
* Authentication [[Assertion]] = The cryptographically signed AuthenticatorAssertionResponse object returned by an Authenticator as the result of an authenticatorGetAssertion operation.
 
* Authentication Ceremony = The ceremony where a user, and the user’s client (in conjunction with at least one Authenticator) works in concert to cryptographically prove to a Relying Party that the user controls the credential private key associated with a previously-registered public key credential (see Registration). Note that this includes a test of user [[Presence]] or user verification.
 
* Authentication Ceremony = The ceremony where a user, and the user’s client (in conjunction with at least one Authenticator) works in concert to cryptographically prove to a Relying Party that the user controls the credential private key associated with a previously-registered public key credential (see Registration). Note that this includes a test of user [[Presence]] or user verification.
  
Line 20: Line 20:
  
 
{|  border="1" padding="2" width="600px"
 
{|  border="1" padding="2" width="600px"
|Vendor ||Technology|| Android || Apple || Windows
+
|Vendor ||Technology|| Android || Apple || Microsoft
 
|-
 
|-
|FIDO 2 Keys|| App Store || phone || iPhone || store
+
|Push Notifications||QR aka.ms/mfasetup || - || - || Azure AD ONLY
 +
|-
 +
|FIDO 2 Keys|| On or Off Line || phone || iPhone || eindows
 
|-
 
|-
 
|Windows Hello|| App Store || phone || iPhone || store
 
|Windows Hello|| App Store || phone || iPhone || store
 
|-
 
|-
|Microsoft Authenticator|| App Store || phone || iPhone || store
+
|Microsoft Authenticator|| Single ID ONLY -- PoP by multiple choice || Notification push || Notification push || n/a
 
|-
 
|-
 
|Google|| database || kavi.com || ||member db is distinct
 
|Google|| database || kavi.com || ||member db is distinct
 
|-
 
|-
|WIKI.IDESG.ORG || Wikimedia || Ping? || ||
+
|Auth0 || SMS or email -- Online OH:Y ||Android || iPhone  ||
 
|-
 
|-
 
|IDEFREGISTRY.ORG || word press || Early Adopter|| || separate trust zone
 
|IDEFREGISTRY.ORG || word press || Early Adopter|| || separate trust zone

Latest revision as of 14:34, 2 March 2021

Full Title or Meme

Authenticators are devices in the user's possession that can generate believable claims that information has been contemporaneously generated by the device.

Context

Problem

Give users a hand-held device that can generate secured claims for access to secure accounts.

Solution

  • The page One-Time Password Authenticator has a description of one type of Authenticator.
  • Web Authentication Authenticator. A cryptographic entity, existing in hardware or software, that can register a user with a given Relying Party and later assert possession of the registered public key credential, and optionally verify the user, when requested by the Relying Party. Authenticators can report information regarding their type and security characteristics via attestation during registration. A WebAuthn Authenticator could be a roaming Authenticator, a dedicated hardware subsystem integrated into the client device, or a software component of the client or client device.
  • Authentication Assertion = The cryptographically signed AuthenticatorAssertionResponse object returned by an Authenticator as the result of an authenticatorGetAssertion operation.
  • Authentication Ceremony = The ceremony where a user, and the user’s client (in conjunction with at least one Authenticator) works in concert to cryptographically prove to a Relying Party that the user controls the credential private key associated with a previously-registered public key credential (see Registration). Note that this includes a test of user Presence or user verification.


Table of Authenticators

Vendor Technology Android Apple Microsoft
Push Notifications QR aka.ms/mfasetup - - Azure AD ONLY
FIDO 2 Keys On or Off Line phone iPhone eindows
Windows Hello App Store phone iPhone store
Microsoft Authenticator Single ID ONLY -- PoP by multiple choice Notification push Notification push n/a
Google database kavi.com member db is distinct
Auth0 SMS or email -- Online OH:Y Android iPhone
IDEFREGISTRY.ORG word press Early Adopter separate trust zone
Showing currently known information

References

Health Care Solutions

  • HIPAA
  • TEFCA technically applies only to members of a "Qualified Health Information Network" (QHIN) to require AAL2 assurance, but since many of the organizations that host the QHIN will fill other roles, the requirement could apply to a large number of health providers.

Other Material

  • Trusted Exchange Framework and Common Agreement (TEFCA) Draft 2 (2019-04-19)
    6.2.5 User Authentication. Each QHIN shall adhere to the user authentication functional requirements as described in the QHIN Technical Framework where applicable. Additionally, each QHIN shall require that any staff or users at the QHIN, Participants, or Individual Users who request EHI or request to send EHI shall be authenticated at a minimum of AAL2 and, if not an Individual User, also provide support for at least FAL2. Each QHIN shall also require each of its Participants to authenticate any Participant Members or Individuals Users that request EHI or request to send EHI at a minimum of AAL2 and, if not an Individual User, also provide support for at least FAL2.
  • A User’s Guide to Understanding to TEFCA Draft 2 A slide deck that introduces some erroneous simplifications. (like credential)