IP Library Granted Patent US 12,505,223
Granted Patent B2
US 12,505,223 · App. 17/731,549 · Granted Dec 23, 2025

System and method for detecting vulnerabilities in cloud-native web applications

Inventors: Dean Agron (Ra+3 anana, IL); Ron Vider (Hod HaSharon, IL)
Assignee: GitLab Inc.
G06F21/577G06F2221/033
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,505,223
App. No.
17/731,549
Granted
Dec 23, 2025
Kind
B2
Abstract

A method for assessing vulnerable flows in a cloud-native application, the method including the steps of: mapping runtime functions in microservices in the cloud-native application; mapping the application cloud-native stack infrastructure configurations; mapping logical flows between microservices and third-party components in the cloud-native application; creating and executing security tests on the mapped logical flows, infrastructure configurations and runtime functions to return tested runtime behavior; and analyzing the tested runtime behavior of the cloud native application to validate the potential vulnerable logical flows so as to return validated vulnerable flows.

Claims (29)

1 . A method for assessing vulnerable flows in a cloud-native application deployed in a runtime environment, the method comprising steps of:

deploying an autonomous testing component to the runtime environment, the autonomous testing component dynamically interacting with different components of the cloud-native application, the components of the cloud-native application including a cloud infrastructure, a plurality of application programming interfaces, and a plurality of microservices, wherein the autonomous testing component updates according to changes in the runtime environment without user input implementing updates to the autonomous testing component;

mapping, by the autonomous component, runtime functions in the plurality of microservices in the cloud-native application, wherein mapping the runtime functions comprises observing each microservice in the runtime environment and analyzing files on a file system that are accessed by the microservice, the runtime functions including input functions that receive input from external components, internal communication functions provide communication within a cluster in which one or more of the plurality of microservices are provided, and hazardous functions that may lead to vulnerabilities;

mapping stack infrastructure configurations of the cloud infrastructure of the cloud-native application;

mapping logical flows between the plurality of microservices and one or more third-party components in the cloud-native application based on an analysis of the inputs of the input functions and internal communication functions, said mapping of logical flows generating a list of potential vulnerable logical flows;

creating security tests to analyze runtime behavior to reduce false positives in the list of potential vulnerable flows;

executing the security tests on the mapped logical flows, the infrastructure configurations, and the runtime functions of the cloud-native application, wherein executing the security tests for a given logical flow of the mapped logical flows comprises:

creating a test input for an input function of the given logical flow;

injecting the test input directly into the input function of the given logical flow;

returning runtime behavior of the cloud-native application in response to the injecting of the test input; and

processing the runtime behavior of the cloud-native application to identify false positives in the list of potential vulnerable flows, thereby producing a reduced list of validated vulnerable flows, the processing of the runtime behavior comprising tracing how the test input reaches hazardous functions and changes that are applied to the test input while the test input went through the given logical flow; and

providing a visualization for display including information about at least some of the validated vulnerable flows.

2 . The method of claim 1 , wherein the mapping of the logical flows is further based on context propagation.

3 . The method of claim 1 , wherein said logical flows are mapped from preexisting functional tests.

4 . The method of claim 1 , further comprising:

providing context to said vulnerable logical flows so as to return a vulnerable flow assessment.

5 . The method of claim 4 , wherein said context includes details provided from said step of mapping said logical flows.

6 . The method of claim 4 , wherein said context includes configurations of said vulnerable flows.

7 . The method of claim 6 , wherein said configurations are received from said step of mapping said application stack configurations.

8 . The method of claim 1 , wherein providing the visualization comprises:

detecting an exploitable vulnerability in the reduced list of validated vulnerable flows; and

generating a reproduction scenario of the exploitable vulnerability, wherein the reproduction scenario includes data inputs that led to the exploitable vulnerability occurring, or generating a visual representation of the logical flow that generated the exploitable vulnerability.

9 . A method for assessing vulnerable flows in a cloud-native application deployed in a runtime environment, the method comprising steps of:

mapping runtime functions in microservices in the cloud-native application, wherein mapping the runtime functions comprises observing each microservice in the runtime environment and analyzing files on a file system that are accessed by the microservices, the runtime functions including input functions that receive input from external components, internal communication functions provide communication within a cluster in which one or more of the plurality of microservices are provided, and hazardous functions that may lead to vulnerabilities;

mapping application cloud-native stack infrastructure configurations;

mapping logical flows between the microservices and third-party components in the cloud-native application, the mapping of the logical flows based on an analysis of the inputs of the input functions and internal communication functions;

creating and executing security tests on said mapped logical flows, infrastructure configurations and the runtime functions to return tested runtime behavior, the security tests including injecting test inputs into the input functions of the mapped logical flows, wherein executing the security tests comprises:

deploying man instant application into the cloud-native application in the runtime environment, wherein the instant application dynamically interacts with different components of the cloud-native application, the components of the cloud-native application including a cloud infrastructure, application programming interfaces and the microservices, and wherein the instant application continually updates according to environment changes without user input implementing updates to the instant application; and

analyzing said tested runtime behavior of the cloud-native application to validate potential vulnerable logical flows so as to return validated vulnerable flows.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 21, 2025
From: GITLAB ISRAEL LTD.
To: GITLAB INC.
Reel/Frame 070291/0846 →
CHANGE OF NAME Recorded Feb 21, 2025
From: OXEYE SECURITY LTD
To: GITLAB ISREAL LTD
Reel/Frame 070296/0409 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 28, 2022
From: AGRON, DEAN; VIDER, RON
To: OXEYE SECURITY LTD.
Reel/Frame 059767/0903 →
Continuity (2)
Provisional Application 63180685 · Apr 28, 2021
Related Publication 20220350895A1 · Nov 3, 2022
References Cited (12)
US 9479526B1 · Yang · 2016 [cited by examiner]
US 11811801B2 · Chang · 2023 [cited by examiner]
US 20160315960A1 · Teilhet · 2016 [cited by examiner]
US 20170098071A1 · Stopel · 2017 [cited by examiner]
US 20180088935A1 · Church · 2018 [cited by examiner]
US 20190332366A1 · Natanzon · 2019 [cited by examiner]
US 20200082095A1 · Mcallister · 2020 [cited by examiner]
US 20200097662A1 · Hufsmith · 2020 [cited by examiner]
US 20200401379A1 · Appel · 2020 [cited by examiner]
US 20210133086A1 · Joyce · 2021 [cited by examiner]
US 20210334384A1 · Ranjan · 2021 [cited by examiner]
US 20220172067A1 · Kang · 2022 [cited by examiner]