Authentication frequency and challenge type based on application usage

• US 9,027,119 B2
• Filed: 09/29/2008
• Issued: 05/05/2015
• Est. Priority Date: 11/19/2007
• Status: Active Grant

• Current Assignee: Arlington Technologies, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: Avaya Incorporated
• Inventors: Bentley, Jon Louis, Erhart, George William, O'Gorman, Lawrence, Sammon, Michael J., Skiba, David Joseph
• Primary Examiner(s): Gelagay, Shewaye
• Assistant Examiner(s): ABEDIN, SHANTO
• Application Number:
  US12/240,912
• Publication Number:
  US 20090133117A1
• Time in Patent Office: 2,409 Days
• Field of Search: 726 2- 7, 726 17- 18, 726/21, 455/411, 455/410, 713/152, 713182-186, 713/166
• US Class Current: 726/21
• 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, via a processor, a first authentication challenge at a device at a first time;

determining, via the processor, a time interval for presenting a second authentication challenge based on (i) an application currently being accessed at the device, (ii) a time duration for which the application is used at the device since the first time, and (iii) input capabilities of the device; and

presenting, via the processor, the second authentication challenge at the device at a second time, wherein the second time is determined based on the time interval, and wherein a challenge type associated with the second authentication challenge is determined based on a function performed by the application.

2. The method of claim 1, wherein the time interval is determined, at a third time, further based on usage of the application prior to the third time.

3. The method of claim 1, wherein at least one of the challenge type or the time interval is determined further based on an identity of the application.

4. The method of claim 1, wherein the time interval is determined further based on a function that is used in the application.

5. The method of claim 1, wherein the time interval is determined further based on an input to the application.

6. The method of claim 1, wherein the time interval is determined further based on an output of the application.

7. The method of claim 1, wherein the time interval is determined further based on how input is supplied to the application.

8. The method of claim 1, wherein the time interval is determined further based on how much time the application is used for before the first time.

9. The method of claim 1, wherein the time interval is determined further based on how often the application is used.

10. The method of claim 1, wherein the time interval is determined further based on how often a function of the application is used.

11. A computer-readable storage device storing instructions which, when executed by a processor, cause the processor to perform operations comprising:

presenting a first authentication challenge at a device at a first time;

determining a time frame for presenting a second authentication challenge at the device based on (i) an application currently being accessed at the device, (ii) a time duration for which the application is used at the device since the first time, and (iii) input capabilities of the device; and

presenting the second authentication challenge at the device at a second time, wherein the second time is determined based on the time frame, and wherein a challenge type associated with the second authentication challenge is determined based on a function performed by the application.

12. A system comprising:

a processor; and

a non-transitory computer-readable storage medium storing instructions which, when executed by the processor, cause the processor to perform operations comprising;

presenting a first authentication challenge at a device at a first time;

determining a magnitude of a time frame for presenting a second authentication challenge based on (i) an application currently being accessed at the device, (ii) a time duration for which the application is used at the device since the first time, and (iii) input capabilities of the device; and

presenting the second authentication challenge at the device at a second time, wherein the second time is determined based on the magnitude, and wherein a challenge type associated with the second authentication challenge is determined based on a function performed by the application.

13. The system of claim 12, wherein the time interval is determined, at a third time, further based on usage of the application prior to the third time.

14. The system of claim 12, wherein at least one of the challenge type or the time interval is determined further based on an identity of the application.

15. The system of claim 12, wherein the time interval is determined further based on a function that is used in the application.

16. The system of claim 12, wherein the time interval is determined further based on an input to the application.

17. The system of claim 12, wherein the time interval is determined further based on an output of the application.

18. The system of claim 12, wherein the time interval is determined further based on a duration of time the application is used for before the first time.

19. The system of claim 12, wherein the time interval is determined further based on how often the application is used.

20. The system of claim 12, wherein the time interval is determined further based on how often a function of the application is used.