System and method for non-intrusive, privacy-preserving authentication

• US 9,396,320 B2
• Filed: 12/31/2013
• Issued: 07/19/2016
• Est. Priority Date: 03/22/2013
• Status: Active Grant

• Current Assignee: Nok Nok Labs Incorporated
• Original Assignee: Nok Nok Labs Incorporated
• Inventors: Lindemann, Rolf
• Primary Examiner(s): Paliwal, Yogesh
• Application Number:
  US14/145,439
• Publication Number:
  US 20140289819A1
• Time in Patent Office: 931 Days
• Field of Search: 713/186
• US Class Current: 1/1
• CPC Class Codes: G06F 21/32 using biometric data, e.g. fingerprints, iris scans or voiceprints
• CPC Class Codes: G06F 21/577 Assessing vulnerabilities and evaluating computer system security
• CPC Class Codes: G06F 2221/2115 Third party
• CPC Class Codes: G06Q 20/204 comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
• CPC Class Codes: G06Q 20/3224 Transactions dependent on location of M-devices
• CPC Class Codes: G06Q 20/3274 using a pictured code, e.g. barcode or QR-code, being displayed on the M-device
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/4012 Verifying personal identification numbers [PIN]
• CPC Class Codes: G06Q 20/40145 Biometric identity checks
• CPC Class Codes: G06Q 20/42 Confirmation, e.g. check or permission by the legal debtor of payment
• CPC Class Codes: G06Q 20/425 using two different networks, one for transaction and one for security confirmation
• CPC Class Codes: G07F 19/20 Automatic teller machines [ATMs]
• CPC Class Codes: H04L 2209/805 Lightweight hardware, e.g. radio-frequency identification [RFID] or sensor
• CPC Class Codes: H04L 2463/102 applying security measure for e-commerce data processing systems or methods, specially adapted for e-commerce G06Q30/00
• CPC Class Codes: H04L 63/0492 by using a location-limited connection, e.g. near-field communication or limited proximity of entities
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/0861 using biometrical features, e.g. fingerprint, retina-scan cryptographic mechanisms or cryptographic arrangements for entity authentication using biological data H04L9/3231
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 9/0819 Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) network architectures or network communication protocols for key distribution in a packet data network H04L63/062
• CPC Class Codes: H04L 9/0822 : using key encryption key
• CPC Class Codes: H04L 9/0841 : involving Diffie-Hellman or related key agreement protocols
• CPC Class Codes: H04L 9/3231 : Biological data, e.g. fingerprint, voice or retina network architectures or network communication protocols for supporting authentication of entities using biometrical features in a packet data network H04L63/0861
• CPC Class Codes: H04L 9/3247 : involving digital signatures
• CPC Class Codes: H04L 9/3297 : involving time stamps, e.g. generation of time stamps
• CPC Class Codes: H04W 12/06 : Authentication
• CPC Class Codes: H04W 12/065 : Continuous authentication

Abstract

A system, apparatus, method, and machine readable medium are described for non-intrusive privacy-preserving authentication. For example, one embodiment of a method comprises: entering into a legitimate user state on a client device for a time period following an explicit authentication by an end user; recording reference data related to user behavior while in the legitimate user state; measuring user behavior when outside of the legitimate user state and arriving at an authentication assurance level based on a distance between the measured user behavior and the recorded reference data; in response to an authentication request within the legitimate user state, providing an authentication assurance level at or above a defined threshold, the authentication assurance level being sufficient to authenticate the user to a relying party; and in response to an authentication request while outside of the legitimate user state, providing the authentication assurance level based on a distance between the measured user behavior and the recorded reference data.

Claims

1. A method comprising:

entering into a legitimate user state on a client device for a specified time period following a first explicit authentication by an end user;

recording reference data related to user behavior while in the legitimate user state;

measuring user behavior when outside of the legitimate user state and arriving at an authentication assurance level based on a distance between the measured user behavior and the recorded reference data;

entering into a first transaction with a relying party over a network resulting in an authentication request from the relying party;

in response to receiving the authentication request within the legitimate user state, transmitting an authentication assurance level at or above a defined threshold from the client device to the relying party over the network, the authentication assurance level being sufficient to authenticate the user to the relying party, and the relying party to responsively allow the first transaction; and

in response to an authentication request while outside of the legitimate user state, transmitting the authentication assurance level based on a distance between the measured user behavior and the recorded reference data from the client device to the relying party over the network;

wherein in response to receiving the authentication assurance level, determining at the relying party whether the authentication assurance level is acceptable to complete the first transaction, wherein if the assurance level is acceptable, then the relying party to responsively allow the first transaction and wherein if the assurance level is not acceptable, then the relying party to transmit a response requesting additional authentication, the method further comprising;

performing a second explicit authentication by the end user on the client device to re-enter the legitimate user state; and

transmitting an authentication assurance level from the client device to the relying party, and the relying party to responsively allow the first transaction.

2. The method as in claim 1 wherein the first and second explicit authentications by the end user comprises the user entering a secret identification code or swiping a finger on a fingerprint authenticator on the client device.

3. The method as in claim 1 wherein recording the reference data based on user behavior comprises using sensors and associated hardware and/or software on the client device to measure gait of the user as the user is walking, the reference data defining a reference gait of the user.

4. The method as in claim 1 wherein recording the reference data based on user behavior comprises using sensors and associated hardware and/or software on the client device to measure locations of the client device while in the legitimate user state, the reference data defining a set of reference locations.

