IP Library Granted Patent US 11,849,000
Granted Patent B2
US 11,849,000 · App. 17/682,644 · Granted Dec 19, 2023

Using real-time monitoring to inform static analysis

Inventors: Oliver M. Williams (San Francisco, CA); Yijou Chen (Cupertino, CA)
Assignee: LACEWORK, INC.
H04L67/535G06F9/455G06F9/545G06F16/9024G06F16/9038G06F16/9535G06F16/9537G06F21/57H04L43/045H04L43/06H04L63/10H04L67/306G06F16/2456
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 11,849,000
App. No.
17/682,644
Granted
Dec 19, 2023
Kind
B2
Abstract

Using real-time monitoring to inform static analysis, including: inspecting, using one or more static code analysis techniques, one or more components of a cloud deployment; detecting, using data gathered during the execution of the component in the cloud deployment, a condition; and modifying, based on the detected condition, the one or more static code analysis techniques.

Claims (29)

1. A method of using real-time monitoring to inform static analysis, the method comprising:

inspecting, using one or more static code analysis techniques, one or more components of a cloud deployment;

detecting, using data gathered during the execution of the component in the cloud deployment, a condition that occurred during the execution of the component, wherein the condition comprises at least one of: a policy violation, a rule violation, or an anomaly; and

modifying, based on the detected condition, the one or more static code analysis techniques to capture the detected condition.

2. The method of claim 1 further comprising modifying, based on one or more modifications to the static code analysis techniques, real-time monitoring of the component.

3. The method of claim 1 further comprising detecting, using the modified one or more static code analysis techniques, the condition.

4. The method of claim 1 further comprising determining whether the condition could have been detected using static code analysis techniques.

5. The method of claim 1 wherein static code analysis techniques deployed for a first customer are different than static code analysis techniques deployed for a second customer.

6. The method of claim 1 wherein the condition was detected for a component in a cloud deployment of a first customer and the static code analysis techniques that were modified are used for inspecting components in a cloud deployment of a second customer.

7. The method of claim 1 wherein the static code analysis techniques are used to inspect source code in a code repository prior to deploying the source code in the cloud deployment.

8. A system for using real-time monitoring to inform static analysis, the system comprising at least one processor and memory storing computer program instructions that, when executed, cause the system to carry out the steps of:

inspecting, using one or more static code analysis techniques, one or more components of a cloud deployment;

detecting, using data gathered during the execution of the component in the cloud deployment, a condition that occurred during the execution of the component, wherein the condition comprises at least one of: a policy violation, a rule violation, or an anomaly; and

modifying, based on the data gathered during the execution of the component in the cloud deployment, the one or more static code analysis techniques to capture the detected condition.

9. The system of claim 8 wherein the computer program instructions, when executed, further cause the system to carry out the step of modifying, based on one or more modifications to the static code analysis techniques, real-time monitoring of the component.

10. The system of claim 8 wherein the computer program instructions, when executed, further cause the system to carry out the step of detecting, using the modified one or more static code analysis techniques, the condition.

11. The system of claim 8 wherein the computer program instructions, when executed, further cause the system to carry out the step of determining whether the condition could have been detected using static code analysis techniques.

12. The system of claim 8 wherein static code analysis techniques deployed for a first customer are different than static code analysis techniques deployed for a second customer.

13. The system of claim 8 wherein the condition was detected for a component in a first cloud deployment and the static code analysis techniques that were modified are used for inspecting components in a second cloud deployment.

14. The system of claim 8 wherein the static code analysis techniques are used to inspect source code in a code repository prior to deploying the source code in the cloud deployment.

15. A computer program product for using real-time monitoring to inform static analysis, the computer program product disposed on a non-transitory computer readable medium, the computer program product including computer program instructions that, when executed, carry out the steps of:

detecting, using data gathered during the execution of the component in the cloud deployment, a condition that occurred during the execution of the component, wherein the condition comprises at least one of: a policy violation, a rule violation, or an anomaly;

determining whether the condition could have been detected using static code analysis techniques; and

modifying, based on the detected condition, one or more static code analysis techniques to capture the detected condition.

16. The computer program product of claim 15 further comprising computer program instructions that, when executed, carry out the step of modifying, based on one or more modifications to the static code analysis techniques, real-time monitoring of the component.

17. The computer program product of claim 15 further comprising computer program instructions that, when executed, carry out the step of detecting, using the modified one or more static code analysis techniques, the condition.

18. The computer program product of claim 15 wherein static code analysis techniques deployed for a first customer are different than static code analysis techniques deployed for a second customer.

19. The computer program product of claim 15 wherein the condition was detected for a component in a cloud deployment of a first customer and the static code analysis techniques that were modified are used for inspecting components in a cloud deployment of a second customer.

20. The computer program product of claim 15 wherein the static code analysis techniques are used to inspect source code in a code repository prior to deploying the source code in the cloud deployment.

Assignments (2)
MERGER Recorded Oct 7, 2024
From: LACEWORK, INC.
To: FORTINET, INC.
Reel/Frame 069269/0377 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 28, 2022
From: WILLIAMS, OLIVER M.; CHEN, YIJOU
To: LACEWORK, INC.
Reel/Frame 059120/0265 →
Cited By (5)
US 12,417,822 US 12,481,758 US 12,506,762 US 12,591,691 US 12,664,280