# US 2024/0179158 A1 · Self learning firewall policy enforcer

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

- Number: US 2024/0179158 A1
- Document ID: US20240179158A1
- Status: Published application
- Kind: A1
- Application number: 18/472,092
- Filed: 2023-09-21
- Published: 2024-05-30
- Earliest claimed: 2022-11-30
- Assignees: Juniper Networks, Inc.
- Applicants: Juniper Networks, Inc.
- Inventors: Raja Kommula; Rahul Gupta; Ganesh Byagoti Matad Sunkada; Tarun Banka; Thayumanavan Sridhar; Raj Yavatkar
- Web page: https://patentgrep.com/patent/US20240179158A1

## CPC

- H04L 63/0263: {Rule management}
- G06N 5/01: Dynamic search techniques; Heuristics; Dynamic trees; Branch-and-bound
- G06N 5/022: Knowledge engineering; Knowledge acquisition
- G06N 7/01: Probabilistic graphical models, e.g. probabilistic networks
- G06N 20/00: Machine learning
- G06N 20/10: using kernel methods, e.g. support vector machines [SVM]
- G06N 20/20: Ensemble learning
- H04L 41/0894: Policy-based network configuration management
- H04L 41/14: Network analysis or design
- H04L 41/16: using machine learning or artificial intelligence
- H04L 41/5009: Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
- H04L 43/026: using flow identification
- H04L 43/0811: by checking connectivity
- H04L 43/0888: Throughput
- H04L 63/0227: {Filtering policies (mail message filtering H04L51/212)}
- H04L 63/0236: {Filtering by address, protocol, port number or service, e.g. IP-address or URL}
- H04L 63/0245: {Filtering by information in the payload}
- H04L 63/1416: {Event detection, e.g. attack signature detection}
- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- H04L 63/1458: {Denial of Service}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS

## Abstract

An example network system includes processing circuitry and one or more memories coupled to the processing circuitry. The one or more memories are configured to store instructions which, when executed by the processing circuitry, cause the network system to obtain first traffic session metrics data and execute a machine learning model to determine a traffic prediction based on the first traffic session metrics data. The instructions cause the network system to obtain second traffic session metrics data and determine an anomaly in traffic based on a comparison of the traffic prediction and the second traffic session metrics data. The instructions cause the network system to, based on the determination of the anomaly, generate an indication of the anomaly.

## Claims

### Claim 1

A network system comprising:
processing circuitry; and
one or more memories coupled to the processing circuitry and configured to store instructions which, when executed by the processing circuitry, cause the network system to:
obtain first traffic session metrics data;
execute a machine learning model to determine a traffic prediction based on the first traffic session metrics data;
obtain second traffic session metrics data;
determine an anomaly in traffic based on a comparison of the traffic prediction and the second traffic session metrics data; and
based on the determination of the anomaly, generate an indication of the anomaly.

### Claim 2 (depends on 1)

The network system of claim 1, wherein the instructions further cause the network system to send the indication of the anomaly to a controller of a distributed firewall.

### Claim 3 (depends on 1)

The network system of claim 1, wherein the anomaly is indicative of a DNS attack or a TCP flood attack.

### Claim 4 (depends on 3)

The network system of claim 3, wherein the second traffic sessions metrics data comprises a number of domain name service requests by a virtual network endpoint of a host device within a period of time, wherein the traffic prediction comprises an expected number of expected domain name service requests during the period of time, and wherein as part of determining the anomaly, the instructions cause the processing circuitry to determine the number of domain name service requests by the virtual network endpoint of the host device within the period of time is greater than the number of expected domain name service requests.

### Claim 5 (depends on 1)

The network system of claim 1, wherein the machine learning model comprises an unsupervised random cut forest machine learning model.

### Claim 6 (depends on 1)

The network system of claim 1, wherein the first traffic session metrics data and the second traffic session metrics data are indicative of service mesh traffic.

### Claim 7 (depends on 1)

The network system of claim 1, wherein the first traffic session metrics data and the second traffic session metrics data are associated with one or more network interface cards (NICs).

### Claim 8 (depends on 7)

The network system of claim 7, wherein the one or more NICs implement a distributed firewall.

### Claim 9 (depends on 1)

The network system of claim 1, wherein the instructions further cause the network system to generate or select a firewall policy based on the indication of the anomaly.

### Claim 10 (depends on 9)

The network system of claim 9, wherein the instructions further cause the network system to:
identify a NIC associated with a host device; and
send the firewall policy or an identification of the firewall policy to the NIC.

### Claim 11

A network system comprising:
processing circuitry; and
one or more memories coupled to the processing circuitry and configured to store instructions which, when executed by the processing circuitry, cause the network system to:
monitor service mesh traffic leaving each network interface card (NIC) of a plurality of NICs, each of the NICs comprising NIC processing circuitry;
monitor service mesh traffic entering each NIC;
determine traffic session metrics data based on the mesh traffic leaving each NIC and the mesh traffic entering each NIC;
receive, from a machine learning model and based on the traffic session metrics data, an indication of an anomaly in traffic;
determine a firewall policy based on the indication of the anomaly; and
send an indication of a firewall policy to at least one of the one or more NICs.

### Claim 12 (depends on 11)

The network system of claim 11, wherein the indication of the firewall policy comprises at least one of the firewall policy or an identification of the firewall policy.

### Claim 13 (depends on 11)

The network system of claim 11, wherein the instructions further cause the network system to store the traffic session metrics data in a time series database.

### Claim 14 (depends on 11)

The network system of claim 11, wherein the traffic sessions metrics data comprises a number of domain name service requests by a virtual network endpoint of a host device within a period of time, wherein the anomaly is indicative of the number of domain name service requests by the virtual network endpoint of the host device within the period of time being greater than a number of expected domain name service requests determined by the machine learning model.

### Claim 15 (depends on 11)

The network system of claim 11, wherein to determine the firewall policy the instructions cause the network system to select the firewall policy or generate the firewall policy.

### Claim 16 (depends on 11)

The network system of claim 11, wherein the one or more NICs implement a distributed firewall.

### Claim 17

A network system comprising:
a network interface card (NIC) comprising processing circuitry; and
one or more memories coupled to the processing circuitry and configured to store instructions which, when executed by the processing circuitry, cause the network system to:
send telemetry data to a controller, the telemetry data comprising traffic session metrics data;
receive, from the controller, an indication of a firewall policy based on a determination of an anomaly in traffic based on the traffic session metrics data; and
implement the firewall policy.

### Claim 18 (depends on 17)

The network system of claim 17, wherein the traffic sessions metrics data comprises a number of domain name service requests by a virtual network endpoint of a host device within a period of time, and wherein the anomaly is determined by a machine learning model.

### Claim 19 (depends on 18)

The network system of claim 18, wherein implementing the firewall policy causes the NIC to cease sending domain name services requests from the virtual endpoint of the host device.

### Claim 20 (depends on 17)

The network system of claim 17, wherein the NIC implements an instance of a distributed firewall.
