System and method for attributing user behavior from multiple technical telemetry sources

Abstract

Systems and methods for attributing user behavior from multiple technical telemetry sources are provided. An example method includes determining that the user has logged into the computing device, in response of the determination, collecting log data from a plurality of telemetry sources associated with the computing device, extracting, from the log data, activity data concerning activities of the computing device, analyzing the activity data to determine that the activity data are attributed to the user, generating, based on the activity data, behavior attributes of the user, associating the behavior attributes with a unique identifier of the computing device, and estimating security integrity of the computing device based on a comparison of the behavior attributes to reference behavior attributes. The reference behavior attributes include further behavior attributes determined using log data of at least one further computing device associated with the user.

Description

TECHNICAL FIELD

The present disclosure relates generally to data processing and, more particularly, to systems and methods for attributing user behavior from multiple technical telemetry sources.

BACKGROUND

Enterprises use computer networks for providing services, content, and offering products. The computer networks can connect both low-risk assets and critical enterprise assets. The low-risk assets can be vulnerable to hacker attacks, computer viruses, and malicious software that may lead to loss or leak of critical data. To get to the critical data attackers can target low-risk assets in order to enter the internal network. Inside the internal network and behind the hardware firewall, attackers can move across the internal network to gain access to critical enterprise assets.

SUMMARY

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

Provided are systems and methods for attributing user behavior from multiple technical telemetry sources. According to an example embodiment, a method for attributing user behavior from multiple technical telemetry sources may include determining that the user has logged into the computing device. The method may include, in response to the determination, collecting log data from a plurality of telemetry sources associated with the computing device. The method may include extracting, from the log data, activity data concerning activities of the computing device. The method may include analyzing the activity data to determine that the activity data are attributed to the user within a graph.

The plurality of the telemetry sources may include one of the following: logs of endpoint security applications (commonly known as Endpoint Protection Platforms or security agents, for example, Tanium™ or Crowdstrike™) installed on the computing device, flow logs from a router or a switch used for communications with the computer device, logs from a cloud-based network or access Application Programming Interfaces (APIs) (for example, Virtual Private Cloud (VPC) flow logs or CloudTrail Identity and Access Management (IAM) logs in Amazon Web Services (AWS™)), logs of operations of the computing devices, and logs of an identity management system.

Extracting the activity data may include determining a network address of the computing device, a list of active directories and files being accessed on the computing device, a list of applications being executed by the computing device, a list of network addresses of websites and other business applications associated with the computing device, types of connections to the websites and application servers (for example, an Amazon Simple Storage Service (S3) object store providing data storage services within AWS), an amount of data transferred between the computing device and the applications, and a type of operations conducted (for example, READ or WRITE operations against a file within an S3 object store).

The method may further include generating, based on the activity data, behavior attributes of the user and associating the behavior attributes with a unique identifier of the computing device. The unique identifier includes a media access control (MAC) address of the computing device.

Generating the behavior attributes may include creating a graph with nodes representing the applications and the websites and edges representing relationships between the user and the applications.

The method may include estimating security integrity of the computing device based on comparison of the behavior attributes to reference behavior attributes. The reference behavior attributes include further behavior attributes determined using log data of at least one further computing device associated with the user. The reference behavior attributes can be determined based on a plurality of further behavior attributes determined using further log data collected for a plurality of further computing devices associated with a plurality of further users having the same role within an enterprise.

The method may include, prior to the determining that the user has logged into the computer device, collecting further log data from the plurality of telemetry sources associated with the computing device. The method may include, prior to extracting the activity data, excluding the further log data from the log data in order to generate a baseline of the computer device without a user activity. The baseline may be used to determine a difference between a steady state of the computer device without the user activity and a state of the computer device with the user activity which represents the activity which can be attributed to the user.

According to another embodiment, a system for attributing user behavior from multiple technical telemetry sources is provided. The system may include at least one processor and a memory storing processor-executable codes, wherein the processor can be configured to implement the operations of the above-mentioned method for attributing user behavior from multiple technical telemetry sources.

