System and method for malware detection learning

SYSTEM AND METHOD FOR MALWARE DETECTION LEARNING

FIELD OF THE DISCLOSURE

The present disclosure relates generally to data security, and particularly to methods and systems for detecting malicious software in computer systems.

BACKGROUND OF THE DISCLOSURE

Various types of malicious software, such as viruses, worms and Trojan horses, are used for conducting illegitimate operations in computer systems. Malicious software may be used, for example, for causing damage to data or equipment, or for extracting or modifying data. Some types of malicious software communicate with a remote host, for example for Command and Control (C&C) purposes .

Various techniques for detecting malicious software are known in the art. For example, Rieck et al. describe methods for detecting malicious software at a point when it initiates contact with its maintainer, in Botzilla: Detecting the 'Phoning Home' of Malicious Software, Proceedings of the ACM Symposium on Applied Computing (SAC), Sierre, Switzerland, March 22-26, 2010.

Jacob et al. describes a system for identifying C&C connections, in JACKSTRAWS: Picking Command and Control Connections from Bot Traffic, Proceedings of the 20^thUsenix Security Symposium, San Francisco, California, August 8-12, 2011.

Gu et al. describe a method that uses network-based anomaly detection to identify botnet C&C channels in a local area network, in BotSniffer: Detecting Botnet Command and Control Channels in Network Traffic, Proceedings of the 15^th Annual Network and Distributed

