Authentication Frequency And Challenge Type Based On Application Usage

• US 20090133117A1
• Filed: 09/29/2008
• Published: 05/21/2009
• Est. Priority Date: 11/19/2007
• Status: Active Grant

• Current Assignee: Arlington Technologies, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: Avaya Incorporated
• Inventors: O'Gorman, Lawrence, Skiba, David Joseph, Bentley, Jon Louis, Erhart, George William, Sammon, Michael J.
• Granted Patent: US 9,027,119 B2
• Time in Patent Office: Days
• US Class Current: 726/17
• 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/0846 using time-dependent-passwords, e.g. periodically changing 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/3271 using challenge-response
• CPC Class Codes: H04W 12/06 Authentication

Abstract

An apparatus and method are disclosed for determining authentication frequency (i.e., the length of time between authenticating and re-authenticating a user) and challenge type (e.g., username/password, fingerprint recognition, voice recognition, etc.) based on what software applications a user is running on a data-processing system, and how those applications are being used (e.g., what functions are used, what data is input to or output by the application, how often and for how long applications are used, what input devices and output devices are used, etc.) Advantageously, the illustrative embodiment enables authentication frequency and challenge type to be adjusted based on the likelihood of malicious activity and/or the potential cost of malicious activity, as inferred from current and past application usage. In addition, the illustrative embodiment enables selection of an authentication challenge type that is less intrusive to a user based on current application usage.

Claims

1. A method comprising:

presenting a first authentication challenge at a data-processing system at time t₁; and

presenting a second authentication challenge at said data-processing system at time t₂;

wherein the magnitude of t₂-t₁ is based on usage of one or more applications of said data-processing system at one or more instants in time interval [t₁, t₂].

2. The method of claim 1 wherein the magnitude of t₂-t₁ is also based on usage of one or more applications of said data-processing system at one or more instants prior to said time t₁.

3. The method of claim 1 wherein the magnitude of t₂-t₁ is based on the identity of an application that is used.

4. The method of claim 1 wherein the magnitude of t₂-t₁ is based on one or more functions that are used in an application.

5. The method of claim 1 wherein the magnitude of t₂-t₁ is based on one or more inputs to an application.

6. The method of claim 1 wherein the magnitude of t₂-t₁ is based on one or more outputs of an application.

7. The method of claim 1 wherein the magnitude of t₂-t₁ is based on how input is supplied to an application.

8. The method of claim 1 wherein the magnitude of t₂-t₁ is based on for how much time an application is used.

9. The method of claim 1 wherein the magnitude of t₂-t₁ is based on how often an application is used.

10. The method of claim 1 wherein the magnitude of t₂-t₁ is based on how often a function of an application is used.

11. A method comprising generating an authentication challenge whose type is based on usage of one or more applications of a data-processing system.

12. The method of claim 11 wherein the type of said authentication challenge is also based on prior usage of one or more applications of said data-processing system.

13. The method of claim 11 wherein the type of said authentication challenge is based on the identity of an application that is used.

14. The method of claim 11 wherein the type of said authentication challenge is based on one or more functions that are used in an application.

15. The method of claim 11 wherein the type of said authentication challenge is based on one or more inputs to an application.

16. The method of claim 11 wherein the type of said authentication challenge is based on one or more outputs of an application.

17. The method of claim 11 wherein the type of said authentication challenge is based on how input is supplied to an application.

18. The method of claim 11 wherein the type of said authentication challenge is based on for how much time an application is used.

19. The method of claim 11 wherein the type of said authentication challenge is based on how often an application is used.

20. The method of claim 11 wherein the type of said authentication challenge is based on how often a function of an application is used.