IP Library Granted Patent US 7,899,828
Granted Patent B2
US 7,899,828 · App. 10/814,093 · Granted Mar 1, 2011

Tag data structure for maintaining relational data over captured objects

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 7,899,828
App. No.
10/814,093
Granted
Mar 1, 2011
Kind
B2
Abstract

Objects captured over a network by a capture system can be indexed to provide enhanced search and content analysis capabilities. In one embodiment the objects can be indexed using a data structure having a source address field to indicate an origination address of the object, a destination address field to indicate a destination address of the object, a source port field to indicate an origination port of the object, a destination port field to indicate a destination port of the object, a content field to indicate a content type from a plurality of content types identifying a type of content contained in the object, and a time field to indicate when the object was captured. The data structure may also store a cryptographic signature of the object to ensure the object is not altered after capture.

Claims (67)

1. A computer readable medium having stored thereon data representing instructions that, when executed by a processor, cause the processor to perform operations comprising:

generating a tag describing an object of a communication captured during transmission of the communication from an origination address to a destination address, extracted from the communication, and stored in a memory block, wherein the tag includes,

a source address field to indicate an origination address of the object,

a destination address field to indicate a destination address of the object,

a source port field to indicate an origination port of the object,

a destination port field to indicate a destination port of the object,

a content field to indicate a content type from a plurality of content types identifying a type of content contained in the object, and

a time field to indicate when the object was captured; and

storing the tag in a database, wherein the tag indexes the object in the memory block, the tag being stored to allow subsequent searching for the object based on one or more of the fields, wherein the fields are obtained from the communication, and wherein the object is part of a document captured based on a capture rule that defines which objects are to be captured, wherein the capture rule is part of a default rule set for a capture system configured to monitor network traffic, and wherein a determination is made based on the capture rule to discard or to store the document, and wherein the capture rule identifies a first internet protocol (IP) address from which the document was sent and a second IP address associated with an intended destination of the document.

2. The computer readable medium of claim 1 , wherein the plurality of content types comprises JPEG, GIF, BMP, TIFF, PNG, Skintone, PDF, MSWord, Excel, PowerPoint, MSOffice, HTML, WebMail, SMTP, Telnet, Rlogin, FTP, Chat, GZIP, ZIP, TAR, C++Source, C Source, FORTRAN Source, Verilog Source, C Shell, K Shell, Bash Shell, Plaintext, Crypto, LIF, Binary Unknown, ASCII Unknown, and Unknown.

3. The computer readable medium of claim 1 , further comprising generating a device identity field to indicate a device that captured the object.

4. The computer readable medium of claim 1 , further comprising generating a protocol field to indicate the protocol that carried the object.

5. The computer readable medium of claim 1 , further comprising an instance field to indicate a number of the object in a connection.

6. The computer readable medium of claim 1 , further comprising generating an encoding field to indicate a how the object was encoded.

7. The computer readable medium of claim 1 , further comprising generating a size field to indicate the size of the object.

8. The computer readable medium of claim 1 , further comprising generating an owner field to indicate an entity that requested capture of the object.

9. The computer readable medium of claim 1 , further comprising generating a capture rule field to indicate a rule that triggered capture of the object.

10. The computer readable medium of claim 1 , further comprising generating a signature field to store a signature of the object.

11. The computer readable medium of claim 10 , wherein the signature comprises a digital cryptographic signature.

12. The computer readable medium of claim 1 , further comprising generating a tag signature field to store a signature of the data structure.

13. The computer readable medium of claim 12 , wherein the tag signature comprises a digital cryptographic signature.

14. A computer readable medium having stored thereon data representing instructions that, when executed by a processor, cause the processor to perform operations comprising:

storing data associated with an object of a communication captured during transmission of the communication from an origination address to a destination address, extracted from the communication, and stored in a memory block by a capture system to create a tag that indexes the object in the memory block, the data comprising:

an Ethernet controller MAC address of the capture system that captured the object;

a source Ethernet IP address of the object;

a destination Ethernet IP address of the object;

a source TCP/IP port number of the object;

a destination TCP/IP port number of the object.

an IP protocol that carried the object when captured by the capture system;

a canonical count of a number of the object within a TCP/IP connection;

a content type of the object;

an encoding that was used on the object;

a size of the object;

a timestamp indicating when the capture system captured the object;

a user who requested capture of the object;

a capture rule that directed capture of the object;

a hash signature of the object; and

a hash signature of the tag, the tag being stored to allow subsequent searching for the object based on one or more of the fields, wherein the IP addresses are obtained from the communication, and wherein the object is part of a document captured based on a capture rule that defines which objects are to be captured, wherein the capture rule is part of a default rule set for the capture system configured to monitor network traffic, and wherein a determination is made based on the capture rule to discard or to store the document, and wherein the capture rule identifies a first internet protocol (IP) address from which the document was sent and a second IP address associated with an intended destination of the document.

15. The computer readable medium of claim 14 , wherein the hash signature of the object comprises a digital cryptographic signature of the object.

16. The computer readable medium of claim 15 , wherein the hash signature of the tag comprises a digital cryptographic signature of the tag.

