Adaptive timeouts for security credentials

• US 9,571,488 B2
• Filed: 11/30/2015
• Issued: 02/14/2017
• Est. Priority Date: 08/23/2012
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Roth, Gregory B., Allen, Nicholas Alexander, Ilac, Cristian M.
• Primary Examiner(s): Gergiso, Techane
• Application Number:
  US14/954,744
• Publication Number:
  US 20160080367A1
• Time in Patent Office: 442 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 2463/121 Timestamp cryptographic mechanisms or cryptographic arrangements involving time stamps H04L9/3297
• CPC Class Codes: H04L 43/106 using time related information in packets, e.g. by adding timestamps
• 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/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• 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/108 when the policy decisions are valid for a limited amount of time
• CPC Class Codes: H04L 63/168 above the transport layer
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding

Abstract

Session-specific information stored to a cookie or other secure token can be selected and/or caused to vary over time, such that older copies will become less useful over time. Such an approach reduces the ability of entities obtaining a copy of the cookie from performing unauthorized tasks on a session. A cookie received with a request can contain a timestamp and an operation count for a session that may need to fall within an acceptable range of the current values in order for the request to be processed. A cookie returned with a response can be set to the correct value or incremented from the previous value based on various factors. The allowable bands can decrease with age of the session, and various parameter values such as a badness factor for a session can be updated continually based on the events for the session.

Claims

1. A system for managing session information, comprising:

at least one processor; and

memory storing instructions that, when executed by the at least one processor, cause the system to;

receive a request from a client, the request seeking access to at least one resource, the request including at least one security credential;

authenticate a source of the request based at least in part on the at least one security credential;

initiate a session and send the client a session token for the session, the session token including a timestamp indicating a time at which the session was initiated;

receive a second request from the client, the second request including the session token;

determine a confidence value, the confidence value being based at least in part on a comparison between a time indicated by the timestamp in the session token and a current time;

process the second request upon a determination that the confidence value meets a threshold value; and

send a response to the client, the response including an updated session token including an updated timestamp, the updated timestamp differing from the current time by an amount based at least in part on the confidence value.

2. The system of claim 1, wherein the instructions when executed further cause the system to:

receive a third request from the client, the third request including the updated session token;

determine an updated confidence value, the updated confidence value being based at least in part on a comparison between a time indicated by the updated timestamp in the updated session token and the current time;

determine that the updated confidence value is below the threshold value;

determine an operation count associated with the updated session token and a current operation count associated with the session; and

increase the confidence value by an amount based at least in part on an amount of difference between the operation count associated with the updated session token and the current operation count.

3. The system of claim 1, wherein multiple clients are capable of submitting requests for the session, and wherein the instructions when executed further cause the system to:

determine an age of the session; and

determine an inactivity limit for the session based at least in part on the age of the session, wherein the session stays active as long as a request is processed within the inactivity limit, regardless of the age of the session.

4. The system of claim 1, wherein the instructions when executed further cause the system to:

store information for up to a determined number of most recently received requests, the information capable of identifying a source of each of the most recently received requests; and

determine an inactivity limit for a particular request of the most recently received requests, the inactivity limit for the particular request based at least in part upon a number of the most recently received requests corresponding to a source of the particular request.

5. The system of claim 4, wherein the instructions when executed further cause the system to:

determine that the number of the most recently received requests corresponding to the source of the particular request is less than a threshold number of the determined number of most recently received requests; and

determine a modification of the confidence value based at least in part on a difference between the number of the most recently received requests corresponding to the source of the particular request and the threshold number.

6. The system of claim 1, wherein the client comprises at least one of an application executing in a virtual computing instance, a computing device operating as part of a distributed computing environment, an application programming interface (API), an interface of a network interface layer of a resource provider in a multi-tenant computing environment, an application executing on a mobile computing device, or a web application.

7. The system of claim 1, wherein the confidence value is further based at least in part on a determination of a number of different clients that are submitting requests associated with the session or a determination of accuracy with regard to information associated with the session token received from the client.

8. A computer-implemented method, comprising:

receiving a request from a client, the request seeking access to at least one resource, the request including at least one security credential;

authenticating a source of the request based at least in part on the at least one security credential;

initiating a session and sending the client a session token for the session, the session token including a timestamp indicating a time at which the session was initiated;

receiving a second request from the client, the second request including the session token;

determining a confidence value, the confidence value being based at least in part on a comparison between a time indicated by the timestamp in the session token and a current time;

processing the second request upon a determination that the confidence value meets a threshold value; and