226,747/2 System Security Symposium (NDSS'08), San Diego, California, February, 2008.

Gu et al. describe a C&C detection framework that is independent of botnet C&C protocol and structure, in BotMiner: Clustering Analysis of Network Traffic for

Protocol- and Structure-Independent Botnet Detection, Proceedings of the 17^th USENIX Security Symposium, San

<td> Jose, California,</td><td> 2008 .</td>

Eslahi describes methods for detecting HTTP-based Botnets based on the network behaviour analysis, in botAnalytics: Improving HTTP-Based Botnet Detection by Using Network Behavior Analysis System, Faculty of

<td> Computer Science</td><td> and Information Technology, University</td>

of Malaya, 2010.

<td> US patent</td><td> 8,402,543 describes machine learning</td>

algorithms for botnet detection.

SUMMARY OF THE DISCLOSURE

An embodiment that is described herein provides a method including monitoring a protected computer network that is to be protected from malicious software, and an infected computer network that is known to be infected with malicious software. First communication transactions that are known to be malicious are extracted from both the protected computer network and the infected computer network. Second communication transactions that are not known to be malicious are extracted only from the protected computer network. One or more malicious

1011-1091S2 communication transactions exchanged with the protected computer network are identified by processing the first and second communication transactions.

In some embodiments, extracting the first communication communication transactions includes selecting the transactions depending on reputation first levels of respective transactions .

hosts participating in the communication

In an embodiment, extracting the first communication transactions includes including transaction in the first communication transactions if host participating in the transaction appears on blacklist.

In some disclosed embodiments, identifying the malicious communication transactions includes creating, based on the extracted first and second communication transactions, one or more models that distinguish the malicious communication transactions from innocent communication transactions, and detecting the malicious communication transactions using the models. In an example embodiment, identifying the malicious communication transactions includes generating alerts based on the models, receiving an analysis of the alerts from an operator, and detecting the malicious communication transactions based on the analysis of the alerts by the operator.

Identifying the malicious communication transactions may include adapting the models based on the analysis of the alerts by the operator. In a disclosed embodiment, extracting the first communication transactions includes selecting the first communication transactions depending on reputation levels of respective hosts participating in the communication transactions, and the method includes

1011-1091S2 updating at least one of the reputation levels based on the analysis of the alerts by the operator.

The method may include updating selection of the first communication transactions based on the updated reputation levels, and updating identification of the malicious communication transactions by processing the updated first communication transactions. In another embodiment, the method includes extracting from the infected computer network one or more third communication transactions that are not known to be malicious, and identifying the malicious communication transactions includes jointly processing the second and third communication transactions.

There is additionally provided, in accordance with an embodiment that is described herein, a system including a network interface and a processor. The network interface is configured to monitor a protected computer network that is to be protected from malicious software, and an infected computer network that is known to be infected with malicious software. The processor is configured to extract, from both the protected computer network and the infected computer network, first communication transactions that are known to be malicious, to extract, only from the protected computer network, second communication transactions that are not known to be malicious, and to identify one or more malicious communication transactions exchanged with the protected computer network, by processing the first and second communication transactions.

The present disclosure will be more fully from the following detailed description understood of the

1011-1091S2 embodiments thereof, taken together with the drawings in which:

BRIEF DESCRIPTION OF THE DRAWINGS

Fig. 1 is a block diagram that schematically illustrates a system for malicious software detection, in accordance with an embodiment that is described herein; and

Fig. 2 is a flow chart that schematically illustrates a method for detecting malicious software, in accordance with an embodiment that is described herein.

DETAILED DESCRIPTION OF EMBODIMENTS

OVERVIEW

Some types of malicious software (malware) are controlled by a remote host. Communication between the malware and the host is referred to herein as Command and Control (C&amp;C) communication, and it may involve communication from the host to the malware and/or from the malware to the host. In some cases, communication between the malware and the controlling host may be carried out via one or more intermediary hosts for the purpose of hiding the IP address of the controlling host, and this type of communication is also referred to herein as C&amp;C communication between malware and remote host.

Embodiments that are described herein provide improved malware detection techniques, which detect malware by identifying the C&amp;C communication between the malware and the remote host, and distinguish between communication transactions that carry C&amp;C communication and transactions of innocent traffic.

In the disclosed embodiments, a malware detection system is configured to protect a computer network,

1011-1091S2 referred to as a protected network or a client network.

The system receives from the protected network communication transactions, e.g.,

HTTP request-response transactions, and attempts to detect transactions relating to malware.

The system typically distinguishes between malware transactions and innocent transactions using malware identification models, which it adapts using machine learning algorithms. In some embodiments, the system trains the machine learning algorithms using external information that points to some transactions as likely to be exchanged with malicious remote hosts. For example, the system may query a reputation database that specifies reputation levels for respective hosts, or a blacklist of hosts known to be malicious .

In practice, however, the number and variety of malicious transactions that can be obtained from the protected network are often extremely limited (often fractions of a percent), too limited for effectively training the machine learning algorithms. Therefore, in some embodiments the system obtains additional malicious transactions from another computer network that is known to be relatively rich in malicious activity. This network is referred to herein as an infected network.

The system is thus able to adapt the malware identification models based on a large number of positive examples

The malicious transactions obtained from both the protected network and the infected network. As a result, the malware identification models are adapted with high speed and accuracy.

Combining malicious transactions from different networks is feasible because, while the features of

1011-1091S2 innocent transactions often differ substantially from one network to another, the features of malicious transactions tend to be similar in different networks.

In some embodiments, malware detection results of the system are fed back and used for updating the host reputation database or blacklist. In an example embodiment, the system generates malware alerts and presents them to an operator. The operator analyzes the alerts and the corresponding transactions, and provides feedback as to the identification quality. This feedback is used both for adapting the models and for updating the reputation database or blacklist. The updated reputation database or blacklist can then be used to detect new types of malware, possibly in a different infected computer in the protected network that communicates with the malicious host. The new malware samples are analyzed, their features extracted, and served to further to enrich the machine learning model.

SYSTEM DESCRIPTION

Fig. 1 is a block diagram that schematically illustrates a system 20 for malicious software (malware) detection, in accordance with an embodiment that is described herein. System 20 is used for protecting a computer network 24 (referred to as protected network or client network) from malware such as viruses, worms or Trojan horses.

Protected network 24 may comprise, for example, an internal computer network of an organization that comprises multiple computers 26, such as personal computers, workstations, mobile computing or communication devices or virtual machines. Protected

1011-1091S2 network 24 is typically connected to public such as the Internet (not shown). Computers 26 may communicate with one another over network 24, and/or with servers or other computers in the public network.

In some scenarios, a certain computer 26 in protected network 24 may be infected with malware that carries out various kinds of illegitimate actions, for example stealing data from the infected computer or otherwise from network 24, modify or damage data, or cause damage to the infected computer or other equipment of network 24. In other scenarios, protected network 24 may comprise multiple infected computers, communicating with one bridgehead computer in network 24. The bridgehead computer in turn communicates with the public network. In these scenarios we typically refer to the bridgehead computer as the infected computer whose transactions are to be identified.

Some types of malware are controlled by a remote host, typically external to network 24. Communication between the malware and the remote host may be bidirectional (e.g., command and control between the host and the malware, and extracted data from the malware to the host) or unidirectional (e.g., only from the host to the malware, or only from the malware to the host).

In some embodiments, system 20 identifies malicious software that has infected one or more of computers 26 of network 24, by monitoring communication transactions in or with network 24, e.g., internal communication within network 24 and/or communication between network 24 and the public network. System 20 attempts to identify C&amp;C communication between the malware and its remote host.

1011-1091S2

In the disclosed embodiments, system 20 also monitors communication transactions in or with an additional network 28, which is referred to as an infected network. Network 28 is known to be relatively

<td> rich in</td><td> malicious i</td><td> activity. Infected</td><td colspan="2"> network 28</td><td> is</td>

<td> typically</td><td colspan="2"> not protected from malware</td><td> by</td><td> system</td><td> 20 .</td>

<td> Instead,</td><td colspan="2"> system 20 uses infected network</td><td> 28</td><td colspan="2"> for obtaining</td>

<td> positive</td><td> examples</td><td> transactions that</td><td> are</td><td> known to</td><td> be</td>

<td> malicious</td><td> for the</td><td colspan="2"> purpose of training</td><td colspan="2"> the machine</td>

<td> learning</td><td> algorithms</td><td> that identify</td><td> the</td><td> malware</td><td> in</td>

<td> protected</td><td> network 24</td><td> This mechanism</td><td> is</td><td> explained</td><td> in</td>

<td colspan="2"> detail below.</td><td></td><td></td><td></td><td></td>

<td> The</td><td> monitoring</td><td> of networks 24</td><td> and</td><td> 2 8 is</td><td> not</td>

necessarily performed at the same time. In an example implementation, the infected network is monitored and analyzed first, and the protected network monitored and analyzed later. Additionally or alternatively to obtaining known malicious transactions from infected network 28, positive examples may be obtained from various other suitable sources that are separate from protected network 24.

In some embodiments, system 20 queries a host reputation database 32 as part of the malware identification process. Database 32 publishes reputation levels of respective hosts (e.g., domains or Web servers on the Internet) . The reputation of a host is indicative of the trust level of the host or the likelihood that the host is innocent. In one example embodiment, the reputation database comprises a blacklist, i.e., a list of hosts that are likely to be malicious and should not be trusted. In other embodiments, determination of well known C&amp;C channels may be performed using other methods,

1011-1091S2 such as pattern matching on the content of monitored communications .

In the example embodiment of Fig. 1, system 20 comprises a network interface 40 for communicating with network 24, network 28 and reputation database 32, a processor that carries out the methods described herein, and an operator interface 48 for interacting with an operator 36. Processor 40 comprises various modules - A data extraction and statistics module 52, a malware identification learning module 56 (learning module, for brevity), a malware identification module 60, and a threshold comparison module 64. The roles and functions of these modules will be explained in detail below.

The configurations of system 20 and of processor 44 shown in Fig. 1 are example configurations, which are chosen purely for the sake of conceptual clarity. In alternative embodiments, any other suitable system and/or processor configuration can be used. For example, the functions of processor 44 may be carried out using a different partitioning into modules than the one shown in the figure.

Some elements of system 20 may be implemented in hardware, e.g., in one or more Application-Specific Integrated Circuits (ASICs), Field-Programmable Gate Arrays (FPGAs) or network processors. Additionally or alternatively, some elements of system 20 can be implemented using software, or using a combination of hardware and software elements.

Some of the functions of system 20, such as the functions of processor 44, may be carried out using one or more general-purpose processors (e.g., servers), which are programmed in software to carry out the functions

1011-1091S2 described herein. The software may be downloaded to the processors in electronic form, over a network, for example, or it may, alternatively or additionally, be provided and/or stored on non-transitory tangible media, such as magnetic, optical, or electronic memory.

As noted above, the malware that infects computers 26 is assumed to communicate with a remote host. The communication between the malware and the host is referred to herein as C&amp;C communication. In some embodiments, processor 44 identifies C&amp;C communication transactions that are disguised as an innocent exchange of request-response transactions of a conventional protocol. Further aspects of such malware detection techniques are addressed in Israel Patent Application 219499, filed April 30, 2012, and Israel Patent Application 222648, filed October 23, 2012, which are assiqned to the assiqnee of the present patent application and whose disclosures are incorporated herein by reference.

MALWARE DETECTION USING ENRICHED MALWARE RECORDS OBTAINED FROM INFECTED NETWORK

Since network 24 is protected from malware, at least to some extent, transactions that the number and variety of malware can be obtained from network 24 are typically small.

The limited number and variety of malware transactions may be problematic for adaptinq the malware identification models of system 20: In a machine learninq environment where the number of true positives is very low relative to the true neqatives, the quality and speed with which the machine learninq alqorithms are trained typically depends on the availability of positive

1011-1091S2 examples, transactions that are known to be malicious .

Thus, in some embodiments system 20 enriches the collection of positive examples by obtaining additional malicious examples from infected network 28. Network 28 may comprise any suitable computer network that is able to provide additional samples of transactions that are known to be malicious. Typically, network 28 is chosen to be a network known to be relatively rich in malicious activity.

Various types of networks can serve as infected for example honey-pot networks specially designed to attract malware, networks whose malware protection is known to be weak such as Internet Service that are often rich in malware, sandbox networks, lab networks used for testing known malware, or any other suitable network.

In the present example, network interface 40 receives communication transactions both from protected network 24 and from infected network 28 (as noted above not necessarily at the same time) . Data extraction &amp;

statistics module 52 analyzes the transactions so as to extract the following:

Malware transactions from protected network 24.

Transactions that are not known to be malware transactions (referred to as unknown transactions for brevity) from protected network 24.

Malware transactions from infected network 28.

As noted above, in a typical embodiment, unknown transactions are extracted only from protected network 24 and not from infected network 28. Nevertheless, in some

1011-1091S2 embodiments module may extract some unknown transactions from and use them together with the unknown transactions obtained from protected network 24. This sort of solution may typically be chosen if networks 24 and 28 are sufficiently similar (e . g., in terms of the number of hosts, the existence or absence of NAT/proxy, protection mechanisms, and other factors). The number of unknown transactions obtained from infected network is typically smaller than the number of unknown transactions obtained from protected network 24.

Module 52 may use any suitable means for distinguishing between known malware transactions and unknown transactions. In the present example, processor 44 queries reputation database 32 with the host names or addresses of the hosts that participate in the transactions. Depending on the reputation levels specified in database 32, module 52 is able to extract a suitable selection of known malware transactions from networks 24 and 28, and unknown transactions from network 24 .

Typically, module 52 extracts certain features from the transactions, whose values help to distinguish malware transactions from innocent transactions. Some possible features relate to the underlying requestresponse protocol (e.g., HTTP), some features are statistical. Further aspects of such features and their correlation with malware identification are addressed in

Israel Patent Applications 219499 and 222648, cited above .

For each transaction (malicious or not, from network or 28), module 52 generates a respective record that

1011-1091S2 is indicative of the extracted feature values. Thus, module 52 generates a volume of malware records (records derived from malware transactions) and unknown records (records derived from transactions that are unknown to be malicious).

The malware records and unknown records are sent from module 52 to learning module 56. Learning module 56 uses the records to adapt one or more malware identification models that are used by processor 44 to identify malware transactions. Since the malware records are enriched with additional malware records from infected network 28, the models can be adapted quickly and accurately.

(Typically although not necessarily, the percentage of malware transactions in the protected network may be very small, e.g., 0.01% of the total transactions. In the infected network, the percentage of malware transactions may be as high as 2%.) In an example scenario, module 52 handles -1 million sessions in the protected network, of which -5,000 are malicious, and -80,000 sessions in the infected network, of which -3,000 are malicious. The actual transaction rate in this scenario is on the order of 10 transactions per session for normal traffic, and 34 transactions per session for malicious traffic. Alternatively, however, any other suitable traffic volumes may be analyzed.

It should be noted that this technique performs well because the features of malicious transactions tend to be similar in different networks. Therefore, it makes sense to combine the malware records from networks 24 and 28 to form a single collection of malware records. The features of innocent transactions, on the other hand, often differ

1011-1091S2 substantially from one network to another (e.g., between networks 24 and 28). For this reason, unknown transactions are obtained only from protected network 24 for which classification is desired.

Malware identification module 60 uses the adapted models to identify malicious transactions in network 24. Typically, the models are defined over the features (e.g., statistical features) extracted by module 52. Examples of such models are given and explained in Israel Patent Applications 219499 and 222648, cited above.

Module 60 typically generates alerts that indicate possible malware detections. Each alert typically comprises an identification of a host participating in the corresponding allegedly-malicious transaction. The alert may also indicate the confidence level of the alert, i.e., the likelihood that the identified transaction in question is indeed malicious.

In an example embodiment, the alerts generated by module 60 indicate an order of 100,000 hosts as possibly malicious. In the present embodiment, threshold comparison module 64 compares the confidence levels of the alerts to some predefined threshold, and retains only the alerts whose confidence level exceeds the thresholds. The other alerts, having lower confidence levels, are discarded. In an embodiment, the alerts at the output of module 64 indicate an order of a hundred hosts as possibly malicious.

In an embodiment, processor 44 sends the alerts generated by module 64 via operator interface 48 for presentation to operator 36 (typically a security analyst). Operator 36 analyzes the alerts, and the corresponding transactions. The operator returns to

1011-1091S2 processor 44, via interface 48, feedback that indicates which of the alerts are correct (i.e., correctly identify malware transactions) and which alerts are false alarms. In an embodiment, the operator feedback narrows down the list of allegedly-malicious hosts to an order of ten.

In some embodiments, processor 44 uses the operator feedback to adapt the malware identification models in module 56, e.g., using any suitable active learning approach known in the art. Additionally or alternatively, processor 44 may use the operator feedback to update one or more of the host reputation values in reputation database 32. For example, if the operator repeatedly identifies a certain host as malicious, processor 44 may reduce the reputation level of that host in database 32. If operator 36 repeatedly identifies a certain host as innocent (i.e., repeatedly marks alerts for this host as false alarms), processor 44 may increase the reputation level of that host in database 32.

The two forms of feedback cause the model adaptation (machine learning) process of system 20 to increase in a performance over time: The operator feedback improves the accuracy of the models applied by module 56. In addition, the operator feedback improves the quality of reputation database 32. Consequently, module 52 classifies subsequent transactions to malicious or unknown with greater accuracy, since the classification is based on the updated reputation levels.

MALWARE DETECTION METHOD DESCRIPTION

Fig. 2 is a flow chart that schematically illustrates a method for detecting malicious software, in accordance with an embodiment that is described herein.

1011-1091S2

The method begins with module 52 in processor 44 extracting malware transactions and unknown transactions from protected network 24, and generating respective malware records and unknown records, at a record generation step 70. Typically, module 52 classifies the transactions obtained from network 24 into malicious and unknown by querying reputation database 32.

Module 52 enriches the collection of malware records with records obtained from infected network 28, at a record enrichment step 74. Typically, module 52 identifies malicious transactions in network 28 and generates the respective records. As explained above, module 52 typically identifies the malicious transactions in network 28 by querying reputation database 32.

Learning module 56 adapts the malware identification models based on the malware records (from both networks) and the unknown records (from the protected network), at a learning step 78. Malware identification module 60 generates alerts based on the adapted models, at an alert generation step 82. The alerts undergo initial screening by threshold comparison module 64, based on confidence level.

Processor 44 sends the alerts remaining at the output of module 64 to operator 36, via operator interface 48, at an alert output step 86. Processor 44 receives feedback regarding the alerts from operator 36, at a feedback input step 90. In some embodiments, module 56 uses the operator feedback to adapt one or more of the malware identification models, at a model adaptation step 94. Additionally or alternatively, processor 44 uses the operator feedback to update one or more of the host

1011-1091S2 reputation levels in database 32, at a reputation updating step 98.

The method then loops back to step 70 above, so that processor 44 extracts additional malicious and unknown transactions, possibly substantially different in terms of content, using the reputation levels that were updated at step 98. Subsequent alerts will be generated based on the models that were adapted at step 94. The process typically continues cyclically in this manner, so that the collection of malicious and unknown records grows and the accuracy of the models improves over time. Iterations of the operator-assisted learning scheme of Fig. 2 can be repeated at any desired frequency, e.g., once a day.

Although the embodiments described herein mainly address malware detection, the principles of the present disclosure can also be used for other types of classification of network data, e.g., fraud detection (for example for bank, credit cards or telecom traffic analysis), user profiling, spam detection, and/or operating-system fingerprinting.

It will thus be appreciated that the embodiments described above are cited by way of example, and that the present disclosure is not limited to what has been particularly shown and described hereinabove. Rather, the scope of the present disclosure includes both combinations and sub-combinations of the various features described hereinabove, as well as variations and modifications thereof which would occur to persons skilled in the art upon reading the foregoing description and which are not disclosed in the prior art. Documents incorporated by reference in the present patent application are to be considered an integral part of the

1011-1091S2

<td> application</td><td colspan="2"> except</td><td> that to</td><td> the extent any</td><td> terms</td><td> are</td>

<td> defined in</td><td> these</td><td colspan="2"> incorporated</td><td> documents in a</td><td> manner</td><td> that</td>

<td> conflicts</td><td> with</td><td> the</td><td colspan="3"> definitions made explicitly</td><td> or</td>

<td> implicitly</td><td> in</td><td> the</td><td> present</td><td> specification,</td><td> only</td><td> the</td>

<td> definitions</td><td> in</td><td> the</td><td> present</td><td> specification</td><td> should</td><td> be</td>

<td> considered.</td><td></td><td></td><td></td><td></td><td></td><td></td>