17. The computer readable medium of claim 14 , wherein the content type of the object is one of JPEG, GIF, BMP, TIFF, PNG, Skintone, PDF, MSWord, Excel, PowerPoint, MSOffice, HTML, WebMail, SMTP, Telnet, Rlogin, FTP, Chat, GZIP, ZIP, TAR, C++Source, C Source, FORTRAN Source, Verilog Source, C Shell, K Shell, Bash Shell, Plaintext, Crypto, LIF, Binary Unknown, ASCII Unknown, and Unknown.

18. A method to index a captured object, comprising:

generating for storage of objects of a communication captured during transmission of the communication from an origination address to a destination address, extracted from the communication, and stored in a memory block:

a source address field to indicate an origination address of the object;

a destination address field to indicate a destination address of the object;

a source port field to indicate an origination port of the object;

a destination port field to indicate a destination port of the object;

a content field to indicate a content type from a plurality of content types identifying a type of content contained in the object; and

a time field to indicate when the object was captured; and

storing data in the fields to create a tag, the tag indexing the objects in the memory block, the tag being stored to allow subsequent searching for the objects based on one or more of the fields, wherein the fields are obtained from the communication, and wherein the object is part of a document captured based on a capture rule that defines which objects are to be captured, wherein the capture rule is part of a default rule set for a capture system configured to monitor network traffic, and wherein a determination is made based on the capture rule to discard or to store the document, and wherein the capture rule identifies a first internet protocol (IP) address from which the document was sent and a second IP address associated with an intended destination of the document.

19. A method to index a captured object, comprising:

storing data associated with an object of a communication captured during transmission of the communication from an origination address to a destination address, extracted from the communication, and stored in a memory block by a capture system to create a tag indexing the object in the memory block, the data comprising:

an Ethernet controller MAC address of the capture system that captured the object;

a source Ethernet IP address of the object;

a destination Ethernet IP address of the object;

a source TCP/IP port number of the object;

a destination TCP/IP port number of the object;

an IP protocol that carried the object when captured by the capture system;

a canonical count of a number of the object within a TCP/IP connection;

a content type of the object;

an encoding that was used on the object;

a size of the object;

a timestamp indicating when the capture system captured the object;

a user who requested capture of the object;

a capture rule that directed capture of the object;

a hash signature of the object; and

a hash signature of the tag, the tag being stored to allow subsequent searching for the object based on one or more of the fields, wherein the IP addresses are obtained from the communication, and wherein the object is part of a document captured based on a capture rule that defines which objects are to be captured, wherein the capture rule is part of a default rule set for the capture system configured to monitor network traffic, and wherein a determination is made based on the capture rule to discard or to store the document, and wherein the capture rule identifies a first internet protocol (IP) address from which the document was sent and a second IP address associated with an intended destination of the document.

Assignments (10)
CORRECTIVE ASSIGNMENT TO CORRECT THE THE PATENT TITLES AND REMOVE DUPLICATES IN THE SCHEDULE PREVIOUSLY RECORDED AT REEL: 059354 FRAME: 0335. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Jun 23, 2022
From: MCAFEE, LLC
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 060792/0307 →
SECURITY INTEREST Recorded Mar 3, 2022
From: MCAFEE, LLC
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT AND COLLATERAL AGENT
Reel/Frame 059354/0335 →
RELEASE OF INTELLECTUAL PROPERTY COLLATERAL - REEL/FRAME 045056/0676 Recorded Mar 2, 2022
From: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
To: MCAFEE, LLC
Reel/Frame 059354/0213 →
RELEASE OF INTELLECTUAL PROPERTY COLLATERAL - REEL/FRAME 045055/0786 Recorded Oct 26, 2020
From: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: MCAFEE, LLC
Reel/Frame 054238/0001 →
CORRECTIVE ASSIGNMENT TO CORRECT THE REMOVE PATENT 6336186 PREVIOUSLY RECORDED ON REEL 045055 FRAME 786. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST. Recorded Oct 22, 2020
From: MCAFEE, LLC
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 055854/0047 →
CORRECTIVE ASSIGNMENT TO CORRECT THE REMOVE PATENT 6336186 PREVIOUSLY RECORDED ON REEL 045056 FRAME 0676. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST. Recorded Oct 22, 2020
From: MCAFEE, LLC
To: MORGAN STANLEY SENIOR FUNDING, INC.
Reel/Frame 054206/0593 →
SECURITY INTEREST Recorded Jan 12, 2018
From: MCAFEE, LLC
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 045055/0786 →
SECURITY INTEREST Recorded Jan 12, 2018
From: MCAFEE, LLC
To: MORGAN STANLEY SENIOR FUNDING, INC.
Reel/Frame 045056/0676 →
CHANGE OF NAME AND ENTITY CONVERSION Recorded Aug 24, 2017
From: MCAFEE, INC.
To: MCAFEE, LLC
Reel/Frame 043665/0918 →
MERGER Recorded Jan 26, 2009
From: RECONNEX CORPORATION
To: MCAFEE, INC.
Reel/Frame 022214/0151 →