According to yet another aspect of the disclosure, there is provided a non-transitory processor-readable medium, which stores processor-readable instructions. When the processor-readable instructions are executed by a processor, they cause the processor to implement the above-mentioned method for attributing user behavior from multiple technical telemetry sources.

Additional objects, advantages, and novel features will be set forth in part in the detailed description section of this disclosure, which follows, and in part will become apparent to those skilled in the art upon examination of this specification and the accompanying drawings or may be learned by production or operation of the example embodiments. The objects and advantages of the concepts may be realized and attained by means of the methodologies, instrumentalities, and combinations particularly pointed out in the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements.

FIG. 1 is a block diagram of an environment, in which systems and methods for attributing user behavior from multiple technical telemetry sources can be implemented, according to some example embodiments.

FIG. 2 is schematic showing functionalities of a behavior attributes monitoring system, according to an example embodiment.

FIG. 3 shows an example subset of nodes and relationships in a graph representing behavior attributes, according to an example embodiment.

FIG. 4 is schematic showing differences in behavior attributes between user devices, according to an example embodiment.

FIG. 5 is a flow chart showing a method for attributing user behavior from multiple technical telemetry sources, according to an example embodiment.

FIG. 6 shows a computing system that can be used to implement a system and a method for attributing user behavior from multiple technical telemetry sources, according to an example embodiment.

DETAILED DESCRIPTION

The following detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show illustrations in accordance with example embodiments. These example embodiments, which are also referred to herein as “examples,” are described in enough detail to enable those skilled in the art to practice the present subject matter. The embodiments can be combined, other embodiments can be utilized, or structural, logical, and electrical changes can be made without departing from the scope of what is claimed. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope is defined by the appended claims and their equivalents.

The present disclosure provides methods and systems for attributing user behavior from multiple technical telemetry sources. The proposed systems may provide a method for monitoring activities of a user when the user logged into a user device. The activities can be monitored based on network log data and application log data associated with the user device and the environment of the user device. The network log and data application log data can be obtained from different telemetry sources, such as routers, switches, and cloud-based applications and APIs. The activities may include typical applications used by the user, websites visited by the user, application servers accessed by the user, transaction performed by the user, and so forth.

Certain embodiments of the present disclosure may facilitate creation of behavioral baseline representing typical activities of the user. The behavioral baseline can be associated with a single user device or multiple user devices. Some embodiments may allow generating behavioral baseline of users associated with the same division or a department of an enterprise or of a common role of a group of users as defined within a corporate directory, an identity store, or the identity store. The behavioral baseline may be used to detect unusual and suspicious activities in a computer environment associated with the user device.

Referring now to the drawings, FIG. 1 is a block diagram of an environment 100, in which systems and methods for attributing user behavior from multiple technical telemetry sources can be implemented, according to some example embodiments. The environment 100 may include user devices 110-i (i=1, . . . , N) associated with user 105, remote (computer) systems 120-i (i=1, . . . , Z), a data network 130, a behavior attributes monitoring system 140, and a graph database 150. As used herein, a user can be represented by an entity associated with user account credentials assigned to a human being, specific role, or software agent.

The user devices 110-i (i=1, . . . , N) may include a notebook computer, a desktop computer, a tablet computer, a phablet, a smart phone, a personal digital assistant, a media player, a mobile telephone, a smart television set, in-vehicle infotainment, a smart home device, a mobile client device, an Internet-of-Things (IoT) device, and the like.

The remote systems 120-i (i=1, . . . , N) can include application servers, database servers, client servers, data storage servers, which may communicate with each other and the user devices 110-i (i=1, . . . , N) via the data network 130. The remote systems 120-i (i=1, . . . , N) can be configured to provide websites, client applications, enterprise applications, enterprise database, file and object services, and so forth.

