# US 2024/0202337 A1 · Techniques for tracking executable images across forking operations

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

- Number: US 2024/0202337 A1
- Document ID: US20240202337A1
- Status: Published application
- Kind: A1
- Application number: 18/085,088
- Filed: 2022-12-20
- Published: 2024-06-20
- Earliest claimed: 2022-12-20
- Assignees: CrowdStrike, Inc.
- Applicants: CrowdStrike, Inc.
- Inventors: Martin Kelly; Jayasankar Divakarla
- Web page: https://patentgrep.com/patent/US20240202337A1

## CPC

- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- G06F 21/52: during program execution, e.g. stack integrity {; Preventing unwanted data erasure; Buffer overflow}
- G06F 2221/034: Test or assess a computer or a system
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A creation of a first process is detected in a kernel space of the operating system executing on a computing device. An exec parent of the first process is determined. The exec parent identifies a second process within an ancestry of the first process that last performed an exec operation prior to the creation of the first process. A unique process identifier (UPID) associated with a process identifier (PID) of the first process is generated. The UPID is associated with the exec parent in a first mapping store that maps the PID to the UPID. Process activity of the first process executing in the operating system is tracked to generate process activity data that comprises the exec parent.

## Claims

### Claim 1

A method comprising:
detecting, in a kernel space of an operating system executing on a computing device, a creation of a first process;
determining, by a processing device, an exec parent of the first process, the exec parent identifying a second process, within an ancestry of the first process, that last performed an exec operation prior to the creation of the first process;
generating a unique process identifier (UPID) associated with a process identifier (PID) of the first process;
associating the UPID with the exec parent in a first mapping store that maps the PID to the UPID; and
tracking process activity of the first process executing in the operating system to generate process activity data that comprises the exec parent.

### Claim 2 (depends on 1)

The method of claim 1, wherein the second process is a different process from a third process that created the first process.

### Claim 3 (depends on 1)

The method of claim 1, wherein the exec operation performed by the second process is a first exec operation, and
wherein generating the UPID associated with the PID of the first process is performed responsive to at least one of detecting the first process performing a second exec operation, detecting a network operation by the first process, or detecting access of a storage device by the first process.

### Claim 4 (depends on 1)

The method of claim 1, wherein the UPID is a first UPID, and
wherein the exec parent of the first process comprises a second UPID of the second process.

### Claim 5 (depends on 1)

The method of claim 1, wherein the exec parent is determined by an application extension executing in an extended Berkeley packet filter (eBPF) infrastructure within the operating system of the computing device.

### Claim 6 (depends on 1)

The method of claim 1, further comprising transmitting a message comprising the PID to a message buffer structure.

### Claim 7 (depends on 1)

The method of claim 1, wherein the exec parent of the first process is a first exec parent, and
wherein determining the first exec parent of the first process comprises:
responsive to determining that a parent process of the first process has performed the exec operation prior to creating the first process, setting the first exec parent of the first process to a value associated with the parent process of the first process; or
responsive to determining that the parent process of the first process has not performed the exec operation prior to creating the first process, setting the first exec parent of the first process to a second exec parent of the parent process of the first process.

### Claim 8

A system comprising:
a memory; and
a processing device, operatively coupled to the memory, to:
detect, in a kernel space of an operating system executing on a computing device, a creation of a first process;
determine an exec parent of the first process, the exec parent identifying a second process, within an ancestry of the first process, that last performed an exec operation prior to the creation of the first process;
generate a unique process identifier (UPID) associated with a process identifier (PID) of the first process;
associate the UPID with the exec parent in a first mapping store that maps the PID to the UPID; and
track process activity of the first process executing in the operating system to generate process activity data that comprises the exec parent.

### Claim 9 (depends on 8)

The system of claim 8, wherein the second process is a different process from a third process that created the first process.

### Claim 10 (depends on 8)

The system of claim 8, wherein the exec operation performed by the second process is a first exec operation, and
wherein the processing device is to generate the UPID associated with the PID of the first process responsive to at least one of detecting the first process performing a second exec operation, detecting a network operation by the first process, or detecting access of a storage device by the first process.

### Claim 11 (depends on 8)

The system of claim 8, wherein the UPID is a first UPID, and
wherein the exec parent of the first process comprises a second UPID of the second process.

### Claim 12 (depends on 8)

The system of claim 8, wherein the exec parent is determined by an application extension executing in an extended Berkeley packet filter (eBPF) infrastructure within the operating system of the computing device.

### Claim 13 (depends on 8)

The system of claim 8, wherein the processing device is further to transmit a message comprising the PID to a message buffer structure.

### Claim 14 (depends on 8)

The system of claim 8, wherein the exec parent of the first process is a first exec parent, and
wherein, to determine the first exec parent of the first process, the processing device is further to:
responsive to determining that a parent process of the first process has performed the exec operation prior to creating the first process, set the first exec parent of the first process to a value associated with the parent process of the first process; or
responsive to determining that the parent process of the first process has not performed the exec operation prior to creating the first process, set the first exec parent of the first process to a second exec parent of the parent process of the first process.

### Claim 15

A non-transitory computer-readable storage medium including instructions that, when executed by a processing device, cause the processing device to:
detect, in a kernel space of an operating system executing on a computing device, a creation of a first process;
determine, by the processing device, an exec parent of the first process, the exec parent identifying a second process, within an ancestry of the first process, that last performed an exec operation prior to the creation of the first process;
generate a unique process identifier (UPID) associated with a process identifier (PID) of the first process;
associate the UPID with the exec parent in a first mapping store that maps the PID to the UPID; and
track process activity of the first process executing in the operating system to generate process activity data that comprises the exec parent.

### Claim 16 (depends on 15)

The non-transitory computer-readable storage medium of claim 15, wherein the exec operation performed by the second process is a first exec operation, and
wherein the processing device is to generate the UPID associated with the PID of the first process responsive to at least one of detecting the first process performing a second exec operation, detecting a network operation by the first process, or detecting access of a storage device by the first process.

### Claim 17 (depends on 15)

The non-transitory computer-readable storage medium of claim 15, wherein the UPID is a first UPID, and
wherein the exec parent of the first process comprises a second UPID of the second process.

### Claim 18 (depends on 15)

The non-transitory computer-readable storage medium of claim 15, wherein the exec parent is determined by an application extension executing in an extended Berkeley packet filter (eBPF) infrastructure within the operating system of the computing device.

### Claim 19 (depends on 15)

The non-transitory computer-readable storage medium of claim 15, wherein the processing device is further to transmit a message comprising the PID to a message buffer structure.

### Claim 20 (depends on 15)

The non-transitory computer-readable storage medium of claim 15, wherein the exec parent of the first process is a first exec parent, and
wherein, to determine the first exec parent of the first process, the processing device is further to:
responsive to determining that a parent process of the first process has performed the exec operation prior to creating the first process, set the first exec parent of the first process to a value associated with the parent process of the first process; or
responsive to determining that the parent process of the first process has not performed the exec operation prior to creating the first process, set the first exec parent of the first process to a second exec parent of the parent process of the first process.
