# US 2020/0351270 A1 · Smart whitelisting for dns security

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0351270 A1
- Document ID: US20200351270A1
- Status: Published application
- Kind: A1
- Application number: 16/399,252
- Filed: 2019-04-30
- Published: 2020-11-05
- Earliest claimed: 2019-04-30
- Assignees: Infoblox Inc.
- Applicants: Infoblox Inc.
- Inventors: Renee Carol Burton
- Web page: https://patentgrep.com/patent/US20200351270A1

## CPC

- H04L 63/101: {Access control lists [ACL]}
- H04L 47/70: Admission control; Resource allocation
- H04L 61/4511: using domain name system [DNS]
- H04L 63/0227: {Filtering policies (mail message filtering H04L51/212)}
- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- H04L 63/1441: {Countermeasures against malicious traffic (countermeasures against attacks on cryptographic mechanisms H04L9/002)}
- H04L 63/145: {the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms}
- H04L 63/1466: {Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks}
- H04L 63/1483: {service impersonation, e.g. phishing, pharming or web spoofing (detection of rogue wireless access points H04W12/12)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Techniques for smart whitelisting for Domain Name System (DNS) security are provided. In some embodiments, a system/process/computer program product for smart whitelisting for DNS security in accordance with some embodiments includes receiving a set of network related event data, wherein the set of network related event data includes Domain Name System (DNS) related event data; receiving a set of network related threat data, wherein the set of network related threat data includes DNS related threat data; and generating a whitelist using the set of network related event data and the set of network related threat data, wherein the whitelist includes a subset of network domains included in the DNS related event data based on a data driven model of the DNS related event data and the DNS related threat data.

## Claims

### Claim 1

A system, comprising:
a processor configured to:
receive a set of network related event data, wherein the set of network related event data includes Domain Name System (DNS) related event data;
receive a set of network related threat data, wherein the set of network related threat data includes DNS related threat data; and
generate a whitelist using the set of network related event data and the set of network related threat data, wherein the whitelist includes a subset of network domains included in the DNS related event data based on a data driven model of the DNS related event data and the DNS related threat data; and
a memory coupled to the processor and configured to provide the processor with instructions.

### Claim 2 (depends on 1)

The system recited in claim 1, wherein the DNS related event data includes a set of is popular network domains.

### Claim 3 (depends on 1)

The system recited in claim 1, wherein the DNS related threat data includes a DNS threat feed.

### Claim 4 (depends on 1)

The system recited in claim 1, wherein the DNS related threat data includes a DNS threat feed that is associated with a first enterprise network.

### Claim 5 (depends on 1)

The system recited in claim 1, wherein the DNS related threat data includes a DNS threat feed that is automatically filtered to determine a popularity of network domains associated with malware.

### Claim 6 (depends on 1)

The system recited in claim 1, wherein the subset of network domains included in the whitelist are selected using a classifier.

### Claim 7 (depends on 1)

The system recited in claim 1, wherein the subset of network domains included in the whitelist are selected using a statistical classifier.

### Claim 8 (depends on 1)

The system recited in claim 1, wherein the processor is further configured to:
filter the DNS related event data to generate a smart whitelist, wherein the DNS related event data is automatically filtered using a classifier to exclude one or more network domains associated with malware; and
output the smart whitelist to a network device for filtering DNS requests using the smart whitelist.

### Claim 9 (depends on 1)

The system recited in claim 1, wherein the processor is further configured to:
filter the DNS related event data to generate a smart whitelist, wherein the DNS related event data is automatically filtered using a classifier to exclude one or more network domains associated with malware; and
periodically update the smart whitelist based on another set of network related event data and another set of network related threat data, wherein the smart whitelist is automatically and dynamically adjusted to changes in a production data environment associated with a first enterprise network.

### Claim 10 (depends on 1)

The system recited in claim 1, wherein the processor is further configured to:
identify a network domain for further evaluation to determine whether the network is domain is properly included on a blacklist.

### Claim 11

A method, comprising:
receiving a set of network related event data, wherein the set of network related event data includes Domain Name System (DNS) related event data;
receiving a set of network related threat data, wherein the set of network related threat data includes DNS related threat data; and
generating a whitelist using the set of network related event data and the set of network related threat data, wherein the whitelist includes a subset of network domains included in the DNS related event data based on a data driven model of the DNS related event data and the DNS related threat data.

### Claim 12 (depends on 11)

The method of claim 11, wherein the DNS related event data includes a set of popular network domains.

### Claim 13 (depends on 11)

The method of claim 11, wherein the DNS related threat data includes a DNS threat feed.

### Claim 14 (depends on 11)

The method of claim 11, wherein the DNS related threat data includes a DNS threat feed that is associated with a first enterprise network.

### Claim 15 (depends on 11)

The method of claim 11, wherein the DNS related threat data includes a DNS threat feed that is automatically filtered to determine a popularity of network domains associated with malware.

### Claim 16

A computer program product, the computer program product being embodied in a tangible computer readable storage medium and comprising computer instructions for:
receiving a set of network related event data, wherein the set of network related event data includes Domain Name System (DNS) related event data;
receiving a set of network related threat data, wherein the set of network related threat data includes DNS related threat data; and
generating a whitelist using the set of network related event data and the set of network related threat data, wherein the whitelist includes a subset of network domains included in the DNS related event data based on a data driven model of the DNS related event data and the DNS related threat data.

### Claim 17 (depends on 16)

The computer program product recited in claim 16, wherein the DNS related event data is includes a set of popular network domains.

### Claim 18 (depends on 16)

The computer program product recited in claim 16, wherein the DNS related threat data includes a DNS threat feed.

### Claim 19 (depends on 16)

The computer program product recited in claim 16, wherein the DNS related threat data includes a DNS threat feed that is associated with a first enterprise network.

### Claim 20 (depends on 16)

The computer program product recited in claim 16, wherein the DNS related threat data includes a DNS threat feed that is automatically filtered to determine a popularity of network domains associated with malware.
