Granted Patent B2

US 12,314,227 · App. 18/382,621 · Granted May 27, 2025

Inventors: Christopher Michael Montgomery (Blaine, MN); Peter John Lindquist (St. Paul, MN); Brent Aethon McCullough (Saint Paul, MN); Vijay Ramanathan (Eden Prairie, MN); Daniel Louis Sullivan (Denver, CO)

Assignee: Code42 Software, Inc.

G06F16/1734G06F16/128G06F16/13G06F16/148G06F16/212

Abstract

Claims (43)

1. A system for forensic file services, the system comprising:

a computing device, comprising a hardware processor and a memory, the memory, storing instructions, which when executed by the hardware processor, causes the system to perform operations comprising:

receiving, over a network and from a monitoring application executing on a computing resource associated with a first tenant for forensic file services, data describing a filesystem element event corresponding to a particular filesystem element on the computing resource associated with the first tenant, the filesystem element event data describing a change to the particular filesystem element on a filesystem of the computing resource associated with the first tenant, and the filesystem element data including metadata of the particular filesystem element;

allocating the filesystem element event data to one of a plurality of parallel processing queues based upon an identifier of the computing resource;

determining that the filesystem element event corresponds to a deletion event;

responsive to determining that the filesystem element event corresponds to the deletion event, searching an event database for a last filesystem element event corresponding to that filesystem element and extracting a filesystem element signature including a hash of content of the particular filesystem element;

adding the filesystem element signature to the filesystem element event data to create enhanced filesystem element event data;

store the enhanced filesystem element event data in a database record of the event database in a partition configured to store a history of filesystem element events of a plurality computing resources associated with the first tenant;

receive a search request from a second computing device to search the event database, the search request comprising a search query and a tenant identifier of a second tenant;

execute the search query on a second partition of the event database to identify records that satisfy the search query, the second partition configured to store a history of filesystem element events of a plurality of computing resources associated with the second tenant; and

provide the identified records in response to the search request.

2. The system of claim 1 , wherein the metadata of the particular filesystem element comprises at least one of: a filename, a filepath, a timestamp, a file size, a checksum, or a file type.

3. The system of claim 1 , wherein allocating the filesystem element event data to one of the plurality of parallel processing queues comprises allocating the filesystem element event data to a processing queue based on a network identifier of the computing resource.

4. The system of claim 1 , wherein the operations further comprise: receiving data describing a second filesystem element event corresponding to a second filesystem element on a second computing resource associated with the first tenant; and allocating the second filesystem element event data to a second one of the plurality of parallel processing queues based upon an identifier of the second computing resource, wherein the second filesystem element event and the filesystem element event are processed in parallel.

5. The system of claim 1 , wherein the operations further comprise: pruning the event database by removing records older than a threshold time period.

6. The system of claim 5 , wherein pruning the event database comprises retaining a record when it is an only record corresponding to a particular filesystem element.

7. A method comprising:

receiving, over a network and from a monitoring application executing on a computing resource associated with a first tenant for forensic file services, data describing a filesystem element event corresponding to a particular filesystem element on the computing resource associated with the first tenant, the filesystem element event data describing a change to the particular filesystem element on a filesystem of the computing resource associated with the first tenant, and the filesystem element data including metadata of the particular filesystem element;

allocating the filesystem element event data to one of a plurality of parallel processing queues based upon an identifier of the computing resource;

determining that the filesystem element event corresponds to a deletion event;

responsive to determining that the filesystem element event corresponds to the deletion event, searching an event database for a last filesystem element event corresponding to that filesystem element and extracting a filesystem element signature including a hash of content of the particular filesystem element;

adding the filesystem element signature to the filesystem element event data to create enhanced filesystem element event data;

storing the enhanced filesystem element event data in a database record of the event database in a partition configured to store a history of filesystem element events of a plurality computing resources associated with the first tenant;

receiving a search request from a second computing device to search the event database, the search request comprising a search query and a tenant identifier of a second tenant;

executing the search query on a second partition of the event database to identify records that satisfy the search query, the second partition configured to store a history of filesystem element events of a plurality of computing resources associated with the second tenant; and

providing the identified records in response to the search request.

8. The method of claim 7 , wherein the metadata of the particular filesystem element comprises at least one of: a filename, a filepath, a timestamp, a file size, a checksum, or a file type.

9. The method of claim 7 , wherein allocating the filesystem element event data to one of the plurality of parallel processing queues comprises allocating the filesystem element event data to a processing queue based on a network identifier of the computing resource.

10. The method of claim 7 , further comprising: receiving data describing a second filesystem element event corresponding to a second filesystem element on a second computing resource associated with the first tenant; and allocating the second filesystem element event data to a second one of the plurality of parallel processing queues based upon an identifier of the second computing resource, wherein the second filesystem element event and the filesystem element event are processed in parallel.

11. The method of claim 7 , further comprising: pruning the event database by removing records older than a threshold time period.

12. The method of claim 11 , wherein pruning the event database comprises retaining a record when it is an only record corresponding to a particular filesystem element.

13. A machine-readable medium, storing instructions, which when executed by a machine, cause the machine to perform operations comprising:

receiving, over a network and from a monitoring application executing on a computing resource associated with a first tenant for forensic file services, data describing a filesystem element event corresponding to a particular filesystem element on the computing resource associated with the first tenant, the filesystem element event data describing a change to the particular filesystem element on a filesystem of the computing resource associated with the first tenant, and the filesystem element data including metadata of the particular filesystem element;

allocating the filesystem element event data to one of a plurality of parallel processing queues based upon an identifier of the computing resource;

determining that the filesystem element event corresponds to a deletion event;

responsive to determining that the filesystem element event corresponds to the deletion event, searching an event database for a last filesystem element event corresponding to that filesystem element and extracting a filesystem element signature including a hash of content of the particular filesystem element;

adding the filesystem element signature to the filesystem element event data to create enhanced filesystem element event data;

storing the enhanced filesystem element event data in a database record of the event database in a partition configured to store a history of filesystem element events of a plurality computing resources associated with the first tenant;

receiving a search request from a second computing device to search the event database, the search request comprising a search query and a tenant identifier of a second tenant;

executing the search query on a second partition of the event database to identify records that satisfy the search query, the second partition configured to store a history of filesystem element events of a plurality of computing resources associated with the second tenant; and

providing the identified records in response to the search request.

14. The machine-readable medium of claim 13 , wherein the metadata of the particular filesystem element comprises at least one of: a filename, a filepath, a timestamp, a file size, a checksum, or a file type.

15. The machine-readable medium of claim 13 , wherein the operations of allocating the filesystem element event data to one of the plurality of parallel processing queues comprises allocating the filesystem element event data to a processing queue based on a network identifier of the computing resource.

Assignments (3)

Continuity (2)

References Cited (22)