Authentication Proxy

• US 20080010678A1
• Filed: 06/05/2007
• Published: 01/10/2008
• Est. Priority Date: 09/17/2004
• Status: Abandoned Application

• Current Assignee: Digital Envoy, Inc. (Landmark Media Enterprises LLC)
• Original Assignee: Digital Envoy, Inc. (Landmark Media Enterprises LLC)
• Inventors: Cabrera, Richard, Helsper, David, Burdette, Jeff
• Application Number:
  US11/758,588
• Publication Number:
  US 20080010678A1
• Time in Patent Office: Days
• US Class Current: 726/015
• CPC Class Codes: G06Q 30/0603 Catalogue ordering

Abstract

Systems, methods, and computer program products for providing fraud analysis to an application using a proxy and a fraud determination unit are provided. An Online Fraud Mitigation Engine is also provided in embodiments of the present invention for determining fraudulent transactions. Embodiments are also provided for calculating travel velocity and transaction frequency, which are useful for determining a fraudulent transaction. Further embodiments are provided for authenticating a transaction using an object stored on a client device and a behavior profile stored on a server.

Claims

1. A method for providing transparent fraud analysis for an application, wherein the application is accessed by a user via a login request, the method comprising the steps of:

a. coupling a fraud determination unit to a proxy;

b. configuring the proxy to intercept the login request and to forward the login request to the fraud determination unit; and

c. configuring the proxy to redirect the login request to the application if the fraud determination unit determines that the login request is not fraudulent.

2. The method of claim 1, further comprising the step of configuring the proxy to initiate a session with the application using the login request.

3. The method of claim 2, further comprising the steps of:

a. configuring the proxy to collect one or more objects associated with the session; and

b. configuring the proxy to provide at least one of the objects to the user upon being redirected to the application.

4. The method of claim 1, further comprising the steps of:

a. determining that the user needs to be associated with personal verification questions;

b. presenting one or more personal verification questions to the user;

c. determining which of the one or more personal verification questions that the user selected for answering;

d. storing the user'"'"'s answers to the selected personal verification questions; and

e. associating the one or more selected personal verification questions and answers with the user.

5. The method of claim 4, further comprising the steps of:

a. retrieving a personal verification question;

b. presenting the user with the personal verification question;

c. providing by the user an answer to the personal verification question; and

d. determining by the fraud determination unit whether the login request is fraudulent using the answer to the personal verification question.

6. The method of claim 1, further comprising the steps of:

a. coupling the proxy to a first network for communicating with the application; and

b. coupling the proxy to a second network for communicating with the fraud determination unit.

7. The method of claim 6, wherein the first network comprises at least one of a local area network, a wide area network, or the Internet.

8. The method of claim 6, wherein the second network comprises at least one of a local area network, a wide area network, or the Internet.

9. The method of claim 1, wherein the proxy communicates with the fraud determination unit over the Internet using a virtual private network.

10. The method of claim 1, wherein the proxy and the fraud determination unit reside on a local area network, and wherein the proxy communicates with the application using the Internet.

11. The method of claim 10, wherein the proxy and the fraud determination unit reside on the same computer.

12. The method of claim 1, wherein the fraud determination unit is coupled to a plurality of proxies that are associated with different entities.

13. The method of claim 8, wherein the fraud determination unit is coupled to a plurality of proxies that are associated with different entities.

14. The method of claim 1, further comprising the steps of:

a. computing one or more factors based on an IP address associated with the login request; and

b. determining by the fraud determination unit whether the login request is fraudulent based on the one or more factors.

15. The method of claim 14, wherein one factor is the travel velocity of the user between a first access location and a second access location.

16. The method of claim 15, wherein the user'"'"'s travel velocity is determined according to the steps of:

a. determining for the user the first access location using the IP address;

b. determining for the user a first access time using the login request;

c. determining for the user the second access location;

d. determining for the user a second access time; and

e. calculating the user'"'"'s travel velocity between the first access location and the second access location as a function of the first access location and the first access time and the second access location and the second access time.

17. The method of claim 14, wherein the proxy and the fraud determination unit communicate over the Internet.

18. The method of claim 14, wherein the fraud determination unit is coupled to a plurality of proxies that are associated with different entities.

19. The method of claim 14, wherein a factor is a frequency with which the login request is attempted within a predetermined period of time.

20. The method of claim 14, wherein a factor is a velocity with which the IP address accesses or uses multiple unique identifiers within a specified period of time.

