Advanced persistent threat detection

• US 9,392,015 B2
• Filed: 04/28/2014
• Issued: 07/12/2016
• Est. Priority Date: 04/28/2014
• Status: Active Grant

• Current Assignee: Sophos Limited (Sophos Group Ltd.)
• Original Assignee: Sophos Limited (Sophos Group Ltd.)
• Inventors: Thomas, Andrew J.
• Primary Examiner(s): Zecher, Dede
• Assistant Examiner(s): LAKHIA, VIRAL S
• Application Number:
  US14/263,955
• Publication Number:
  US 20150312266A1
• Time in Patent Office: 806 Days
• Field of Search: 726/11, 726/22, 726/23, 707/169, 713180-183
• US Class Current: 1/1
• CPC Class Codes: H04L 2463/146 Tracing the source of attacks
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 63/0227 Filtering policies mail message filtering H04L51/212
• CPC Class Codes: H04L 63/1416 Event detection, e.g. attack signature detection
• CPC Class Codes: H04L 63/145 the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 65/1033 Signalling gateways

Abstract

A variety of techniques are disclosed for detection of advanced persistent threats and similar malware. In one aspect, the detection of certain network traffic at a gateway is used to trigger a query of an originating endpoint, which can use internal logs to identify a local process that is sourcing the network traffic. In another aspect, an endpoint is configured to periodically generate and transmit a secure heartbeat, so that an interruption of the heartbeat can be used to signal the possible presence of malware. In another aspect, other information such as local and global reputation information is used to provide context for more accurate malware detection.

Claims

1. A system for threat detection, comprising:

a gateway in an enterprise, the gateway configured to detect a request for network traffic from an endpoint in the enterprise, the request including a destination address and the request containing a violation of a network policy for the enterprise, the gateway further configured to identify the endpoint that originated the request, and to query the endpoint to access a log of network requests from processes executing on the endpoint to determine a source process on the endpoint that generated the request on the endpoint, the gateway further configured to map the source process to one or more files on the endpoint; and

a threat management facility for managing the enterprise, the threat management facility coupled in a communicating relationship with the gateway, and the threat management facility configured to locate one or more other endpoints associated with the enterprise that contain the one or more files mapped to the source process, and to remediate the one or more other endpoints with respect to the the one or more files.

2. The system of claim 1 wherein the violation includes a prohibited Uniform Resource Identifier in the destination address.

3. The system of claim 1 wherein the violation includes a prohibited domain in the destination address.

4. The system of claim 1 wherein the violation includes prohibited content in the request.

5. The system of claim 1 wherein the threat management facility is configured to remediate the one or more other endpoints by quarantining the one or more other endpoints.

6. The system of claim 1 wherein the threat management facility is configured to remediate the one or more other endpoints by quarantining the source process on each of the one or more other endpoints.

7. The system of claim 1 wherein the threat management facility is configured to remediate the one or more other endpoints by terminating the source process on each of the one or more other endpoints.

8. The system of claim 1 wherein the threat management facility is configured to remediate the one or more other endpoints by removing the one or more files on each of the one or more other endpoints.

9. The system of claim 1 wherein the threat management facility is configured to remediate the one or more other endpoints by blocking network traffic for the one or more other endpoints.

10. The system of claim 1 wherein the threat management facility is configured to remediate the one or more other endpoints by blocking access to the destination address by the one or more other endpoints.

11. The system of claim 1 wherein the violation includes command and control protocol traffic for an advanced persistent threat.

12. The system of claim 1 wherein the violation includes a command and control location for an advanced persistent threat in the destination.

13. The system of claim 1 wherein the gateway is configured to identify the endpoint based on a machine ID for the endpoint within a heartbeat received at the gateway from the endpoint.

14. The system of claim 13 wherein the heartbeat is a secure heartbeat.

15. The system of claim 1 wherein the gateway is configured to query the endpoint for entries in the log corresponding to a time of the request.