The data network 130 may include the Internet or any other network capable of communicating data between devices. Suitable networks may include or interface with any one or more of, for instance, a local intranet, a corporate data network, a data center network, a home data network, a Personal Area Network, a Local Area Network (LAN), a Wide Area Network (WAN), a Metropolitan Area Network, a virtual private network, a storage area network, a frame relay connection, an Advanced Intelligent Network connection, a synchronous optical network connection, a digital T1, T3, E1 or E3 line, Digital Data Service connection, Digital Subscriber Line connection, an Ethernet connection, an Integrated Services Digital Network line, a dial-up port such as a V.90, V.34 or V.34bis analog modem connection, a cable modem, an Asynchronous Transfer Mode connection, or a Fiber Distributed Data Interface or Copper Distributed Data Interface connection. Furthermore, communications may also include links to any of a variety of wireless networks, including Wireless Application Protocol, General Packet Radio Service, Global System for Mobile Communication, Code Division Multiple Access or Time Division Multiple Access, cellular phone networks, Global Positioning System, cellular digital packet data, Research in Motion, Limited duplex paging network, Bluetooth radio, or an IEEE 802.11-based radio frequency network. The data network 130 can further include or interface with any one or more of a Recommended Standard 232 (RS-232) serial connection, an IEEE-1394 (FireWire™) connection, a Fiber Channel connection, an IrDA (infrared) port, a Small Computer Systems Interface connection, a Universal Serial Bus (USB) connection or other wired or wireless, digital or analog interface or connection, mesh or Digi® networking.

The behavior attributes monitoring system 140 can include an application executed on a standalone server or a closed-based computing resource. In some embodiments, the behavior attributes monitoring system 140 can be located on one of the remote systems 120-i (i=1, . . . , Z).

FIG. 2 is schematic 200 showing functionalities of the behavior attributes monitoring system 140, according to some example embodiments. The behavior attributes monitoring system 140 can monitor network log data 210, application log data 220, and user access log data 225, and can be in contact with an identity store (directory) 235. The identity store 235 can store role memberships of users. The behavior attributes monitoring system 140 can extract behavior attributes 230 from the network log data 210, application log data 220, user access log data 225, and the identity store 235. The behavior attributes 230 may include activity data associated with the user devices 110-i (i=1, . . . , N), such as active directories accessed by a user of the user devices, active applications used by the user, network connections of the user devices caused by activity of the user.

The network log data 210 can be recorded by switches or routers connected to the user devices 110-i (i=1, . . . , N). The network log data 210 can also be recorded by a cloud-based monitoring system (such as VPC Flow logs or CloudTrail within AWS). For example, the router or the cloud-based monitoring system can be configured to record logs of network data of connections of the user devices 110-i (i=1, . . . , N) to the remote systems 120-i (i=1, . . . , Z).

The application log data 220 may include logs of endpoint security applications (Endpoint Protection Platforms (EPPs), such as Tanium or CrowdStrike) installed on the user devices, logs of operations of the user devices (for example, generated by AuditD), and logs of an identity management system associated with the user devices 110-i (i=1, . . . , N).

Once the user 105 has logged into one of the user devices 110-i (i=1, . . . , N), the operational system of the user device generates a record of logs. The user 105 may open and close applications (for example, an Internet browser or client application) on the user devices. The user 105 may initiate, via the applications, connections to one of the remote systems 120-i (i=1, . . . , N). These activities of the user 105 (activity data) can be tracked using logs of the applications, logs of an endpoint security application, logs of an identity management system, and logs of the operational system of the user device. The activities of the user 105 can also be tracked using network logs from the router or the switch connected to the user device. Based on the determination that the user device is being utilized by the user 105, the behavior attributes monitoring system 140 can also track the relationship between the user 105 and the application, and can continue to do so over time as long as the user 105 is connected to the application via one or more user devices 110-i (i=1, . . . , N).

The activity data may include a network address of the user device, a list of active directories and files being accessed on the computing device, list of applications being executed by the computing device, list of network addresses of websites associated with the computing device, types of connections to the websites, and an amount of data transferred between the computing device and the websites or the applications.

