TOR-BASED MALWARE DETECTION
A machine learning model for classifying encrypted traffic as benign or malicious without having to decrypt the traffic is provided that used traffic patterns from network logs to classify the traffic based on learned patterns for malware, and is capable of identifying zero-day malware is provided via: extracting encrypted traffic from communication logs for a network; identifying, from the encrypted traffic, while still encrypted, traffic patterns for users of the network; and classifying, via a machine learning model, the encrypted traffic as benign traffic or malicious traffic without decrypting the encrypted traffic according to the traffic patterns identified.
1 . A method, comprising:
extracting encrypted traffic from communication logs for a network;
identifying, from the encrypted traffic, while still encrypted, traffic patterns for users of the network; and
classifying, via a machine learning model, the encrypted traffic as benign traffic or malicious traffic without decrypting the encrypted traffic according to the traffic patterns identified.
2 . The method of claim 1 , further comprising:
quarantining a computing device connected to the network that is associated with encrypted traffic identified as malicious.
3 . The method of claim 1 , further comprising:
generating or supplementing a training dataset based on the traffic patterns and classifications of the encrypted traffic as malicious or benign.
4 . The method of claim 3 , wherein the training dataset includes labels provided from an administrative user for a correctness of the traffic patterns and classifications being identified as malicious or benign by the machine learning model.
5 . The method of claim 3 , further comprising:
retraining the machine learning model via the training dataset.
6 . The method of claim 1 , wherein the malicious traffic is cause by a zero-day malware operating on a computing device connected to the network.
7 . The method of claim 1 , wherein the machine learning model classifies the encrypted traffic as benign traffic or malicious traffic using features consisting of:
duration features, including at least one of:
an average, shortest, or longest duration connection,
a number of short duration connections less than 1 minute, and
an average duration between each Tor connection;
data features, including at least one of:
a mean, median, or mode of total data exchanged,
a mean, median, or mode of total data sent or received, and
a mean, median, or mode of total packets sent or received;
port features, including at least one of:
a number of unique destination ports used across connections,
a most frequent destination port used across Tor connections,
a number of non-standard DST ports seen, and
a most frequent non-standard DST port;
connection features, including at least one of:
a number of connections seen (per host or PCAP),
a number of failed or rejected attempts,
a number of connections per second, and
a number of failed attempts per second; and
Domain Name Service (DNS) features, including at least one of:
a number of DNS queries with rcode_name: REFUSED
a number of DNS queries with rcode_name: SERVFAIL
a number of uniform resource locators (URLs) seen using “consensus” keyword,
a number of URLs with “\tor” keyword,
a number of DNS queries rcode_name: NXDOMAINS,
a total Number of leaked onion domains,
a number of unique onion domains leaked, and
a number of ‘rejected’ onion domain queries.
8 . A system, comprising:
a processor; and
a memory, including instructions, that when executed by the processor, perform operations that include:
extracting encrypted traffic from communication logs fora network;
identifying, from the encrypted traffic, while still encrypted, traffic patterns for users of the network; and
classifying, via a machine learning model, the encrypted traffic as benign traffic or malicious traffic without decrypting the encrypted traffic according to the traffic patterns identified.
9 . The system of claim 8 , the operations further comprising:
quarantining a computing device connected to the network that is associated with encrypted traffic identified as malicious.
10 . The system of claim 8 , the operations further comprising:
generating or supplementing a training dataset based on the traffic patterns and classifications of the encrypted traffic as malicious or benign.
11 . The system of claim 10 , wherein the training dataset includes labels provided from an administrative user for a correctness of the traffic patterns and classifications being identified as malicious or benign by the machine learning model.
12 . The system of claim 10 , further comprising:
retraining the machine learning model via the training dataset.
13 . The system of claim 8 , wherein the malicious traffic is cause by a zero-day malware operating on a computing device connected to the network.
14 . The system of claim 8 , wherein the machine learning model classifies the encrypted traffic as benign traffic or malicious traffic using features consisting of:
duration features, including at least one of:
an average, shortest, or longest duration connection,
a number of short duration connections less than 1 minute, and
an average duration between each Tor connection;
data features, including at least one of:
a mean, median, or mode of total data exchanged,
a mean, median, or mode of total data sent or received, and
a mean, median, or mode of total packets sent or received;
port features, including at least one of:
a number of unique destination ports used across connections,
a most frequent destination port used across Tor connections,
a number of non-standard DST ports seen, and
a most frequent non-standard DST port;
connection features, including at least one of:
a number of connections seen (per host or PCAP),
a number of failed or rejected attempts,
a number of connections per second, and
a number of failed attempts per second; and
Domain Name Service (DNS) features, including at least one of:
a number of DNS queries with rcode_name: REFUSED
a number of DNS queries with rcode_name: SERVFAIL
a number of uniform resource locators (URLs) seen using “consensus” keyword,
a number of URLs with “\tor” keyword,
a number of DNS queries rcode_name: NXDOMAINS,
a total Number of leaked onion domains,
a number of unique onion domains leaked, and
a number of ‘rejected’ onion domain queries.
15 . A non-transitory computer readable storage medium including instructions, that when executed by a processor perform operations, comprising:
extracting encrypted traffic from communication logs for a network;
identifying, from the encrypted traffic, while still encrypted, traffic patterns for users of the network; and
classifying, via a machine learning model, the encrypted traffic as benign traffic or malicious traffic without decrypting the encrypted traffic according to the traffic patterns identified.
16 . The medium of claim 15 , the operations further comprising:
quarantining a computing device connected to the network that is associated with encrypted traffic identified as malicious.
17 . The medium of claim 15 , the operations further comprising:
generating or supplementing a training dataset based on the traffic patterns and classifications of the encrypted traffic as malicious or benign.
18 . The medium of claim 17 , wherein the training dataset includes labels provided from an administrative user for a correctness of the traffic patterns and classifications being identified as malicious or benign by the machine learning model.
19 . The medium of claim 17 , further comprising:
retraining the machine learning model via the training dataset.
20 . The medium of claim 15 , wherein the malicious traffic is cause by a zero-day malware operating on a computing device connected to the network.