Systems and methods for IP-based intrusion detection

• US 10,505,991 B1
• Filed: 09/05/2018
• Issued: 12/10/2019
• Est. Priority Date: 03/13/2015
• Status: Active Grant

• Current Assignee: Snap, Inc.
• Original Assignee: Snap, Inc.
• Inventors: Yang, Jinlin
• Primary Examiner(s): Brown, Christopher J
• Application Number:
  US16/122,797
• Time in Patent Office: 461 Days
• Field of Search: 726 4
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/105 Multiple levels of security
• CPC Class Codes: H04L 63/108 when the policy decisions are valid for a limited amount of time
• CPC Class Codes: H04L 63/1416 Event detection, e.g. attack signature detection
• CPC Class Codes: H04L 63/1425 Traffic logging, e.g. anomaly detection
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 63/308 retaining data, e.g. retaining successful, unsuccessful communication attempts, internet access, or e-mail, internet telephony, intercept related information or call content

Abstract

Systems and methods for account security are provided. In one example embodiment, a first login request including a username and a password is analyzed to identify a first internet protocol (IP) address and a first request time associated with the first login request. A login history comprising login request data for the server computer is analyzed to identify a plurality of usernames, wherein each username of the plurality of usernames is associated with a corresponding login request from the first IP address within a threshold time period of the first request time. In response to determining a login success ratio is below a threshold login success ratio and a number of unique usernames in the analyzed data is above the unique username threshold, the system automatically performs a security action.

Claims

1. A method comprising:

identifying, using one or more processors of a server computer analyzing a login history comprising login request data for the server computer, a plurality of usernames, wherein each username of the plurality of usernames is associated with a corresponding login request from a first internet protocol (IP) address within a threshold time period of a first request time of a first login request, and wherein the number of usernames associated with the total number of login requests is determined by comparing each username with each other username to determine a difference value for each username pair, wherein the difference value for each username pair comprises a sum of each character change, character addition, and character subtraction required to transform a first username of each username pair into a second username of each username pair, and for each username pair identified as similar usernames having a difference value less than a threshold difference value, counting the similar usernames as a single username for the number of usernames as compared to a username threshold;

determining that a total number of login requests from the first IP address within the threshold time period is above a credential security threshold;

determining that a number of usernames associated with the total number of login requests is above the username threshold;

determining that a login success ratio is below a threshold login success ratio after determining that the total number of login requests from the first IP address is above the credential security threshold; and

in response to determining the login success ratio is below the threshold login success ratio and determining that the number of unique usernames is above the username threshold, automatically performing a security action using the server computer.

2. The method of claim 1 wherein the security action comprises communicating a security notification to an e-mail address associated with a username.

3. The method of claim 2 wherein the security action further comprises communicating the security notification to a corresponding e-mail address for each of the plurality of usernames.

4. The method of claim 1 wherein the security action comprises temporarily blocking accesses to an account associated with a username and automatically initiating a password reset process for the account.

5. The method of claim 4 wherein the security action further comprises temporarily blocking access to a plurality of accounts associated with each of the plurality of usernames and initiating the password reset process for each of the plurality of accounts.

6. The method of claim 1 wherein the security action further comprises:

identifying a plurality of accounts, wherein each account of the plurality of accounts is associated with a successful login from the IP address during the threshold time period.

7. The method of claim 6 wherein the security action further comprises:

identifying, for each account of the plurality of accounts, an associated set of user actions taken during the threshold time period; and

initiating a custom security action for each account based on the associated set of user actions for each account.

8. The method of claim 7 wherein the security action further comprises:

determining a location associated with the IP address; and

identifying, for each account of the plurality of accounts, a difference between the IP address and a registration IP address associated with a creation of each account;

wherein the custom security action for each account is further based on the difference between the IP address and the registration IP address associated with the creation of each account.

9. The method of claim 8 wherein the security action further comprises:

determining a total number of locations associated with registration of the plurality of usernames; and

initiating a group security action for the plurality of usernames when the total number of locations is above a location threshold value.

10. The method of claim 6 wherein the security action further comprises:

identifying, for each successful login, a user agent value associated with a requesting client device;

identifying, for each account of the plurality of accounts from the login history, a user agent value history, associated with historical requesting client devices; and

comparing, for each account, the user agent value and the user agent value history;

wherein the custom security action for each account is further based on the comparing of the user agent value and the user agent value history.