In some embodiments, to distinguish between operations of the user device caused by the user and operations of computing device caused by the operational system and background agents running on the user devices, the behavior attributes monitoring system 140 can monitor network log data and application log data in prior to the user 105 has logged into the user device and after the user has logged off the user device. This facilitates generation of a user device baseline which can be subtracted (or otherwise accounted for) from the user behavior when the user is connected to determine the behavior that can be attributed to the user only.

The activity data determined based on network log data and application log data recorded when the user is not logged into the user device, can be attributed to user device itself. These activity data can be extracted from the activity data generated when the user is logged into the user device to obtain activity data that can be attributed to behavior of the user. The activity data attributed to the behavior of the user can be used to determine behavior attributes 230. The behavior attributes 230 can be associated with one of the user devices 110-i (i=1, . . . , N) or multiple user devices. The behavior attributes 230 may include active directories, active applications, network connections, amount of data transferred between user device and one of the remote systems, the time the user logged into the user device, the time the user logged out of the computing device, and so forth. In some embodiments, the behavior attributes 230 can be represented by a graph.

FIG. 3 shows an example graph 300 representing behavior attributes 230, according to an example embodiment. The example graph includes nodes 305, 310, 320, 330, 340, 350, and 360. The node 305 may represent the user device of the user 105. The node 305 can be associated with information concerning the user device, such as a type of the user device, operational system of the user device, network address of the user device, MAC address of the user device, and so forth.

The node 310 may represent an active directory accessed by the user 105. The node 310 can be associated with a path and name of the active directory. The nodes 320 and 330 may represent applications started on the user device when the user is logged into the user device. The nodes 320 and 330 can be associated with names of applications, version of the applications, directories used by the applications and so forth. The nodes 340, 350, and 360 can represent remote systems to which the applications are connected. The nodes 340, 350, and 360 can be associated with the name of server, network address of the server, website address, and the like. The graph 300 can represent typical actions (behavior) of the user 105 while the user 105 is logged into the user device 110-1. The graph 300 can be stored in graph database 150 (shown in FIG. 1).

The behavior attributes 230 can be associated with the user device 305 and can be further used for attributing the activity data of the user device 305 to the user 105. For example, when the user 105 is logged into the user device 305, the behavior attributes monitoring system 140 may generate, based on network log data 210 and application log data 220, a new graph representing new behavior attributes 230 during current login session. The new graph can be compared to previously recorded graphs associated with the user device to determine whether the new activity data can be attributed to the same user. The previous graphs can be stored in the graph database 150. The previous graphs can be identified based on MAC address of the user device.

If the user 105 is associated with a department or a role within an enterprise (represented by objects within an organizational unit structure, a role, or a group), then the behavior attributes (the graph) can be compared to reference behavior attributes that can be generated based on the behavior attributes of users associated with the department or the role within the enterprise.

FIG. 4 is schematic 400 showing differences of behavior attributes between user devices, according to an example embodiment. The user 105 can log into different user devices 110-1 and 110-2 to perform similar operations. For example, the user device 110-1 can include a notebook and the user device 110-2 can include a mobile client device, such as smartphone. The behavior attributes monitoring system 140 can determine behavior attributes 230-1 based on network log data and application log data associated with the user device 110-1. The behavior attributes monitoring system 140 can determine behavior attributes 230-2 based on network log data and application log data associated with the user device 110-2. The behavior attributes monitoring system 140 can determine differences 410 between the behavior attributes 230-1 and the behavior attributes 230-2. For example, the differences 410 can represent servers, websites, and applications accessed by the user 105 via both the user device 110-1 and the user device 110-2. The differences 410 can be used as reference behavior attributes of the user 105.

FIG. 5 is a flow chart of a method 500 for attributing user behavior from multiple technical telemetry sources, according to some example embodiments. The method 500 can be performed by the behavior attributes monitoring system 140 in environment 100 of FIG. 1.

The method 500 may commence in block 502 with determining that the user has logged into the computing device. In block 504, the method 500 may proceed, in response to the determination, with collecting log data from a plurality of telemetry sources associated with the computing device. The plurality of the telemetry sources may include one of the following: logs of endpoint security applications installed on the computing device, logs of a router providing a communications path to the computer device, logs of a cloud-based monitoring system configured to track network connections of the computer device, logs of operations of the computing devices, and logs of an identity management system.

