IP Library Granted Patent US 8,635,697
Granted Patent B2
US 8,635,697 · App. 13/083,501 · Granted Jan 21, 2014

Method and system for operating system identification in a network based security monitoring solution

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 8,635,697
App. No.
13/083,501
Granted
Jan 21, 2014
Kind
B2
Abstract

A method and system for providing network based malware detection in a service provider network is disclosed. Transmission control protocol (TCP) packets defining originating from an access device coupled to the service provider network defining a TCP session between a computing device coupled to the access device, and a destination coupled to the service provider network are received. An operating system identifier (OS ID) associated with the TCP session and the computing device is determined. If malware is present in the TCP session and an associated malware ID is determined by comparing a malware signature to the one or more TCP packets. An alert identifying a network address associated with the access device, the malware ID and the OS ID associated with TCP session that generated the alert can then be generated.

Claims (53)

1. A method of network based malware detection in a service provider network, the method comprising:

receiving one or more transmission control protocol (TCP) packets originating from an access device coupled to the service provider network, the one or more TCP packets defining a TCP session between a computing device coupled to the access device, and a destination coupled to the service provider network;

determining an operating system identifier (OS ID) associated with the TCP session and the computing device;

determining if malware is present in the TCP session and an associated malware ID by comparing a malware signature to the one or more TCP packets; and

generating an alert identifying a network address associated with the access device, the malware ID and the OS ID associated with TCP session that generated the alert.

2. The method of claim 1 wherein determining the operating system ID further comprises:

determining a protocol associated with the TCP packets and matching an OS fingerprint from one or more protocol parameters if present in the TCP packets to determine a first operating system identifier (ID);

determining an application parameter associated with the TCP session if present, and identifying a second OS ID from the application parameter; and

wherein the OS ID in the alert comprises one of the first OS ID or second OS ID associated with one or more computing devices coupled to the access device.

3. The method of claim 2 further comprising sending a notification to a subscriber associated with the network address associated with the access device, the notification identifying a remediation portal to remove the determined malware in the alert.

4. The method of claim 3 further comprising:

identifying at the remediation portal the subscriber accessing the remediation portal;

identifying the OS associated with the computing device used by the subscriber to access the remediation portal;

comparing the OS associated with the computing device to the at least one of the first OS ID or second OS ID identified in the alert; and

providing malware remediation to the computing device when the at least one of the first OS ID or second OS ID matches the OS associated with the computing device.

5. The method of claim 3 wherein if the OS of the computing device is not the at least one of the first OS ID or second OS ID identified in the alert an indication is provided to the subscriber to connect to the remediation portal with an other computing device connected to the access device.

6. The method of claim 3 wherein the alert is cleared when all computing devices associated with the access device and the computing device having the at least one of the first OS ID or second OS ID have accessed the remediation portal.

7. The method of claim 2 wherein determining the first OS ID is performed by comparing one or more protocol parameters of the one or more TCP packets having a SYN flag associated with the session, wherein the OS fingerprints identify the protocol parameters of the SYN flagged packet and the OS ID associated with parameters.

8. The method of claim 2 wherein determining the application parameter associated with the session and identifying the second OS ID from the application parameter by inspecting an HTTP user agent string to determine the second OS ID.

9. The method of claim 2 further comprising verifying the first OS ID against the second OS ID, wherein if the second OS ID does not match the first OS ID the session is identified by the OS ID identified as a more reliable OS ID.

10. The method of claim 2 further comprising verifying the first OS ID against the second OS ID, wherein if the second OS ID matches the first OS ID either OS ID is used.

11. The method of claim 2 further comprising verifying the first OS ID against the second OS ID, wherein if the second OS ID matches the first OS ID but the second OS ID provides additional information, the second OS ID is used.

12. The method of claim 3 wherein sending the notification to the subscriber associated with the access device further comprises replacing the network address of the access device with a subscriber ID.

13. The method of claim 12 wherein sending the notification to the subscriber associated with the access device further comprises aggregating one or more detailed alerts having the subscriber ID into a single alert summary associated with the subscriber ID.

14. The method of claim 12 wherein the one or more computing devices are coupled to the access device through a local area network (LAN), the access device providing network address translation (NAT) or is coupled to NAT device to share the network address of the access device.

15. A system for network based malware detection in a service provider network, the system comprising:

a plurality of network sensors coupled to the service provider network, each of the network sensors for:

receiving one or more transmission control protocol (TCP) packets originating from an access device coupled to the service provider network, the one or more TCP packets defining a TCP session between a computing device coupled to the access device, and a destination coupled to the service provider network;

determining an operating system identifier (OS ID) associated with the TCP session and the computing device associated;

determining if malware is present in the TCP session and an associated malware ID by comparing a malware signature to the one or more TCP packets; and

generating an alert identifying a network address associated with the access device, the malware ID and the OS ID associated with TCP session that generated the alert.

16. The system of claim 15 wherein the plurality of network sensors in determining the OS ID further:

