IP Library Patent Application 15903499
Patent Application
App. No. 15/903,499

SYSTEMS AND METHODS FOR PREVENTING MALICIOUS NETWORK TRAFFIC FROM ACCESSING TRUSTED NETWORK RESOURCES

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 None
App. No.
15/903,499
Abstract

Systems, methods, and apparatuses prevent malicious network traffic from accessing or being transmitted to trusted network resources in a network environment. In one embodiment, a management microservice initializes a security microservice on a computing device and configures a network interface as a secure channel for communications with the security microservice. When the management microservice authenticates the network interface, the management microservice enables a data channel interface for the security microservice, allowing the security microservice to receive network traffic from other security microservices. Prior to enabling the data channel interface, the security microservice does not have an active interface with any other security microservices, which prevents any traffic, including malicious network traffic from reaching areas of the security microservice during the initialization process.

Claims (47)

1 . A computer-implemented method comprising:

receiving instructions to initialize a security microservice on a computing device;

initializing the security microservice on the computing device;

configuring a management network interface as a secure channel with the security microservice;

authenticating the management network interface;

enabling a data channel interface for the security microservice responsive to authenticating the management network interface, the data channel interface for receiving network traffic from one or more of a plurality of security microservices; and

executing a security action on the network traffic received at the enabled data channel interface.

2 . The computer-implemented method of claim 1 , wherein the security microservice is prevented from receiving the network traffic prior to enabling the data channel interface for the security microservice.

3 . The computer-implemented method of claim 1 , further comprising:

determining whether an interface microservice is running on the computing device; and

deploying the interface microservice on the computing device when the interface microservice is not running on the computing device.

4 . The computer-implemented method of claim 1 , wherein the network traffic is received at the enabled data channel interface of the security microservice from one of the interface microservice and one of the plurality of security microservices.

5 . The computer-implemented method of claim 1 , wherein the management network interface operates in a control plane, and wherein the data channel interface operates in a data plane.

6 . The computer-implemented method of claim 1 , further comprising:

receiving a security policy to apply to the network traffic via one or more interfaces.

7 . One or more non-transitory computer-readable storage media storing instructions which, when executed by one or more hardware processors, cause performance of a method comprising:

receiving instructions to initialize a security microservice on a computing device;

initializing the security microservice on the computing device;

configuring a management network interface as a secure channel with the security microservice;

authenticating the management network interface;

enabling a data channel interface for the security microservice responsive to authenticating the management network interface, the data channel interface for receiving network traffic from one or more of a plurality of security microservices; and

executing a security action on the network traffic received at the enabled data channel interface.

8 . The one or more non-transitory computer-readable storage media of claim 7 , wherein the security microservice is prevented from receiving the network traffic prior to enabling the data channel interface for the security microservice.

9 . The one or more non-transitory computer-readable storage media of claim 7 , further comprising:

determining whether an interface microservice is running on the computing device; and

deploying the interface microservice on the computing device when the interface microservice is not running on the computing device.

10 . The one or more non-transitory computer-readable storage media of claim 7 , wherein the network traffic is received at the enabled data channel interface of the security microservice from one of the interface microservice and one of the plurality of security microservices.

11 . The one or more non-transitory computer-readable storage media of claim 7 , wherein the management network interface operates in a control plane, and wherein the data channel interface operates in a data plane.

12 . The one or more non-transitory computer-readable storage media of claim 7 , further comprising:

receiving a security policy to apply to the network traffic via one or more interfaces.

13 . An apparatus comprising:

one or more hardware processors;

memory coupled to the one or more hardware processors, the memory storing instructions which, when executed by the one or more hardware processors, causes the apparatus to:

receive instructions to initialize a security microservice on a computing device;

initialize the security microservice on the computing device;

configure a management network interface as a secure channel with the security microservice;

authenticate the management network interface;

enable a data channel interface for the security microservice responsive to authenticating the management network interface, the data channel interface for receiving network traffic from one or more of a plurality of security microservices; and

execute a security action on the network traffic received at the enabled data channel interface.

14 . The apparatus of claim 13 , wherein the security microservice is prevented from receiving the network traffic prior to enabling the data channel interface for the security microservice.

15 . The apparatus of claim 13 , wherein the instructions further cause the apparatus to:

determine whether an interface microservice is running on the computing device; and

deploy the interface microservice on the computing device when the interface microservice is not running on the computing device.

16 . The apparatus of claim 13 , wherein the network traffic is received at the enabled data channel interface of the security microservice from one of the interface microservice and one of the plurality of security microservices.

17 . The apparatus of claim 13 , wherein the management network interface operates in a control plane, and wherein the data channel interface operates in a data plane.

18 . The apparatus of claim 13 , wherein the instructions further cause the apparatus to:

receive a security policy to apply to the network traffic via one or more interfaces.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 19, 2021
From: SHIELDX NETWORKS, INC.
To: FORTINET, INC.
Reel/Frame 055661/0470 →
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 Mar 21, 2018
From: AHUJA, RATINDER PAUL SINGH; NEDBAL, MANUEL; SHAH, SAMIR
To: SHIELDX NETWORKS, INC.
Reel/Frame 045307/0339 →