IP Library › Granted Patent US 11,469,976
Granted Patent B2
US 11,469,976 · App. 17/176,071 · Granted Oct 11, 2022

System and method for cloud-based control-plane event monitor

Inventors: Joe Baker (Burlington, MA); Ryan Plessner (Brighton, MA); Dan Weiss (Medford, MA); Nick Goodwin (Everett, MA); Laura Haiduck (Canton, MA); Daniel Kirsch (Belmont, MA)
Assignee: F5, Inc.
H04L43/04G06F11/0709G06F21/552G06F21/604H04L43/0876H04L63/1425H04L63/1433H04L63/20H04L67/1097H04L67/51
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,469,976
App. No.
17/176,071
Granted
Oct 11, 2022
Kind
B2
Abstract

A method for cloud-based, control-plane-event monitoring includes receiving control-plane events from a cloud-based element associated with a first and a second cloud environment. The received control-plane events are ingested from the cloud-based elements associated with the first and second cloud environments to generate a multiple-source data set from the control-plane events from the cloud-based elements associated with the first and second cloud environments. The multiple-source data set is then evaluated based on attributes of the first and second cloud environments in order to generate a common event data set. The common event data set is then processed using a rule set to generate an outcome.

Claims (31)

1. A method for cloud-based threat identification, the method implemented by a network traffic management system comprising one or more network traffic apparatuses, client devices, or server devices, the method comprising:

receiving a control-plane event associated with a threat from a cloud-based element associated with a first cloud environment;

receiving another control-plane event associated with the threat from another cloud-based element associated with a second cloud environment, wherein the threat operates across both the first cloud environment and the second cloud environment;

transforming a format of the received control-plane event associated with the threat from the cloud-based element associated with the first cloud environment to a common format and transforming another format of received another control-plane event associated with the threat from the another cloud-based element associated with the second cloud environment to the common format, wherein the format of the received control-plane event and the another format of the received another control-plane event are two different formats; and

processing the transformed control-plane event associated with the threat from the cloud-based element associated with the first cloud environment and the transformed another control-plane event associated with the threat from the another cloud-based element associated with the second cloud environment using a rule set to identify the threat.

2. The method for cloud-based threat identification of claim 1 further comprising generating a policy violation based on the identification of the threat.

3. The method for cloud-based threat identification of claim 1 further comprising generating an alert based on the identification of the threat.

4. The method for cloud-based threat identification of claim 1 further comprising reconfiguring an infrastructure based on the identification of the threat.

5. The method for cloud-based threat identification of claim 1 further comprising presenting the identified threat to a user using a single viewpoint.

6. The method for cloud-based threat identification of claim 1 wherein transforming the format of at least one of the received control-plane event associated with the threat from the cloud-based element associated with the first cloud environment to the common format and transforming the another format of the another control-plane event associated with the threat from the another cloud-based element associated with the second cloud environment to the common format comprises categorizing like properties into a single property.

7. The method for cloud-based threat identification of claim 1 wherein the receiving control-plane associated with the threat from the cloud-based element associated with the first cloud environment comprises receiving real-time continuous event information from an operating system kernel.

8. The method for cloud-based threat identification of claim 1 wherein the receiving control-plane event associated with the threat from the cloud-based element associated with the first cloud environment comprises receiving real-time continuous event information from a containerization platform.

9. The method for cloud-based threat identification of claim 1 wherein the threat comprises a change in an access level.

10. The method for cloud-based threat identification of claim 1 wherein the threat comprises a breach in the first cloud environment that happens at a same time as a breach in the second cloud environment.

11. The method for cloud-based threat identification of claim 1 wherein the threat comprises disabling monitoring in the first or second cloud environments.

12. The method for cloud-based threat identification of claim 1 wherein the received control plane event associated with the threat from the cloud-based element associated with the first cloud environment comprises a key management event, an access control event, a network process event, a user activity event, a file activity event, a policy change event, or an infrastructure change event.

13. A system comprising one or more network traffic management modules, networking modules, or server modules, memory comprising programmed instructions stored thereon, and one or more processors configured to be capable of executing the stored programmed instructions to:

receive a control-plane event associated with a threat from a cloud-based element associated with a first cloud environment;

receive another control-plane event associated with the threat from another cloud-based element associated with a second cloud environment, wherein the threat operates across both the first cloud environment and the second cloud environment;

transform a format of the received control-plane event associated with the threat from the cloud-based element associated with the first cloud environment to a common format and transforming another format of the received another control-plane event associated with the threat from the another cloud-based element associated with the second cloud environment to the common format, wherein the format of the received control-plane event and the another format of the received another control-plane event are two different formats; and

process the transformed control-plane event associated with the threat from the cloud-based element associated with the first cloud environment and the transformed another control-plane event associated with the threat from the another cloud-based element associated with the second cloud environment using a rule set to identify the threat.

14. A non-transitory computer readable medium having stored thereon instructions comprising executable code that, when executed by one or more processors, causes the processors to:

receive a control-plane event associated with a threat from a cloud-based element associated with a first cloud environment;

receive another control-plane event associated with the threat from another cloud-based element associated with a second cloud environment, wherein the threat operates across both the first cloud environment and the second cloud environment;

transform a format of the received control-plane event associated with the threat from the cloud-based element associated with the first cloud environment to a common format and transforming another format of the received another control-plane event associated with the threat from the another cloud-based element associated with the second cloud environment to the common format, wherein the format of the received control-plane event and the another format of the received another control-plane event are two different formats; and

process the transformed control-plane event associated with the threat from the cloud-based element associated with the first cloud environment and the transformed another control-plane event associated with the threat from the another cloud-based element associated with the second cloud environment using a rule set to identify the threat.

15. A network traffic management apparatus, comprising memory comprising programmed instructions stored thereon and one or more processors configured to be capable of executing the stored programmed instructions to:

receive a control-plane event associated with a threat from a cloud-based element associated with a first cloud environment;

receive another control-plane event associated with the threat from another cloud-based element associated with a second cloud environment, wherein the threat operates across both the first cloud environment and the second cloud environment;

transform a format of the received control-plane event associated with the threat from the cloud-based element associated with the first cloud environment to a common format and transforming another format of the received another control-plane event associated with the threat from the another cloud-based element associated with the second cloud environment to the common format, wherein the format of the received control-plane event and the another format of the received another control-plane event are two different formats; and

process the transformed control-plane event associated with the threat from the cloud-based element associated with the first cloud environment and the transformed another control-plane event associated with the threat from the another cloud-based element associated with the second cloud environment using a rule set to identify the threat.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 20, 2022
From: THREAT STACK, INC.
To: F5, INC.
Reel/Frame 058713/0079 →
Continuity (3)
Continuation 16297059 · Mar 8, 2019
Provisional Application 62784643 · Dec 24, 2018
Related Publication 20210184948A1 · Jun 17, 2021