# US 2022/0035783 A1 · Storage and Structured Search of Historical Security Data

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

- Number: US 2022/0035783 A1
- Document ID: US20220035783A1
- Status: Published application
- Kind: A1
- Application number: 17/451,579
- Filed: 2021-10-20
- Published: 2022-02-03
- Earliest claimed: 2018-11-21
- Assignees: Google Inc.
- Applicants: Google LLC
- Inventors: Collin Lambert; Innokentiy Basmov; Ethan Daniel Gaebel; Andrew Liang Ping Chang; Iulia Ion
- Web page: https://patentgrep.com/patent/US20220035783A1

## CPC

- G06F 16/2228: {Indexing structures}
- G06F 16/2477: {Temporal data queries}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 16/284: {Relational databases}
- G06F 16/951: Indexing; Web crawling techniques
- G06F 21/604: {Tools and structures for managing or administering access control systems}
- G06F 21/62: Protecting access to data via a platform, e.g. using keys or access control rules
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method includes ingesting event data over a network for a plurality of events obtained by disparate computing resources. Each event is associated with a respective timestamp and one or more ingestion-attributes. The method includes identifying whether the corresponding event is associated with any custom indexing-attributes defined by a user. The method also includes indexing the corresponding event into a data store as structured data based on the respective timestamp, the one or more ingestion-attributes, and any identified custom indexing-attributes. The method includes evicting any of the events of the event data in the data store for a period of time that satisfies an eviction time period threshold. The method also includes retrieving the data from the data store that is associated with the time range, the ingestion-attributes, or the one custom indexing-attributes.

## Claims

### Claim 1

A computer-implemented method when executed on data processing hardware causes the data processing hardware to perform operations comprising:
receiving an event over a network obtained by a plurality of disparate computing resources in communication with the data processing hardware, the event comprising an ingestion-attribute associated with the event;
determining whether the ingestion-attribute associated with the event satisfies ingestion criteria;
when the ingestion-attribute associated with the event fails to satisfy the ingestion criteria, discarding the event obtained by the one of the plurality of disparate computing resources;
when the ingestion-attribute associated with the event satisfies the ingestion criteria, ingesting the event obtained by the one of the plurality of disparate computing resources for persistent storage in a data store;
determining whether the event has been stored in the data store for a period of time that satisfies an eviction time period threshold; and
when the event has been stored in the data store for the period of time that satisfies the eviction time period threshold, evicting the event from the data store.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein ingesting the event is in response to at least one of:
receiving an ingestion request;
an indication from a time schedule; or
an indication from an event.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, wherein the operations further comprise, identifying whether the event is associated with any custom indexing-attributes defined by a user for indexing events.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, wherein the operations further comprise:
applying a set of validity rules to the event;
determining whether the event is valid based on the set of validity rules; and
when the event is valid, indexing the event into the data store as structured data.

### Claim 5 (depends on 4)

The computer-implemented method of claim 4, wherein the set of validity rules comprises a set of priority rules to determine a priority of the event.

### Claim 6 (depends on 4)

The computer-implemented method of claim 4, wherein the operations further comprise, when the event is invalid, rejecting the event for indexing into the data store.

### Claim 7 (depends on 1)

The computer-implemented method of claim 1, wherein the operations further comprise:
receiving a retrieval request for data stored in the data store,
wherein receiving the retrieval request comprises receiving a data retrieval offset, the data retrieval offset indicating a position in a list of data to be retrieved, and wherein only data after the position in the list of data is retrieved.

### Claim 8 (depends on 1)

The computer-implemented method of claim 1, wherein the data store comprises a distributed storage system.

### Claim 9 (depends on 1)

The computer-implemented method of claim 1, wherein ingesting the event comprises obtaining the event by the one of the plurality of disparate computing resources via an application programming interface.

### Claim 10 (depends on 1)

The computer-implemented method of claim 1, wherein the event is indicative of a measured characteristic of a corresponding one of the plurality of disparate computing resources.

### Claim 11

A system comprising:
data processing hardware; and
memory hardware in communication with the data processing hardware, the memory hardware storing instructions that when executed on the data processing hardware cause the data processing hardware to perform operations comprising.
receiving an event over a network obtained by a plurality of disparate computing resources in communication with the data processing hardware, the event comprising an ingestion-attribute associated with the event;
determining whether the ingestion-attribute associated with the event satisfies ingestion criteria;
when the ingestion-attribute associated with the event fails to satisfy the ingestion criteria, discarding the event obtained by the one of the plurality of disparate computing resources;
when the ingestion-attribute associated with the event satisfies the ingestion criteria, ingesting the event obtained by the one of the plurality of disparate computing resources for persistent storage in a data store;
determining whether the event has been stored in the data store for a period of time that satisfies an eviction time period threshold; and
when the event has been stored in the data store for the period of time that satisfies the eviction time period threshold, evicting the event from the data store.

### Claim 12 (depends on 11)

The system of claim 11, wherein ingesting the event is in response to at least one of:
receiving an ingestion request;
an indication from a time schedule; or
an indication from an event.

### Claim 13 (depends on 11)

The system of claim 11, wherein the operations further comprise, identifying whether the event is associated with any custom indexing-attributes defined by a user for indexing events.

### Claim 14 (depends on 11)

The system of claim 11, wherein the operations further comprise:
applying a set of validity rules to the event;
determining whether the event is valid based on the set of validity rules; and
when the event is valid, indexing the event into the data store as structured data.

### Claim 15 (depends on 14)

The system of claim 14, wherein the set of validity rules comprises a set of priority rules to determine a priority of the event.

### Claim 16 (depends on 14)

The system of claim 14, wherein the operations further comprise, when the event is invalid, rejecting the event for indexing into the data store.

### Claim 17 (depends on 11)

The system of claim 11, wherein the operations further comprise:
receiving a retrieval request for data stored in the data store,
wherein receiving the retrieval request comprises receiving a data retrieval offset, the data retrieval offset indicating a position in a list of data to be retrieved, and wherein only data after the position in the list of data is retrieved.

### Claim 18 (depends on 11)

The system of claim 11, wherein the data store comprises a distributed storage system.

### Claim 19 (depends on 11)

The system of claim 11, wherein ingesting the event comprises obtaining the event by the one of the plurality of disparate computing resources via an application programming interface.

### Claim 20 (depends on 11)

The system of claim 11, wherein the event is indicative of a measured characteristic of a corresponding one of the plurality of disparate computing resources.
