IP Library › Granted Patent US 11,196,546
Granted Patent B2
US 11,196,546 · App. 16/701,373 · Granted Dec 7, 2021

Passive decryption of encrypted traffic to generate more accurate machine learning training data

Inventors: Blake Harrell Anderson (San Jose, CA); Andrew Chi (Chapel Hill, NC); David McGrew (Poolesville, MD); Scott William Dunlop (Des Moines, WA)
Assignee: Cisco Technology, Inc.
H04L9/0822G06N5/025H04L9/0894H04L63/0428H04L63/1416H04L63/1441H04L63/1458H04W72/0426
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,196,546
App. No.
16/701,373
Granted
Dec 7, 2021
Kind
B2
Abstract

In one embodiment, an apparatus captures a memory dump of a device in a sandbox environment executing a malware sample. The apparatus identifies a cryptographic key based on a particular data structure in the captured memory dump. The apparatus uses the identified cryptographic key to decrypt encrypted traffic sent by the device. The apparatus labels at least a portion of the decrypted traffic sent by the device as benign. The apparatus trains a machine learning-based traffic classifier based on the at least a portion of the decrypted traffic sent by the device and labeled as benign.

Claims (51)

1. A method comprising:

capturing a memory dump of a device in a sandbox environment executing a malware sample;

identifying a cryptographic key based on a particular data structure in the captured memory dump;

using the identified cryptographic key to decrypt encrypted traffic sent by the device;

labeling at least a portion of the decrypted traffic sent by the device as benign; and

training a machine learning-based traffic classifier to classify encrypted traffic in a network as malicious or non-malicious based on the at least a portion of the decrypted traffic sent by the device and labeled as benign.

2. The method as in claim 1 , further comprising:

deploying the machine learning-based traffic classifier to a node in the network, to detect the presence of malware in the network.

3. The method as in claim 1 , wherein the particular data structure comprises a wrapper for the cryptographic key, the method further comprising:

identifying a particular encryption suite used by the device to encrypt the traffic; and

identifying the data structure based on the identified encryption suite used by the device to encrypt the traffic.

4. The method as in claim 1 , wherein capturing the memory dump of the device executing the malware sample comprises:

detecting a triggering condition to initiate the memory dump.

5. The method as in claim 4 , wherein the triggering condition to initiate the memory dump comprises one of: a Change Cipher Spec message appearing in the traffic of the device, multiple socket.send( ) calls to a particular 5-tuple being observed, detecting multiple calls to a particular application programming interface (API) of the device.

6. The method as in claim 1 , wherein identifying the encryption key based on the particular data structure in the captured memory dump comprises:

identifying a set of bytes in the memory dump having high entropy in comparison to bytes preceding or following the set of bytes in the memory dump.

7. The method as in claim 1 , wherein the traffic sent by the device is encrypted using Transport Layer Security (TLS).

8. An apparatus, comprising:

one or more network interfaces to communicate with a network;

a processor coupled to the network interfaces and configured to execute one or more processes; and

a memory configured to store a process executable by the processor, the process when executed configured to:

capture a memory dump of a device in a sandbox environment executing a malware sample;

identify a cryptographic key based on a particular data structure in the captured memory dump;

use the identified cryptographic key to decrypt encrypted traffic sent by the device;

label at least a portion of the decrypted traffic sent by the device as benign; and

train a machine learning-based traffic classifier to classify encrypted traffic in the network as malicious or non-malicious based on the at least a portion of the decrypted traffic sent by the device and labeled as benign.

9. The apparatus as in claim 8 , wherein the process when executed is further configured to:

deploy the machine learning-based traffic classifier to a node in the network, to detect the presence of malware in the network.

10. The apparatus as in claim 8 , wherein the particular data structure comprises a wrapper for the cryptographic key, wherein the process when executed is further configured to:

identify a particular encryption suite used by the device to encrypt the traffic; and

identify the data structure based on the identified encryption suite used by the device to encrypt the traffic.

11. The apparatus as in claim 8 , wherein the apparatus captures the memory dump of the device executing the malware sample by:

detecting a triggering condition to initiate the memory dump.

12. The apparatus as in claim 11 , wherein the triggering condition to initiate the memory dump comprises one of: a Change Cipher Spec message appearing in the traffic of the device, multiple socket.send( ) calls to a particular 5-tuple being observed, detecting multiple calls to a particular application programming interface (API) of the device.

13. The apparatus as in claim 8 , wherein the apparatus identifies the encryption key based on the particular data structure in the captured memory dump by:

identifying a set of bytes in the memory dump having high entropy in comparison to bytes preceding or following the set of bytes in the memory dump.

14. The apparatus as in claim 8 , wherein the traffic sent by the device is encrypted using Transport Layer Security (TLS).

15. A tangible, non-transitory, computer-readable medium storing program instructions that cause a computing device to execute a process comprising:

capturing a memory dump of a device in a sandbox environment executing a malware sample;

identifying a cryptographic key based on a particular data structure in the captured memory dump;

using the identified cryptographic key to decrypt encrypted traffic sent by the device;

labeling at least a portion of the decrypted traffic sent by the device in the sandbox environment as benign; and

training a machine learning-based traffic classifier to classify encrypted traffic in a network as malicious or non-malicious based on the at least a portion of the decrypted traffic sent by the device in the sandbox environment and labeled as benign.

16. The computer-readable medium as in claim 15 , wherein capturing the memory dump of the device executing the malware sample comprises:

detecting a triggering condition to initiate the memory dump.

17. The computer-readable medium as in claim 16 , wherein the triggering condition to initiate the memory dump comprises one of: a Change Cipher Spec message appearing in the traffic of the device, multiple socket.send( ) calls to a particular 5-tuple being observed, detecting multiple calls to a particular application programming interface (API) of the device.

18. The computer-readable medium as in claim 16 , wherein the traffic sent by the device is encrypted using Transport Layer Security (TLS).

19. The computer-readable medium as in claim 16 , wherein the program instructions when executed is further configured to:

deploy the machine learning-based traffic classifier to a node in the network, to detect the presence of malware in the network.

20. The computer-readable medium as in claim 15 , wherein the program instructions identify the encryption key based on the particular data structure in the captured memory dump by:

identifying a set of bytes in the memory dump having high entropy in comparison to bytes preceding or following the set of bytes in the memory dump.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 3, 2019
From: ANDERSON, BLAKE HARRELL; CHI, ANDREW; MCGREW, DAVID; DUNLOP, SCOTT WILLIAM
To: CISCO TECHNOLOGY, INC.
Reel/Frame 051160/0122 →
Continuity (2)
Continuation 15692288 · Aug 31, 2017
Related Publication 20200106604A1 · Apr 2, 2020
Cited By (1)
US 12,592,915