MULTI-DIMENSIONAL FRAMEWORK FOR DEFINING CRITERIA THAT INDICATE WHEN AUTHENTICATION SHOULD BE REVOKED

• US 20170054718A1
• Filed: 08/29/2016
• Published: 02/23/2017
• Est. Priority Date: 08/12/2014
• Status: Active Grant

• Current Assignee: BOKU Identity Incorporated
• Original Assignee: Danal Incorporated (Twilio, Inc.)
• Inventors: Banerjee, Atreedev, Cocklin, Jillian
• Granted Patent: US 9,942,230 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/335 for accessing specific resources, e.g. using Kerberos tickets
• CPC Class Codes: G06F 21/41 where a single sign-on provides access to a plurality of computers
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• 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/0815 providing single-sign-on or federations
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/0884 by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 9/3268 using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]

Abstract

Methods and systems are presented for defining criteria that indicate when authentication for an identified client device should be revoked based on rules associated with interested parties. Authentication information is stored that indicates that an identified client device is authenticated. Rules that are associated with a plurality of interested parties and include rules of different rule types may also be stored. Criteria may be defined based on the rules and the authentication information, the criteria indicating when authentication of the identified client device should be revoked. Authentication of the identified client device may be revoked based on the criteria.

Claims

1-26. -26. (canceled)

27. An aggregator system comprising:

a storage system configured to store;

authentication information associated with a client device, wherein the, authentication information indicates that the client device has been authenticated,

first rules information received from a first interested party,

second rules information received from a second interested party, wherein the first rules information and the second rules information each comprise respective rules of at least two different rule types selected from the group consisting of;

a predetermined number of uses of the client device, an event identifying the device as lost, an event identifying the client device as stolen, an event identifying a deactivated mobile number associated with the client device, an event identifying a fraud alert associated with the client device, a detected change between previously stored hashed information associated with the client device and current hashed information associated with the client device, a change in geographic location of the client device, detected mismatch in biometric authentication associated with the client device, an event identifying a change of account ownership associated with the client device, and an event identifying that an account associated with the client device has a payment status of past-due;

circuitry implementing a credentials engine configured to;

reconcile the respective rules of the first rules information and the second rules information having the same rule type based on a priority associated with each of the respective rules;

define criteria indicating when authentication of the client device will be revoked based on the authentication information and on the reconciling; and

invalidation circuitry configured to revoke authentication for the identified client device based on the criteria.

28. The system of claim 27, wherein each of the first interested party and the second interested party is one of:

a carrier system, a merchant system, a government organization, and a school organization.

29. The system of claim 27, wherein the first interested party is a carrier system configured to provide mobile network services to the client device, and wherein the second interested party is a merchant system configured to perform at least one transaction with the client device.

30. The system of claim 27, wherein the reconciling comprises determining rules for a combination of the first interested party and the second interested party.

31. The system of claim 27, wherein the authentication information comprises at least one credential.

32. The system of claim 31, wherein the at least one credential comprises a digital key.

33. The system of claim 27, wherein the invalidation circuitry is further configured to revoke authentication for the identified client device based on the criteria being met.

34. The system of claim 33, wherein the criteria are met upon receiving an event notification which matches at least one predetermined event.

35. The system of claim 27, wherein the respective rules of the first rules information and the second rules information conflict with each other.

36. The system of claim 35, wherein the credentials engine is configured to resolve the conflict based on the priority associated with each of the respective rules.

37. A method comprising:

storing, on a storage device, authentication information associated with an identified client device, wherein the authentication information indicates that the client device has been authenticated;

storing, on the storage device, first rules information received from a first interested party;

storing, on the storage device, second rules information received from a second interested party, wherein the first rules information and the second rules information each comprise respective rules of at least two different rule types selected from the group consisting of;

a predetermined number of uses of the client device, an event identifying the device as lost, an event identifying the client device as stolen, an event identifying a deactivated mobile number associated with the client device, an event identifying a fraud alert associated with the client device, a detected change between previously stored hashed information associated with the client device and current hashed information associated with the client device, a change in geographic location of the client device, detected mismatch in biometric authentication associated with the client device, an event identifying a change of account ownership associated with the client device, and an event identifying that an account associated with the client device has a payment status of past-due;

reconciling, using a credentials engine, the respective rules of the first rules information and the second rules information having the same rule type based on a priority associated with each of the respective rules

defining, using the credentials engine, criteria indicating when authentication of the client device will be revoked based on the authentication information and on the reconciling; and

revoking, using invalidation circuitry, authentication for the identified client device based on the criteria.

38. The method of claim 37, wherein each of the first interested party and the second interested party is one of:

a carrier system, a merchant system, a government organization, and a school organization.

39. The method of claim 37, wherein the first interested party is a carrier system configured to provide mobile network services to the client device, and wherein the second interested party is a merchant system configured to perform at least one transaction with the client device.

40. The method of claim 37, wherein the reconciling comprises determining rules for a combination of the first interested party and the second interested party.

41. The method of claim 37, wherein the authentication information comprises at least one credential.

42. The method of claim 41, wherein the at least one credential comprises a digital key.

43. The method of claim 37, further comprising:

revoking, using the invalidation circuitry, the authentication for the identified client device based on the criteria being met.

44. The method of claim 43, wherein the criteria are met upon receiving, using the credentials engine, an event notification which matches at least one predetermined event.

45. The method of claim 37, wherein the respective rules of the first rules information and the second rules information conflict with each other.

46. The method of claim 45, further comprising:

resolving, using the credentials engine, the conflict based on the priority associated with each of the respective rules.