In block 506, the method 500 may proceed with extracting, from the log data, activity data concerning activities of the computing device. Extracting the activity data can include determining a network address of the computing device, list of active directories and files being accessed on the computing device, list of applications being executed by the computing device, list of network addresses of websites associated with the computing device, types of connections to the websites, and amount of data transferred between the computing device and the websites or the applications.

In block 508, the method 500 may proceed with analyzing the activity data to determine that the activity data are attributed to the user. The method may then generate, based on the activity data, behavior attributes of the user and associate the behavior attributes with a unique identifier of the computing device. The unique identifier may include a media access control (MAC) address or a universally unique identifier (UUID) of the computing device.

The generation of the behavior attributes may include creating a graph. The graph may include nodes representing the applications and the websites and edges representing relationships between the user and the applications and/or the websites.

The method 500 may include estimating security integrity of the computing device based on comparison of the behavior attributes to reference behavior attributes. The reference behavior attributes may include further behavior attributes determined using log data of at least one further computing device associated with the user. Alternatively, the reference behavior attributes can be determined based on a plurality of further behavior attributes determined using further log data collected for a plurality of further computing devices associated with a plurality of further users having a same role within an enterprise.

The method 500 may include, prior to the determining that the user has logged into the computer device, collecting further log data from the plurality of telemetry sources associated with the computing device. The method 500 may include, prior to extracting the activity data, excluding the further log data from the log data.

FIG. 6 illustrates an exemplary computing system 600 that can be used to implement embodiments described herein. The computing system 600 can be implemented in the contexts of the remote systems 120-i (i=1, . . . , Z), the behavior attributes monitoring system 140, the graph database 150, and the user devices 110-i (i=1, . . . , N). The exemplary computing system 600 of FIG. 6 may include one or more processors 610 and memory 620. Memory 620 may store, in part, instructions and data for execution by the one or more processors 610. Memory 620 can store the executable code when the exemplary computing system 600 is in operation. The exemplary computing system 600 of FIG. 6 may further include a mass storage 630, portable storage 640, one or more output devices 650, one or more input devices 660, a network interface 670, and one or more peripheral devices 680.

The components shown in FIG. 6 are depicted as being connected via a single bus 690. The components may be connected through one or more data transport means. The one or more processors 610 and memory 620 may be connected via a local microprocessor bus, and the mass storage 630, one or more peripheral devices 680, portable storage 640, and network interface 670 may be connected via one or more input/output buses.

Mass storage 630, which may be implemented with a magnetic disk drive or an optical disk drive, is a non-volatile storage device for storing data and instructions for use by a magnetic disk or an optical disk drive, which in turn may be used by one or more processors 610. Mass storage 630 can store the system software for implementing embodiments described herein for purposes of loading that software into memory 620.

Portable storage 640 may operate in conjunction with a portable non-volatile storage medium, such as a compact disk (CD) or digital video disc (DVD), to input and output data and code to and from the computing system 600 of FIG. 6. The system software for implementing embodiments described herein may be stored on such a portable medium and input to the computing system 600 via the portable storage 640.

One or more input devices 660 provide a portion of a user interface. The one or more input devices 660 may include an alphanumeric keypad, such as a keyboard, for inputting alphanumeric and other information, or a pointing device, such as a mouse, a trackball, a stylus, or cursor direction keys. Additionally, the computing system 600 as shown in FIG. 6 includes one or more output devices 650. Suitable one or more output devices 650 include speakers, printers, network interfaces, and monitors.

