IP Library Granted Patent US 9,894,088
Granted Patent B2
US 9,894,088 · App. 14/015,582 · Granted Feb 13, 2018

Data mining to identify malicious activity

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 9,894,088
App. No.
14/015,582
Granted
Feb 13, 2018
Kind
B2
Abstract

Systems and methods may determine suspicious network traffic. A monitoring system comprising a processor in communication with a network may monitor network traffic to or from an asset associated with the network. The monitoring system may assess the network traffic to determine a source and/or destination for the network traffic anchor content of the network traffic. The monitoring system may determine whether the network traffic is suspicious network traffic based on the assessed source and/or destination and/or content. When the network traffic is determined to be suspicious network traffic, the monitoring system may capture metadata associated with the suspicious network traffic and store the metadata in a database in communication with the processor. When the network traffic is not determined to be suspicious network traffic, the monitoring system may disregard metadata associated with the network traffic.

Claims (38)

1. A method comprising:

monitoring, with at least one processor in communication with a network, network traffic of an asset associated with the network;

assessing, with the at least one processor, the network traffic to determine a content of the network traffic a source for the network traffic, and a destination for the network traffic;

wherein assessing the source for the network traffic comprises at least one of determining a source reputation score and determining whether the source is associated with a suspicious domain generation algorithm cluster, and

wherein assessing the destination for the network traffic comprises determining a destination reputation score based on a relation to a domain generation algorithm (DGA) and a threat level of the content of the network traffic, the threat level being based on at least one of file content, one or more headers, HTTP traffic, and one or more scripts;

determining, with the at least one processor, whether the network traffic is suspicious network traffic based on the assessed network traffic; and

when the network traffic is determined to be suspicious network traffic, capturing, with the at least one processor, metadata associated with the suspicious network traffic and storing the metadata in a database in communication with the processor.

2. The method of claim 1 , wherein the monitoring comprises monitoring a transport protocol of the network traffic, monitoring an application protocol of the network traffic, monitoring the source and/or destination of the network traffic, and/or monitoring the content of the network traffic.

3. The method of claim 1 , further comprising:

when the network traffic is determined to be suspicious network traffic, indexing, with the at least one processor, the metadata.

4. The method of claim 1 , wherein the metadata comprises a source port, a destination port, a transport protocol, an application protocol, a time stamp, a duration, a source identifier, a destination identifier, a bytes in count, a bytes out count, a connection success indicator, a connection status, a DNS RR set, HTTP data, a file within the content of the network traffic, the content of the network traffic, and/or a subsequent communication.

5. The method of claim 1 , further comprising:

when the network traffic is determined to be suspicious network traffic, sending, with the at least one processor, a report indicating that the network traffic is determined to be suspicious network traffic to a display in communication with the at least one processor.

6. The method of claim 1 , wherein determining whether the network traffic is suspicious network traffic comprises determining that all traffic to and/or from the asset is suspicious network traffic when the asset is an asset with a potential malware infection.

7. A system comprising:

a database; and

at least one microprocessor in communication with a network and in communication with the database, the at least one microprocessor being constructed and arranged to:

monitor network traffic of an asset associated with the network;

assess the network traffic to determine a content of the network, a source for the network traffic, and a destination for the network traffic;

wherein the assessment of the source for the network traffic comprises of a determination of a source reputation score based on of a relation to a domain generation algorithm (DGA) and a threat level of the content of the network traffic, the threat level being based on at least one of file content, one or more headers, HTTP traffic, and one or more scripts;

determine whether the network traffic is suspicious network traffic based on the assessed network traffic; and

when the network traffic is determined to be suspicious network traffic, capture metadata associated with the suspicious network traffic and store the metadata in the database.

8. The system of claim 7 , wherein the monitoring comprises monitoring a transport protocol of the network traffic, monitoring an application protocol of the network traffic, monitoring the source and/or destination of the network traffic, and/or monitoring the content of the network traffic.

9. The system of claim 7 , wherein the at least one microprocessor is further constructed and arranged to:

when the network traffic is determined to be suspicious network traffic, index the metadata.

10. The system of claim 7 , wherein the metadata comprises a source port, a destination port, a transport protocol, an application protocol, a time stamp, a duration, a source identifier, a destination identifier, a bytes in count, a bytes out count, a connection success indicator, a connection status, a DNS RR set, HTTP data, a file within the content of the network traffic, the content of the network traffic, and/or a subsequent communication.

11. The system of claim 7 , wherein the at least one microprocessor is further constructed and arranged to:

when the network traffic is determined to be suspicious network traffic, send a report indicating that the network traffic is determined to be suspicious network traffic to a display in communication with the at least one microprocessor.

12. The system of claim 7 , wherein the at least one microprocessor is constructed and arranged to determine whether the network traffic is suspicious network traffic with a method comprising determining that all traffic to and/or from the asset is suspicious network traffic when the asset is an asset with a potential malware infection.

13. A method comprising:

assessing, with at least one processor, network traffic associated with one or more applications from an external network to determine at least one of a source for the network traffic and a destination for the network traffic;

wherein the assessment of the at least one source for the network traffic comprises determining a source reputation score based on a relation to a domain generation algorithm (DGA) and a threat level of the content of the network traffic;

determining, with the at least one processor, whether the network traffic is suspicious network traffic based on the assessed network traffic;

based on the determining, capturing, with the at least one processor, metadata associated with the suspicious network traffic and storing the metadata in a database in communication with the processor;

