Cloud-based anomalous traffic detection and protection in a remote network via DNS properties

1. A method for anomaly detection in a local network, the method comprising:

maintaining, by a central platform, a plurality of DNS server IP addresses, wherein the central platform is remotely located from the local network;

receiving, by the central platform, configuration data for the local network;

receiving, by the central platform, a DNS lookup request from a device on the local network;

determining, by the central platform, based at least in part on a source IP address of the DNS lookup request and an IP address of a DNS server receiving the DNS lookup request, the local network associated with the DNS lookup request;

determining, by the central platform, current flow statistics for the local network;

determining, by a machine learning engine of the central platform, an anomaly in the local network based, at least in part, on comparing the current flow statistics with expected flow statistics; and

determining, by the machine learning engine, a device on the local network causing the anomaly based, at least in part, on at least one member of the group consisting of the configuration data for the local network, a port number in the source IP address, and a DNS sequence number;

assigning, by the central platform, a pair of DNS server IP addresses to the local network, wherein the pair of DNS server IP addresses is comprised of two DNS server IP addresses of the plurality of DNS server IP addresses, and wherein the pair of DNS server IP addresses are selected to be unique within pairings of the plurality of DNS server IP addresses; and

identifying, by the central platform, a device within the local network based, at least in part, on the configuration data and the pair of DNS server IP addresses assigned to the local network.

2. The method of claim 1 , further comprising:

providing, by the central platform, a token to an agent on the local network;

receiving, by the central platform, a DNS lookup request from the agent, the DNS lookup request including information from the token; and

determining, by the central platform, based at least in part on the information from the token and an IP address of a DNS server receiving the DNS lookup request, that the local network is correctly assigned to the pair of DNS server IP addresses.

3. The method of claim 1 , further comprising:

receiving, by a first DNS server of the central platform having a first IP address of the pair of DNS server IP addresses, a first DNS lookup request; and

in response to determining, based at least in part on a source IP address associated with the first DNS lookup request, that the source IP address is not associated with the first DNS server, dropping the first DNS lookup request and creating data indicating that the source IP address may be associated with an IP address change of a router on the local network.

4. The method of claim 3 , further comprising:

receiving, by a second DNS server of the central platform having a second IP address of the pair of DNS server IP addresses, a second DNS lookup request; and

in response to determining that the source IP address is not associated with the second DNS server and that data exists indicating that the source IP address may be associated with an IP address change of the router on the local network, reassigning the source IP address to the pair of DNS server IP addresses.

5. The method of claim 1 , wherein an IP address assigned to the local network is dynamic, thereby preventing identifying the device within the local network based on the assigned IP address as the assigned IP address changes over time.

6. A non-transitory computer readable storage medium comprising a set of instructions executable by a computer, the non-transitory computer readable storage medium comprising:

instructions for maintaining, by a central platform, a plurality of DNS server IP addresses, wherein the central platform is remotely located from the local network;

instructions for receiving, by the central platform, configuration data for the local network;

instructions for assigning, by the central platform, a pair of DNS server IP addresses to the local network, wherein the pair of DNS server IP addresses is comprised of two DNS server IP addresses of the plurality of DNS server IP addresses, and wherein the pair of DNS server IP addresses are selected to be unique within pairings of the plurality of DNS server IP addresses;

instructions for receiving, by the central platform, a DNS lookup request from a device on the local network;

instructions for determining, by the central platform, based at least in part on a source IP address of the DNS lookup request and an IP address of a DNS server receiving the DNS lookup request, the local network associated with the DNS lookup request;

instructions for determining, by the central platform, current flow statistics for the local network; and

instructions for determining, by a machine learning engine of the central platform, an anomaly in the local network based, at least in part, on comparing the current flow statistics with expected flow statistics;

instructions for determining, by the machine learning engine, a device on the local network causing the anomaly based, at least in part, on at least one member of the group consisting of the configuration data for the local network, a port number in the source IP address, and a DNS sequence number; and

instructions for identifying, by the central platform, a device within the local network based, at least in part, on the configuration data and the pair of DNS server IP addresses assigned to the local network,

wherein an IP address assigned to the local network is dynamic, thereby preventing identifying the device within the local network based on the assigned IP address as the assigned IP address changes over time.

7. The non-transitory computer readable storage medium of claim 6 , further comprising:

instructions for providing, by the central platform, a token to an agent on the local network;

instructions for receiving, by the central platform, a DNS lookup request from the agent, the DNS lookup request including information from the token; and

instructions for determining, by the central platform, based at least in part on the information from the token and an IP address of a DNS server receiving the DNS lookup request, that the local network is correctly assigned to the pair of DNS server IP addresses.

8. The non-transitory computer readable storage medium of claim 6 , further comprising:

instructions for receiving, by a first DNS server of the central platform having a first IP address of the pair of DNS server IP addresses, a first DNS lookup request; and

instructions for, in response to determining, based at least in part on a source IP address associated with the first DNS lookup request, that the source IP address is not associated with the first DNS server, dropping the first DNS lookup request and creating data indicating that the source IP address may be associated with an IP address change of a router on the local network.

9. The non-transitory computer readable storage medium of claim 8 , further comprising:

instructions for receiving, by a second DNS server of the central platform having a second IP address of the pair of DNS server IP addresses, a second DNS lookup request; and

instructions for, in response to determining that the source IP address is not associated with the second DNS server and that data exists indicating that the source IP address may be associated with an IP address change of the router on the local network, reassigning the source IP address to the pair of DNS server IP addresses.