# US 2024/0205259 A1 · Multi-layer application security graph for cloud-native applications using runtime application telemetry collected in real-time

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

- Number: US 2024/0205259 A1
- Document ID: US20240205259A1
- Status: Published application
- Kind: A1
- Application number: 18/544,071
- Filed: 2023-12-18
- Published: 2024-06-20
- Earliest claimed: 2022-12-20
- Assignees: Operant AI, Inc.
- Applicants: Operant AI, Inc.
- Inventors: Priyanka Mohan Tembey; Vrajesh Rajesh Bhavsar; Ashley Michelle Chapman Roof
- Web page: https://patentgrep.com/patent/US20240205259A1

## CPC

- H04L 63/1433: {Vulnerability analysis}
- G06F 21/554: {involving event detection and direct action}
- G06F 21/577: {Assessing vulnerabilities and evaluating computer system security}
- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- G06F 2221/033: Test or assess software
- 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 computer-implemented method generates and manages a dynamic security graph, displaying runtime security and risk context across a cloud-native application. The security graph shows, in real-time, a customer's application components and their interactions. It reveals API traffic flows spanning multiple layers, extending from the public-facing API endpoint layer to internal microservices, external third-party APIs, and a data store layer. Additionally, it depicts how external and internal users and services, with established identities and roles, interact with diverse API and data resources, as well as the microservices involved in these interactions. The graph outlines data flows originating within internal microservices of a customer's environment but ultimately leaving the environment towards third-party APIs, external IP addresses, services, or external data stores. Moreover, the security graph highlights security vulnerabilities within each layer of the application and indicates potential attack vectors. In various embodiments, a computer-implemented method, a computer system with a distributed systems architecture, and a computer program product are programmed to generate and manage an application security graph bringing together runtime security and risk context across every layer of a cloud-native application for security engineering teams. In this context, a security graph is a dynamic map of a customer's application stack displayed in real-time. A visualization of the security graph in a graphical user interface can show API Traffic flows across multiple layers of the application from the public-facing API endpoint layer to internal microservices, external third-party APIs, and a data store layer; external and internal user and service identities and roles at play and how they access various API and data resources and through which microservices; data flows that originate within internal microservices of a customer environment but end up egressing the environment to either third party APIs/external IP addresses/services or external data stores; security vulnerabilities within each application layer, such as unauthenticated API endpoints allowing open access to a service's APIs, a container image having a critical CVE vulnerability, or an external data store that is misconfigured with suboptimal security parameters. Using graph analytics, the dynamic map shows potential attack vectors into a customer's applications by triangulating risk across multiple layers including identities, API accesses, and data stores and vulnerabilities to show what assets are at critical risk, how can they be breached in a potential attack, and what can be done to protect those assets.

## Claims

### Claim 1

A computer-implemented method of managing security of an application, the computer-implemented method executed using one or more processors of a server computer and comprising:
using a local controller service deployed within a computing environment:
interfacing with application programming interfaces (APIs) of microservices executing in the computing environment and obtaining telemetry data in response, the telemetry data comprising security-related data;
aggregating the telemetry data into a telemetry data payload; and
sending a message containing the telemetry data payload to a message queue service of a central control plane;
using the central control plane:
creating and storing in memory a graph representing interactions of the microservices based on the telemetry data payload;
identifying an attack path in the computing environment based on vulnerabilities identified in the security-related data using the graph; and
displaying the graph and the attack path in real time in a graphical user interface of a computer display device.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, further comprising identifying a vulnerable API of the microservices that allows an unauthenticated access and automatically preventing the unauthenticated access to the vulnerable API.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, wherein the local controller service comprises a plurality of sidecar processes, each sidecar process among the plurality of sidecar processes being generated for and corresponding to each microservice among the microservices; wherein each sidecar process among the plurality of sidecar processes is configured to have access to data flowing in and out of a corresponding microservice of the microservices.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, wherein the local controller service comprising an application container that a container platform API brings up in the computing environment.

### Claim 5 (depends on 4)

The computer-implemented method of claim 4, wherein the local controller service is further configured to query a metadata service of the container platform API to obtain additional security-related data including:
whether data stored in a database accessed by a microservice is encrypted;
whether a connection to a data service is encrypted; and
how open is an access to a specific data resource based on its network configuration.

### Claim 6 (depends on 1)

The computer-implemented method of claim 1, wherein the local controller service is programmed to automatically detect a known open port of a microservice from the microservices, and output associated telemetry data based on a protocol associated with the open port.

### Claim 7 (depends on 1)

The computer-implemented method of claim 1, wherein the telemetry data includes at least one of: a request source namespace, a request destination namespace, a request API endpoint, a request API method, or a request authentication header.

### Claim 8 (depends on 1)

The computer-implemented method of claim 1, wherein the telemetry data includes identifying information about entities accessing any one of the microservices.