21. The method of claim 14, wherein a factor comprises at least one of a connection type associated with the IP address or a host type associated with the IP address, wherein connection type comprises dial-up, Integrated Services Digital Network (ISDN), cable modem, Digital Subscriber Line (DSL), Digital Signal 1 (T1), or Optical Carrier 3 (OC3), and wherein host type comprises network end point, network proxy, or network firewall.

22. The method of claim 1, further comprising the steps of:

a. computing a frequency with which one or more other login requests have been attempted from an IP address associated with the login request;

b. determining a host type associated with the IP address, and

c. determining by the fraud determination unit whether the login request is fraudulent using the frequency and the host type.

23. The method of claim 1, further comprising the steps of:

a. storing a behavior profile associated with the user, the behavior profile including one or more factors associated with the user, the behavior profile also including an encryption key associated with the user;

b. encrypting the one or more factors using the encryption key to create one or more encrypted factors;

c. storing an object on a client device of the user, the object including the one or more encrypted factors;

d. generating by the user the login request using the client device;

e. deriving one or more factors from the login request;

f decrypting the one or more factors stored in the object using the encryption key to create one or more decrypted factors; and

g. comparing by the fraud determination unit the one or more factors in the behavior profile with the one or more decrypted factors to determine if the login request is fraudulent.

24. The method of claim 23, wherein the object comprises at least one of a Flash shared object or a cookie.

25. The method of claim 5, further comprising the steps of:

a. storing an object on a client device associated with the user, wherein the object includes at least a first identifier associated with the client device, and wherein a behavior profile is associated with the user;

b. generating by the user the login request using the client device;

c. performing a first comparison between one or more factors derived from the login request and one or more factors stored in the behavior profile;

d. performing a second comparison between the first device identifier and a second device identifier derived from the login request;

e. performing a third comparison between a last access time associated with the user and stored in the behavior profile and a last access time stored in the object; and

f determining by the fraud determination unit whether the login request is fraudulent based on the first comparison, the second comparison, and the third comparison.

26. The method of claim 25, wherein the object comprises at least one of a Flash shared object or a cookie.

27. The method of claim 9, further comprising the steps of:

a. storing an object on a client device associated with the user, wherein the object includes at least a first identifier associated with the client device, and wherein a behavior profile is associated with the user;

b. generating by the user the login request using the client device;

c. performing a first comparison between one or more factors derived from the login request and one or more factors stored in the behavior profile;

d. performing a second comparison between the first device identifier and a second device identifier derived from the login request;

e. performing a third comparison between an IP address derived from the login request and a plurality of IP addresses stored in the object; and

f. determining by the fraud determination unit whether the transaction is fraudulent based on the first comparison, the second comparison, and the third comparison.

28. The method of claim 27, wherein the object comprises at least one of a Flash shared object or a cookie.

29. A system for providing fraud analysis for an application, the system comprising:

a. a user that accesses the application via a login request;

b. a proxy configured to intercept the login request; and

c. a fraud determination unit comprising a processor programmed to perform the steps of;

i. receiving the login request from the proxy;

ii. determining whether the login request is fraudulent; and

iii. if the processor determines that the login request is not fraudulent, notifying the proxy that the login request is not fraudulent.

30. The system of claim 29, wherein the proxy communicates with the fraud determination unit using the Internet.

31. The system of claim 29, wherein the proxy communicates with the application using the Internet.

32. The system of claim 31, wherein the proxy and the fraud determination unit reside on the same local area network.

33. The system of claim 32, wherein the proxy and the fraud determination unit reside on the same computer.

34. The system of claim 30, wherein the fraud determination unit is coupled to a plurality of proxies associated with different entities.

35. The system of claim 34, wherein the processor of the fraud determination unit is further programmed to perform the steps of:

a. determining that the user needs to be associated with personal verification questions;

b. presenting one or more personal verification questions to the user;

c. determining which of the one or more personal verification questions that the user selected for answering;

d. storing the user'"'"'s answers to the selected personal verification questions; and

e. associating the one or more selected personal verification questions and answers with the user.

36. The system of claim 35, wherein the processor of the fraud determination unit is further programmed to perform the steps of:

a. retrieving a personal verification question;

b. presenting the user with the personal verification question; and

c. determining whether the login request is fraudulent using an answer to the personal verification question.

37. The system of claim 36, wherein the processor of the fraud determination unit is further programmed to perform the steps of:

a. initiating a session with the application using the login request;

b. collecting one or more objects associated with the session; and

c. providing at least one of the objects to the user upon being redirected to the application.

38. The system of claim 37, wherein the object comprises at least one of a Flash shared object or a cookie.