determine a protocol associated with the TCP packets and matching an OS fingerprint from one or more protocol parameters if present in the TCP packets to determine a first OS ID;

determine an application parameter associated with the TCP session if present, and identifying a second OS ID from the application parameter; and

wherein the identified OS ID in the alert comprises one of the first OS ID or the second OS ID associated with one or more computing devices coupled to the access device.

17. The system of claim 15 wherein the plurality of network sensors further: send a notification to a subscriber associated with the network address associated with the access device, the notification identifying a remediation portal to remove the determined malware in the alert.

18. The system of claim 17 wherein the plurality of network sensors send the notification to the subscriber associated with the access device by retrieving a subscriber ID from a subscriber ID repository and replacing the network address of the access device with the subscriber ID.

19. The system of claim 16 wherein the plurality of network sensors determine the first OS ID by comparing one or more protocol parameters of the one or more TCP packets having a SYN flag associated with the session, the OS fingerprints identify the protocol parameters of the SYN flagged packet and the OS ID associated with parameters.

20. The system of claim 19 wherein the plurality of network sensors determine the application parameter associated with the session and identifies the second OS ID from the application parameter by inspecting an HTTP user agent string to determine the second OS ID.

21. The system of claim 20 wherein the plurality of network sensors verify the first OS ID against the second OS ID, wherein if the second OS ID does not match the first OS ID the session is identified by the OS ID providing a more reliable OS ID.

22. The system of claim 20 wherein the plurality of network sensors verify the first OS ID against the second OS ID, wherein if the second OS ID matches the first OS ID either OS ID is used.

23. The system of claim 20 wherein the plurality of network sensors verify the first OS ID against the second OS ID, wherein if the second OS ID matches the first OS ID but the second OS ID provides additional information, the second OS ID is used.

24. A computer readable memory containing instructions for network based malware detection in a service provider network, the instructions when executed by a processor performing:

receiving one or more transmission control protocol (TCP) packets originating from an access device coupled to the service provider network, the one or more TCP packets defining a TCP session between a computing device coupled to the access device, and a destination coupled to the service provider network;

determining an operating system identifier (OS ID) associated with the TCP session and the computing device;

determining if malware is present in the TCP session and an associated malware ID by comparing a malware signature to the one or more TCP packets; and

generating an alert identifying a network address associated with the access device, the malware ID and the OS ID associated with TCP session that generated the alert.

25. The system of claim 16 further comprising:

a remediation portal coupled to the service provider network, the remediation portal for:

identifying a subscriber accessing the remediation portal;

identifying the OS associated with the computing device used by the subscriber to access the remediation portal;

comparing the OS associated with the computing device to the OS ID identified in the alert; and

providing malware remediation to the computing device.

Assignments (15)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 5, 2024
From: RPX CORPORATION
To: NETSKOPE, INC.
Reel/Frame 067918/0690 →
RELEASE OF SECURITY INTEREST IN SPECIFIED PATENTS Recorded May 31, 2024
From: BARINGS FINANCE LLC
To: RPX CORPORATION
Reel/Frame 067596/0606 →
PATENT SECURITY AGREEMENT Recorded Apr 22, 2023
From: RPX CORPORATION
To: BARINGS FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 063429/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 28, 2021
From: PROVENANCE ASSET GROUP LLC
To: RPX CORPORATION
Reel/Frame 059352/0001 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: NOKIA US HOLDINGS INC.
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058363/0723 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: CORTLAND CAPITAL MARKETS SERVICES LLC
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058983/0104 →
ASSIGNMENT AND ASSUMPTION AGREEMENT Recorded Feb 14, 2019
From: NOKIA USA INC.
To: NOKIA US HOLDINGS INC.
Reel/Frame 048370/0682 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 13, 2017
From: NOKIA TECHNOLOGIES OY; NOKIA SOLUTIONS AND NETWORKS BV; ALCATEL LUCENT SAS
To: PROVENANCE ASSET GROUP LLC
Reel/Frame 043877/0001 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP LLC
To: NOKIA USA INC.
Reel/Frame 043879/0001 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP, LLC
To: CORTLAND CAPITAL MARKET SERVICES, LLC
Reel/Frame 043967/0001 →
RELEASE OF SECURITY INTEREST Recorded Aug 28, 2014
From: CREDIT SUISSE AG
To: ALCATEL-LUCENT USA
Reel/Frame 033647/0251 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 21, 2013
From: ALCATEL-LUCENT USA INC.
To: ALCATEL LUCENT
Reel/Frame 031650/0207 →
SECURITY AGREEMENT Recorded Jul 22, 2013
From: ALCATEL LUCENT USA, INC.
To: CREDIT SUISSE AG
Reel/Frame 030851/0364 →
MERGER Recorded Jun 6, 2013
From: KINDSIGHT, INC.
To: ALCATEL-LUCENT USA INC.
Reel/Frame 030559/0110 →
RELEASE OF SECURITY INTEREST Recorded Jun 6, 2013
From: ALCATEL-LUCENT USA INC.
To: KINDSIGHT, INC.
Reel/Frame 030572/0657 →