Secure System and Method for Managing the Multi-factor Authentication Data of A User

• US 20180176212A1
• Filed: 12/18/2017
• Published: 06/21/2018
• Est. Priority Date: 12/16/2016
• Status: Active Grant

• Current Assignee: Vivek Chinar Nair
• Original Assignee: Vivek Chinar Nair
• Inventors: Nair, Vivek Chinar
• Granted Patent: US 10,701,064 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 21/32 using biometric data, e.g. fingerprints, iris scans or voiceprints
• CPC Class Codes: G06F 21/40 by quorum, i.e. whereby two or more security principals are required
• CPC Class Codes: G06F 9/4451 User profiles; Roaming
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: G10L 15/26 Speech to text systems G10L15/08 takes precedence
• CPC Class Codes: H04L 2463/082 applying multi-factor authentication
• CPC Class Codes: H04L 63/0838 using one-time-passwords
• 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 9/0863 involving passwords or one-time passwords network architectures or network communication protocols for using one-time keys in a packet data network H04L63/067
• CPC Class Codes: H04L 9/3228 One-time or temporary data, i.e. information which is sent for every authentication or authorization, e.g. one-time-password, one-time-token or one-time-key
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements

Abstract

A system for managing multi-factor authentication of a user includes: one or more source components for obtaining multi-factor authentication data by one or more of: receiving multi-factor authentication data via a network; generating multi-factor authentication data using an algorithm, and a user providing multi-factor authentication data; a routing component for associating the multi-factor authentication codes from the one or more source components with an appropriate user account; a database comprising multi-factor authentication data wherein components of the multi-factor authentication data are stored in association with a particular user account; and one or more delivery components for providing the multi-factor authentication data to a user on a user device.

Claims

1. A system for receiving multi-factor authentication messages comprising:

one or more virtual phones hosted on a server, the one or more virtual phones associated with one or more telephone numbers and configured to receive multi-factor authentication messages directed to the one or more telephone numbers;

a routing component for associating data derived from a received multi-factor authentication message with an appropriate user account;

a database comprising multi-factor authentication data wherein portions of the multi-factor authentication data are stored in association with a particular user account;

a user-facing application interface for providing data derived from the received authentication message and authentication code to a user on a user device.

2. The multi-factor authentication system of claim 1, further comprising a message parsing component that recognizes a source of the multi-factor authentication message based on one or more of:

text within a body of the received multi-factor authentication message;

an origination number of the received multi-factor authentication message;

a destination number of the received multi-factor authentication message; and

data derived from the received multi-factor authentication message.

3. The multi-factor authentication system of claim 2, wherein the message parsing component further improves recognition of a source of the multi-factor authentication message based on previous actions of one or more of the users.

4. The multi-factor authentication system of claim 1, further comprising a message parsing component that identifies a multi-factor authentication code within the received multi-factor authentication message.

5. The multi-factor authentication system of claim 1, one or more of the telephone numbers is capable of receiving data for multiple user accounts.

6. The system for receiving multi-factor authentication messages of claim 1, wherein multi-factor authentication messages comprise SMS messages containing a multi-factor authentication code.

7. The system for receiving multi-factor authentication messages of claim 1, wherein multi-factor authentication messages comprise audio messages containing a multi-factor authentication code.

8. The system for receiving multi-factor authentication messages of claim 7, wherein audio messages containing the multi-factor authentication code are further analyzed using speech-to-text software prior to data derived from the received audio messages being provided to the user on the user device.

9. A system for managing multi-factor authentication of a user, the system comprising:

one or more source components for obtaining multi-factor authentication data by one or more of;

receiving multi-factor authentication data via a network;

generating multi-factor authentication data using an algorithm; and

a user providing multi-factor authentication data;

a routing component for associating the multi-factor authentication codes from the one or more source components with an appropriate user account;

a database comprising multi-factor authentication data wherein components of the multi-factor authentication data are stored in association with a particular user account;

one or more delivery components for providing the multi-factor authentication data to a user on a user device.

10. The system for managing multi-factor authentication of a user of claim 9, wherein one or more of the one or more source components comprises receiving a multi-factor authentication code via an SMS message.

11. The system for managing multi-factor authentication of a user of claim 9, wherein one or more of the one or more source components comprises receiving a multi-factor authentication code via an audio message.

12. The system for managing multi-factor authentication of a user of claim 9, wherein one or more of the one or more source components comprises receiving multi-factor authentication over a network via an API.

13. The system for managing multi-factor authentication of a user of claim 9, wherein one or more of the one or more source components comprises generating a multi-factor authentication code using one or more of TOTP and HOTP.

14. The system for managing multi-factor authentication of a user of claim 9, wherein one or more of the one or more delivery components comprises an application implemented on the user'"'"'s mobile device.

15. The system for managing multi-factor authentication of a user of claim 14, wherein the application implemented on the user'"'"'s mobile device comprises one of the one or more source components by forwarding authentication messages received on the user'"'"'s mobile device to the routing component.

16. The system for managing multi-factor authentication of a user of claim 14, wherein the application implemented on the user'"'"'s mobile device verifies an identity of the user through biometric data collected via one or more sensors of the user'"'"'s mobile device.

17. The system for managing multi-factor authentication of a user of claim 9, wherein one or more of the one or more delivery components comprises a browser extension implemented on a web browser of the user.

18. The system for managing multi-factor authentication of a user of claim 17, wherein the browser extension implemented on the user'"'"'s web browser is further configured to input multi-factor authentication data into websites supporting multi-factor authentication.

19. The system for managing multi-factor authentication of a user of claim 9, wherein one or more of the one or more delivery components comprises transmitting authentication data to a third-party service over a network via an API.

20. The system for managing multi-factor authentication of a user of claim 9, wherein the database further comprises additional authentication data for authenticating the user with one or more third-party services, the additional authentication data comprising one or more of:

a username;

an email address;

a password;

a recovery code;

a PIN code;

a security question;

an answer to the security question;

biometric data; and

geolocation data.

21. The system for managing multi-factor authentication of a user of claim 20, wherein one or more of the delivery components is further configured to provide the additional authentication to the user on a user device.

22. The system for managing multi-factor authentication of a user of claim 9, further comprising an access control component for restricting user access to authentication data stored on the database based on one or more access control policies.

23. The system for managing multi-factor authentication of a user of claim 22, wherein the access control module is further configured to allow two or more users access to the same multi-factor authentication data.

24. The system for managing multi-factor authentication of a user of claim 9, further comprising an auditing component for retaining events related to user security, including one or more of:

addition of a user account;

removal of a user account;

retrieval of multi-factor authentication data from the database;

addition of new multi-factor authentication data from the database;

receipt of multi-factor authentication data via a network by a source component;

a change of settings for a user account; and

a user accessing a user account.

25. The system for managing multi-factor authentication of a user of claim 24, wherein authentication data is displayed on the user-facing application interface only when a user provides instructions to retrieve the authentication data, and wherein the audit module retains information related to the user instructing the system to retrieve the authentication data to ensure that a record exists containing every instance the authentication data was accessed.