executing, on a simulated network, a copy of the one or more applications from the external network and capturing metadata associated with simulated network traffic;

comparing the metadata associated with the suspicious network traffic to the metadata associated with the simulated network traffic;

determining, based on the comparing, when a statistical similarity exists between the metadata associated with the suspicious network traffic and the metadata associated with the simulated network traffic;

identifying, when a statistical similarity exists, the one or more applications as malicious.

Assignments (20)
SECURITY INTEREST Recorded Jan 6, 2026
From: ALERT LOGIC, INC.; DIGITAL GUARDIAN LLC; ECRIME MANAGEMENT STRATEGIES, INC.; FORTRA, LLC; GLOBALSCAPE, INC.; TRIPWIRE, INC.
To: ACQUIOM AGENCY SERVICES LLC, AS COLLATERAL AGENT
Reel/Frame 074233/0632 →
TERMINATION AND RELEASE OF FIRST LIEN INTELLECTUAL PROPERTY SECURITY INTEREST RECORDED AT REEL/FRAME 51059/0861 Recorded Nov 24, 2025
From: JEFFERIES FINANCE LLC
To: FORTRA, LLC (FORMERLY KNOWN AS HELP/SYSTEMS, LLC)
Reel/Frame 073783/0406 →
TERMINATION AND RELEASE OF SECOND LIEN INTELLECTUAL PROPERTY SECURITY INTEREST RECORDED AT REEL/FRAME 51059/0911 Recorded Nov 21, 2025
From: ACQUIOM AGENCY SERV ICES LLC
To: FORTRA, LLC (F/K/A HELP/SYSTEMS, LLC)
Reel/Frame 073662/0442 →
NEW MONEY FIRST LIEN INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Nov 21, 2025
From: ALERT LOGIC, INC.; DIGITAL GUARDIAN LLC; ECRIME MANAGEMENT STRATEGIES, INC.; FORTRA, LLC; GLOBALSCAPE, INC.; TRIPWIRE, INC.; VERA SECURITY, INC.
To: ARES CAPITAL CORPORATION, AS COLLATERAL AGENT
Reel/Frame 073683/0534 →
EXTENDED FIRST LIEN INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Nov 21, 2025
From: FORTRA, LLC
To: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 073663/0914 →
EXTENDED RCF FIRST LIEN INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Nov 21, 2025
From: FORTRA, LLC
To: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 073663/0327 →
ASSIGNMENT OF INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Aug 14, 2025
From: GOLUB CAPITAL MARKETS LLC (AS EXISTING AGENT)
To: ACQUIOM AGENCY SERVICES LLC (AS SUCCESSOR COLLATERAL AGENT)
Reel/Frame 072471/0665 →
RELEASE OF SECURITY INTEREST Recorded Feb 3, 2025
From: PNC BANK, NATIONAL ASSOCIATION
To: DAMBALLA, INC.
Reel/Frame 070086/0189 →
CHANGE OF NAME Recorded Dec 15, 2022
From: HELP/SYSTEMS, LLC
To: FORTRA, LLC
Reel/Frame 062136/0777 →
ASSIGNMENT OF INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 20, 2021
From: JEFFERIES FINANCE LLC, AS EXISTING AGENT
To: GOLUB CAPITAL MARKETS LLC, AS SUCCESSOR AGENT
Reel/Frame 056322/0628 →
SECOND LIEN INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Nov 19, 2019
From: HELP/SYSTEMS, LLC
To: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 051059/0911 →
FIRST LIEN INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Nov 19, 2019
From: HELP/SYSTEMS, LLC
To: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 051059/0861 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 20, 2019
From: DAMBALLA, INC.
To: HELP/SYSTEMS, LLC
Reel/Frame 048386/0329 →
RELEASE OF SECURITY INTEREST Recorded Feb 8, 2019
From: PNC BANK, NATIONAL ASSOCIATION
To: COURION INTERMEDIATE HOLDINGS, INC.; CORE SECURITY SDI CORPORATION; CORE SECURITY TECHNOLOGIES, INC.; CORE SDI, INC.; CORE SECURITY LIVE CORPORATION; CORE SECURITY HOLDINGS, INC.; DAMABLLA, INC.
Reel/Frame 048281/0835 →
RELEASE OF SECURITY INTEREST Recorded Jan 4, 2018
From: SARATOGA INVESTMENT CORP. SBIC LP
To: DAMBALLA, INC.
Reel/Frame 044535/0907 →
SECURITY INTEREST Recorded Dec 27, 2017
From: DAMBALLA, INC.
To: PNC BANK, NATIONAL ASSOCIATION
Reel/Frame 044492/0654 →
PATENT SECURITY AGREEMENT Recorded Oct 10, 2016
From: DAMBALLA, INC.
To: SARATOGA INVESTMENT CORP. SBIC LP, AS ADMINISTRATIVE AGENT
Reel/Frame 040297/0988 →
RELEASE OF SECURITY INTEREST Recorded Sep 8, 2016
From: SILICON VALLEY BANK
To: DAMBALLA, INC.
Reel/Frame 039678/0960 →
SECURITY INTEREST Recorded May 14, 2015
From: DAMBALLA, INC.
To: SILICON VALLEY BANK
Reel/Frame 035639/0136 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 31, 2014
From: WARD, JOSEPH; HOBSON, ANDREW
To: DAMBALLA, INC.
Reel/Frame 033439/0551 →