5. The method as in claim 4 wherein in addition to measuring locations of the client device while in the legitimate user state, the client device allows the user to specify certain locations as trusted regions.

6. The method as in claim 1 wherein recording the reference data based on user behavior comprises using sensors and associated hardware and/or software on the client device to measure one or more of the following variables to be used as reference data:

networks or devices to which the client device is connected;

smart watches;

Bluetooth devices;

near field communication (NFC) devices;

other computing devices;

Nymi bracelets;

Wifi networks in reach;

Wifi-enabled computers in reach;

acceleration sensor characteristics;

digital camera sensor pattern noise;

touch screen gestures of normal user interaction; and

user typing behavior from normal user interaction.

7. The method as in claim 1 further comprising:

continuing to record reference data related to user behavior for an extended window of time outside the legitimate user state.

8. The method as in claim 1 wherein the client device provides for multiple forms of explicit user authentication, wherein at least some forms of explicit user authentication will not result in a maximum assurance level.

9. The method as in claim 1 further comprising:

encrypting the assurance level using a key prior to transmitting the assurance level to the relying party.

10. The method as in claim 1 wherein the explicit authentication by the end user comprises requiring user interaction in order to trigger and/or unlock the explicit authentication.

11. The method as in claim 10 wherein the user interaction comprises selecting a button or tapping on the client device.

12. The method as in claim 1 wherein the relying party initially specifies a required assurance level for a particular transaction and the assurance level gain is selected to ensure that the required assurance level is met.

13. An client device having a memory for storing program code and a processor for processing the program code, the client device comprising:

an explicit user authenticator comprising at least one biometric sensor or keypad to perform a first explicit authentication of an end user, the explicit user authenticator to cause the client device to enter into a legitimate user state for a specified time period following the first explicit authentication; and

one or more additional sensors to collect reference data related to user behavior while in the legitimate user state, the one or more sensors in communication with the processor, the processor to perform the operations of;

recording the reference data related to user behavior while in the legitimate user state;

measuring user behavior using the one or more sensors when outside of the legitimate user state and arriving at an authentication assurance level based on a distance between the measured user behavior and the recorded reference data;

entering into a first transaction with a relying party over a network resulting in an authentication request from the relying party;

in response to receiving the authentication request within the legitimate user state, transmitting an authentication assurance level at or above a defined threshold from the client device to the relying party over the network, the authentication assurance level being sufficient to authenticate the user to the relying party, and the relying party to responsively allow the first transaction; and

in response to an authentication request while outside of the legitimate user state, transmitting the authentication assurance level based on a distance between the measured user behavior and the recorded reference data from the client device to the relying party over the network;

wherein in response to receiving the authentication assurance level, determining at the relying party whether the authentication assurance level is acceptable to complete the first transaction, wherein if the assurance level is acceptable, then the relying party to responsively allow the first transaction and wherein if the assurance level is not acceptable, then the relying party to transmit a response requesting additional authentication, the processor to perform the additional operations of;

performing a second explicit authentication by the end user on the client device to re-enter the legitimate user state; and

transmitting an authentication assurance level from the client device to the relying party, and the relying party to responsively allow the first transaction.

14. The client device as in claim 13 wherein the first and second explicit authentications by the end user comprises the user entering a secret identification code or swiping a finger on a fingerprint authenticator on the client device.

15. The client device as in claim 13 wherein recording the reference data based on user behavior comprises using sensors and associated hardware and/or software on the client device to measure gait of the user as the user is walking, the reference data defining a reference gait of the user.

16. The client device as in claim 13 wherein recording the reference data based on user behavior comprises using sensors and associated hardware and/or software on the client device to measure locations of the client device while in the legitimate user state, the reference data defining a set of reference locations.

17. The client device as in claim 16 wherein in addition to measuring locations of the client device while in the legitimate user state, the non-intrusive privacy-preserving authenticator allows the user to specify certain locations as trusted regions.

18. The client device as in claim 13 wherein recording the reference data based on user behavior comprises using sensors and associated hardware and/or software on the client device to measure one or more of the following variables to be used as reference data:

networks or devices to which the client device is connected;

smart watches;

Bluetooth devices;

near field communication (NFC) devices;

other computing devices;

Nymi bracelets;

Wifi networks in reach;

Wifi-enabled computers in reach;

acceleration sensor characteristics;

digital camera sensor pattern noise;

touch screen gestures of normal user interaction; and

user typing behavior from normal user interaction.

19. The client device as in claim 13 wherein the non-intrusive privacy-preserving authenticator continues to record reference data related to user behavior for an extended window of time outside the legitimate user state.

20. The client device as in claim 13 wherein the client device provides for multiple forms of explicit user authentication, wherein at least some forms of explicit user authentication will not result in a maximum assurance level.

21. The client device as in claim 13 further comprising:

a secure communication module to encrypt the assurance level using a key prior to transmitting the assurance level to the relying party.

22. The client device as in claim 13 wherein the explicit authentication by the end user comprises requiring user interaction in order to trigger and/or unlock the explicit authentication.

23. The client device as in claim 22 wherein the user interaction comprises selecting a button or tapping on the client device.

24. The client device as in claim 13 wherein the relying party initially specifies a required assurance level for a particular transaction and the assurance level gain is selected to ensure that the required assurance level is met.

25. The client device as in claim 24 wherein explicit user authentication is required if the calculated assurance level does not reach the required assurance level.