Patent Application
20170099311
The present disclosure relates to systems, methods, and techniques for computer and network security, and more specifically to improving the security of computer systems and networks, and even more specifically to detecting anomalous behavior indicative of hacking.
Computer systems and networks can employ various measures to prevent activity by unauthorized users. For example, a network can require a username and password to authenticate a user before allowing access. However, there remains a need for a security system to better detect anomalous activity, for example, when an authenticated user is actually a malicious actor, and furthermore, there remains a need to implement such a security system in a dynamic manner that reduces the need for manual configuration with more accurate results.
The systems, methods, and devices described herein each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this disclosure, several non-limiting features will now be discussed briefly.
An anomaly-detection computer system is disclosed herein to identify when a user of a network is a malicious actor. The system can include one or more computer readable storage devices configured to store one or more software modules including computer executable instructions, and one or more hardware computer processors in communication with the one or more computer readable storage devices. The instructions are executed on the one or more software modules to cause the computer system to: log, to the one or more computer readable storage devices, activity on the network by a plurality of users; calculate similarity scores based at least in part on the logged activity on the network; sort the plurality of users into a plurality of cohorts based at least in part on the similarity scores; store data about the plurality of cohorts into a memory; detect a first port used in a new network activity of a first user of the plurality of users sorted into a first cohort of the plurality of cohorts; determine, based at least in part on a comparison performed by the one or more processors of the first port to other ports used by the first cohort, that the new network activity by the first user is anomalous; and restrict, based at least in part on determining that the new network activity by the first user is anomalous, an ability of the first user to access a network resource.
The anomaly-detection computer system of the preceding paragraph can have any sub-combination of the following features: the network resource is a distributed resource that is accessible through a plurality of different network IP addresses; calculating the similarity scores can include a determination of at least one of a cosine similarity score and a Jaccard similarity score; calculating the similarity scores can include performing an inverse user frequency transform; determining if the network activity by the first user is anomalous by determining the first port has been used by other members of the first cohort; performing a Kullback-Leibler divergence; receiving user information about the plurality of users; sorting the plurality of users into a plurality of cohorts based at least in part on the similarity scores and the user information; new network activity is authenticated by the credentials of the first user; the first port is a port of a computer of the first user; the first port comprises at least one of a port of a server hosting the network resource and a port of a second server hosting the network resource; and the network is a virtual private network.
Another aspect of the disclosure is directed to a computer readable, non-transitory storage medium having a computer program stored thereon executable by one or more processors of an anomaly detection system in a network. When the computer program of the non-transitory storage medium is executed, a computer system can: log resource access by a plurality of users during a first time period; calculate a plurality of similarity scores for the plurality of users, the plurality of similarity scores comprising a first similarity score between a first user of the plurality of users and a second user of the plurality of users; assign, based at least in part on the first similarity score, the first user and the second user to a first cohort; log a first plurality of resource accesses by the first user during a second time period that is at least partially different from the first time period; log a second plurality of resource accesses by members of the first cohort; determine a probability score of the first plurality of resource accesses; and generate, based at least on the divergence, an indicator of a potential anomaly.
The computer readable, non-transitory storage medium having a computer program stored thereon can further be executed to have any sub-combination of the following features: the probability score is a Kullback-Leibler divergence of the first plurality of resource accesses to the second plurality of resource accesses; the probability score is a Kullback-Leibler divergence of the second plurality of resource accesses to the first plurality of resource accesses; and the first plurality of resources accesses contains a first distribution of access to a set of resources, and wherein the second plurality of resource accesses contains a second distribution of accesses to the set of resources.
Another aspect of the disclosure is directed to a computer-implemented method for detecting an anomalous activity in a network. The method, as implemented by one or more computer readable storage devices configured to store one or more software modules including computer executable instructions, and by one or more hardware computer processors in communication with the one or more computer readable storage devices configured to execute the one or more software modules, comprises: logging, to the one or more computer readable storage devices, user activity for a plurality of users in the network; sorting the plurality of users into a plurality of cohorts; detecting a new activity by a first user of the first plurality of users sorted into a first cohort of the plurality of cohorts; determining a origin of the new activity; determining the probability that the new activity is an attack based, at least in part, on the origin of the new activity; and generating, based at least in part on the probability that the new activity is an attack, an indicator of a potential anomaly.
The computer-implemented method of the preceding paragraph can have any sub-combination of the following features: determining a distribution of ordinary network activity, where determining the probability that the new activity is an attacked is further based, at least in part, on the distribution of ordinary network activity; determining the probability that the new activity is an attacked is further based, at least in part, on attack origin distribution data; receiving the attack origin distribution data for a plurality of countries, and interpolating attack origin distribution data for a country not in the plurality of countries; comparing the new user activity to logged activity of the first user to generate a second comparison result, and comparing the new user activity to logged activity the first cohort to generate a second comparison result, where generating the indicator of the potential anomaly is further based, at least in part, on the second comparison result and the third comparison result.
The following drawings and the associated descriptions are provided to illustrate embodiments of the present disclosure and do not limit the scope of the claims. Aspects and many of the attendant advantages of this disclosure will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
Throughout the drawings, reference numbers may be reused to indicate correspondence between referenced elements. Nevertheless, use of different numbers does not necessarily indicate a lack of correspondence between elements. And, conversely, reuse of a number does not necessarily indicate that the elements are the same.
In order to facilitate an understanding of the systems and methods discussed herein, a number of terms are defined below. The terms defined below, as well as other terms used herein, should be construed to include the provided definitions, the ordinary and customary meaning of the terms, and/or any other implied meaning for the respective terms. Thus, the definitions below do not limit the meaning of these terms, but only provide exemplary definitions.
“Anomalous activity” includes, without limitation, actions performed on a network that are not characteristic of actions performed by an authorized user, and the anomalous activity indicates that a different individual has gained access to the network.
“Cohort” includes, without limitation, a group of network users who perform similar activities on a network, at least more similar when compared to activities performed by members of a different group.
“Port” includes, without limitation, a software created communication number in a computer that can be used to by different software to share a physical communication connection.
“Network resources” include, without limitation, resources available through a network. Examples of resources include, without limitation, an email, a database, a file, a program, a server, a computer, a directory, a file path or directory, a permission, a program, a program license, memory, processors, a machine, time to utilize a machine, etc.
“Distributed resources” include, without limitation, resources accessible from different points on a network, such as two separate servers. A resource can be distributed, for example, by being mirrored or striped across different machines, or if a plurality of the resource exists across different network points, such as a software license available on a first server and the same software license available on a different server.
“Network activity” includes, without limitation, all actions performed on a network, such as commands, receptions, traffic, etc. Logging network activity can include, for example, any aspect or combinations of aspects of the network activity, for example, sources, destinations, traffic size, traffic speed, traffic type, data, user ID, user IP address, bandwidth, a total amount of data transmitted by users, a total amount of data received by users, a port used by a user to access the network, a port used by network resources to communicate with the user, an IP address of network resources accessed by the user, times of activity, an origin from which the user accesses the network, a permission level necessary to perform user requests, etc.
“Score” includes, without limitation, numeric rankings, ratings, or grades and can be represented as a number in a range (e.g., 0.0 to 1.0, 0 to 100, −100 to 100), letter (e.g., A+, B, F), label (e.g., safe, neutral, danger), etc. A score can be determined by an algorithm or formula.
Various embodiments of the present disclosure provide improvements to various technologies and technological fields. For example, various aspects of the embodiments can improve anomaly detection in a network. Anomalies can be detected even after a user is authenticated, for example, by a username and password. Fewer false positives can be generated. More anomalies can be detected. Anomalies can be detected more accurately. The security system can better determine what is normal for a user to more accurately detect anomalous activity. The security system can detect anomalous behavior because it has not been performed by any member of a cohort. The security system can detect anomalous behavior even if it was previously performed by members of a cohort. The security system can dynamically sort users into cohorts. The security system can dynamically log user activity to adjust data used in detecting anomalies. The security system can dynamically determine anomalous behavior and adjust the determination over time. The security system can require less manual configuration. Not necessarily all such advantages can be achieved in accordance with any particular embodiment of the invention. Thus, the invention can be embodied or carried out in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other advantages as can be taught or suggested herein.
Various embodiments of the present disclosure discuss recently arisen technological problems and solutions inextricably tied to those technologies. For example, some parts of the specification disclose technology that reduces the number of false positive warnings generated by security systems as a result of distributed resources in a network, a recently arisen technological problem. As another example, parts of the specification disclose an anomaly detection system's use of ports to detect anomalies. Such a usage of ports is not possible in a system without port technology, and therefore is inextricably tied to at least specialized systems featuring port technology.
Parts of the specification disclose how to implement specific technological solutions that are otherwise difficult to implement on a computer. Some parts of the specification discuss computer-implementable solutions to non-mathematical problems such as determining Is this activity suspicious?”
Parts of the specification disclose improvements to existing technological solutions. For example, some embodiments implement anomaly detection systems that require less setup time or less manual input than prior solutions. As another example, some embodiments feature improved anomaly detection accuracy over previous solutions.
Parts of the specification disclose the use of computer systems to solve problems that cannot be inherently solved by humans alone. For example, computers can perform some functions very quickly to provide security measures that can prevent hacking and data theft. Computers can receive inputs and detect anomalies as fast as or nearly as fast as they occur, and computers can then perform security measures (e.g., disable network access or generate warnings) before the network is compromised. Computer network systems can process data at speeds far faster than humans. By the time humans finish certain computations by hand and discover an anomaly, hackers could have long ago compromised the network, and it would be too late to take any preventative security measures. As a result, a human performing some calculations instead of computers would render useless the anomaly detection system for a computer network. Accordingly, some parts of disclosed methods are performed in real-time or fast enough to prevent further hacking.
The users 103[a-e] can access the network 105 through a variety of different terminals. For example, user 103a can access the network 105 through a desktop computer. User 103e can access the network 105 through a handheld portable device. In some embodiments, users can access the network through desktops, laptops, tablets, smartphones, or other suitable devices.
The users 103[a-e] can access the network to perform similar or different tasks. In order to connect to the network 105, the users can be required to identify themselves, for example, with a username or other identification such has MAC address, IP address, key card, etc. To prevent unauthorized access to the network, the users 103[a-e] can need to authenticate their identity by a password or other type of security token.
The network 105 can be any type of network. For example, it can be a virtual private network (VPN), the internet, an intranet, an internal network, corporate network, local area network (LAN), wireless network, etc.
The resources 107a, 107b, and 107c accessible to a user through the network can include, for example: an email, a database, a file, a program, a server, a computer, a directory, a file path or directory, a permission, a program, a program license, memory, processors, a machine, time to utilize a machine, etc. The resources can be distributed, and the physical machines through which the resources are accessible can be located in different places.
While a username and password provide basic network security to prevent unauthorized access by some individuals, there remains a need for a security system to detect network intrusions after this front line of defense has been breached. For example, a username and password might be stolen by a hacker through phishing, social engineering, keyloggers, etc. In another example, a username and password can be guessed, discovered through a brute-force attack, or reset by an impersonator. As yet another example, a virus, Trojan, or other computer exploit can allow a hacker to infect a user's machine, enabling the hacker to gain access to the network once the user logs into the network from the infected machine. After gaining access, a hacker might attempt to steal sensitive information. This can include, for example, credit card information, personal user information, sales data, business strategies, engineering data, health information, customer lists, pricing records, etc.
As an additional security measure, a network can use an anomaly detection system 101 to detect when an authorized user begins to perform suspicious or anomalous activities that might indicate an unauthorized network access. This anomaly detection system can supplement the username and password security system. However, to detect when anomalous activity occurs, the anomaly detection needs to be able to differentiate between normal and anomalous behaviors. The anomaly detection system 101 logs user activity in an activity log 109. The anomaly detection system can obtain this information on its own, e.g., by itself analyzing network packets, or it can receive this information from other sources in the network, e.g. from network routers or servers. The anomaly detection system, including the activity log, can be centralized or distributed across the network. The activity log can log a variety of user activity, such as user ID, user IP address, the type of network activity being performed by users, a bandwidth used by users, a total amount of data transmitted by users, a total amount of data received by users, a port used by a user to access the network, a port used by network resources to communicate with the user, an IP address of network resources accessed by the user, times of activity, an origin from which the user accesses the network, a permission level necessary to perform user requests, etc.
The analysis engine 111 can analyze the activity log and compare it to user activity to determine if the user activity is anomalous, even if the user has presented the proper authenticating username and password or other credentials. If the analysis engine 111 detects anomalous user activity, the warning generator 113 can generate a warning to a system administrator 115. In some embodiments, the warning generator can take other measures to secure the network, such as revoking access from an individual suspected of anomalous activity, taking resources offline, etc. The warning generator can warn an administrator in different ways, for example, through a daily activity report, through a text message, through an email, or through an immediate alert. The warning generator can communicate through the network to send the warning to the administrator (e.g., send an internal company email through the network), communicate through an external network (e.g., send a text message through a cell phone carrier), or it can directly generate a warning on an administrator computer.
For example, in a first embodiment, a corporation can have many different types of resources accessible to different users through a corporate network after the users are authenticated. In the first embodiment, users 103a and 103b are corporate salesmen. In the first embodiment, resource 107a is server containing customer contact information, resource 107b is a server containing product pricing information, and resource 107c contains human resources hiring information. In this first embodiment, salesman 103a might regularly access resource 107a through the network in order to contact clients to make sales. Salesman 013b might also regularly access resource 107a and additionally access resource 107b when giving price quotes to clients. Neither salesman 103a nor 103b ever access human resources hiring information 107c because they do not work in the human resources department. The activity log 109 has logged this previous activity of the salesmen 103a and 103b.
In the first embodiment, suppose a hacker is able to obtain the network credentials of salesman 103a. The hacker begins to download all available information, accessing resource 107a, 107b, and 107c. When this happens, analysis engine 111 can analyze the user activity coming from the computer of salesman 103a. It can first detect that salesman 103a is accessing pricing information resource 107b. In some embodiments, the analysis engine can flag the behavior as anomalous and generate a warning because it is inconsistent with previous activity of 103a. In some other embodiments, the analysis engine can determine, based on the behavior of 103b, that it is normal for salesmen to access pricing information resource 107b.
The analysis engine 111 can flag the activity of salesman 103a as anomalous for accessing human resource information 107c, something that neither salesman has been logged to do. The analysis engine 111 can flag the activity of salesman 103a as anomalous for accessing more than a usual amount of data, accessing the resources at an odd time, accessing the resources from a remote computer in a different location or IP address, or based on a variety of other anomalous conditions inconsistent with previously logged behavior. If the analysis engine has flagged a sufficient amount of suspicious user activity, then a warning can be sent by the warning generator 113 to a network administrator. In some embodiments, a single flag of anomalous user activity (for example, user activity originating from an IP address in a foreign country when the user is actually local) can trigger a warning generation. In some other embodiments, multiple flags of anomalous user activity are required to avoid false positives. For example, a detection of an authorized user accessing resources at a later time can simply be the user performing occasional overtime work, not a hacker, and so other indicators of anomalous activity would be required before a warning is generated.
In the embodiment described, the analysis engine 111 is able to determine that the salesman 103a is similar to salesman 103b, and that “normal” behavior consists of activity regularly performed by either salesman. In performing this analysis, the analysis engine 111 can places similar users into various cohorts in order to analyze what “normal” behavior is for users of that cohort.
In an example embodiment, resource 207 is tax data. As a precautionary measurement, the system mirrors the tax data on two separate servers 209 and 211 in case one server goes down such that the tax data 207 is duplicated as 207a and 207b. The user 203 regularly initiates a program on the user machine which requests to access the tax data 207 through a port 223 having port number 20 on the user machine. The request gets routed through the network 205 to the first server 209 having IP address 192.168.0.2. The user is able to access the tax data 207a on the first server 209 through a port 213 on the server 209 having port number 22. An anomaly detection system, such as the anomaly detection system 101 of
In some embodiments, a distributed resource 207 can be an executable program. For example, a user 203 can normally communicate through a port 213 on the first server to run software on the first server 209. The first server can have a finite number of licenses or a finite capacity to run the software. If the first server has no more licenses or processing capacity, the user 203 can run the same software on the second server 211 instead. In some embodiments, a distributed resource can be different parts a resource stored at different locations in a stripe array. In some embodiments, a distributed resource can be multiple instances of a resource distributed at different locations. In some embodiments, distributed resources can refer to similar applications distributed across different hosts as long as the port numbers are the same.
In some embodiments, a distributed resource can be accessed through different IP addresses but a same port number. The port number can be the port 223 number of a user machine or a port 213, 215 number of a server 209, 211. The anomaly detection system can identify that a user is acting normally because the same distributed resource is being accessed, even if a user is accessing the distributed resource through different IP addresses, because the same port number is being used along with other similar identifying information. This can minimize the number of false positive warnings that the anomaly detection system generates. In some embodiments, a different identifying signature (e.g., same file size, same time, same packets, same directory, etc.) of repeated access to the same distributed resource at different locations can be detected and not flagged as anomalous behavior.
It should be recognized that a decision to use port numbers is not an obvious solution. It can be against conventional wisdom in a system that relies, at least in part, on unique identifiers to use a port number when other identifiers better identify a unique activity. For example, a port number alone will not identify the accessed server—information could be identified by an IP address. Nonetheless, using the less unique port number in some embodiments, can nonetheless detect anomalies with increased accuracy.
At block 301, an anomaly detection system such as anomaly detection system 101 of
At block 305, the system can receive user information. User information can include information that helps to sort the users. For example, location, job titles, job descriptions, a corporate hierarchy, email lists, email data, address books, mailing lists, user groups, active directory data, user profile information (e.g., age, location), etc. can be used to help determine which users need to access similar network resources.
At block 307, the system can calculate similarity scores between users. In some embodiments, this can be done, for example, in part by analyzing the user information. In some embodiments, this can be done dynamically by analyzing the activity log. A similarity score can be determined for users based on their history of user activity. Users who access similar resources are assigned a higher score. This can be recalculated as users continue perform additional activity that gets logged. The similarity score can be calculated, for example, by performing an inverse user frequency transform and calculating a Jaccard similarity score or cosine similarity score between the different users. Example calculations are provided in the discussion of
At block 309, the users can be divided into cohorts based, at least in part, on the similarity score. Similar users with high similarity scores can be placed into the same cohort.
At block 311, another user can be placed a different cohort. This user can have a low similarity score with users of the first cohort. However, this user can have high similarity scores with other members of the different cohort.
In some embodiments, a user can be placed into more than one cohort. For example, a network user who is an accountant can get placed in a first cohort with tax attorneys and also placed in a second cohort with inventory managers. In some embodiments, user information can be used to finalize the cohort placement. For example, a large group of users can have high similarity scores with each other. The received user information can indicate that those users are either contractors or employees, and so the finalized cohort can divide the users along those lines. In another embodiment, the received user information is used as part of the calculation so that the similarity score between users accounts for whether they hold the same job title.
The dynamic placement of users into cohorts based on an analysis of the activity log can yield better results than simply based on user information alone. For example, a network many have 1000 users who hold the job of “contractor.” These contractors can in fact access very different network resources to perform very different job functions. Other data, such as job descriptions, job titles, corporate directories, etc. can become out of date. For example, a successful engineer hired to design a product can initially access technical resources in a network but later perform product marketing due to his superior product knowledge, and the engineer can instead begin to routinely access marketing resources in a network. A dynamic system can continue to log user activity, calculate new similarity scores, and adjust the cohort groupings or place users into new ones. Furthermore, such a dynamic system can log the necessary data on its own without needing to receive user information or require manual intervention.
In the example, user activity is logged as whether or not a user accessed a resource. Resource 1 is a distributed resource and is identified by a partial IP and a port. Resource 401 can be distributed across a plurality of servers having different IP addresses that begin with 198.10.555 and is accessed through port 18. Resource 402 is a resource accessed at IP address 192.168.0.1. In the example embodiment, resource 402 can be a network home page. Resource 403 is the network administrative controls. Resource 404 is the network directory “H:\Data.”
The logged data indicates that user 103a has accessed resource 401 and 402. User 103b has accessed resource 401, 402, and 404. User 103c has accessed resource 402 and 403.
An inverse user frequency scale factor 405 can be calculated. This can be used to determine the importance of an access to a resource. The inverse user frequency scale factor can be calculated to indicate the relative significance of an access to a resource. Resources frequently accessed by many users are less important in a similarity calculation. For example, the users 103a, 103b, and 103c all access the resource 2, the network home page at IP address 192.168.0.1 as a default browser home page. This logged data has relatively less value than other logged data in determining similarity.
One example formula for calculating an inverse user frequency scale factor for a given resource is according to the equation:
The total number of accesses to a resource is divided by the total number of possible users who could have accessed the resource. The result is then subtracted from 1.
Another example formula for calculating an inverse user frequency scale factor for a given resource is according to the equation:
The Log is taken of the number of users divided by the number of access to the resource. This can generate a scale factor that gives greater weight to unique resource accesses. Here and elsewhere, the Log base can be various numbers.
The table 400 shows the inverse user frequency scale factor 405 calculated according to Eq. 2 for the logged data. Resource 401 is assigned a scale factor of approximately 0.17. Resource 402 is assigned a scale factor of 0. This reflects its relative lack of importance, because accessing a network home page is a typical activity of many users and not a good indicator of anomalous activity. Resources 403 and 404 are assigned scale factors of approximately 0.47.
In some embodiments, a Jaccard similarity score can be calculated for the users. The Jaccard similarity score between two users A and B can be calculated according to the equation:
The size of the intersection of resources accessed between user A and user B is divided by the size of the union of resources accessed for user A and user B. This produces a result between 0 and 1.
Applied to the logged user activity shown in table 400 without scale factors, user 103a and user 103b both accessed resources 401 and 402, so the size of the intersection of resources accessed is 2. The union of resources accessed by user 103a and user 103b includes resources 401, 402, and 404, so the size of the union of resources accessed is 3. The similarity score for users 103a and 103b would be calculated as ⅔.
User 103a and user 103c both accessed resource 402, so the size of the intersection of resources accessed is 1. The union of resources accessed by user 103a and user 103c includes resources 401, 402, and 403, so the size of the union of resources accessed is 3. The similarity score for users 103a and 103c would be calculated as ⅓.
User 103b and user 103c both accessed resources 402, so the size of the intersection of resources accessed is 1. The union of resources accessed by user 103b and user 103c includes resources 401, 402, 403, and 404, so the size of the union of resources accessed is 4. The similarity score for users 103b and 103c would be calculated as ¼.
In an embodiment using the Jaccard similarity scores without scale factors, user 103a and user 103b would have the highest similarity score of approximately 0.67, and users 103b and 103c would have the lowest similarity score of 0.25.
Applied to the logged user activity shown in table 400 with scale factors to both the union and the intersection, user 103a and user 103b both accessed resources 401 and 402, so the size of the intersection of resources accessed is (0.17+0). The union of resources accessed by user 103a and user 103b includes resources 401, 402, and 404, so the size of the union of resources accessed is (0.17+0+0.47). The similarity score for users 103a and 103b would be calculated as 0.17/0.64 or about 0.27.
User 103a and user 103c both accessed resource 402, so the size of the intersection of resources accessed is 0. The union of resources accessed by user 103a and user 103c includes resources 401, 402, and 403, so the size of the union of resources accessed is (0.17+0+0.47). The similarity score for users 103a and 103c would be calculated as zero.
User 103b and user 103c both accessed resources 402, so the size of the intersection of resources accessed is 0. The union of resources accessed by user 103b and user 103c includes resources 401, 402, 403, and 404, so the size of the union of resources accessed is (0.17+0+0.47+0.47). The similarity score for users 103b and 103c would be calculated as zero.
In an embodiment using the Jaccard similarity scores with scale factors applied to both the union and the intersection, user 103a and user 103b would have the highest similarity score of approximately 0.27, and all other user combinations have a similarity score of zero.
In some embodiments, the scale factor can be applied to one of the union calculation or the intersection calculation in determining the Jaccard similarity score.
In some embodiments, a cosine similarity score can be calculated for the users. The cosine similarity score between two users A and B can be calculated according to the equation:
In equation 4, where
An example is provided without using scale factors. Applied to the logged user activity shown in table 400 for user 103a and user 103b, the numerator is (1×1+1×1+0×0+0×1) or 2. The denominator is √{square root over (1+1+0+0)}·√{square root over (1+1+0+1)} or approximately 2.45. The cosine similarity score for the users would be approximately 0.82.
For user 103a and user 103c, the numerator would be (1×0+1×1+0×1+0×0) or 1. The denominator is √{square root over (1+1+0+0)}·√{square root over (0+1+1+0)} or 2. The cosine similarity score for the users would be 0.5.
For user 103b and user 103c, the numerator would be (1×0+1×1+0×1+1×0) or 1. The denominator is √{square root over (1+1+0+1)}·√{square root over (0+1+1+0)} or approximately 2.45. The cosine similarity score for the users would be approximately 0.41.
In an embodiment using the cosine similarity scores without scale factors, user 103a and user 103b would have the highest similarity score of approximately 0.82, and users 103b and 103c would have the lowest similarity score of 0.41.
In some embodiments, the scaling factors can likewise be applied to the vector values when performing a cosine similarity score calculation, and the scaling factors can be applied to the numerator, denominator, or both. In some embodiments, a different equation can be used to calculate the similarity score.
In some embodiments, the data used can be non-binary data. For example, instead of comparing whether or not a resource was accessed, the similarity score can be calculated based on the amount of data transferred to access resource, a time that activity took place, etc.
In some embodiments, a similarity score can be calculated between all users in a network in order to determine which groups of users are the most similar to each other.
The groupings can occur based on similarity scores and received user information. For example, users 103a, 103b, and 103e can have high similarity scores and they all hold similar job titles, perform similar tasks, are described similarly in an active directory, and access the same resources over the network. In the other cohort, users 103c and 103d can have high similarity scores between each other but lower similarity scores with the users 103a, 103b, and 103e.
By grouping users into cohorts, the anomaly detection system is better able to compare user activity to logged activity of similar users to determine if the user activity is anomalous.
In some embodiments, the cohorts can be readjusted and users will be reassigned based on additional logged user activity. The cohort sizes can also vary, and the sizes can also dynamically change with new logged activity. In some embodiments, cohorts can be of a fixed size, such as 5, 10, 15, 20, 25, 30, 40, 50 100, 200, 250, 500, 750, or 1000 users. In some embodiments, cohorts can be a mix of sizes. For example, a CEO of a company can be in a unique cohort, or a very small cohort with other C-level network users. On the other hand, the same company can have thousands of customer service representatives, and the cohort size for the customer service representatives can be very large. In some embodiments, users can be assigned to more than one cohort. For example, a user can be assigned to a cohort based on similar job descriptions with other users, another different cohort based on accessing similar resources with a first group, another different cohort based on accessing similar resources to a second group, and a different cohort based on the location of the user.
In an example embodiment, resource 207 is tax data mirrored on two separate servers 209 and 211. The user 203 regularly accesses the tax data 207 through a port 223 having port number 20 on the user machine. The request gets routed through the network 205 to the first server 209 having IP address 192.168.0.2. The user is able to access the tax data 207a on the first server 209 through a port 213 on the server 209 having port number 22. An anomaly detection system, such as the anomaly detection system 101 of
In the example embodiment, a second user 601 attempts to access resource 207 for the first time. The second user's 601 access can get routed to a second server 211 having IP address 192.168.0.3, for example, if the second user 601 happens to be physically closer to the second server 211 or if the first server 209 is busy. The anomaly detection system 101 can log the user ID, port 20 of the user machine, the IP address 192.168.0.3 of the server, and the port 22 of the server for access of 207b by the second user 601. The anomaly detection system can analyze to the logged data to determine that the second user 601 is acting anomalous.
If user 601 and user 203 belong to the same cohort, the anomaly detection system can determine based on the logged activity for user 203 that accesses to resource 207 is normal for cohort members. The anomaly detection system can analyze the logged user activity and determine that resource 207 is a distributed resource accessed through port 22 on a server. The anomaly detection system can then determine that the activity of user 601, despite being previously unlogged activity to server 192.168.0.3 by user 601, is merely routine activity of a cohort member to access resource 207b in a cohort whose members routinely access the same distributed resource 207.
If instead, user 601 is not a part of the same cohort as user 203, then the anomaly detection system can analyze the logged user activity and see that user 601 is performing anomalous user activity. Although accessing resource 207 is normal for user 203, doing so is not normal for user 601. This would even be true if user 601 were attempting to access, for the first time, resource 207a on server 209. The anomaly detection system can flag the anomalous user activity and generate a warning.
If the new activity is within the set of user activity, then the new activity is normal. At block 711, new user activity can continue to be monitored and logged.
If, on the other hand, the new activity is not within the set of user activity, then the new activity is anomalous. At block 713, a warning can be generated to warn of the anomalous activity. In some embodiments, the user activity is flagged as anomalous without generating a warning, and only after enough flagged activities accumulate does a warning get generated. At block 715, initial security measures can be taken. These can include automatic security measures that partially, but do not completely, disrupt the workflow of the anomalous user, for example, limiting the bandwidth or total data that the anomalous user can access, requiring the anomalous user to re-authenticate a username and password, generating a communication to a phone number or email to the user alerting them of suspicious activity on their user account, logging in detail activity of the user, tracing additional characteristics of the user activity (e.g., location, speed, signs of automation), running a virus scan on the anomalous user's machine, etc. These initial security measures can also include more drastic security measures such as restricting the anomalous user's access to a resource, disabling the anomalous user access to a resource, etc. These initial security measures can take place until an administrative decision is received regarding the user activity at block 717. The administrative decision can come from, for example, a network administrator, or it can come from, for example, the user suspected of anomalous activity after receiving additional verification of the user's identity such as through two factor authentication. The decision can either approve or disapprove of the new user activity at block 719.
If the new user activity is approved as normal, then at block 721, the new user activity can be added to the set of user activity for the cohort, and in the future, it will not be flagged as potentially anomalous. The system can continue to monitor for new user activity at block 711.
If, however, the new user activity is reviewed and deemed to be unauthorized network activity, the decision received might not approve the new user activity. At block 723, additional security measures can be taken. For example, the user's network access can be restricted or disabled, an attempt can be made to determine the true location and identity of the user, authorities can be alerted, recent network activity by the unauthorized user can be reversed, etc.
At block 801, similar users are sorted into a cohort. This can include, in part, performing a Jaccard similarity calculation or cosine similarity calculation. At block 803, logged data of the cohort members is analyzed to produce a histogram of the frequency of certain types of user activity. This can include, for example, resource access, port usage, etc. Initially, the logged data can include data that was previously logged and previously used to sort the users into cohorts. Data can continue to be logged after the users are sorted into cohorts. In some embodiments, data can be logged at a time starting after the users have been sorted into cohorts. This can happen, for example, after logging a sufficient amount of data, or if a long time has passed since the users were sorted into cohorts.
At block 805, the histogram data can be normalized to determine the probability of an activity. For example, if cohort members rarely access resources ABC only 1% of the time but frequently access resources XYZ 99% of the time, then the probability of an access to XYZ is 99%, and the probability of an access to ABC is 1%.
At block 807, new user activity of a user in the cohort is detected.
At block 809, a probability score for the user's activity is determined. This can be determined with reference to the normalized data. Continuing the example, if the new user activity is an access to ABC, then the probability score is low, such as 1%. In other embodiments, the probability score for the user's activity is determined based on the user's historical data combined with the user's new activity. For example, if the user previous accessed XYZ 99 times and just now accessed ABC, then the user's overall history probability score is relatively high. On the other hand, if the user previously accessed XYZ 50 times and also previously accessed ABC 50 times and is now accessing ABC again, then the user's overall history probability score is relatively low.
In some embodiments, the user's probability score for a history of user activity can be calculated according to the equation:
Where P(A,U) represents the probability P of a user U performing an activity (e.g., accessing a resource, using a certain port, etc.). The sum of the probabilities P for each past activity A of the user U is summed up and divided by the total number of activity events.
In some embodiments, the user's probability score for a history of user activity can be calculated using the Kullback-Leibler (KL) Divergence principle according to the equation:
The divergence is equal to the sum for all activities A of the probability of an action A given a cohort C times the log of the probability of an action A given cohort C divided by the probability of action A given a user U. In an application, for each activity A (e.g., access to a resource) performed by members of a cohort C, the sum is calculated of the probability of a cohort member C performing that activity A multiplied by the Log of the probability of a cohort member C performing that activity A divided by the probability of the user U performing that activity A. The resulting divergence can be as a probability score or converted into a probability score.
In some embodiments, the Log function can be an Ln function or have a different base, the cohort's divergence from the user can be calculated instead of the user's divergence from the cohort, or other applications of the principle can be used.
At block 811, it can be determined if the user's activity is probable or not. This can be done, for example, by comparing the probability score to a threshold level.
If the user's activity is probable, then at block 823, the histogram data can be dynamically updated to account for the new user activity, and the probabilities of activity are updated. At block 813, the system can continue to monitor for new user activity.
If, on the other hand, the user's activity is not probable, then the activity is anomalous. At block 815, a warning can be generated to warn of the anomalous activity. In some embodiments, the user activity is flagged as anomalous without generating a warning, and only after enough flagged activities accumulate does a warning get generated. At block 817, initial security measures can be taken. These can include automatic security measures that partially, but do not completely, disrupt the workflow of the anomalous user, for example, limiting the bandwidth or total data that the anomalous user can access, requiring the anomalous user to re-authenticate a username and password, generating a communication to a phone number or email to the user alerting them of suspicious activity on their user account, logging in detail the activity of the user, tracing additional characteristics of the user activity (e.g., location, speed, signs of automation), running a virus scan on the anomalous user's machine, etc. These initial security measures can also include more drastic security measures such as restricting the anomalous user's access to a resource, disabling the anomalous user access to a resource, etc. These initial security measures can take place until an administrative decision is received regarding the user activity at block 819. The administrative decision can come from, for example, a network administrator, or it can come from, for example, the user suspected of anomalous activity after receiving additional verification of the user's identity such as through two factor authentication. The decision can either approve or disapprove of the new user activity at block 821.
If the new user activity is approved as normal, then at block 823, the histogram data can be updated to account for the new user activity, and the probabilities of activities are updated. The system can continue to monitor for new user activity at block 813.
If, however, the new user activity is reviewed and deemed to be unauthorized network activity, the decision received might not approve the new user activity. At block 825, additional security measures can be taken. For example, the user's network access can be restricted or disabled, an attempt can be made to determine the true location and identify of the user, authorities can be alerted, recent network activity by the unauthorized user can be reversed, etc.
At block 901, attack origin distribution data is received. This can come from, for example, statistics provided from consulting or security firms. As an example, 5% of all network attacks come from Country AAA, 4% of all network attacks come from Country BBB, 3% of all network attacks come from America, 3% of all network attacks come from Country CCC, etc. When a complete set of attack origin distribution data for all countries cannot be obtained from a single source, the data can be aggregated from multiple sources. The data can be supplemented interpolating data points for missing countries based on relative danger levels. For example, Country DDD is known to be about as dangerous as Country AAA or Country BBB in terms of network attacks. Country DDD can be assigned an attack distribution from about 4% (same as Country BBB) to about 5% (same as Country AAA). For example, Country DDD can be assigned an attack distribution of 4%, 4.5%, 5%, etc. In addition, the attack distributions can be based, in part, on lists of potentially dangerous countries (e.g., countries that the U.S. is currently at war with, countries on a terrorism list, countries sanctioned by the United Nations). The countries on these lists can receive a minimum attack distribution or otherwise have their attack distribution adjusted to account for the risk. These distributions can indicate the probability of any country being the source of an attack and represented as P(CIA).
At block 903, the network activity origin distribution can be determined. This can be determined uniquely for each network implementing an anomaly detection system. This data can be collected, for example, by analyzing the user activity to determine the origin of user activity over a period of time. For example, a local American business that deals with American suppliers, American workers, and American employees can have 100% of its network access originate in America. The country of origin can be determined, at least in part, by the IP address from which a network is accessed, the latency of access to a network (lower latency can indicate closer distances), the time of day during which activity occurs, etc. In another example, a large international company can have 30% of its network access originate from America, 25% of its network access originate from Country AAA, 25% from Country BBB, and 20% from Country CCC, and 0% from Country DDD. In some embodiments, this activity origin distribution can be determined for each cohort. In some embodiments, the activity origin distribution can be determined for connections to different parts of a network. For example, the activity origin distribution can be determined for a network in America and separately determined for a network in a foreign country, or it can be determined for accesses to a database in English and separately determined for access to a database in a foreign language, etc.
At block 905, new user activity is detected. In some embodiments, the user can be a part of a cohort for which the distribution of user activity origin has been determined. At block 907, the origin of the new user activity is determined. This can be done, for example, based on the user's IP address or other techniques.
At block 909, the probability that the new user activity is an attack can be determined. The determining can be done based, at least in part, on the determined origin of the new user activity, the network activity origin distribution (e.g., for the entire network, for a part of the network, or for the user's cohort), and the attack origin distribution data. The probability that the new user activity is an attack can be determined according to the equation:
The probability of an attack A given a country C is equal to the probability of a country C given an attack A multiplied by the probability of an attack A divided by the probability of a country C. In an application, the probability that activity determined to be from country C is an attack A is equal to the probability that country C is the source of an attack A multiplied by the probability of an attack A on the network divided by the probability of activity coming from country C. The probability of an attack on the network P(A) can be a constant for networks that are under a constant threat of attacks, but this variable can also change, for example, when the rate of attacks on the network increases or decreases. In the following examples, P(A) is assumed to be constant, or at least it will be later factored out when making a comparison, so it is dropped from the equation. In an example embodiment applying the equation, the probability that the new user activity determined to be from country C is an attack is equal to the distribution of attacks coming from that country divided by the probability of network activity coming from country C.
Referring to the example with the local American business that has all of its network activity originate in America, if new user activity is determined to come from America, where 3% of all network attacks originate from, the probability of that new activity being an attack is equal to 3%/100%, or 0.03. If new user activity is determined to come from a foreign Country AAA from where 5% of all network attacks originate, then the probability of that new activity being an attack is equal to 5%/0% or 5%/(0%+1 access) depending on whether or not the last access is included in the total network access distributions, and the result is a very large number (or divide by zero) indicative of anomalous network activity.
Referring to the example with the large international company, if new user activity is determined to come from America, where 3% of all network attacks originate from, the probability of that new activity being an attack is equal to 3%/30%, or 0.1. If new user activity is determined to come from a foreign Country AAA from where 5% of all network attacks originate, then the probability of that new activity being an attack is equal to 5%/25% or 0.2. Comparing the example of the large international company to the previous example with the local American company, activity originating from foreign country AAA reflect a lower probability of a network attack for the large international company because a part of its authorized network access originates from country AAA.
At block 911, the probability that the new user activity is an attack can be compared to a threshold value to determine if the new activity is likely an attack.
If the new user activity is probably not an attack, then at block 913, new user activity can continue to be monitored and logged.
If, on the other hand, the user's activity is probably an attack, then the activity is anomalous. At block 915, a warning can be generated to warn of the anomalous activity. In some embodiments, the user activity is flagged as anomalous without generating a warning, and only after enough flagged activities accumulate does a warning get generated. At block 917, initial security measures can be taken. These can include automatic security measures that partially, but do not completely, disrupt the workflow of the anomalous user, for example, limiting the bandwidth or total data that the anomalous user can access, requiring the anomalous user to re-authenticate a username and password, generating a communication to a phone number or email to the user alerting them of suspicious activity on their user account, logging in detail activity of the user, tracing additional characteristics of the user activity (e.g., location, speed, signs of automation), running a virus scan on the anomalous user's machine, etc. These initial security measures can also include more drastic security measures such as restricting the anomalous user's access to a resource, disabling the anomalous user access to a resource, etc. These initial security measures can take place until an administrative decision is received regarding the user activity at block 919. The administrative decision can come from, for example, a network administrator, or it can come from, for example, the user suspected of anomalous activity after receiving additional verification of the user's identity such as through two factor authentication. The decision can either approve or disapprove of the new user activity at block 921.
If the new user activity is approved as normal, then at block 913, the system can continue to monitor for new user activity.
If, however, the new user activity is reviewed and deemed to be unauthorized network activity, the decision received might not approve the new user activity. At block 923, additional security measures can be taken. For example, the user's network access can be restricted or disabled, an attempt can be made to determine the true location and identity of the user, authorities can be alerted, recent network activity by the unauthorized user can be reversed, etc.
The first, second, and Nth security analysis can include, for example, anomaly detection techniques disclosed in this application. These can include for example, comparing new user activity to activity of a cohort; comparing new user activity to activity of some other group; comparing new user activity to previous network activity performed by all users; comparing new user activity to previous user behavior; determining a probability of an attack based on the origin of user activity; identifying anomalous characteristics such as an anomalous amount of data being transferred or at an anomalous time or from an anomalous source; previous or recent activity flagged as anomalous by this or other users; etc. In one example, a first security analysis analyzes the new activity in light of the user's previous activity, a second security analysis analyzes the new activity in light of the cohort's activity, and a third security analysis analyzes the origin of the user activity.
At block 1015, the risk results can be weighed. This can include determining a risk score according using the equation:
S+W
1
R
1
+W
2
R
2
+ . . . +W
N
R
N
The risk score S is equal to the sum of a weighting factor W1 times the first risk factor R1 plus a weighting factor W2 times the second risk factor R2 and so on until adding the Nth weighting factor multiplied by the Nth risk result.
At block 1017, it can be determined, based at least in part on the risk score, whether or not there is likely anomalous activity. If it is determined that the activity is anomalous, then at block 1019, a warning can be generated. In some embodiments, the warning can be an internal flag of anomalous activity, and notifications and security measures will not be taken until a threshold number of internal flags have been raised in a given time period. In other embodiments, a warning is sent to administrators and the system automatically takes measures to prevent unauthorized network access, such as disabling a user account. If it is instead determined that the user activity is not anomalous, then the system can continue to monitor for new activity at block 1021.
If it is determined that the activity is not anomalous for the user based on the user's previous history, then at block 1107 the system can continue to monitor for new user activity.
If it is determined that the activity is anomalous for the user, this does not automatically trigger a warning at block 1109. Instead, at block 1105, it can be determined whether or not the new user activity is anomalous for any of the cohorts that the user belongs to.
If the new user activity, although anomalous for the user, is nonetheless normal for users of the cohort, then at block 1107 the system can continue to monitor for new user activity.
If the new user activity is anomalous for both the user and for the cohort, then at block 1109, the system can generate a warning of anomalous user activity.
Although the example method 1100 shows a specific analysis being performed, it can be generalized to include other types of analysis and additional analysis steps. In some embodiments, the methods can be performed in series or parallel with each other. In some embodiments, certain security analysis can directly generate flags or warnings of anomalous behavior even if other types of analysis do not generate warnings of anomalous behavior.
The disclosed methods discuss a variety of potential responses to detecting an anomaly. The methods can use a variety of responses when an anomaly is detected. Conclusive anomaly detection can cause immediate security measures such as revoking access to the network and warning administrators. Likely but inconclusive detection can result in less drastic measures such as limiting access to a lesser degree, raising internal flags, increasing network security, sending warnings, etc. In some embodiments, an initial anomaly detection will cause a user to be flagged as anomalous, and only after a certain number of flags is reached within a period of time will additional action be taken.
The disclosure also discusses logged activity. Where the context allows, logged activity can include all logged activity or logged activity for a selected period of time, such as the past 30 days. For example, when analyzing a new user activity against logged activity of the user, the logged activity of the user can be recent activity within the past year, excluding the new user activity.
The disclosure also discusses new user activity on a network. Where the context allows, this includes newly attempted user activity, newly performed user activity, and new activity being performed.
According to one embodiment, the techniques described herein are implemented by one or more special-purpose computing devices. The special-purpose computing devices can be hard-wired to perform the techniques, or can include digital electronic devices such as one or more application-specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs) that are persistently programmed to perform the techniques, or can include one or more general purpose hardware processors programmed to perform the techniques pursuant to program instructions in firmware, memory, other storage, or a combination. Such special-purpose computing devices can also combine custom hard-wired logic, ASICs, or FPGAs with custom programming to accomplish the techniques. The special-purpose computing devices can be desktop computer systems, server computer systems, portable computer systems, handheld devices, networking devices or any other device or combination of devices that incorporate hard-wired and/or program logic to implement the techniques.
Computing device(s) are generally controlled and coordinated by operating system software, such as iOS, Android, Chrome OS, Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server, Windows CE, Unix, Linux, SunOS, Solaris, Blackberry OS, VxWorks, or other compatible operating systems. In other embodiments, the computing device can be controlled by a proprietary operating system. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system, networking, I/O services, and provide a user interface functionality, such as a graphical user interface (GUI), among other things.
For example,
Computer system 1200 includes a bus 1202 or other communication mechanism for communicating information, and a hardware processor, or multiple processors, 1204 coupled with bus 1202 for processing information. Hardware processor(s) 1204 can be, for example, one or more general purpose microprocessors.
Computer system 1200 also includes a main memory 1206, such as a random access memory (RAM), cache and/or other dynamic storage devices, coupled to bus 1202 for storing information and instructions to be executed by processor 1204. Main memory 1206 also can be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 1204. Such instructions, when stored in storage media accessible to processor 1204, render computer system 1200 into a special-purpose machine that is customized to perform the operations specified in the instructions.
Computer system 1200 further includes a read only memory (ROM) 1208 or other static storage device coupled to bus 1202 for storing static information and instructions for processor 1204. A storage device 1210, such as a magnetic disk, optical disk, or USB thumb drive (Flash drive), and so forth, is provided and coupled to bus 1202 for storing information and instructions.
Computer system 1200 can be coupled via bus 1202 to a display 1212, such as a cathode ray tube (CRT) or LCD display (or touch screen), for displaying information to a computer user. An input device 1214, including alphanumeric and other keys, is coupled to bus 1202 for communicating information and command selections to processor 1204. Another type of user input device is cursor control 1216, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 1204 and for controlling cursor movement on display 1212. This input device typically has two degrees of freedom in two axes, a first axis (for example, x) and a second axis (for example, y), that allows the device to specify positions in a plane. In some embodiments, the same direction information and command selections as cursor control can be implemented via receiving touches on a touch screen without a cursor.
Computing system 1200 can include a user interface module to implement a GUI that can be stored in a mass storage device as executable software codes that are executed by the computing device(s). This and other modules can include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.
In general, the word “module,” as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, possibly having entry and exit points, written in a programming language, such as, for example, Java, Lua, C or C++. A software module can be compiled and linked into an executable program, installed in a dynamic link library, or can be written in an interpreted programming language such as, for example, BASIC, Perl, or Python. It will be appreciated that software modules can be callable from other modules or from themselves, and/or can be invoked in response to detected events or interrupts. Software modules configured for execution on computing devices can be provided on a computer readable medium, such as a compact disc, digital video disc, flash drive, magnetic disc, or any other tangible medium, or as a digital download (and can be originally stored in a compressed or installable format that requires installation, decompression, or decryption prior to execution). Such software code can be stored, partially or fully, on a memory device of the executing computing device, for execution by the computing device. Software instructions can be embedded in firmware, such as an EPROM. It will be further appreciated that hardware modules can be comprised of connected logic units, such as gates and flip-flops, and/or can be comprised of programmable units, such as programmable gate arrays or processors. The modules or computing device functionality described herein are preferably implemented as software modules, but can be represented in hardware or firmware. Generally, the modules described herein refer to logical modules that can be combined with other modules or divided into sub-modules despite their physical organization or storage
Computer system 1200 can implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computer system causes or programs computer system 1200 to be a special-purpose machine. According to one embodiment, the techniques herein are performed by computer system 1200 in response to processor(s) 1204 executing one or more sequences of one or more instructions included in main memory 1206. Such instructions can be read into main memory 1206 from another storage medium, such as storage device 1210. Execution of the sequences of instructions included in main memory 1206 causes processor(s) 1204 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry can be used in place of or in combination with software instructions.
The term “non-transitory media,” and similar terms, as used herein refers to any media that store data and/or instructions that cause a machine to operate in a specific fashion. Such non-transitory media can comprise non-volatile media and/or volatile media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 1210. Volatile media includes dynamic memory, such as main memory 1206. Common forms of non-transitory media include, for example, a floppy disk, a flexible disk, hard disk, solid state drive, magnetic tape, or any other magnetic data storage medium, a CD-ROM, any other optical data storage medium, any physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip or cartridge, and networked versions of the same.
Non-transitory media is distinct from but can be used in conjunction with transmission media. Transmission media participates in transferring information between non-transitory media. For example, transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 1202. Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.
Various forms of media can be involved in carrying one or more sequences of one or more instructions to processor 1204 for execution. For example, the instructions can initially be carried on a magnetic disk or solid state drive of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 1200 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal. An infra-red detector can receive the data carried in the infra-red signal and appropriate circuitry can place the data on bus 1202. Bus 1202 carries the data to main memory 1206, from which processor 1204 retrieves and executes the instructions. The instructions received by main memory 1206 can retrieve and execute the instructions. The instructions received by main memory 1206 can optionally be stored on storage device 1210 either before or after execution by processor 1204.
Computer system 1200 also includes a communication interface 1218 coupled to bus 1202. Communication interface 1218 provides a two-way data communication coupling to a network link 1220 that is connected to a local network 1222. For example, communication interface 1218 can be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, communication interface 1218 can be a local area network (LAN) card to provide a data communication connection to a compatible LAN (or WAN component to communicate with a WAN). Wireless links can also be implemented. In any such implementation, communication interface 1218 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
Network link 1220 typically provides data communication through one or more networks to other data devices. For example, network link 1220 can provide a connection through local network 1222 to a host computer 1224 or to data equipment operated by an Internet Service Provider (ISP) 1226. ISP 1226 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the “Internet” 1228. Local network 1222 and Internet 1228 both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on network link 1220 and through communication interface 1218, which carry the digital data to and from computer system 1200, are example forms of transmission media.
Computer system 1200 can send messages and receive data, including program code, through the network(s), network link 1220 and communication interface 1218. In the Internet example, a server 1230 might transmit a requested code for an application program through Internet 1228, ISP 1226, local network 1222 and communication interface 1218.
The received code can be executed by processor 1204 as it is received, and/or stored in storage device 1210, or other non-volatile storage for later execution.
To provide a framework for the above discussion of the specific systems and methods described herein, an example system will now be described. This description is provided for the purpose of providing an example and is not intended to limit the disclosure.
Each of the processes, methods, and algorithms described in the preceding sections can be embodied in, and fully or partially automated by, code modules executed by one or more computer systems or computer processors comprising computer hardware. The processes and algorithms can be implemented partially or wholly in application-specific circuitry.
At block 1308, a rule can be used to determine if the user is accessing the network from a safe country. This can be a whitelist of countries, such as NATO countries, or based on a blacklist. For some networks, a custom or dynamic list can be used. If the network access is determined to be from an unsafe location, such as from a blacklisted country, then an anomaly can be flagged at block 1312. In some embodiments, an access from an unsafe country can affect a score indicative of the likelihood of an anomaly.
Upon determining that the network access is from a safe or trusted location, at block 1314 a host score can be determined based at least on the hostname used to access the network. The host score can reflect the likelihood anomalous user activity given an access from a new hostname.
Upon determining that the network access is from a safe or trusted location, at block 1316 a speed score can be determined based at least on a minimum theoretical speed of the user based on location and timestamps of consecutive network accesses from the same user.
Upon determining that the network access is from a safe or trusted location, at block 1320 a location score can be determined based at least on the location from which the network is being accessed. Even within the list of safe access locations, accesses from some locations can be more suspicious than others. For example, for a network in New York with all of its users in New York, an access from New York can have a score of zero, an access from a different state such as California can have a score such as 10, and an access from the United Kingdom can have a score of 50.
At block 1324, an aggregate score for the network access can be determined. The aggregate score can be a weighted score based on at least two of the hostname score, the speed score, and the location score.
At block 1328, the aggregate score can be convoluted with other logged scores for the user to determine a convoluted score. The convolution can be with an impulse, pulse, triangle, curve, or other function. The convolution can be performed for a certain period of time or a certain number of log entries.
At block 1332, the highest convoluted score can be displayed in a user interface for an administrator. In some embodiments, an aggregate score can be displayed in the user interface.
At block 1336, the convoluted scores that exceed a threshold convoluted score can be displayed in a user interface for the administrator. In some embodiments, an aggregate score exceeding an aggregate threshold can be displayed in the user interface.
In the embodiment shown, when the network 205 is accessed from user 203, a log entry 1404 is generated to include the timestamp 1408a of the network access event. The username 1412a is “John Doe.” John Doe can access the network 205 by presenting the proper credentials (e.g., password). The network 205 is accessed from a computing device 203 that has a hostname “CPU2-WIN7,” 1416a, which is logged in the entry 1404. The IP address 1420a that John Doe uses to access the network 205 is also logged.
The username 1412a and hostname 1416a can be matched against other log entries 1424 in the same or a different log. In the other log entries 1424, the user John Doe 1432 is identified, and the corresponding hostnames 1436 that John Doe used to access the network from can be obtained. In the entries 1424, John Doe has previously accessed the network from a device hostname “CPU1-WINXP” and “Phone-IOS,” the devices respectively being his work computer and cellphone. The history of past log entries 1424 does not contain “CPU2-WIN7,” so this new hostname would be the third unique hostname 1444, which can be logged in the expanded log entry 1440. In some embodiments, the expanded log entry 1440 can be the same as log entry 1404, but with more data added, and in some embodiments, the expanded log entry can be a different log.
The IP address 1420a can be input into an IP lookup system 1464 to determine the country 1448, city 1452, longitude 1456, and latitude 1460 of the IP address. In the embodiment, the user's IP address 1420a is traced to the USA in the city of Los Angeles, located at 34° N, 118° W. The IP address 1420b, country 1448, city 1452, longitude 1456, and latitude 1460 are logged into the expanded log entry 1440.
The graph can reflect a reality that is counter to intuition and expectations. It can be expected that a single user has a limited number of computers, and so the single user will not access the same network through a large number of devices. Along the same line of reasoning, if a user accesses a network from many different devices (e.g., 3, 5, 10, 20, 50, 100 or more), then the accesses from the different machines must in fact be from different people at different machines who have compromised the username and password.
However, as the graph shows, this expectation does not conform to results. As the graph shows, a user typically accesses a network through a small number of devices with different hostnames. For example, a user might have a work computer, a laptop at home, and a smartphone to access the network—a total of three devices. The probability of a network access being from the non-malicious user decreases until a number 1520 of hostnames have been used to access the network for the reasoning described above. However, past that number 1520 of hostnames, the probability of a non-malicious user accessing the network from new hostnames begins to become high again.
This is because, for many networks, the administrators, technical support personnel, and other specialized network users need to log into the network from a large number of machines. If a certain user has previously accessed the network from a large number of machines with different hostnames and then accesses the network again from a new hostname, it is more likely that the new access is non-malicious actor (such as an IT guy who sets up everyone's computer now setting up a new employee's computer) instead of being from a malicious actor.
As a result, the anomaly detection system can assign a higher probability score of a non-malicious actor for a first network access from a unique Nth hostname (e.g., at a 5th, 10th, 20th, 50th, 100th or higher) than it did for a first network access from a number 1520 of hostnames that is lower than the Nth hostname. It can also assign a higher probability score of a non-malicious actor for a first network access from a low number unique hostnames (e.g., at a 1st, 2nd, 3rd, 5th) than it does for when the network is accessed from a number 1520 of unique hostnames that is higher than the low number of unique hostnames. The number 1520 can vary. In some embodiments, the number 1520 ranges from 3 to 15.
The graph 1550 shows that a single user accessing the network from a few different hostnames is not likely to be a malicious actor. However, the probability of an access to the network from a new hostname increases until a number 1570 of unique hostnames have been used to access the network. Then, further accesses to the network from additional unique hostnames are not as likely to be malicious actors.
The graphs 1500 and 1550 can vary with time and user. For example, after a new user is authorized to a network, there is an initial setup period where the user can use a multitude of devices with different usernames to access the network for the first time. It would not be anomalous during this time period for the user to use 3, 5, or 10 different devices. However, a longtime user with an established history of using N devices can cause suspicion when the N+1th device is used to access the network. In effect, for a time range, the network anomaly detestation systems can normalize a user's number of devices, raise flags or increase an anomaly score when the next few (e.g., the next 1, 2, 3, 4, 5) hostnames are used by that user to access the network, and not raise flags or use lower anomaly scores when a high number of hostnames are used to access the network.
The data table shows entries for the username John Doe, with the new log from
Log entry 3 shows that on January 23, at 9 PM, John Doe used his cellphone with hostname Phone-IOS to access the network from an IP address originating in New York. This is John Doe's second new hostname, so a host score of 30 is assigned, which is weighted by 0.5× to generate an aggregate score of 15.
Log entry 4 shows that on January 23 at 11 PM, John Doe used a new computer with hostname CPU2-WIN7 to access the network from an IP address originating in Los Angeles. Using the longitude and latitude information, it can be determined that in traveling from New York to Los Angeles in two hours requires flying at about 1,400 miles per hour, about MACH-2 or twice the speed of sound. First, because a 3rd new hostname is used, a high host score of 70 is assigned. Next, because of the highly unlikely speed that John Doe would have needed to travel, a speed score of 100 is assigned. Finally, because the location is not from John Doe's ordinary New York location, but still within a popular domestic American city, a low location score of 10 is assigned. The host score is weighted by 0.5×, the speed score is weighted by 1×, and the location score is weighted by 0.8×. The scores are added to generate an aggregate score of 143, indicating a high chance of anomalous activity by a malicious user who compromised John Doe's network login credentials.
Log entry 5 shows that on January 24 at 9 AM, John Doe used his computer with hostname CPU1-WINXP to access the network from a IP address located in New York. No new hostname is used, so no host score is assigned. However, a small speed score of 30 is assigned because John Doe would need to have traveled back to New York at about 275 miles per hour, a reasonable speed for a commercial airliner. The resulting aggregate score is 30 after weighting the speed score with 1×.
Log entries 6-10 show John Doe using his CPU1-WINXP and Phone-IOS computers to access the network on subsequent days from New York, and no anomalous activity is detected.
In some embodiments, high aggregate scores can be flagged and reported to a network administrator, or other precautionary measures can be taken such as restricting or denying access to the network.
In some embodiments, convolution can be used to generate a convoluted score reflecting the anomalous probability given multiple log entries. The convolution score is the mathematical convolution of the aggregate scores with a function. The function can be illustrated as convolution curve 1670A, can be applied to multiple entries to generate the convoluted scores. The entries can be proximate in the data table within a number of lines or within a time range (e.g., same day, 24 hours, 48 hours). In the embodiment shown in
In some embodiments, the convoluted score can be used to detect anomalous network activity if it exceeds a threshold value. It can be reported to an administrator, or the network can automatically take actions such as restricting or denying access to the user.
In addition to using convolution to represent the anomalous potential of multiple log entries, other techniques can be used to give the appropriate weight to multiple log entries.
In one embodiment, a small score (e.g., 20) for an unsuccessful login attempt can be logged. By itself, the unsuccessful login attempt might not be high enough to be flagged as anomalous activity, as it may simply be a non-malicious user who mistyped a password. However, the small scores of 20 from repeated (for example, 5) unsuccessful login attempts within a time period can be added up to 100, a score that can be flagged as an anomaly.
As described above, the example user interface 10 includes user compromise scores associated with “Remote Access” 1, and includes user compromise scores measuring types of user behavior when user accounts, or network accessible systems, are initially accessed.
For instance, the “Host Score” 1722 for a particular user account is a measure associated with network accessible systems the particular user account accessed. The “Host Score” 1724 can be based off a number of network accessible systems an average user account accesses, and a number of systems the particular user account normally accesses. In addition to a number of network accessible systems, the “Host Score” 1724 can be greater if the particular user account has recently accessed network accessible systems not historically associated with the particular user account.
The “Speed Score” 1726 for a particular user account measures how likely it is that a single user has accessed the particular user account from disparate locations in a period of time. For instance, if the particular user account was accessed in a first remote session from a first location (e.g., New York), and a short period of time later (e.g., 15 minutes), accessed from a second location (e.g., Los Angeles), the “Speed Score” 1726 can indicate that one user could not travel fast enough between those two locations to effect the two remote sessions.
The “Location Score” 1728 for a particular user account measures risk associated with the locations from which the particular user account was accessed. For instance, a particular geographic region can be known (e.g., to a system administrator) to be associated with malicious activity. The “Location Score” 1728 can thus be greater if the particular user account is being accessed from the particular geographic region. Additionally, the “Location Score” 1728 can be greater if the particular user account is being accessed from geographic regions that the particular user account has not, or rarely, previously been accessed from.
The “Anomaly Score” 1722 for a particular account is a combination of the “Host Score” 1724, “Speed Score” 1726, and “Location Score” 1728. In some implementations, the “Anomaly Score” 1722 is a convolution of the weighted sum taken over time with a user selectable window size. In some embodiments, the “anomaly score” 1722 is the aggregate score.
The user interface 1700 further includes a map 1716 of the Earth, and countries which remote sessions (e.g., VPN sessions) to access user accounts have emanated from. In some implementations, the map 1716 can be a heat-map identifying a frequency of the access, and each country in the map 1716 can be selectable by a user. Upon selection of a country, the user interface 1710 can be updated to include user accounts that have been accessed from the selected country.
A user of the user interface 1710 can mark a particular user account according to a “Triage Status” 1730, which can include an identification of whether the particular user account needs further review, or has already been reviewed (e.g. the user can mark the particular user account according to a color code system such as red or green displayed in the graph 38). In this way, a different user can view the user interface 1710, and identify a user account to review according to the “Triage Status” 1730.
Additionally, the user interface 1730 includes summary data describing user accounts associated with the business. For instance, the summary data can include a graph identifying a number of countries 1732 that user accounts have been accessed from, a graph identifying a number of network accessible systems or “Hosts” 1734 that each user account has accessed, determined distribution of anomaly scores 1736, and a graph identifying a number of user accounts for each “Triage Status” 1738 identified by users of the user interface 1710.
Utilizing the user interface 1710, a user (e.g., a system administrator) can gain valuable insights into the user accounts associated with the business. The user can determine that a particular user account is need of further review, and can select the particular user account to view more detailed information.
The various features and processes described above can be used independently of one another, or can be combined in various ways. All possible combinations and sub-combinations are intended to fall within the scope of this disclosure. In addition, certain method or process blocks can be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate. For example, described blocks or states can be performed in an order other than that specifically disclosed, or multiple blocks or states can be combined in a single block or state. The example blocks or states can be performed in serial, in parallel, or in some other manner. Blocks or states can be added to or removed from the disclosed example embodiments. The example systems and components described herein can be configured differently than described. For example, elements can be added to, removed from, or rearranged compared to the disclosed example embodiments.
Conditional language, such as, among others, “can,” “could,” “might,” or “can,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment. Where the context permits, words in the Detailed Description using the singular or plural number can also include the plural or singular number, respectively. The words “or” in reference to a list of two or more items, is intended to cover all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.
The term “comprising” as used herein should be given an inclusive rather than exclusive interpretation. For example, a general purpose computer comprising one or more processors should not be interpreted as excluding other computer components, and may possibly include such components as memory, input/output devices, and/or network interfaces, among others.
Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions can be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art. Furthermore, the embodiments illustratively disclosed herein may be suitably practiced in the absence of any element or aspect which is not specifically disclosed herein.
It should be emphasized that many variations and modifications can be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure. The foregoing description details certain embodiments of the invention. It will be appreciated, however, that no matter how detailed the foregoing appears in text, the invention can be practiced in many ways. As is also stated above, it should be noted that the use of particular terminology when describing certain features or aspects of the invention should not be taken to imply that the terminology is being re-defined herein to be restricted to including any specific characteristics of the features or aspects of the invention with which that terminology is associated. The scope of the invention should therefore be construed in accordance with the appended claims and any equivalents thereof.
The present disclosure references various features of and claims priority to U.S. patent application Ser. No. 14/970,317, filed Dec. 15, 2015, which application claims priority to U.S. Provisional Pat. App. No. 62/185,453, filed Jun. 26, 2015, and U.S. Provisional Pat. App. No. 62/207,297, filed Aug. 19, 2015. The entire disclosure of those applications are hereby made part of this specification as if set forth fully herein and incorporated by reference for all purposes, for all that it contains.
| Number | Date | Country | |
|---|---|---|---|
| 62207297 | Aug 2015 | US | |
| 62185453 | Jun 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14970317 | Dec 2015 | US |
| Child | 15224443 | US |
