# US 2025/0097043 A1 · System and method of filtering internet traffic via client fingerprint

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

- Number: US 2025/0097043 A1
- Document ID: US20250097043A1
- Status: Published application
- Kind: A1
- Application number: 18/968,347
- Filed: 2024-12-04
- Published: 2025-03-20
- Earliest claimed: 2018-12-28
- Assignees: Plaid Inc.
- Applicants: Plaid Inc.
- Inventors: Shawn BRACKEN
- Web page: https://patentgrep.com/patent/US20250097043A1

## CPC

- H04L 9/3236: {using cryptographic hash functions}
- H04L 63/166: {at the transport layer}
- H04L 43/026: using flow identification
- H04L 43/028: by filtering
- H04L 63/0281: {Proxies}
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 63/1408: {by monitoring network traffic (monitoring network traffic per se H04L43/00)}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L 67/303: Terminal profiles
- H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC}
- H04L 43/04: Processing captured monitoring data, e.g. for logfile generation
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system and method that includes receiving a client data packet from network traffic with a client device; extracting a set of packet components from the client data packet; generating a client fingerprint from the set of packet components; assigning a client type to the network traffic using the client fingerprint; and optionally filtering the network traffic of the client device based at least in part on the client type.

## Claims

### Claim 1

A method comprising:
extracting, by a device, a set of packet components from a data packet;
generating, by the device, a tiered client fingerprint with an overall client fingerprint based on encoding an encoded collection of packet components of the set of packet components; and
assigning, by the device based on the tiered client fingerprint, a type to network traffic associated with the data packet.

### Claim 2 (depends on 1)

The method of claim 1, wherein the tiered client fingerprint is a multi-tiered client fingerprint.

### Claim 3 (depends on 1)

The method of claim 1, wherein the data packet is a hello message received during negotiation associated with a cryptographic protocol.

### Claim 4 (depends on 3)

The method of claim 3, further comprising:
extracting identifying data from client point formats from the hello message;
encoding the client point formats; and
including the encoded client point formats in a set of sub-fingerprints.

### Claim 5 (depends on 1)

The method of claim 1, further comprising filtering the network traffic based on the type.

### Claim 6 (depends on 1)

The method of claim 1, wherein assigning the type to the network traffic comprises selecting the type from a database,
wherein the database includes a mapping of the tiered client fingerprint to a classification of client type.

### Claim 7 (depends on 1)

The method of claim 1, wherein the data packet is a hello message received during negotiation associated with a transport layer security (TLS) protocol.

### Claim 8

A device, comprising:
one or more memories; and
one or more processors, coupled to the one or more memories, configured to:
extract a set of packet components from a data packet;
generate a tiered client fingerprint with an overall client fingerprint based on encoding an encoded collection of packet components of the set of packet components; and
assign, based on the tiered client fingerprint, a type to a network traffic associated with the data packet.

### Claim 9 (depends on 8)

The device of claim 8, wherein the tiered client fingerprint is a multi-tiered client fingerprint.

### Claim 10 (depends on 8)

The device of claim 8, wherein the data packet is a hello message received during negotiation associated with a cryptographic protocol.

### Claim 11 (depends on 10)

The device of claim 10, wherein the one or more processors are further configured to:
extract identifying data from client point formats from the hello message;
encode the client point formats; and
include the encoded client point formats in a set of sub-fingerprints.

### Claim 12 (depends on 8)

The device of claim 8, wherein the one or more processors are further configured to filter the network traffic based on the type.

### Claim 13 (depends on 8)

The device of claim 8, wherein the one or more processors, to assign the type to the network traffic, are configured to select the type from a database,
wherein the database includes a mapping of the tiered client fingerprint to a classification of client type.

### Claim 14 (depends on 8)

The device of claim 8, wherein the data packet is a hello message received during negotiation associated with a transport layer security (TLS) protocol.

### Claim 15

A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:
one or more instructions that, when executed by one or more processors of a device, cause the device to:
extract a set of packet components from a data packet;
generate a tiered client fingerprint with an overall client fingerprint based on encoding an encoded collection of packet components of the set of packet components; and
assign, based on the tiered client fingerprint, a type to a network traffic associated with the data packet.

### Claim 16 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the tiered client fingerprint is a multi-tiered client fingerprint.

### Claim 17 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the data packet is a hello message received during negotiation associated with a cryptographic protocol.

### Claim 18 (depends on 17)

The non-transitory computer-readable medium of claim 17, wherein the one or more instructions further cause the device to:
extract identifying data from client point formats from the hello message;
encode the client point formats; and
include the encoded client point formats in a set of sub-fingerprints.

### Claim 19 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the one or more instructions further cause the device to filter the network traffic based on the type.

### Claim 20 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, that cause the device to assign the type to the network traffic, cause the device to select the type from a database,
wherein the database includes a mapping of the tiered client fingerprint to a classification of client type.