11. The method of claim 1 wherein counting the similar usernames as a single username comprises, for each username pair identified as similar usernames, subtracting one from the number of usernames prior to comparing the number of usernames to the username threshold.

12. A device comprising:

a memory configured to store a login history comprising login request data for a server computer; and

one or more processors coupled to the memory and configured to;

identify, using the login request data for the server computer, a plurality of usernames, wherein each username of the plurality of usernames is associated with a corresponding login request from a first internet protocol (IP) address within a threshold time period of a first request time of a first login request, and wherein the number of usernames associated with the total number of login requests is determined by comparing each username with each other username to determine a difference value for each username pair, wherein the difference value for each username pair comprises a sum of each character change, character addition, and character subtraction required to transform a first username of each username pair into a second username of each username pair, and for each username pair identified as similar usernames having a difference value less than a threshold difference value, counting the similar usernames as a single username for the number of usernames as compared to a username threshold;

determine that a total number of login requests from the first IP address within the threshold time period is above a credential security threshold;

determine that a number of usernames associated with the total number of login requests is above the username threshold;

determine that a login success ratio is below a threshold login success ratio after determining that the total number of login requests from the first IP address is above the credential security threshold; and

automatically performing a security action in response to a determination that both the login success ratio is below the threshold login success ratio and the number of unique usernames is above the username threshold.

13. The device of claim 12 wherein the security action comprises initiating communication of a security notification to a corresponding e-mail address for each of the plurality of usernames.

14. The device of claim 12 wherein the security action comprises temporarily blocking accesses to an account associated with a username and automatically initiating a password reset process for the account;

and

wherein the security action further comprises temporarily blocking access to a plurality of accounts associated with each of the plurality of usernames and initiating the password reset process for each of the plurality of accounts.

15. A non-transitory computer readable medium comprising instructions that, when executed by one or more processors of a server computer, cause the server computer to perform operations comprising:

identifying, using the login request data for the server computer, a plurality of usernames, wherein each username of the plurality of usernames is associated with a corresponding login request from a first internet protocol (IP) address within a threshold time period of a first request time of a first login request, and wherein the number of usernames associated with the total number of login requests is determined by comparing each username with each other username to determine a difference value for each username pair, wherein the difference value for each username pair comprises a sum of each character change, character addition, and character subtraction required to transform a first username of each username pair into a second username of each username pair, and for each username pair identified as similar usernames having a difference value less than a threshold difference value, counting the similar usernames as a single username for the number of usernames as compared to the username threshold;

determining that a total number of login requests from the first IP address within the threshold time period is above a credential security threshold;

determining that a number of usernames associated with the total number of login requests is above a username threshold;

determining that a login success ratio is below a threshold login success ratio after determining that the total number of login requests from the first IP address is above the credential security threshold; and

automatically performing a security action using the server computer in response to the determining that the login success ratio is below the threshold login success ratio and the determining that the number of unique usernames is above the unique username threshold.

16. The non-transitory computer readable medium of claim 15, wherein the security action further comprises identifying a plurality of accounts, wherein each account of the plurality of accounts is associated with a successful login from the IP address during the threshold time period:

identifying, for each account of the plurality of accounts, an associated set of user actions taken during the threshold time period; and

initiating a custom security action for each account based on the associated set of user actions for each account.

17. The non-transitory computer readable medium of claim 16, wherein the security action further comprises:

determining a location associated with the IP address;

identifying, for each account of the plurality of accounts, a difference between the IP address and a registration IP address associated with a creation of each account;

wherein the custom security action for each account is further based on the difference between the IP address and the registration IP address associated with the creation of each account.

18. The non-transitory computer readable medium of claim 15, wherein the security action further comprises:

determining a total number of locations associated with registration of the plurality of usernames; and

initiating a group security action for the plurality of usernames when the total number of locations is above a location threshold value.

19. The non-transitory computer readable medium of claim 15, wherein the security action further comprises:

identifying a plurality of accounts, wherein each account of the plurality of accounts is associated with a successful login from the IP address during the threshold time period;

identifying, for each successful login, a user agent value associated with a requesting client device;

identifying, for each account of the plurality of accounts from the login history, a user agent value history, associated with historical requesting client devices; and

comparing, for each account, the user agent value and the user agent value history;

wherein the custom security action for each account is further based on the comparing of the user agent value and the user agent value history.

20. The non-transitory computer readable medium of claim 15, wherein counting the similar usernames as a single username comprises, for each username pair identified as similar usernames, subtracting one from the number of usernames prior to comparing the number of usernames to the username threshold.