Systems and methods for aida based second chance
Methods and systems are described in which a system provides a user interface to confirm whether to review or take an action associated with an untrusted email. A driver on a device monitors the startup of any processes. Responsive to monitoring, the driver detects an application process that was created that indicates than an application was launched, and notifies a user console about the creation of the application process. The user console determines if the application process is of significance, if so, it injects a monitor library into the process. Once injected into the process, the monitor library detects if the application process receives an action of a user to access a domain that is not identified as trusted. The monitor library notifies the user console of the user's URL-access request.
1. A method for using information from intercepted actions to configure a simulated phishing campaign, the method comprising:
(a) receiving, by a campaign controller, information identifying one or more actions of a plurality of users to access, via one or more applications, one or more domains not identified as trusted, the one or more actions intercepted prior to accessing the one or more domains and the plurality of users prompted via a user interface to either review or take the one or more actions, the information identifying at least whether each user of the plurality of users reviewed the one or more actions and provided input via the user interface to revert back to a point in an application of the one or more applications at which the user requested the one or more actions;
(b) storing, by the campaign controller, the information to a database; and
(c) selecting, by the campaign controller based on applying artificial intelligence to at least the information and independent of any user determining a model or a template based on at least the information, one of the model from a plurality of models or the template from a plurality of templates to use for a simulated phishing campaign.
2. The method of claim 1 , wherein the information comprises one or more of the following: a type of action, a type of exploit, an identifier of an application of the one or more applications, a domain of the one or more domains and whether a user chose to review the action or take the action.
3. The method of claim 1 , wherein (a) further comprises receiving the information comprising a plurality of inputs from a plurality of users, each of the plurality of inputs identifying whether to take or review the one or more actions to access the one or more domains not identified as trusted.
4. The method of claim 3 , further comprising receiving the plurality of inputs from a plurality of user interfaces, each of the plurality of user interfaces displayed while the one or more applications are paused, the plurality of user interfaces configured to receive the plurality of inputs to confirm whether to take or review the one or more actions.
5. The method of claim 1 , wherein (a) further comprises receiving the information responsive to one or more drivers on one or more devices detecting that the one or more applications received one or more actions of the one or more users to access the one or more domains not identified as trusted.
6. The method of claim 1 , wherein (a) further-comprises receiving the information responsive to one or more drivers on one or more devices intercepting the one or more actions of the one or more users via the one or more applications to access the one or more domains not identified as trusted.
7. The method of claim 1 , wherein (b) further comprises storing the information in association with a plurality of attributes of one or more users.
8. The method of claim 1 , wherein (b) further comprises storing the information in association with a plurality of attributes of one or more companies of one or more users.
9. The method of claim 1 , wherein (b) further comprises storing the information in association with results of execution of a plurality of simulated phishing campaigns.
10. The method of claim 1 , wherein (c) further comprises correlating, using the information, between selection parameters of one or more simulated phishing campaigns and the one or more actions.
11. The method of claim 10 , further comprising determining one of the model or the template based on the correlation.
12. The method of claim 1 , wherein (c) further comprises training, by a model trainer, the model, using at least a portion of the information.
13. The method of claim 1 , wherein (c) further comprises selecting, by the campaign controller, the template from a plurality of templates based on at least a portion of the information.
14. The method of claim 1 , wherein (c) further comprises selecting, by the campaign controller, content for the template based on at least a portion of the information.
15. The method of claim 1 , wherein (c) further comprises selecting, by the campaign controller, parameters for a simulated phishing campaign based on at least a portion of the information.
16. A system for using information from intercepted actions to configure a simulated phishing campaign, the system comprising:
a campaign controller, executable on one or more processors, coupled to memory and configured to receive information identifying one or more actions of a plurality of users to access, via one or more applications, one or more domains not identified as trusted, wherein the one or more actions are intercepted prior to accessing the one or more domains and the plurality of users are prompted via a user interface to either review or take the one or more actions, the information identifying at least whether each user of the plurality of users reviewed the one or more actions and provided input via the user interface to revert back to a point in an application of the one or more applications at which the user requested the one or more actions;
wherein the campaign controller is configured to:
store the information to a database; and
select, based on applying artificial intelligence to at least the information and independent of any user determining a model or a template based on at least the information, one of the model from a plurality of models or the template from a plurality of templates to use for a simulated phishing campaign.
17. The system of claim 16 , wherein the information comprises one or more of the following: a type of action, a type of exploit, an identifier of an application of the one or more applications, a domain of the one or more domains and whether a user chose to review the action or take the action.
18. The system of claim 16 , wherein the information comprises a plurality of inputs from a plurality of users, each of the plurality of inputs identifying whether to take or review the one or more actions to access the one or more domains not identified as trusted.
19. The system of claim 18 , wherein the campaign controller is further configured to receive the plurality of inputs from a plurality of user interfaces, each of the plurality of user interfaces displayed while the one or more applications are paused, the plurality of user interfaces configured to receive the plurality of inputs to confirm whether to take or review the one or more actions.
20. The system of claim 16 , wherein the campaign controller is further configured to receive the information responsive to one or more drivers on one or more devices detecting that the one or more applications received one or more actions of the one or more users to access the one or more domains not identified as trusted.
21. The system of claim 16 , wherein the campaign controller is further configured to receive the information responsive to one or more drivers on one or more devices intercepting the one or more actions of the one or more users via the one or more applications to access the one or more domains not identified as trusted.
22. The system of claim 16 , wherein the campaign controller is further configured to store the information in association with a plurality of attributes of one or more users.
23. The system of claim 16 , wherein the campaign controller is further configured to store the information in association with a plurality of attributes of one or more companies of one or more users.
24. The system of claim 16 , wherein the campaign controller is further configured to store the information in association with results of execution of a plurality of simulated phishing campaigns.
25. The system of claim 16 , wherein the campaign controller is further configured to receive correlating, using the information, between selection parameters of one or more simulated phishing campaigns and the one or more actions.
26. The system of claim 25 , wherein the campaign controller is further configured to determine one of the model or the template based on the correlation.
27. The system of claim 16 , further comprising a model trainer configured to train the model using at least a portion of the information.
28. The system of claim 16 , wherein the campaign controller is further configured to select the template from a plurality of templates based on at least a portion of the information.
29. The system of claim 16 , wherein the campaign controller is further configured to select content for the template based on at least a portion of the information.
30. The system of claim 16 , wherein the campaign controller is further configured to select parameters for a simulated phishing campaign based on at least a portion of the information.