sending a response to the client, the response including an updated session token including an updated timestamp, the updated timestamp differing from the current time by an amount based at least in part on the confidence value.

9. The computer-implemented method of claim 8, further comprising:

receive a third request from the client, the third request including the updated session token;

determining an updated confidence value, the updated confidence value being based at least in part on a comparison between a time indicated by the updated timestamp in the updated session token and the current time;

determining that the updated confidence value is below the threshold value;

determining an operation count associated with the updated session token and a current operation count associated with the session; and

increasing the confidence value by an amount based at least in part on an amount of difference between the operation count associated with the updated session token and the current operation count.

10. The computer-implemented method of claim 8, wherein multiple clients are capable of submitting requests for the session, and further comprising:

determining an age of the session; and

determining an inactivity limit for the session based at least in part on the age of the session, wherein the session stays active as long as a request is processed within the inactivity limit, regardless of the age of the session.

11. The system of claim 8, wherein the instructions when executed further cause the system to:

storing information for up to a determined number of most recently received requests, the information capable of identifying a source of each of the most recently received requests; and

determining an inactivity limit for a particular request of the most recently received requests, the inactivity limit for the particular request based at least in part upon a number of the most recently received requests corresponding to a source of the particular request.

12. The computer-implemented method of claim 11, further comprising:

determining that the number of the most recently received requests corresponding to the source of the particular request is less than a threshold number of the determined number of most recently received requests; and

determining a modification of the confidence value based at least in part on a difference between the number of the most recently received requests corresponding to the source of the particular request and the threshold number.

13. The computer-implemented method of claim 8, wherein the client comprises at least one of an application executing in a virtual computing instance, a computing device operating as part of a distributed computing environment, an application programming interface (API), an interface of a network interface layer of a resource provider in a multi-tenant computing environment, an application executing on a mobile computing device, or a web application.

14. The computer-implemented method of claim 8, wherein the confidence value is further based at least in part on a determination of a number of different clients that are submitting requests associated with the session or a determination of accuracy with regard to information associated with the session token received from the client.

15. A non-transitory computer-readable storage medium including instructions that, when executed by at least one processor of a computing device, cause the computing device to:

receive a request from a client, the request seeking access to at least one resource, the request including at least one security credential;

authenticate a source of the request based at least in part on the at least one security credential;

initiate a session and send the client a session token for the session, the session token including a timestamp indicating a time at which the session was initiated;

receive a second request from the client, the second request including the session token;

determine a confidence value, the confidence value being based at least in part on a comparison between a time indicated by the timestamp in the session token and a current time;

process the second request upon a determination that the confidence value meets a threshold value; and

send a response to the client, the response including an updated session token including an updated timestamp, the updated timestamp differing from the current time by an amount based at least in part on the confidence value.

16. The non-transitory computer-readable storage medium of claim 15, wherein the instructions when executed further cause the computing device to:

receive a third request from the client, the third request including the updated session token;

determine an updated confidence value, the updated confidence value being based at least in part on a comparison between a time indicated by the updated timestamp in the updated session token and the current time;

determine that the updated confidence value is below the threshold value;

determine an operation count associated with the updated session token and a current operation count associated with the session; and

increase the confidence value by an amount based at least in part on an amount of difference between the operation count associated with the updated session token and the current operation count.

17. The non-transitory computer-readable storage medium of claim 15, wherein the instructions when executed further cause the computing device to:

determine an age of the session; and

determine an inactivity limit for the session based at least in part on the age of the session, wherein the session stays active as long as a request is processed within the inactivity limit, regardless of the age of the session.

18. The non-transitory computer-readable storage medium of claim 15, wherein the instructions when executed further cause the computing device to:

store information for up to a determined number of most recently received requests, the information capable of identifying a source of each of the most recently received requests; and

determine an inactivity limit for a particular request of the most recently received requests, the inactivity limit for the particular request based at least in part upon a number of the most recently received requests corresponding to a source of the particular request.

19. The non-transitory computer-readable storage medium of claim 18, wherein the instructions when executed further cause the computing device to:

determine that the number of the most recently received requests corresponding to the source of the particular request is less than a threshold number of the determined number of most recently received requests; and

determine a modification of the confidence value based at least in part on a difference between the number of the most recently received requests corresponding to the source of the particular request and the threshold number.

20. The non-transitory computer-readable storage medium of claim 15, wherein the client comprises at least one of an application executing in a virtual computing instance, a computing device operating as part of a distributed computing environment, an application programming interface (API), an interface of a network interface layer of a resource provider in a multi-tenant computing environment, an application executing on a mobile computing device, or a web application.