Privilege inference and monitoring based on network behavior

Patent metadata

Field	Value
Publication number	US-10277618-B1
Application number	US-201816174051-A
Country	US
Kind code	B1
Filing date	Oct 29, 2018
Priority date	May 18, 2018
Publication date	Apr 30, 2019
Grant date	Apr 30, 2019

Abstract

Embodiments are directed to monitoring network traffic. A monitoring engine may monitor network traffic associated with entities in one or more networks. A device relation model may be provided based on the entities and the network traffic. An inference engine associate the entities with privilege levels based on the device relation model based on an amount of access or an amount of control that source entities exert over the target entities. An anomaly engine may determine one or more interactions between the source entities and the target entities based on the monitored network traffic. The anomaly engine may generate escalation events based on the interactions associated with the source entities and the target entities where the target entities have a higher privilege level than the source entities. The anomaly engine may provide the escalation events to one or more users.

First claim

What is claimed as new and desired to be protected by Letters Patent of the United States is:

1. A method for monitoring network traffic using one or more network computers, wherein execution of instructions by the one or more network computers perform the method comprising:
instantiating a monitoring engine to perform actions, including:
monitoring network traffic associated with a plurality of entities in one or more networks; and
providing a device relation model based on the network traffic, the plurality of entities, and the one or more metrics based on the monitored network traffic; and

instantiating an inference engine to perform actions, including:
associating the plurality of entities with one or more privilege levels based on one or more device relation models and the one or more metrics; and
increasing the one or more privilege levels for a source entity based on one or more metric values that are associated with one or more target entities that are linked to the source entity; and

instantiating an anomaly engine to perform actions, including:
determining one or more interactions between one or more source entities and the one or more target entities;
providing one or more escalation events to one or more users based on the one or more interactions and the one or more privilege levels associated with the one or more source entities; and
employing related credential information employed with one or more different applications having related activity from the one or more other activities to identify one or more sources of privilege escalation.

2. The method of claim 1 , wherein the anomaly engine performs further actions, comprising:
determining each of the one or more users that is associated with one or more privilege policies; and
employing the one or more privilege policies to determine which of the one or more escalation events to provide to each of the one or more users.

3. The method of claim 1 , wherein the anomaly engine performs further actions, comprising:
employing one or more responses by the one or more users to the one or more provided escalation events to modify one or more privilege policies associated with the one or more users.

4. The method of claim 1 , further comprising:
employing the monitoring engine to perform further actions including discovering a new entity in the one or more networks based on privilege activity monitoring; and
employing the inference engine to perform further actions, including:
adding the new entity to a dependency graph as a critical entity based on one or more of network conditions, entity behavior, or entity characteristics; and
adding one or more inferred privilege levels to the critical entity in the dependency graph based on one or more of privilege activity information or privilege relation information.

5. The method of claim 1 , further comprising:
employing the monitoring engine to perform further actions including discovering a new entity in the one or more networks based on protocol analysis and identifying remote access behavior directed to the one or more entities; and
employing the inference engine to perform further actions, including:
adding the new entity to an administration graph based on one or more of relationship information detected during administrative activities by the new entity; and
adding one or more inferred privilege levels to the new entity in the administration graph based on one or more of privilege activity information or privilege relation information.

6. The method of claim 1 , wherein the anomaly engine performs further actions, comprising:
traversing the one or more device relation models to trace network flows that pass through the one or more entities; and
determine network traffic flows that are associated with one or more different applications having related activity from one or more other entities.

7. A system for monitoring network traffic in a network:
one or more network computers, comprising:
one or more memories that store instructions; and
one or more processors that execute instructions that perform actions, including:
instantiating a monitoring engine to perform actions, including:
monitoring network traffic associated with a plurality of entities in one or more networks; and
providing a device relation model based on the network traffic, the plurality of entities, and the one or more metrics based on the monitored network traffic; and

instantiating an inference engine to perform actions, including:
associating the plurality of entities with one or more privilege levels based on one or more device relation models and the one or more metrics; and
increasing the one or more privilege levels for a source entity based on one or more metric values that are associated with one or more target entities that are linked to the source entity; and

instantiating an anomaly engine to perform actions, including:
determining one or more interactions between one or more source entities and the one or more target entities;
providing one or more escalation events to one or more users based on the one or more interactions and the one or more privilege levels associated with the one or more source entities; and
employing related credential information employed with one or more different applications having related activity from the one or more other activities to identify one or more sources of privilege escalation.

8. The system of claim 7 , wherein the anomaly engine performs further actions, comprising:
determining each of the one or more users that is associated with one or more privilege policies; and
employing the one or more privilege policies to determine which of the one or more escalation events to provide to each of the one or more users.

9. The system of claim 7 , wherein the anomaly engine performs further actions, comprising:
employing one or more responses by the one or more users to the one or more provided escalation events to modify one or more privilege policies associated with the one or more users.

10. The system of claim 7 , further comprising:
employing the monitoring engine to perform further actions including discovering a new entity in the one or more networks based on privilege activity monitoring; and
employing the inference engine to perform further actions, including:
adding the new entity to a dependency graph as a critical entity based on one or more of network conditions, entity behavior, or entity characteristics; and
adding one or more inferred privilege levels to the critical entity in the dependency graph based on one or more of privilege activity information or privilege relation information.

11. The system of claim 7 , further comprising:
employing the monitoring engine to perform further actions including discovering a new entity in the one or more networks based on protocol analysis and identifying remote access behavior directed to the one or more entities; and
employing the inference engine to perform further actions, including:
adding the new entity to an administration graph based on one or more of relationship information detected during administrative activities by the new entity; and
adding one or more inferred privilege levels to the new entity in the administration graph based on one or more of privilege activity information or privilege relation information.

12. The system of claim 7 , wherein the anomaly engine performs further actions, comprising:
traversing the one or more device relation models to trace network flows that pass through the one or more entities; and
determine network traffic flows that are associated with one or more different applicati

Assignees

• Extrahop Networks Inc

Inventors

• Wu xue jun
• Chen Songqian
• Kazakova Olga

Classifications

• H04L41/046

  comprising network management agents or mobile agents therefor · CPC title

• H04L63/1425 Primary

  Traffic logging, e.g. anomaly detection · CPC title

• H04L63/105

  Multiple levels of security · CPC title

• H04L63/1416

  Event detection, e.g. attack signature detection · CPC title

• H04L43/062

  related to network traffic · CPC title