Network interface 670 can be utilized to communicate with external devices, external computing devices, servers, and networked systems via one or more communications networks such as one or more wired, wireless, or optical networks including, for example, the Internet, intranet, LAN, WAN, cellular phone networks (e.g., Global System for Mobile communications network, packet switching communications network, circuit switching communications network), Bluetooth radio, and an IEEE 802.11-based radio frequency network, among others. Network interface 670 may be a network interface card, such as an Ethernet card, optical transceiver, radio frequency transceiver, or any other type of device that can send and receive information. Other examples of such network interfaces may include Bluetooth®, 3G, 4G, and WiFi® radios in mobile computing devices as well as a USB.

One or more peripheral devices 680 may include any type of computer support device to add additional functionality to the computing system. The one or more peripheral devices 680 may include a modem or a router.

The components contained in the exemplary computing system 600 of FIG. 6 are those typically found in computing systems that may be suitable for use with embodiments described herein and are intended to represent a broad category of such computer components that are well known in the art. Thus, the exemplary computing system 600 of FIG. 6 can be a personal computer, handheld computing device, telephone, mobile computing device, workstation, server, minicomputer, mainframe computer, or any other computing device. The computer can also include different bus configurations, networked platforms, multi-processor platforms, and so forth. Various operating systems (OS) can be used including UNIX, Linux, Windows, Macintosh OS, Palm OS, and other suitable operating systems.

Some of the above-described functions may be composed of instructions that are stored on storage media (e.g., computer-readable medium). The instructions may be retrieved and executed by the processor. Some examples of storage media are memory devices, tapes, disks, and the like. The instructions are operational when executed by the processor to direct the processor to operate in accord with the example embodiments. Those skilled in the art are familiar with instructions, processor(s), and storage media.

It is noteworthy that any hardware platform suitable for performing the processing described herein is suitable for use with the example embodiments. The terms “computer-readable storage medium” and “computer-readable storage media” as used herein refer to any medium or media that participate in providing instructions to a central processing unit (CPU) for execution. Such media can take many forms, including, but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media include, for example, optical or magnetic disks, such as a fixed disk. Volatile media include dynamic memory, such as RAM. Transmission media include coaxial cables, copper wire, and fiber optics, among others, including the wires that include one embodiment of a bus. Transmission media can also take the form of acoustic or light waves, such as those generated during radio frequency and infrared data communications. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, a hard disk, magnetic tape, any other magnetic medium, a CD-read-only memory (ROM) disk, DVD, any other optical medium, any other physical medium with patterns of marks or holes, a RAM, a PROM, an EPROM, an EEPROM, a FLASHEPROM, any other memory chip or cartridge, a carrier wave, or any other medium from which a computer can read.

Various forms of computer-readable media may be involved in carrying one or more sequences of one or more instructions to a CPU for execution. A bus carries the data to system RAM, from which a CPU retrieves and executes the instructions. The instructions received by system RAM can optionally be stored on a fixed disk either before or after execution by a CPU.

Thus, systems and methods for attributing user behavior from multiple technical telemetry sources are described. Although embodiments have been described with reference to specific exemplary embodiments, it will be evident that various modifications and changes can be made to these exemplary embodiments without departing from the broader spirit and scope of the present application. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.

Claims

1. A system for attributing user behavior of a user of a first computing device, the system comprising: at least one processor; anda memory communicatively coupled to the at least one processor, the memory storing instructions executable by the at least one processor to perform a method comprising: determining that the user has logged into the first computing device to initiate a start of a first log-in session;in response to the determination that the user has logged into the first computing device: collecting log data from a plurality of telemetry sources associated with the first computing device during the first log-in session;extracting, from the collected log data associated with the first computing device, activity data concerning activities of the first computing device;analyzing the activity data associated with the first computing device to determine that the activity data associated with the first computing device are attributed to the user; anddetermining that the user has logged into a second computing device to initiate a start of a second log-in session;in response to the determination that the user has logged into the second computing device: collecting log data from a plurality of telemetry sources associated with the second computing device during the second log-in session;extracting, from the collected log data associated with the second computing device, activity data concerning activities of the second computing device;determining a difference between the log data during the first log-in session and the log data during the second log-in session; anddetermining that the user has terminated the first and second log-in sessions:in response to the determination that the user has terminated the first and the second log-in sessions, terminating the collection of the log data from the plurality of telemetry sources associated with the first and the second computing device;prior to the determining that the user has logged into the first computing device, collecting further log data from the plurality of telemetry sources associated with the first computing device;prior to extracting the activity data concerning activities of the first computing device, excluding the further log data associated with the first computing device from the collected log data associated with the first computing device to generate of a baseline of the first computing device;accounting for the baseline of the first computing device for a security integrity of the first computing device;prior to the determining that the user has logged into the second computing device, collecting further log data from the plurality of telemetry sources associated with the second computing device;prior to extracting the activity data concerning activities of the second computing device, excluding the further log data associated with the second computing device from the log data associated with the second computing device to generate of a baseline of the second computing device; andaccounting for the baseline of the second computing device for a security integrity of the second computing device.

