EVENT SPECIFIC RELATIONSHIP GRAPH GENERATION AND APPLICATION IN A MACHINE DATA PROCESSING PLATFORM

• US 20170142140A1
• Filed: 01/27/2017
• Published: 05/18/2017
• Est. Priority Date: 08/31/2015
• Status: Active Grant

• Current Assignee: Splunk Inc.
• Original Assignee: Splunk Inc.
• Inventors: Bulusu, Ravi Prasad, Muddu, Sudhakar, Tryfonas, Christos
• Granted Patent: US 10,116,670 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/24578 using ranking
• CPC Class Codes: G06F 16/254 Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses
• CPC Class Codes: G06F 16/285 Clustering or classification
• CPC Class Codes: G06F 16/444 Spatial browsing, e.g. 2D maps, 3D or virtual spaces
• CPC Class Codes: G06F 16/9024 Graphs; Linked lists G06F16/9027 takes precedence
• CPC Class Codes: G06F 3/0482 Interaction with lists of selectable items, e.g. menus
• CPC Class Codes: G06F 3/0484 for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
• CPC Class Codes: G06F 3/04842 Selection of displayed objects or displayed text elements G06F3/0482 takes precedence
• CPC Class Codes: G06F 3/04847 Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
• CPC Class Codes: G06F 40/134 Hyperlinking
• CPC Class Codes: G06N 20/00 Machine learning
• CPC Class Codes: G06N 20/20 Ensemble learning
• CPC Class Codes: G06N 5/022 Knowledge engineering; Knowledge acquisition
• CPC Class Codes: G06N 5/04 Inference or reasoning models
• CPC Class Codes: G06N 7/01 Probabilistic graphical models, e.g. probabilistic networks
• CPC Class Codes: G06V 10/225 based on a marking or identifier characterising the area
• CPC Class Codes: H04L 2463/121 Timestamp cryptographic mechanisms or cryptographic arrangements involving time stamps H04L9/3297
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/145 involving simulating, designing, planning or modelling of a network
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 43/00 : Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/045 : for graphical visualisation of monitoring data
• CPC Class Codes: H04L 43/062 : related to network traffic
• CPC Class Codes: H04L 43/08 : Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 63/06 : for supporting key management in a packet data network cryptographic mechanisms or cryptographic arrangements for key management H04L9/08
• CPC Class Codes: H04L 63/1408 : by monitoring network traffic monitoring network traffic per se H04L43/00
• CPC Class Codes: H04L 63/1416 : Event detection, e.g. attack signature detection
• CPC Class Codes: H04L 63/1425 : Traffic logging, e.g. anomaly detection
• CPC Class Codes: H04L 63/1433 : Vulnerability analysis
• CPC Class Codes: H04L 63/1441 : Countermeasures against malicious traffic countermeasures against attacks on cryptographic mechanisms H04L9/002
• CPC Class Codes: H04L 63/20 : for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H05K 999/99 : dummy group

Abstract

A security platform employs a variety techniques and mechanisms to detect security related anomalies and threats in a computer network environment. The security platform is “big data” driven and employs machine learning to perform security analytics. The security platform performs user/entity behavioral analytics (UEBA) to detect the security related anomalies and threats, regardless of whether such anomalies/threats were previously known. The security platform can include both real-time and batch paths/modes for detecting anomalies and threats. By visually presenting analytical results scored with risk ratings and supporting evidence, the security platform enables network security administrators to respond to a detected anomaly or threat, and to take action promptly.

Claims

1. A method comprising:

receiving event data representing an event on a computer network, the event data being indicative of a plurality of entities and an action involved in the event;

identifying the entities and a relationship between the entities, based on the action in the event data; and

creating, for the event, a record of the relationship between the entities by using a data structure representing a relationship graph, the relationship graph including at least two nodes and an edge between the two nodes, each node representing one of the entities, the edge representing the relationship between the entities.

2. The method of claim 1, further comprising:

attaching the record of the relationship to the event data representing the event.

3. The method of claim 1, further comprising:

sending the event data including the record of the relationship to a distributed messaging system.

4. The method of claim 1, further comprising:

sending the event data including the record of the relationship to a distributed messaging system that is implemented based on Apache Kafka™

.

5. The method of claim 1, further comprising:

sending the event data including the record of the relationship to an event processing engine for further processing, wherein the event processing engine is operable to perform analytics based on event data representing a plurality of events and relationship graphs associated with the plurality of events.

6. The method of claim 1, further comprising:

sending the event data including the record of the relationship to an event processing engine for further processing, wherein the event processing engine is operable to perform analytics on event data representing a plurality of events and relationship graphs associated with the plurality of events; and

using the event processing engine to identify security-oriented anomalies in the plurality of events.

7. The method of claim 1, further comprising:

sending the record of the relationship to an event processing engine for further processing, wherein the event processing engine is operable to use a downstream entity to perform analytics on event data representing a plurality of events and relationship graphs associated with the plurality of events.

8. The method of claim 1, further comprising:

repeating said receiving, identifying, and generating steps for event data representing each of a plurality of events on the computer network to generate a relationship graph for each of the plurality of events.

