Detection of malware beaconing activities

US9038178B1 · US · B1

Patent metadata
FieldValue
Publication numberUS-9038178-B1
Application numberUS-201213532385-A
CountryUS
Kind codeB1
Filing dateJun 25, 2012
Priority dateJun 25, 2012
Publication dateMay 19, 2015
Grant dateMay 19, 2015

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Malware beaconing activity detection is disclosed, including: monitoring a plurality of conversations between an internal device and one or more external destinations; extracting feature sets based at least in part on the plurality of conversations; and determining that a conversation of the plurality of conversations is anomalous based at least in part on the extracted feature sets.

First claim

Opening claim text (preview).

What is claimed is: 1. A malware beaconing detection system, comprising: a processor configured to: identify a plurality of conversations between an internal device and one or more external destinations, wherein at least some of the plurality of conversations are determined from stored logs associated with communication between one or more internal devices associated with an enterprise network and the one or more external destinations, wherein identifying a first conversation of the plurality of conversations between a pair comprising the internal device and a first external destination of the one or more external destination comprises to: obtain a plurality of communication events among the stored logs that includes the pair comprising the internal device and the first external destination, wherein to obtain a communication event that includes the pair comprising the internal device and the first external destination includes to: identify traffic between a dynamically assigned Internal Protocol (IP) address and the first external destination; and determine that the dynamically assigned IP address maps to a statically assigned address associated with the internal device; and generate the first conversation between the pair comprising the internal device and the first external destination based at least in part on the plurality of communication events; extract feature sets based at least in part on the plurality of conversations; and determine that a conversation of the plurality of conversations is anomalous based at least in part on the extracted feature sets; and a memory coupled to the processor and configured to store the extracted feature sets. 2. The system of claim 1 , wherein at least one of the one or more external destinations comprises an external IP address outside of the enterprise network. 3. The system of claim 1 , wherein the at least some of the plurality of conversations are determined based at least in part on stored logs comprising one or more of the following: firewall logs, proxy logs, and dynamic host configuration protocol (DHCP) logs. 4. The system of claim 1 , wherein the anomalous conversation is potentially indicative of malware being present at the internal device. 5. The system of claim 1 , wherein to determine that the conversation is anomalous includes building a model based at least in part on at least some of the feature sets and a plurality of historical conversations. 6. The system of claim 5 , wherein at least some of the extracted feature sets are input into the model and the model is configured to determine that the conversation is anomalous based on the inputted feature sets. 7. The system of claim 1 , wherein one of the feature sets includes a feature associated with an age of the internal device. 8. The system of claim 1 , wherein one of the feature sets includes a feature associated with an age of one of the one or more external destinations. 9. The system of claim 1 , wherein one of the feature sets includes a feature associated with a service associated with one of the one or more external destinations. 10. The system of claim 1 , wherein one of the feature sets includes a feature associated with a geolocation of one of the one or more external destinations. 11. The system of claim 1 , wherein the processor is further configured to present information associated the anomalous conversation. 12. The system of claim 1 , wherein identifying the first conversation further includes the processor being further configured to store attributes associated with the plurality of communication events, the internal device, and the first external destination with the first conversation, and wherein extracting feature sets includes the processor being further configured to extract a feature set from the attributes associated with the first conversation. 13. A method for malware beaconing detection, comprising: identifying a plurality of conversations between an internal device and one or more external destinations, wherein at least some of the plurality of conversations are determined from stored logs associated with communication between one or more internal devices associated with an enterprise network and the one or more external destinations, wherein identifying a first conversation of the plurality of conversations between a pair comprising the internal device and a first external destination of the one or more external destination comprises: obtaining a plurality of communication events among the stored logs that includes the pair comprising the internal device and the first external destination, wherein to obtain a communication event that includes the pair comprising the internal device and the first external destination includes: identifying traffic between a dynamically assigned Internal Protocol (IP) address and the first external destination; and determining that the dynamically assigned IP address maps to a statically assigned address associated with the internal device; and generating the first conversation between the pair comprising the internal device and the first external destination based at least in part on the plurality of communication events; extracting feature sets based at least in part on the plurality of conversations; and determining, using a processor, that a conversation of the plurality of conversations is anomalous based at least in part on the extracted feature sets. 14. The method of claim 13 , wherein at least some of the plurality of conversations are determined based at least in part on stored logs comprising one or more of the following: firewall logs, proxy logs, and dynamic host configuration protocol (DHCP) logs. 15. The method of claim 13 , wherein determining that the conversation is anomalous includes building a model based at least in part on at least some of the feature sets and a plurality of historical conversations. 16. The method of claim 15 , wherein at least some of the extracted feature sets are input into the model and the model is configured to determine that the conversation is anomalous based on the inputted feature sets. 17. The method of claim 13 , further comprising presenting information associated the anomalous conversation. 18. A computer program product for malware beaconing detection, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for: identifying a plurality of conversations between an internal device and one or more external destinations, wherein at least some of the plurality of conversations are determined from stored logs associated with communication between one or more internal devices associated with an enterprise network and the one or more external destinations, wherein identifying a first conversation of the plurality of conversations between a pair comprising the internal device and a first external destination of the one or more external destination comprises: obtaining a plurality of communication events among the stored logs that includes the pair comprising the internal device and the first external destination, wherein to obtain a communication event that includes the pair comprising the internal device and the first external destination includes: identifying traffic between a dynamically assigned Internal Protocol (IP) address and the first external destination; and determining that the dynamically assigned IP address maps to a statically assigned address associated with the internal device; and generating the first conversation between the pai

Assignees

Inventors

Classifications

  • for separating internal from external traffic, e.g. firewalls · CPC title

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

  • Countermeasures against malicious traffic (countermeasures against attacks on cryptographic mechanisms H04L9/002) · CPC title

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

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9038178B1 cover?
Malware beaconing activity detection is disclosed, including: monitoring a plurality of conversations between an internal device and one or more external destinations; extracting feature sets based at least in part on the plurality of conversations; and determining that a conversation of the plurality of conversations is anomalous based at least in part on the extracted feature sets.
Who is the assignee on this patent?
Lin Derek, Emc Corp
What technology area does this patent fall under?
Primary CPC classification H04L63/1416. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue May 19 2015 00:00:00 GMT+0000 (Coordinated Universal Time) (B1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).