2. The system of claim 1, wherein the plurality of the telemetry sources includes one or more of the following: logs of endpoint security applications installed on the first and the second computing device, logs of at least one of a router or a switch providing communications services to the first and the second computing device, logs from a cloud-based network, logs from access Application Programming Interfaces, logs from a monitoring system configured to track network connections of the first and the second computing device, logs of operations of the first and the second computing device, and logs of an identity management system.

3. The system of claim 1, wherein the extracting the activity data concerning activities of the first and the second computing device includes determining a network address of the first and the second computing device, a list of active directories and files being accessed on the first and the second computing device, a list of applications being executed by the first and the second computing device, a list of network addresses of websites associated with the first and the second computing device, types of connections to the websites, types of connections to the applications, an amount of data transferred between the first and the second computing device and the websites or the applications, and a type of operations conducted.

4. The system of claim 3, wherein the method further comprises: generating, based on the activity data concerning activities of the first and the second computing device, behavior attributes of the user; andassociating the behavior attributes of the user with a unique identifier of the first and the second computing device being operated by the user during the first and the second log-in session.

5. The system of claim 4, wherein the unique identifier includes one of a media access control (MAC) address and a universally unique identifier (UUID) of the first and the second computing device.

6. The system of claim 4, wherein the generating the behavior attributes includes creating a graph, the graph including nodes representing the applications and the websites and edges representing relationships between the user and one or more of the applications and the websites.

7. The system of claim 4, wherein the method further comprises estimating the security integrity of the first and the second computing device based on a comparison of the behavior attributes to reference behavior attributes.

8. The system of claim 7, wherein the reference behavior attributes include further behavior attributes determined using log data of at least one further computing device associated with the user.

9. The system of claim 7, wherein the reference behavior attributes are determined based on a plurality of further behavior attributes determined using further log data collected for a plurality of further computing devices associated with a plurality of further users having a same role within an enterprise.

10. A method for attributing user behavior of a user of a first computing device, the method comprising: determining that the user has logged into the first computing device to initiate a start of a first log-in session;in response to the determination that the user has logged into the first computing device: collecting log data from a plurality of telemetry sources associated with the first computing device;extracting, from the log data associated with the first computing device, activity data concerning activities of the first computing device;analyzing the activity data associated with the first computing device to determine that the activity data associated with the first computing device are attributed to the user; anddetermining that the user has logged into a second computing device to initiate a start of a second log-in session;in response to the determination that the user has logged into the second computing device: collecting log data from a plurality of telemetry sources associated with the second computing device during the second log-in session;extracting, from the collected log data associated with the second computing device, activity data concerning activities of the second computing device;determining a difference between the log data during the first log-in session and the log data during the second log-in session; anddetermining that the user has terminated the first log-in session;in response to the determination that the user has terminated the first and the second log-in sessions terminating the collection of the log data from the plurality of telemetry sources associated with the first and second computing device;prior to the determining that the user has logged into the first computing device, collecting further log data from the plurality of telemetry sources associated with the first computing device;prior to extracting the activity data concerning activities of the first computing device, excluding the further log data associated with the first computing device from the log data associated with the first computing device to generate of a baseline of the first computing device;accounting for the baseline of the first computing device for a security integrity of the first computing device;prior to the determining that the user has logged into the second computing device, collecting further log data from the plurality of telemetry sources associated with the second computing device;prior to extracting the activity data concerning activities of the second computing device, excluding the further log data associated with the second computing device from the log data associated with the second computing device to generate of a baseline of the second computing device; andaccounting for the baseline of the second computing device for a security integrity of the second computing device.

