Systems and methods for discovering suspect bot IP addresses and using validated bot IP address to ignore actions in a simulated phishing environment
View Patent ↗Methods, systems and apparatus are provided which allow a server of a security awareness system to associate IP addresses with events representing user interactions with simulated phishing campaigns. The server receives a plurality of events related to one or more simulated phishing campaigns for a plurality of accounts. The server determines if an IP address of the plurality of IP addresses is associated with one or more events for multiple accounts of the plurality of accounts. Based upon this determination, the server provides identification of the IP address as suspected as having the one or more events associated with it not originating from any user of the multiple accounts. The server receives an indication of whether the IP address is validated as having the one or more events originating from a bot instead of a user of one of the multiple accounts.
1. A method for validating internet protocol addresses as having events originating from a user associated with an account, the method comprising
(a) receiving, by a server, a plurality of events comprising clicks of users on one or more links of one or more campaigns for a plurality of accounts and a plurality of internet protocol (IP) addresses of devices of the users clicking on the one or more links;
(b) determining, by the server, that an IP address of the plurality of IP addresses is associated with one or more events for multiple accounts of the plurality of accounts;
(c) providing, by the server based on at least the determination, identification of the IP address as suspected as having the one or more events not originating from any user of the multiple accounts; and
(d) receiving, by the server, an indication of whether the IP address is validated as having the one or more events originating from a bot instead of any user of one of the multiple accounts.
2. The method of claim 1 , wherein (a) further comprises receiving, by the server, the plurality of events comprising automatic clicks on one or more links of one or more campaigns from at least one of a network device or a software, and IP addresses of the at least one of the network device or the software.
3. The method of claim 1 , wherein (b) further comprises performing, by the server, one or more queries on a database comprising the plurality of events to determine which accounts of the plurality of accounts have events associated with the same IP address.
4. The method of claim 1 , wherein (b) further comprises determining, by the server, that a first account of the plurality of accounts has at least a first event associated with a first IP address and that a second account of the plurality of accounts has at least a second event associated with the first IP address.
5. The method of claim 1 , wherein (b) further comprises determining, by the server, a number of occurrences of the IP address across multiple accounts and a number of unique accounts of the plurality of accounts for which the IP address is associated.
6. The method of claim 1 , wherein (c) further comprises providing, by the server, a user interface to display identification of the IP addresses suspected as having the one or more events originating from a user of one of the multiple accounts.
7. The method of claim 1 , wherein (c) further comprises providing, by the server, a number of occurrences of the IP address across multiple accounts and a number of unique accounts of the plurality of accounts for which the IP address is associated.
8. The method of claim 1 , wherein (d) further comprises receiving, by the server, via a user interface the indication that the IP address is from a bot instead of a user of one of the multiple accounts.
9. The method of claim 1 , further comprising receiving, by the server, specification of a rule identifying whether the IP address is validated as a bot or a user and automatically determining, by the server, whether the rule overlaps with any other rules.
10. A system for validating internet protocol addresses as having events originating from a user associated with an account, the system comprising
a server comprising one or more processors, coupled to non-transitory memory, and configured to:
receive a plurality of events comprising clicks of users on one or more links of one or more campaigns for a plurality of accounts and a plurality of internet protocol (IP) addresses of devices of the users clicking on the one or more links;
determine that an IP address of the plurality of IP addresses is associated with one or more events for multiple accounts of the plurality of accounts;
provide identification, based on at least the determination, of the IP addresses suspected as having the one or more events not originating from any user of the multiple accounts; and
receive an indication of whether the IP address is validated as having the one or more events originating from a bot instead of any user of one of the multiple accounts.
11. The system of claim 10 , wherein the plurality of events comprises automatic clicks on one or more links of one or more campaigns from at least one of a network device or a software, and IP addresses of the at least one of the network device or the software.
12. The system of claim 10 , wherein the server is further configured to perform one or more queries on a database comprising the plurality of events to determine which accounts of the plurality of accounts have events associated with the same IP address.
13. The system of claim 10 , wherein the server is further configured to determine that a first account of the plurality of accounts has at least a first event associated with a first IP address and that a second account of the plurality of accounts has at least a second event associated with the first IP address.
14. The system of claim 10 , wherein the server is further configured to determine a number of occurrences of the IP address across multiple accounts and a number of unique accounts of the plurality of accounts for which the IP address is associated.
15. The system of claim 10 , wherein the server is further configured to provide a user interface to display identification of the IP addresses suspected as having the one or more events originating from a user of one of the multiple accounts.
16. The system of claim 10 , wherein the server is further configured to provide a number of occurrences of the IP address across multiple accounts and a number of unique accounts of the plurality of user accounts for which the IP address is associated.
17. The system of claim 10 , wherein the server is further configured to receive via a user interface the indication that the IP address is from the user of one of the multiple accounts.
18. The system of claim 10 , wherein the server is further configured to establish a rule identifying whether the IP address is validated as a bot or a user and automatically determine whether the rule overlaps with any other rules.