9. The method of claim 1, further comprising:

repeating said receiving, identifying, and generating steps for event data representing each of a plurality of events on the computer network to generate a relationship graph for each of the plurality of events; and

combining the relationship graphs for the plurality of events into a composite relationship graph.

10. The method of claim 1, further comprising:

repeating said receiving, identifying, and generating steps for event data representing each of a plurality of events on the computer network to generate a relationship graph for each of the plurality of events; and

combining the relationship graphs for the plurality of events into a composite relationship graph,

wherein the composite relationship graph includes all identified relationships among all identified entities involved in the plurality of events.

11. The method of claim 1, wherein said identifying step comprises:

tokenizing the event data by extracting, as tokens, a key or a value or a key-value pair in the event data; and

parsing the event data based on a predetermined data format that specifies which tokens represent entities and which tokens represent actions in the extracted tokens.

12. The method of claim 1, wherein said identifying step comprises:

parsing the event data based on a predetermined data format that specifies which data represent entities and which data represent the action in the event.

13. The method of claim 1, wherein said identifying step comprises:

parsing the event data based on a predetermined data format that specifies which data represent entities and which data represent the action in the event,

wherein the predetermined data format comprises a data format representing output from at least one of;

an active directory, a proxy, a firewall, a web gateway, a virtual private network (VPN) connection, an intrusion detection system, a network traffic analyzer, or a malware engine.

14. The method of claim 1, wherein identifying the entities and the action in the event comprises:

tokenizing the event data by extracting, as tokens, a key or a value or a key-value pair in the event.

15. The method of claim 1, wherein the action is performed by one entity with respect to another entity, and wherein the identified relationship between the entities is identified based on the action.

16. The method of claim 1, wherein the identified relationship between the entities is indicative of the action, and wherein the identified relationship is identified based on comparing the action with a table of identifiable relationships.

17. The method of claim 1, wherein said identifying step comprises:

detecting a data format of the event data.

18. The method of claim 1, further comprising:

issuing a query to a data processing system that is operable to perform the query against data stored in a distributed file system,

wherein said receiving step includes receiving the event data as a result of the query from the processing system.

19. The method of claim 1, further comprising:

issuing a query to a data processing system that is operable to perform the query against data stored in a distributed file system,

wherein said receiving step includes receiving the event data as a result of the query from the processing system, and

wherein the data processing system includes executing a version of Hadoop MapReduce™

, and wherein the distributed file system comprises Hadoop Distributed File System (HDFS)™

.

20. The method of claim 1, further comprising:

requesting a machine on the computer network to transmit the event data, and wherein said receiving event data occurs in response to the machine on the computer network transmitting the event data.

21. The method of claim 1, wherein said identifying step comprises identifying a timestamp in the event.

22. The method of claim 1, further comprising:

configuring said identifying step by making an adjustment to a configuration file.

23. The method of claim 1, wherein the event data comprises timestamped machine data.

24. The method of claim 1, wherein the method is performed as part of an extract-transform-load stage of at least one of a distributed event processing system or an anomaly detection system.

25. The method of claim 1, further comprising:

identifying a plurality of attributes of the event, based on the event data; and

adding a view identifier to the event data to allow a downstream entity, by having designated the view identifier, to receive select information extracted from and/or generated based on the plurality of attributes of the event, through an interface identified by the view identifier.

26. The method of claim 1, further comprising:

identifying a plurality of attributes of the event, based on the event data; and

adding a view identifier to the event data to allow a downstream entity, by having designated the view identifier, to receive select information extracted from and/or generated based on the plurality of attributes of the event, through an interface identified by the view identifier,

wherein the interface further includes logic operable to perform an action on the attributes of the event to generate the information.

27. The method of claim 1, wherein each of the entities is of a type that is one of:

user, device, application, uniform resource locator (URL), session, or threat; and

wherein at least two of the entities are not of the same type.

28. The method of claim 1, wherein each of the entities is of a type that is one of:

user, device, application, uniform resource locator (URL), session, or threat; and

wherein the action includes at least one of;

uses, visits, connects to, logs in, or logs out.

29. A computer system comprising:

a communication device; and

a processor configured to;

receive, via the communication device, event data representing an event on a computer network, the event data being indicative of a plurality of entities and an action involved in the event;

identify the entities and a relationship between the entities, based on the action in the event data; and

create, for the event, a record of the relationship between the entities by using a data structure representing a relationship graph, the relationship graph including at least two nodes and an edge between the two nodes, each node representing one of the entities, the edge representing the relationship between the entities.

30. A non-transitory machine-readable storage medium for use in a processing system, the non-transitory machine-readable storage medium storing instructions, an execution of which in the processing system causes the processing system to perform operations comprising:

receiving event data representing an event on a computer network, the event data being indicative of a plurality of entities and an action involved in the event;

identifying the entities and a relationship between the entities, based on the action in the event data; and

creating, for the event, a record of the relationship between the entities by using a data structure representing a relationship graph, the relationship graph including at least two nodes and an edge between the two nodes, each node representing one of the entities, the edge representing the relationship between the entities.