# US 2021/0279117 A1 · Systems and methods for multi-event correlation

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

- Number: US 2021/0279117 A1
- Document ID: US20210279117A1
- Status: Published application
- Kind: A1
- Application number: 17/327,663
- Filed: 2021-05-21
- Published: 2021-09-09
- Earliest claimed: 2019-05-31
- Assignees: Digital Guardian, Inc.
- Applicants: Digital Guardian LLC
- Inventors: John H. Lehmann
- Web page: https://patentgrep.com/patent/US20210279117A1

## CPC

- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- G06F 11/3017: {where the computing system is implementing multitasking (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50)}
- G06F 11/3072: {where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting}
- G06F 21/554: {involving event detection and direct action}
- G06F 21/56: Computer malware detection or handling, e.g. anti-virus arrangements
- H04L 63/1416: {Event detection, e.g. attack signature detection}
- H04L 63/108: {when the policy decisions are valid for a limited amount of time}
- H04L 63/145: {the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Provided herein are systems and methods for multi-event correlation. Receiving a stream of events, each leaf rule engine may detect a plurality of events from the stream that matches a characteristic for the leaf rule engine. Each leaf rule engine may identify, from the plurality of events and within a time window, a group of events that satisfies a condition for the respective leaf rule engine. A root conditions engine may receive a stream of leaf events corresponding to the group of events identified by each leaf rule engine. The root conditions engine may identify, from the received stream of leaf events and within a root time window, a collection of events that satisfies a condition for the root conditions engine. A trigger may execute an action according to the collection of events identified within the root time window.

## Claims

### Claim 1

A system for multi-event correlation, comprising:
one or more processors coupled with memory, configured to:
receive, for a leaf rule, a stream of events each corresponding to an activity of at least one of a user, a device, or a program;
detect, from the stream of events, a first plurality of events in accordance with a filter of the leaf rule;
identify, from the first plurality of events, a second plurality of events satisfying a condition within a time window of the leaf rule; and
provide the second plurality of events to a root rule to identify a third plurality of events with which to execute an action in accordance with a trigger.

### Claim 2 (depends on 1)

The system of claim 1, wherein the one or more processors is further configured to modify at least one of the filter, the condition, or the time window of the leaf rule based at least on an administrative specification.

### Claim 3 (depends on 1)

The system of claim 1, wherein the one or more processors is further configured to set at least one of the filter, the condition, or the time window of the leaf rule using a machine learning model.

### Claim 4 (depends on 1)

The system of claim 1, wherein the one or more processors is further configured to shift the time window to apply the conditions to the first plurality of events.

### Claim 5 (depends on 1)

The system of claim 1, wherein the filter of the leaf rule defines a characteristic of events identified to be at least one of a potential anomaly, a risk, or a threat to detect the first plurality of events.

### Claim 6 (depends on 1)

The system of claim 1, wherein the condition of the leaf rule defines at least one of a total number of events, a total number of devices, a total number of files, or a total number of bytes accumulated within the time window to identify the second plurality of events.

### Claim 7 (depends on 1)

The system of claim 1, wherein at least one of the filter, the condition, or the time window of the leaf rule differs from a corresponding filter, condition, or time window of another leaf rule.

### Claim 8

A system for multi-event correlation, comprising:
one or more processors coupled with memory, configured to:
receive, for a root rule, a stream of events identified by a leaf rule, each event of the stream of events corresponding to an activity at least one of a user, a device, or a program;
determine, from the stream of events, a first plurality of events within a time window of the root rule;
identify, from the first plurality of events within the time window, a second plurality of events satisfying a condition of the root rule; and
provide, to a trigger, the second plurality of events with which to execute an action.

### Claim 9 (depends on 8)

The system of claim 8, wherein the one or more processors is further configured to modify at least one of the filter, the condition, or the time window of the root rule based at least on an administrative specification.

### Claim 10 (depends on 8)

The system of claim 8, wherein the one or more processors is further configured to set at least one of the filter, the condition, or the time window of the root rule using a machine learning model.

### Claim 11 (depends on 8)

The system of claim 8, wherein the one or more processors is further configured to aggregate the stream of events identified from a plurality of leaf rules, each of the plurality of leaf rules identifying a corresponding subset of events in accordance with a respective filter, time window, and condition.

### Claim 12 (depends on 8)

The system of claim 8, wherein the time window of the root rule differs from a time window of the leaf rule to determine the first plurality of events from the stream of events.

### Claim 13 (depends on 8)

The system of claim 8, wherein the condition of the root rule defines at least one of a total number of events, a total number of devices, a total number of files, or a total number of bytes accumulated within the time window to identify the second plurality of events.

### Claim 14 (depends on 8)

The system of claim 8, wherein the action executed by the trigger includes at least one of: an initiation of an alarm for a potential anomaly, a risk, or threat; or a provision of an instruction to pause or terminate execution of the program.

### Claim 15

A method of correlating across multiple events, comprising:
receiving, by a computing system, for a leaf rule, a stream of events each corresponding to an activity of at least one of a user, a device, or a program;
detecting, by the computing system, from the stream of events, a first plurality of events in accordance with a filter of the leaf rule;
identifying, by the computing system, from the first plurality of events, a second plurality of events satisfying a condition within a time window of the leaf rule; and
providing, by the computing system, the second plurality of events to a root rule to identify a third plurality of events.

### Claim 16 (depends on 15)

The method of claim 15, further comprising:
determining, by the computing system, from the second plurality of events, the third plurality of events within a time window of the root rule;
identifying, by the computing system, from the third plurality of events within the time window of the root rule, a fourth plurality of events satisfying a condition of the root rule; and
provide, to a trigger, the fourth plurality of events with which to execute an action.

### Claim 17 (depends on 16)

The method of claim 16, further comprising aggregating, by the computing system, the second plurality of events identified from a plurality of leaf rules, each of the plurality of leaf rules identifying a corresponding subset of events in accordance with a respective filter, time window, and condition.

### Claim 18 (depends on 16)

The method of claim 16, wherein the action executed by the trigger includes at least one of: an initiation of an alarm for a potential anomaly, a risk, or threat; or a provision of an instruction to pause or terminate execution of the program.

### Claim 19 (depends on 15)

The method of claim 15, wherein the filter of the leaf rule defines a characteristic of events identified to be at least one of a potential anomaly, a risk, or a threat to detect the first plurality of events.

### Claim 20 (depends on 15)

The method of claim 15, wherein the condition of the leaf rule defines at least one of a total number of events, a total number of devices, a total number of files, or a total number of bytes accumulated within the time window to identify the second plurality of events.
