IP Library Granted Patent US 11,539,731
Granted Patent B2
US 11,539,731 · App. 17/080,659 · Granted Dec 27, 2022

Dynamic hyper context-driven microsegmentation

Inventors: Srinivas Akella (San Jose, CA); Arun Kumar Dheena (San Jose, CA)
Assignee: NETSKOPE, INC.
H04L63/1425H04L63/0876H04L63/20
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,539,731
App. No.
17/080,659
Granted
Dec 27, 2022
Kind
B2
Abstract

Systems and methods for dynamic, hyper context-based microsegmentation are described. In one aspect, span traffic associated with a computing device on a network is processed. Meta data associated with the span traffic is transmitted to a hyper context cloud server. It is determined whether the span traffic meta data matches a policy condition. Responsive to the span traffic meta data matching a policy condition, a policy is triggered. It is determined whether an action associated with the triggered policy is segment. Responsive to determining that the action is segment, a MAC address of the computing device is added to a segment name provided in the policy. The segment name is pushed to one or more enforcement points associated with the network.

Claims (34)

1. A method for dynamic hyper context-driven segmentation comprising:

processing span traffic associated with a computing device on a network:

monitoring span traffic and collecting computer network hyper context associated with the computing device;

transmitting span traffic meta data to a hyper context cloud server:

determining by the hyper context cloud server whether the span traffic meta data matches a policy condition corresponding to a set of computer network hyper context comprising a list of network connectivity properties and computing device properties;

responsive to the span traffic meta data matching a policy condition by identifying the collected computer network hyper context from within the hyper context set, triggering a policy;

determining whether an action associated with the triggered policy is segment in conjunction with the collected network hyper context;

responsive to determining that the action is segment, adding a MAC address of the computing device to a segment name provided in the policy; and

pushing, by a cloud controller collaborated with the hyper context cloud server, the provided segment name to one or more network enforcement points associated with the network.

2. The method of claim 1 , wherein the processing is performed by a hyper context network sensor.

3. The method of claim 2 , further comprising the hyper context network sensor monitoring the span traffic prior to the processing.

4. The method of claim 1 , further comprising generating span traffic meta data responsive to the processing.

5. The method of claim 1 , wherein pushing the segment name is performed by a cloud controller.

6. The method of claim 1 , wherein the computing device is any of a desktop computer, a laptop computer, a mobile device, an internet-of-things (IoT) device, a printer, a smart television, an audio conferencing device, or a medical smart device.

7. The method of claim 1 , wherein a policy includes an ownership condition, a risk condition, and a compliant condition.

8. An apparatus for dynamic hyper context-driven segmentation comprising:

one or more processor devices;

a hyper context network sensor associated with a network, the hyper context network sensor being configured to process span traffic and collect computer network hyper context associated with a computing device on the network and generate span traffic meta data;

a hyper context cloud server configured to receive the span traffic meta data, determine whether the span traffic meta data matches a policy condition corresponding to a set of computer network hyper context comprising a list of network connectivity properties and computing device properties,

responsive to the span traffic meta data matching a policy condition by identifying the collected computer network hyper context from within the hyper context set, trigger a policy,

determine whether an action associated with the trigger policy is segment in conjuction with the collected network hyper context, and

responsive to determining that the action is segment, add a MAC address of the computing device to a segment name provided in the policy; and

a cloud controller, collaborated with the hyper context cloud server, configured to push the segment name to one or more network enforcement points associated with the network.

9. The apparatus of claim 8 , wherein the hyper context network sensor monitors the span traffic prior to processing the span traffic.

10. The apparatus of claim 8 , wherein the computing device is any of a desktop computer, a laptop computer, a mobile device, an internet-of-things (IoT) device, a printer, a smart television, an audio conferencing device, or a medical smart device.

11. The apparatus of claim 8 , further comprising a network switch configured to interface a computing device with the network via an Ethernet connection.

12. The apparatus of claim 8 , wherein the network includes one or more wireless access points, wherein each access point enables a computing device to connect to the network via a wireless communication link.

13. The apparatus of claim 12 , wherein a wireless communication link is any of Wi-Fi, Bluetooth, Bluetooth Low Energy (BLE), ZigBee, Long-Term Evolution (LTE), Lorawan, or zwave.

14. The apparatus of claim 8 , wherein the policy includes an ownership condition, a risk condition, and a compliant condition.

15. The apparatus of claim 8 , wherein the network is a computer network.

16. The apparatus of claim 8 , wherein the segment is a VLAN.

17. The apparatus of claim 16 , further comprising a DHCP server configured to store a VLAN pool that includes a listing of one or more VLANs.

18. The apparatus of claim 8 , wherein an enforcement point is any of a cloud-based access point, a cloud radius provider, or a hyper context network sensor.

19. The apparatus of claim 8 , wherein the hyper context network sensor enforces the action to one or more network access controllers, local radius servers, and DHCP servers associated with the network.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 30, 2022
From: WOOTCLOUD INC.
To: NETSKOPE, INC.
Reel/Frame 060943/0474 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 26, 2020
From: AKELLA, SRINIVAS; DHEENA, ARUN KUMAR
To: WOOTCLOUD INC.
Reel/Frame 054170/0243 →
Continuity (1)
Related Publication 20220131882A1 · Apr 28, 2022
Cited By (1)
US 12,316,647