IP Library Granted Patent US 9,716,617
Granted Patent B1
US 9,716,617 · App. 15/182,573 · Granted Jul 25, 2017

Dynamic, load-based, auto-scaling network security microservices architecture

Inventors: Ratinder Paul Singh Ahuja (Saratoga, CA); Manuel Nedbal (Santa Clara, CA)
Assignee: ShieldX Networks, Inc.
H04L41/08H04L67/1097H04L67/141H04L69/324
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 9,716,617
App. No.
15/182,573
Granted
Jul 25, 2017
Kind
B1
Abstract

System, methods, and apparatuses used to monitor network traffic of a datacenter and report security threats are described. For example, one embodiment scales out a hierarchy of microservices in a security system. In particular, the embodiment calls for scaling out a hierarchy of microservices in such a security system, creating a new microservice of a first hierarchy, configuring data plane connectivity between the new microservice and a microservice of a second, higher-level hierarchy; configuring data plane connectivity between the new microservice and a microservice of a third, lower-level hierarchy; and configuring the microservices of the third level of hierarchy to include the new microservice in load balancing decisions to the first hierarchy.

Claims (39)

1. A computer-implemented method comprising:

creating a first security microservice of a first level of a hierarchy of security microservices to scale up the first level of the hierarchy, wherein there exists, prior to a creation of the first security microservice, a microservice of a same hierarchy level as the first microservice;

configuring data plane connectivity between the first security microservice and a second security microservice of a second, higher-level of a hierarchy of security microservices, wherein any new security microservice of the hierarchy is configured to use the data plane;

configuring data plane connectivity between the first security microservice and a third security microservice of a third, lower-level of the hierarchy of security microservices;

configuring at least one microservice of the third, lower-level of the hierarchy of security microservices to include information from the first microservice in load balancing decisions to the first level of the hierarchy of security microservices; and

processing a packet from a flow of packets with a security microservice of the third, lower-level of the hierarchy;

passing the processed packet from the security microservice of the third, lower-level of the hierarchy to the first security microservice; and

processing a processed packet with the first security microservice, wherein each level of the hierarchy of security microservices performs a different security operation.

2. The computer-implemented method of claim 1 wherein the first microservice is created by an existing microservice.

3. The computer-implemented method of claim 2 wherein the existing microservice is a configuration microservice.

4. The computer-implemented method of claim 2 wherein the first security and existing microservices communicate over a backplane.

5. The computer-implemented method of claim 1 wherein the load balancing decision utilizes information from microservices of a higher-level hierarchy than the first hierarchy.

6. The computer-implemented method of claim 1 wherein data plane connectivity is configured through communication on a backplane.

7. The computer-implemented method of claim 1 wherein a backplane and data plane comprise managed networks.

8. A non-transitory computer-readable medium storing instructions, which when executed by a hardware processor cause the processor to perform a method, the method comprising:

creating a first security microservice of a first level of a hierarchy of security microservices to scale up the first level of the hierarchy, wherein there exists, prior to a creation of the first security microservice, a microservice of a same hierarchy level as the first microservice;

configuring data plane connectivity between the first security microservice and a second security microservice of a second, higher-level of a hierarchy of security microservices, wherein any new security microservice of the hierarchy is configured to use the data plane;

configuring data plane connectivity between the first security microservice and a third security microservice of a third, lower-level of the hierarchy of security microservices;

configuring at least one microservice of the third, lower-level of the hierarchy of security microservices to include information from the first microservice in load balancing decisions to the first level of the hierarchy of security microservices; and

processing a packet from a flow of packets with a security microservice of the third, lower-level of the hierarchy;

passing the processed packet from the security microservice of the third, lower-level of the hierarchy to the first security microservice; and

processing a processed packet with the first security microservice, wherein each level of the hierarchy of security microservices performs a different security operation.

9. The non-transitory computer-readable medium of claim 8 wherein the first microservice is created by an existing microservice.

10. The non-transitory computer-readable medium of claim 9 wherein the existing microservice is a configuration microservice.

11. The non-transitory computer-readable medium of claim 9 wherein the first security and existing microservices communicate over a backplane.

12. The non-transitory computer-readable medium of claim 8 wherein the load balancing decisions utilize information from microservices of a higher-level hierarchy than the first hierarchy.

13. The non-transitory computer-readable medium of claim 8 wherein data plane connectivity is configured through communication on a backplane.

14. An apparatus comprising:

a hardware processor to execute instructions; and

memory coupled to the processor, the memory to store instructions which when executed by the processor cause:

creating a first security microservice of a first level of a hierarchy of security microservices to scale up the first level of the hierarchy, wherein there exists, prior to a creation of the first security microservice, a microservice of a same hierarchy level as the first microservice;

configuring data plane connectivity between the first security microservice and a second security microservice of a second, higher-level of a hierarchy of security microservices, wherein any new security microservice of the hierarchy is configured to use the data plane;

configuring data plane connectivity between the first security microservice and a third security microservice of a third, lower-level of the hierarchy of security microservices;

configuring at least one microservice of the third, lower-level of the hierarchy of security microservices to include information from the first microservice in load balancing decisions to the first level of the hierarchy of security microservices; and

processing a packet from a flow of packets with a security microservice of the third, lower-level of the hierarchy;

passing the processed packet from the security microservice of the third, lower-level of the hierarchy to the first security microservice; and

processing a processed packet with the first security microservice, wherein each level of the hierarchy of security microservices performs a different security operation.

15. The apparatus of claim 14 , wherein the microservices communicate over a virtual backplane.

16. The apparatus of claim 14 , the load balancing decisions utilize information from microservices of a higher-level hierarchy than the first hierarchy.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 13, 2021
From: SHIELDX NETWORKS, INC.
To: FORTINET, INC.
Reel/Frame 056227/0125 →
RELEASE OF SECURITY INTEREST Recorded Mar 15, 2021
From: COMERICA BANK
To: SHIELDX NETWORKS, INC.
Reel/Frame 055585/0847 →
SECURITY INTEREST Recorded Jul 27, 2020
From: SHIELDX NETWORKS, INC.
To: COMERICA BANK
Reel/Frame 053313/0544 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 14, 2016
From: AHUJA, RATINDER PAUL SINGH; NEDBAL, MANUEL
To: SHIELDX NETWORKS, INC.
Reel/Frame 038913/0841 →