Method and system for detecting two-factor authentication
Embodiments disclosed herein generally related to a system and method for assessing a fraud risk. In one embodiment, a method for assessing a fraud risk is disclosed herein. A web browser extension executing on the computing device identifies an account associated with the computing device. The web browser extension detects that the computing device navigated to a web page hosted by a third party server. The web browser extension determines that the third party server prompted the computing device to opt into two-factor authentication functionality. The web browser extension determines that the computing device did not opt into the two-factor authentication functionality. The web browser extension prompts, via an application programming interface (API), an organization computing system to update a fraud metric associated with the account.
1. A method, comprising:
detecting, by a software module, that a user accessed a third party application executing on a client device of the user, the third party application associated with a third party server;
determining, by the software module, a type of application associated with the third party application;
monitoring, by the software module, the third party application to determine whether the user was prompted with a request for a second factor in a multi-factor authentication protocol;
determining, by the software module and based on the monitoring, that the user was not prompted with the request; and
based on the determining, updating, by the software module, a fraud metric associated an account of the user based on the type of application associated with the third party application.
2. The method of claim 1 , wherein the type of application associated with the third party application corresponds to a first set of applications associated with a first security level.
3. The method of claim 2 , further comprising:
detecting, by the software module, that the user accessed a second third party application associated with a second third party server;
determining, by the software module, a second type of application associated with the second third party application, the second type of application corresponding to a second set of applications associated with a second security level;
monitoring, by the software module, the second third party application to determine whether the user was prompted with a second request for another second factor in the multi-factor authentication protocol;
determining, by the software module and based on the monitoring, that the user was not prompted with the second request; and
based on the determining, further updating, by the software module, the fraud metric associated the account of the user based on the second type of application associated with the second third party application.
4. The method of claim 3 , wherein the second type of application causes the fraud metric to be updated to a lesser degree than the type of application.
5. The method of claim 1 , wherein monitoring, by the software module, the third party application to determine whether the user was prompted with the request for the second factor in the multi-factor authentication protocol comprises:
analyzing an application script for one or more fields associated with the multi-factor authentication protocol.
6. The method of claim 1 , wherein determining, by the software module, the type of application associated with the third party application comprises:
analyzing an application script to determine the type of application associated with the third party application.
7. The method of claim 1 , wherein updating, by the software module, the fraud metric associated the account of the user based on the type of application associated with the third party application comprises:
increasing a sensitivity of a fraud algorithm.
8. A non-transitory computer readable medium comprising one or more sequences of instructions, which, when executed by one or more processors, causes a computing system to perform operations, comprising:
detecting, by a browser extension executing in a web browser on a client device, that a user navigated to a webpage hosted by a third party server;
determining, by the browser extension, a type of website associated with the webpage;
monitoring, by the browser extension, the webpage to determine whether the user was prompted with a request for a second factor in a multi-factor authentication protocol;
determining, by the browser extension and based on the monitoring, that the user was not prompted with the request; and
based on the determining, updating, by the browser extension, a fraud metric associated an account of the user based on the type of website associated with the webpage.
9. The non-transitory computer readable medium of claim 8 , wherein the type of website associated with the webpage corresponds to a first set of webpages associated with a first security level.
10. The non-transitory computer readable medium of claim 9 , further comprising:
detecting, by the browser extension, that the user navigated to a second webpage hosted by a second third party server;
determining, by the browser extension, a second type of website associated with the second webpage, the second type of website corresponding to a second set of webpages associated with a second security level;
monitoring, by the browser extension, the second webpage to determine whether the user was prompted with a second request for another second factor in the multi-factor authentication protocol;
determining, by the browser extension and based on the monitoring, that the user was not prompted with the second request; and
based on the determining, further updating, by the browser extension, the fraud metric associated the account of the user based on the second type of website associated with the second webpage.
11. The non-transitory computer readable medium of claim 10 , wherein the second type of website causes the fraud metric to be updated to a lesser degree than the type of website.
12. The non-transitory computer readable medium of claim 8 , wherein monitoring, by the browser extension, the webpage to determine whether the user was prompted with the request for the second factor in the multi-factor authentication protocol comprises:
analyzing a webpage script for one or more fields associated with the multi-factor authentication protocol.
13. The non-transitory computer readable medium of claim 8 , wherein determining, by the browser extension, the type of website associated with the webpage comprises:
analyzing a webpage script to determine the type of website associated with the webpage.
14. The non-transitory computer readable medium of claim 8 , wherein updating, by the browser extension, the fraud metric associated the account of the user based on the type of web site associated with the webpage comprises:
increasing a sensitivity of a fraud algorithm.
15. A system, comprising:
a processor; and
a memory having programming instructions stored thereon, which, when executed by the processor, causes the system to perform operations comprising:
detecting, by a software module, launch of a third party application on a client device of a user, the third party application associated with a third party server;
determining, by the software module, a type of application associated with the third party application;
monitoring, by the software module, the third party application to determine whether the third party application presented a prompt comprising a request for a second factor in a multi-factor authentication protocol;
determining, by the software module and based on the monitoring, that the third party application did not present the prompt; and
based on the determining, updating, by the software module, a fraud metric associated an account of the user based on the type of application associated with the third party application.
16. The system of claim 15 , wherein the type of application associated with the third party application corresponds to a first set of applications associated with a first security level.
17. The system of claim 16 , further comprising:
detecting, by the software module, launch of a second third party application associated with a second third party server;
determining, by the software module, a second type of application associated with the second third party application, the second type of application corresponding to a second set of applications associated with a second security level;
monitoring, by the software module, the second third party application to determine whether the second third party application presented a second prompt comprising a second request for another second factor in the multi-factor authentication protocol;
determining, by the software module and based on the monitoring, that the second third party application did not present the second prompt; and
based on the determining, further updating, by the software module, the fraud metric associated the account of the user based on the second type of application associated with the second third party application.
18. The system of claim 17 , wherein the second type of application causes the fraud metric to be updated to a lesser degree than the type of application.
19. The system of claim 15 , wherein monitoring, by the software module, the third party application to determine whether the third party application presented the prompt comprising the request for the second factor in the multi-factor authentication protocol comprises:
analyzing an application script for one or more fields associated with the multi-factor authentication protocol.
20. The system of claim 15 , wherein determining, by the software module, the type of application associated with the third party application comprises:
analyzing an application script to determine the type of application associated with the third party application.