# US 2024/0267405 A1 · Detecting malware infection path in a cloud computing environment utilizing a security graph

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

- Number: US 2024/0267405 A1
- Document ID: US20240267405A1
- Status: Published application
- Kind: A1
- Application number: 18/617,225
- Filed: 2024-03-26
- Published: 2024-08-08
- Earliest claimed: 2021-12-27
- Assignees: Wiz, Inc.
- Applicants: Wiz, Inc.
- Inventors: Elad GABAY; Yaniv SHAKED; Alon SCHINDEL; Roy REZNIK; Ami LUTTWAK
- Web page: https://patentgrep.com/patent/US20240267405A1

## CPC

- H04L 63/145: {the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms}
- G06F 21/53: by executing in a restricted environment, e.g. sandbox or secure virtual machine
- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- H04L 63/1416: {Event detection, e.g. attack signature detection}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system and method detect a malware infection path in a compute environment. The method includes detecting a malware object on a first workload in a computing environment including a plurality of workloads, wherein the first workload is represented by a resource node on a security graph, the security graph including an endpoint node representing a resource which is accessible to a public network; generating a potential infection path between the resource node and the endpoint node including at least a second resource node connected to the resource node; inspecting a second workload of the plurality of workloads represented by the second resource node; determining that the potential infection path is a confirmed infection path, in response to detecting the malware on the second workload; and determining that the potential infection path is not an infection path, in response to detecting that the second workload does not include the malware.

## Claims

### Claim 1

A method for detecting a malware infection path in a compute environment, comprising:
detecting a cybersecurity object, indicating a malware, on a first workload in a computing environment, the computing environment including a plurality of workloads, wherein the first workload is represented by a resource node on a security graph, the security graph further including an endpoint node representing access to a public access network;
traversing the security graph from the resource node to the endpoint node to generate a plurality of potential infection paths between the resource node and the endpoint node;
inspecting a second workload of the plurality of workloads for the cybersecurity object, wherein the second workload is represented by a second resource node, and the second resource node is on a first potential infection path of the plurality of potential infection paths;
determining that the first potential infection path is a confirmed infection path, in response to detecting the cybersecurity object on the second workload;
determining that the firs potential infection path is not an infection path, in response to detecting that the second workload does not include the cybersecurity object; and
initiating a mitigation action in response to detecting the cybersecurity object on the second workload.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
generating the mitigation action to isolate the cybersecurity object, wherein the cybersecurity object is a malware code.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
traversing the security graph to detect a number of second resource nodes connected to the resource node; and
initiating the mitigation action in response to determining that the number of second resource nodes exceeds a threshold.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
determining that the first workload is authorized to access the second workload.

### Claim 5 (depends on 4)

The method of claim 4, further comprising:
determining that the first workload is authorized to access the second workload by detecting a vertex in the security graph connecting the second resource node to the resource node, wherein the vertex indicates an authorization to access.

### Claim 6 (depends on 5)

The method of claim 5, further comprising:
generating an impact analysis of the malware on a potential infection path of the plurality of potential infections paths, including an identifier of the second workload, in response to detecting the vertex in the security graph.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
generating an instruction to inspect the second workload to detect the cybersecurity object.

### Claim 8 (depends on 7)

The method of claim 7, further comprising:
generating an inspectable disk based on a disk of the second workload; and
providing access of the inspectable disk to a malware inspector, wherein the malware inspector is a software application deployed in a software container cluster.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
initiating the mitigation action on the second workload.

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
accessing a malware database to retrieve a first malware signature corresponding to the malware; and
inspecting the first workload for the malware based on the first malware signature.

### Claim 11