### Claim 9 (depends on 1)

The computer-implemented method of claim 1, wherein the telemetry data payload is processed in an event-based asynchronous manner.

### Claim 10 (depends on 1)

The computer-implemented method of claim 1, wherein the security-related data includes at least one of: a number of API requests that are unauthenticated, security-related vulnerabilities within containers and virtual machines hosting the microservices, or security-related gaps in data storage with which the microservices interact.

### Claim 11 (depends on 1)

The computer-implemented method of claim 1, wherein the graph comprises:
a plurality of graph nodes, each graph node corresponding to at least one of: a microservice from the microservices, an API of an external application, an external server, or an external client; and
a plurality of graph edges, each graph edge connecting two graph nodes, each graph edge having associated connection attributes related to a connection between the two graph nodes.

### Claim 12 (depends on 11)

The computer-implemented method of claim 11, where the connection attributes include at least one of: a number of requests to an API of a graph node per unit time, a number of unauthorized requests to an API of a graph node per a unit time, or errors associated with a connection to a graph node.

### Claim 13 (depends on 1)

The computer-implemented method of claim 1, wherein identifying the attack path, the attack path includes identifying vulnerable graph nodes and graph edges.

### Claim 14

A computer-implemented method of managing security of an application, the computer-implemented method comprising:
interfacing with application programming interface (API) of microservices operated within a computing environment to obtain telemetry data, the telemetry data comprising security-related data;
aggregating the telemetry data into a telemetry data payload;
generating a graph representing interactions of the microservices based on the telemetry data payload;
identifying an attack path within the computing environment based on vulnerabilities identified in the security-related data using the graph; and
displaying the graph and the attack path in real-time to a user.

### Claim 15 (depends on 14)

The computer-implemented method of claim 14, further comprising:
identifying a vulnerable API of the microservices that allows an unauthenticated access;
preventing the unauthenticated access to the vulnerable API in an automated manner.

### Claim 16 (depends on 14)

The computer-implemented method of claim 14, wherein the interfacing includes accessing data flowing in and out of a corresponding microservice from the microservices using a sidecar process, the computer-implemented method further comprising collecting the accessed data, thereby forming the telemetry data.

### Claim 17

One or more non-transitory computer-readable storage media storing one or more sequences of instructions which, when executed using one or more processors, cause the one or more processors to execute a method comprising:
interfacing with application programming interface (API) of microservices operated within a computing environment to obtain telemetry data, the telemetry data comprising security-related data;
aggregating the telemetry data into a telemetry data payload;
generating a graph representing interactions of the microservices based on the telemetry data payload;
identifying an attack path within the computing environment based on vulnerabilities identified in the security-related data using the graph;
displaying the graph and the attack path in real-time to a user.

### Claim 18 (depends on 17)

The one or more non-transitory computer-readable storage media of claim 17, wherein displaying the graph includes displaying:
a plurality of graph nodes, each graph node corresponding to at least one of: a microservice from the microservices, an API of an external application, an external server, or an external client; and
a plurality of graph edges, each graph edge connecting two graph nodes, each graph edge having associated connection attributes related to a connection between the two graph nodes.

### Claim 19 (depends on 17)

The one or more non-transitory computer-readable storage media of claim 17, wherein the attack path includes identifying vulnerable graph nodes and graph edges.

### Claim 20 (depends on 17)

The one or more non-transitory computer-readable storage media of claim 17, wherein the method executed by the one or more processors further includes:
identifying a vulnerable API of the microservices that allows an unauthenticated access; and
automatically preventing the unauthenticated access to the vulnerable API.

### Claim 21 (depends on 17)

The one or more non-transitory computer-readable storage media of claim 17, wherein the method executed by the one or more processors further includes:
automatically detecting a known open port of a microservice from the microservices; and
outputting associated telemetry data based on a protocol associated with the open port.

### Claim 22 (depends on 17)

The one or more non-transitory computer-readable storage media of claim 17, wherein the telemetry data includes at least one of: a request source namespace, a request destination namespace, a request API endpoint, a request API method, or a request authentication header.

### Claim 23 (depends on 17)

The one or more non-transitory computer-readable storage media of claim 17, wherein the telemetry data includes identifying information about entities accessing any one of the microservices.

### Claim 24 (depends on 17)

The one or more non-transitory computer-readable storage media of claim 17, wherein the security-related data includes at least one of: a number of API requests that are unauthenticated, security-related vulnerabilities within containers and virtual machines hosting the microservices, or security-related gaps in data storage with which the microservices interact.

### Claim 25 (depends on 17)

The one or more non-transitory computer-readable storage media of claim 17, where the connection attributes include at least one of: a number of requests to an API of a graph node per unit time, a number of unauthorized requests to an API of a graph node per a unit time, or errors associated with a connection to a graph node.
