# US 2022/0286471 A1 · Honeypot Network with Dynamically Updated Alert Modules for Detecting Anomalous Connections

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

- Number: US 2022/0286471 A1
- Document ID: US20220286471A1
- Status: Published application
- Kind: A1
- Application number: 17/664,373
- Filed: 2022-05-20
- Published: 2022-09-08
- Earliest claimed: 2018-01-23
- Assignees: Rapid7, Inc.
- Applicants: Rapid7, Inc.
- Inventors: Roy Hodgman; Wah-Kwan Lin; Vasudha Shivamoggi
- Web page: https://patentgrep.com/patent/US20220286471A1

## CPC

- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- H04L 63/0227: {Filtering policies (mail message filtering H04L51/212)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Analyzing and reporting anomalous internet traffic data by accepting a request for a connection to a virtual security appliance, collecting attribute data about the connection, applying an alert module to the data, and automatically generating an alert concerning an identified incident. An alert system for analyzing and reporting the anomalous internet traffic data. A processor to analyze and report anomalous internet traffic data.

## Claims

### Claim at position 1

-20. (canceled)

### Claim 21

A method, comprising:
performing, by one or more computing devices that implement a honeypot network:
adding or deleting one or more alert modules to or from a set of alert modules, wherein individual ones of the alert modules in the set is configured to analyze different subsets of attribute data about connections accepted by the honeypot network for one or more anomalies, wherein the one or more anomalies includes:
an IP port of a given connection,
a TCP flag of the given connection,
a handshake of the given connection,
a timing of the given connection,
a duration of the given connection, or
a termination of the given connection;
accepting a request for a connection to the honeypot network;
collecting attribute data about the connection, wherein the attribute data includes a time of the connection, a number of bytes associated with the connection, a source IP address of the connection, or an IP port of the connection;
applying the set of alert modules to at least some of the attribute data about the connection to identify an anomaly about the connection; and
reporting an incident via a user interface, wherein the incident indicates the anomaly.

### Claim 22 (depends on 21)

The method of claim 21, wherein an alert module is added or deleted to or from the set of alert modules as decided by a machine learning system.

### Claim 23 (depends on 21)

The method of claim 21, wherein the connection is accepted by a virtual security appliance implemented in the honeypot network, and the set of alert modules are implemented by the virtual security appliance.

### Claim 24 (depends on 23)

The method of claim 23, wherein an alert module is added or deleted to or from the set of alert modules based on user input while the set of alert modules are running on the virtual security appliance.

### Claim 25 (depends on 21)

The method of claim 21, wherein the attribute data collected about the connection includes content of data sent through the connection.

### Claim 26 (depends on 21)

The method of claim 21, wherein reporting the incident comprises sending an alert to a subscriber of detected incidents, wherein the alert indicates a time of the incident.

### Claim 27 (depends on 26)

The method of claim 26, wherein the alert indicates a source of the connection and a record of data exchange over the connection.

### Claim 28 (depends on 26)

The method of claim 26, wherein the alert causes a text message, an email, or a pop-up warning to be received at a user device associated with the subscriber.

### Claim 29 (depends on 21)

The method of claim 21, further comprising the honeypot network reporting detected incidents at a reporting frequency, wherein the reporting frequency is configurable.

### Claim 30 (depends on 21)

The method of claim 21, further comprising the honeypot network filtering the collected to discard non-anomalous attribute data about the connection prior to applying the set of alert modules.

### Claim 31 (depends on 21)

The method of claim 21, wherein the incident is formatted as a plot, a table, or a chart on the user interface.

### Claim 32 (depends on 21)

The method of claim 21, wherein the incident is identified based on an anomalous trend observed over a plurality of connections including the connection.

### Claim 33

A system comprising:
one or more computing devices that implement a honeypot network, configured to:
add or delete one or more alert modules to or from a set of alert modules, wherein individual ones of the alert modules in the set is configured to analyze different subsets of attribute data about connections accepted by the honeypot network for one or more anomalies, wherein the one or more anomalies includes:
an IP port of a given connection,
a TCP flag of the given connection,
a handshake of the given connection,
a timing of the given connection,
a duration of the given connection, or
a termination of the given connection;
accept a request for a connection to the honeypot network;
collect attribute data about the connection, wherein the attribute data includes a time of the connection, a number of bytes associated with the connection, a source IP address of the connection, or an IP port of the connection;
apply the set of alert modules to at least some of the attribute data about the connection to identify an anomaly about the connection; and
report an incident via a user interface, wherein the incident indicates the anomaly.

### Claim 34 (depends on 33)

The system of claim 33, wherein the connection is accepted by a virtual security appliance implemented in the honeypot network, and the set of alert modules are implemented by the virtual security appliance.

### Claim 35 (depends on 33)

The system of claim 33, wherein the attribute data collected about the connection includes content of data sent through the connection.

### Claim 36 (depends on 33)

The system of claim 33, wherein to report the incident, the honeypot network is configured to send an alert to a subscriber of detected incidents, wherein the alert indicates a time of the incident.

### Claim 37 (depends on 36)

The system of claim 36, wherein the alert indicates a source of the connection and a record of data exchange over the connection.

### Claim 38 (depends on 36)

The system of claim 36, wherein the alert causes a text message, an email, or a pop-up warning to be received at a user device associated with the subscriber.

### Claim 39 (depends on 33)

The system of claim 33, wherein the honeypot network is configured to identify the incident based on an anomalous trend observed over a plurality of connections including the connection.

### Claim 40

One or more non-transitory computer-readable media storing program instructions that when executed on one or more processors of one or more computing devices to implement a honeypot network and cause the honeypot network to:
add or delete one or more alert modules to or from a set of alert modules, wherein individual ones of the alert modules in the set is configured to analyze different subsets of attribute data about connections accepted by the honeypot network for one or more anomalies, wherein the one or more anomalies includes:
an IP port of a given connection,
a TCP flag of the given connection,
a handshake of the given connection,
a timing of the given connection,
a duration of the given connection, or
a termination of the given connection;
accept a request for a connection to the honeypot network;
collect attribute data about the connection, wherein the attribute data includes a time of the connection, a number of bytes associated with the connection, a source IP address of the connection, or an IP port of the connection;
apply the set of alert modules to at least some of the attribute data about the connection to identify an anomaly about the connection; and
report an incident via a user interface, wherein the incident indicates the anomaly.