A non-transitory computer-readable medium storing a set of instructions for detecting a malware infection path in a compute environment, the set of instructions comprising:
one or more instructions that, when executed by one or more processors of a device, cause the device to:
detect a cybersecurity object, indicating a malware, on a first workload in a computing environment, the computing environment including a plurality of workloads, wherein the first workload is represented by a resource node on a security graph, the security graph further including an endpoint node representing access to a public access network;
traverse the security graph from the resource node to the endpoint node to generate a plurality of potential infection paths between the resource node and the endpoint node
inspect a second workload of the plurality of workloads for the cybersecurity object, wherein the second workload is represented by a second resource node, and the second resource node is on a first potential infection path of the plurality of potential infection paths
determine that the first potential infection path is a confirmed infection path, in response to detecting the cybersecurity object on the second workload
determine that the firs potential infection path is not an infection path, in response to detecting that the second workload does not include the cybersecurity object; and
initiate a mitigation action in response to detecting the cybersecurity object on the second workload.

### Claim 12

A system for detecting a malware infection path in a compute environment comprising:
a processing circuitry;
a memory, the memory containing instructions that, when executed by the processing circuitry, configure the system to:
detect a cybersecurity object, indicating a malware, on a first workload in a computing environment, the computing environment including a plurality of workloads, wherein the first workload is represented by a resource node on a security graph, the security graph further including an endpoint node representing access to a public access network;
traverse the security graph from the resource node to the endpoint node to generate a plurality of potential infection paths between the resource node and the endpoint node
inspect a second workload of the plurality of workloads for the cybersecurity object, wherein the second workload is represented by a second resource node, and the second resource node is on a first potential infection path of the plurality of potential infection paths
determine that the first potential infection path is a confirmed infection path, in response to detecting the cybersecurity object on the second workload
determine that the firs potential infection path is not an infection path, in response to detecting that the second workload does not include the cybersecurity object; and
initiate a mitigation action in response to detecting the cybersecurity object on the second workload.

### Claim 13 (depends on 12)

The system of claim 12, wherein the memory contains further instructions which when executed by the processing circuitry further configure the system to:
generate the mitigation action to isolate the cybersecurity object, wherein the cybersecurity object is a malware code.

### Claim 14 (depends on 12)

The system of claim 12, wherein the memory contains further instructions which when executed by the processing circuitry further configure the system to:
traverse the security graph to detect a number of second resource nodes connected to the resource node; and
initiate the mitigation action in response to determining that the number of second resource nodes exceeds a threshold.

### Claim 15 (depends on 12)

The system of claim 12, wherein the memory contains further instructions which when executed by the processing circuitry further configure the system to:
determine that the first workload is authorized to access the second workload.

### Claim 16 (depends on 15)

The system of claim 15, wherein the memory contains further instructions which when executed by the processing circuitry further configure the system to:
determine that the first workload is authorized to access the second workload by detecting a vertex in the security graph connecting the second resource node to the resource node, wherein the vertex indicates an authorization to access.

### Claim 17 (depends on 16)

The system of claim 16, wherein the memory contains further instructions which when executed by the processing circuitry further configure the system to:
generate an impact analysis of the malware on a potential infection path of the plurality of potential infections paths, including an identifier of the second workload, in response to detecting the vertex in the security graph.

### Claim 18 (depends on 12)

The system of claim 12, wherein the memory contains further instructions which when executed by the processing circuitry further configure the system to:
generate an instruction to inspect the second workload to detect the cybersecurity object.

### Claim 19 (depends on 18)

The system of claim 18, wherein the memory contains further instructions which when executed by the processing circuitry further configure the system to:
generate an inspectable disk based on a disk of the second workload; and
provide access of the inspectable disk to a malware inspector, wherein the malware inspector is a software application deployed in a software container cluster.

### Claim 20 (depends on 19)

The system of claim 19, wherein the memory contains further instructions which when executed by the processing circuitry further configure the system to:
initiate the mitigation action on the second workload.

### Claim 21 (depends on 12)

The system of claim 12, wherein the memory contains further instructions which when executed by the processing circuitry further configure the system to:
access a malware database to retrieve a first malware signature corresponding to the malware; and
inspect the first workload for the malware based on the first malware signature.