11. The method of claim 10, wherein the plurality of the telemetry sources includes one or more of the following: logs of endpoint security applications installed on the first and the second computing device, logs of at least one of a router or a switch providing communications services to the first and the second computing device, logs from a cloud-based network, logs from access Application Programming Interfaces, logs from a monitoring system configured to track network connections of the first and the second computing device, logs of operations of the first and the second computing device, and logs of an identity management system.

12. The method of claim 10, wherein the extracting the activity data concerning activities of the first and the second computing device includes determining a network address of the first and the second computing device, a list of active directories and files being accessed on the first and the second computing device, a list of applications being executed by the first and the second computing device, a list of network addresses of websites associated with the first and the second computing device, types of connections to the websites, types of connections to the applications, an amount of data transferred between the first and the second computing device and the websites or the applications, and a type of operations conducted.

13. The method of claim 12, further comprising: generating, based on the activity data concerning activities of the first and the second computing device, behavior attributes of the user; andassociating the behavior attributes of the user with a unique identifier of the first and the second computing device being operated by the user during the first and the second log-in session.

14. The method of claim 13, wherein the unique identifier includes one of a media access control (MAC) address and a universally unique identifier (UUID) of the first and the second computing device.

15. The method of claim 13, wherein the generating the behavior attributes includes creating a graph, the graph including nodes representing the applications and the websites and edges representing relationships between the user and one or more of the applications and the websites.

16. The method of claim 13, further comprising estimating the security integrity of the first and the second computing device based on a comparison of the behavior attributes to reference behavior attributes.

17. The method of claim 16, wherein the reference behavior attributes include further behavior attributes determined using log data of at least one further computing device associated with the user.

18. The method of claim 16, wherein the reference behavior attributes are determined based on a plurality of further behavior attributes determined using further log data collected for a plurality of further computing devices associated with a plurality of further users having a same role within an enterprise.

19. A non-transitory processor-readable medium having embodied thereon a program being executable by at least one processor to perform a method for attributing user behavior of a user of a first computing device, the method comprising: determining that the user has logged into the first computing device to initiate a start of a first log-in session;in response to the determination that the user has logged into the first computing device: collecting log data from a plurality of telemetry sources associated with the first computing device during first log-in session;extracting, from the collected log data associated with the first computing device, activity data concerning activities of the first computing device;analyzing the activity data associated with the first computing device to determine that the activity data associated with the first computing device are attributed to the user; anddetermining that the user has logged into a second computing device to initiate a start of a second log-in session;in response to the determination that the user has logged into the second computing device: collecting log data from a plurality of telemetry sources associated with the second computing device during the second log-in session;extracting, from the collected log data associated with the second computing device, activity data concerning activities of the second computing device;determining a difference between the log data during the first log-in session and the log data during the second log-in session;determining that the user has terminated the second log-in session;in response to the determination that the user has terminated the first and the second log-in sessions, terminating the collection of the log data from the plurality of telemetry sources associated with the first and the second computing device;prior to the determining that the user has logged into the first computing device, collecting further log data from the plurality of telemetry sources associated with the first computing device;prior to extracting the activity data concerning activities of the first computing device, excluding the further log data associated with the first computing device from the log data associated with the first computing device to generate of a baseline of the first computing device;accounting for the baseline of the first computing device for a security integrity of the first computing device;prior to the determining that the user has logged into the second computing device, collecting further log data from the plurality of telemetry sources associated with the second computing device;prior to extracting the activity data concerning activities of the second computing device, excluding the further log data associated with the second computing device from the log data associated with the second computing device to generate of a baseline of the second computing device; andaccounting for the baseline of the second computing device for a security integrity of the second computing device.