Malware classification and attribution through server fingerprinting using server certificate data
US-10686831-B2 · Jun 16, 2020 · US
US12506772B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12506772-B2 |
| Application number | US-202418417256-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 19, 2024 |
| Priority date | Nov 16, 2016 |
| Publication date | Dec 23, 2025 |
| Grant date | Dec 23, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
In one embodiment, a device in a network receives certificate data for an encrypted traffic flow associated with a client node in the network. The device determines one or more data features from the certificate data. The device determines one or more flow characteristics of the encrypted traffic flow. The device performs a classification of an application executed by the client node and associated with the encrypted traffic flow by using a machine learning-based classifier to assess the one or more data features from the certificate data and the one or more flow characteristics of the traffic flow. The device causes performance of a network action based on a result of the classification of the application.
Opening claim text (preview).
What is claimed is: 1. A method comprising: receiving first network traffic including an encrypted flow; extracting connection data from the encrypted flow without decrypting the encrypted flow, the connection data including one or more certificates, ciphersuites used, and metrics regarding the encrypted flow; characterizing the encrypted flow as malicious or non-malicious by using the connection data as input to a machine learning classifier; and responsive to characterizing of the encrypted flow as malicious, updating a policy on a first network node to block the encrypted flow. 2. The method of claim 1 , wherein receiving first network traffic including an encrypted flow is performed at the first network node and; characterizing the encrypted flow as malicious by using the connection data as input to a machine learning classifier is performed at a classifying device. 3. The method of claim 1 , wherein the method further comprises: responsive to characterizing of the encrypted flow as malicious, updating a policy on a second network node to block the encrypted flow. 4. The method of claim 1 , wherein the connection data further includes information regarding a sequence of packet lengths and timing data of the encrypted flow. 5. The method of claim 1 , wherein the method further comprises: identifying an application within the encrypted flow by using the connection data as input to a machine learning classifier. 6. The method of claim 5 , wherein the connection data further includes information regarding a sequence of application packet lengths and timing data of the encrypted flow. 7. The method of claim 1 , further including, responsive to classifying the encrypted flow as malicious, sending an alert. 8. A system, comprising: one or more nodes connected in a network, each node with a processor, a memory, and one or more network interfaces, wherein the system is configured to receive a series of instructions, which when executed on one or more processors across the one or more nodes, cause the system to perform actions including: receiving first network traffic including an encrypted flow; extracting connection data from the encrypted flow without decrypting the encrypted flow, the connection data including one or more certificates, ciphersuites used, and metrics regarding the encrypted flow; characterizing the encrypted flow as malicious or non-malicious by using the connection data as input to a machine learning classifier; and responsive to characterizing of the encrypted flow as malicious, updating a policy on a first network node to block the encrypted flow. 9. The system of claim 8 , wherein receiving first network traffic including an encrypted flow is performed at the first network node and characterizing the encrypted flow as malicious by using the connection data as input to a machine learning classifier is performed at a classifying device. 10. The system of claim 8 , the actions further including: responsive to characterizing of the encrypted flow as malicious, updating a policy on a second network node to block the encrypted flow. 11. The system of claim 8 , wherein the connection data further includes information regarding a sequence of packet lengths and timing data of the encrypted flow. 12. The system of claim 8 , the actions further including: identifying an application within the encrypted flow by using the connection data as input to a machine learning classifier. 13. The system of claim 12 , wherein the connection data further includes information regarding a sequence of application packet lengths and timing data of the encrypted flow. 14. The system of claim 8 , the actions further including, responsive to classifying the encrypted flow as malicious, sending an alert. 15. A non-transitory computer-readable medium, the medium including instructions which, when executed on one or more processors across one or more nodes connected through a network, cause the one or more nodes to perform actions including: receiving first network traffic including an encrypted flow; extracting connection data from the encrypted flow without decrypting the encrypted flow, the connection data including one or more certificates, ciphersuites used, and metrics regarding the encrypted flow; characterizing the encrypted flow as malicious or non-malicious by using the connection data as input to a machine learning classifier; and responsive to characterizing of the encrypted flow as malicious, updating a policy on a first network node to block the encrypted flow. 16. The computer-readable medium of claim 15 , wherein receiving first network traffic including an encrypted flow is performed at the first network node and characterizing the encrypted flow as malicious by using the connection data as input to a machine learning classifier is performed at a classifying device. 17. The computer-readable medium of claim 15 , the actions further including: responsive to characterizing of the encrypted flow as malicious, updating a policy on a second network node to block the encrypted flow. 18. The computer-readable medium of claim 15 , wherein the connection data further includes information regarding a sequence of packet lengths and timing data of the encrypted flow. 19. The computer-readable medium of claim 15 , the actions further including: identifying an application within the encrypted flow by using the connection data as input to a machine learning classifier. 20. The computer-readable medium of claim 19 , wherein the connection data further includes information regarding a sequence of application packet lengths and timing data of the encrypted flow. 21. The computer-readable medium of claim 15 , the actions further including, responsive to classifying the encrypted flow as malicious, sending an alert.
wherein the data content is protected, e.g. by encrypting or encapsulating the payload · CPC title
Machine learning · CPC title
by monitoring network traffic (monitoring network traffic per se H04L43/00) · CPC title
the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.