System and method for generating and implementing a real-time multi-factor authentication policy across multiple channels

1. A method for generating and implementing a real-time multi-factor authentication policy across multiple channels, the method performed on a computer having a processor, memory, and one or more code sets stored in the memory and executing by the processor, the method comprising:

during a pre-authentication stage:

receiving, via a user interface, information defining one or more scenarios;

receiving, via the user interface, information defining one or more authentication flows;

for each of the one or more scenarios, mapping, by the processor, one of the one or more authentication flows to a given scenario; and

generating a real-time multi-factor authentication policy associated with each of the one or more scenarios; and

during a real-time authentication stage:

upon receiving an interaction, identifying, by a decision engine, a relevant scenario of the one or more scenarios;

implementing, by the decision engine, the real-time multi-factor authentication policy associated with the relevant scenario; and

determining, by the decision engine, an authentication result.

2. The method as in claim 1 , wherein information defining one or more scenarios comprises at least one scenario parameter and at least one corresponding parameter value.

3. The method as in claim 1 , wherein a given authentication flow comprises:

at least one analysis vertex, wherein the at least one analysis vertex represents one of a collection of available authentication methods to execute during a real-time authentication stage;

at least one condition vertex, wherein the at least one condition vertex represents a matrix containing a collection of one or more predicates defining one or more conditions for a given result of each authentication method; and

at least one decision vertex, wherein the at least one decision vertex represents one of a plurality of potential authentication results of a given authentication flow.

4. The method as in claim 3 , wherein the authentication result is satisfied if all predicates in the collection of one or more predicates are determined to be true.

5. The method as in claim 1 , wherein a given authentication flow is mapped to a scenario based on a user indication linking the authentication flow and the scenario.

6. The method as in claim 1 , wherein an authentication result indicates a relative strength of the authentication.

7. The method as in claim 1 , further comprising:

determining a fraud suspicion level result based on implementation of the real-time multi-factor authentication policy, wherein the fraud suspicion level result indicates a relative level of suspicion of fraud.

8. The method as in claim 3 , further comprising:

providing to the user, via the user interface, an authentication flow generator, the authentication flow generator comprising:

one or more authentication method selection boxes for selecting one or more of a plurality of authentication methods;

one or more condition selection boxes for selecting one or more of a plurality of conditions to be associated with a given authentication method;

one or more predicate selection boxes for selecting one or more of a plurality of predicates to be associated with a given condition; and

one or more decision selection boxes for selecting a potential authentication result to be associated with the given authentication method.

9. The method as in claim 1 , wherein one or more authentication flows is executed at least one of in parallel and in series.

10. The method as in claim 2 , further comprising:

monitoring by the decision engine, a frequency with which a scenario is identified;

prioritizing the scenario when the frequency meets a predefined threshold; and

modifying at least one scenario parameter or at least one corresponding parameter value when the frequency does not meet the predefined threshold.

11. The method as in claim 2 , further comprising:

monitoring by the decision engine, an authentication failure rate of the real-time multi-factor authentication policy associated with the relevant scenario; and

when the authentication failure rate meets a predefined threshold, modifying, by the decision engine, at least one authentication flow mapped to the given scenario.

12. The method as in claim 7 , further comprising:

monitoring by the decision engine, a fraudulent detection rate of the real-time multi-factor authentication policy associated with the relevant scenario;

when the fraudulent detection rate does not meet a predefined threshold, modifying, by the decision engine, at least one authentication flow mapped to the given scenario; and

when the fraudulent detection rate meets a predefined threshold, prioritizing the relevant scenario.

13. A system for generating and implementing a real-time multi-factor authentication policy across multiple channels, comprising:

a computer having a processor and memory; and

one or more code sets stored in the memory and executing by the processor, which configure the processor to:

during a pre-authentication stage:

receive, via a user interface, information defining one or more scenarios;

receive, via the user interface, information defining one or more authentication flows;

for each of the one or more scenarios, map one of the one or more authentication flows to a given scenario; and

generate a real-time multi-factor authentication policy associated with each of the one or more scenarios; and

during a real-time authentication stage:

upon receiving an interaction, identify, by a decision engine, a relevant scenario of the one or more scenarios;

implement, by the decision engine, the real-time multi-factor authentication policy associated with the relevant scenario; and

determine, by the decision engine, an authentication result.

14. The system as in claim 13 , wherein information defining one or more scenarios comprises at least one scenario parameter and at least one corresponding parameter value.

15. The system as in claim 13 , wherein a given authentication flow comprises:

at least one analysis vertex, wherein the at least one analysis vertex represents one of a collection of available authentication methods to execute during a real-time authentication stage;

at least one condition vertex, wherein the at least one condition vertex represents a matrix containing a collection of one or more predicates defining one or more conditions for a given result of each authentication method; and

at least one decision vertex, wherein the at least one decision vertex represents one of a plurality of potential authentication results of a given authentication flow.

16. The system as in claim 15 , wherein the authentication result is satisfied if all predicates in the collection of one or more predicates are determined to be true.

17. The system as in claim 13 , wherein a given authentication flow is mapped to a scenario based on a user indication linking the authentication flow and the scenario.

18. The system as in claim 13 , wherein an authentication result indicates a relative strength of the authentication.

19. The system as in claim 13 , wherein the processor is further configured to:

determine a fraud suspicion level result based on implementation of the real-time multi-factor authentication policy, wherein the fraud suspicion level result indicates a relative level of suspicion of fraud.

20. The system as in claim 15 , wherein the processor is further configured to:

provide to the user, via the user interface, an authentication flow generator, the authentication flow generator comprising:

one or more authentication method selection boxes for selecting one or more of a plurality of authentication methods;

one or more condition selection boxes for selecting one or more of a plurality of conditions to be associated with a given authentication method;

one or more predicate selection boxes for selecting one or more of a plurality of predicates to be associated with a given condition; and

one or more decision selection boxes for selecting a potential authentication result to be associated with the given authentication method.

21. The system as in claim 13 , wherein one or more authentication flows is executed at least one of in parallel and in series.

22. The system as in claim 14 , further configured to:

monitor by the decision engine, a frequency with which a scenario is identified;

prioritize the scenario when the frequency meets a predefined threshold; and

modify at least one scenario parameter or at least one corresponding parameter value when the frequency does not meet the predefined threshold.

23. The system as in claim 14 , further configured to:

monitor by the decision engine, an authentication failure rate of the real-time multi-factor authentication policy associated with the relevant scenario; and

when the authentication failure rate meets a predefined threshold, modify, by the decision engine, at least one authentication flow mapped to the given scenario.

24. The system as in claim 19 , further comprising:

monitoring by the decision engine, a fraudulent detection rate of the real-time multi-factor authentication policy associated with the relevant scenario;

when the fraudulent detection rate does not meet a predefined threshold, modifying, by the decision engine, at least one authentication flow mapped to the given scenario; and

when the fraudulent detection rate meets a predefined threshold, prioritizing the relevant scenario.