US 8,701,196 B2Grant

System, method and computer program product for obtaining a reputation associated with a file

Issue Date:2014-04-15

•25 Claims

•7 Drawing Sheets

Abstract

A reputation system, method and computer program product are provided. In use, a file associated with a first computer is identified. Thereafter, a reputation associated with the file stored at a second computer is obtained.

Metadata

Assignee

McAfee, Inc.

Inventors

George L. Heron
Christopher S. Bolin

Application Information

Application Number:US 11/395,758

Filing Date:2006-03-31

Priority Date:2006-03-31

Art Unit:2434

Classifications

IPC:

G06F11/00

Patent Drawings (7 sheets)

Description

Field of the Invention

[0001] The present invention relates to security applications, and more particularly to reputation rating systems.

Background

[0002] Increasingly, computer systems have needed to protect themselves against undesirable code. Such undesirable computer code has generally taken the form of viruses, worms, Trojan horses, spyware, adware, and so forth. The damage and/or inconvenience capable of being incurred by these types of undesirable code has ranged from mild interference with a program, such as the display of an unwanted political message in a dialog box, to the complete destruction of contents on a hard drive, and even the theft of personal information.

[0003] Many mechanisms have been created in order to provide the much needed protection from such undesirable code and the affects thereof. For example, prior art systems are capable of identifying a “reputation” of a web site. This is traditionally accomplished by reviewing various files that are available from the site. If such files are determined to be free of malware, spyware, etc., the foregoing systems assume that the entity providing such content is “good” and can perhaps be trusted in other areas such as data accuracy, authenticity, etc. On the other hand, however, if the available files are determined to contain undesirable code that proves to be harmful or otherwise hinder normal computer operation, etc., the entity and associated site providing such files can be assumed to be “bad.”

[0004] Unfortunately, such prior art systems only provide the “reputation” of web sites, as opposed to individual files. Thus, the “good” or “bad” rating of files associated with a given on-line site is typically done manually by a computer user. For example, such user may either hear that a new music download site has files infected with spyware and, as a result, the user will not download such files. In more serious situations, such person may empirically learn of the “bad” nature of the files by personally downloading one or more of the files and becoming infected, a truly undesirable situation.

[0005] There is thus a need for overcoming these and/or other problems associated with the prior art.

Summary

[0006] A reputation system, method and computer program product are provided. In use, a file associated with a first computer is identified. Thereafter, a reputation associated with the file stored at a second computer is obtained.

Brief Description of the Drawings

[0007] FIG. 1 illustrates a network architecture, in accordance with one embodiment.

[0008] FIG. 2 shows a representative hardware environment that may be associated with the server computers and/or client computers of FIG. 1, in accordance with one embodiment.

[0009] FIG. 3 shows a method for obtaining a reputation associated with a file, in accordance with one embodiment.

[0010] FIG. 4 shows a method for generating a reputation database in an automated manner, in accordance with one embodiment.

[0011] FIG. 5 shows a method for using a reputation database, in accordance with one embodiment.

[0012] FIG. 6 shows a method for generating a reputation database in a distributed manner, in accordance with another embodiment.

Detailed Description

[0013] FIG. 1 illustrates a network architecture 100, in accordance with one embodiment. As shown, a plurality of networks 102 is provided. In the context of the present network architecture 100, the networks 102 may each take any form including, but not limited to a local area network (LAN), a wireless network, a wide area network (WAN) such as the Internet, peer-to-peer network, etc.

[0014] Coupled to the networks 102 are server computers 104 which are capable of communicating over the networks 102. Also coupled to the networks 102 and the server computers 104 is a plurality of client computers 106. Such server computers 104 and/or client computers 106 may each include a desktop computer, lap-top computer, hand-held computer, mobile phone, hand-held computer, peripheral (e.g. printer, etc.), any component of a computer, and/or any other type of logic. In order to facilitate communication among the networks 102, at least one gateway 108 is optionally coupled therebetween.

[0015] FIG. 2 shows a representative hardware environment that may be associated with the server computers 104 and/or client computers 106 of FIG. 1, in accordance with one embodiment. Such figure illustrates a typical hardware configuration of a workstation in accordance with one embodiment having a central processing unit 210, such as a microprocessor, and a number of other units interconnected via a system bus 212.

[0016] The workstation shown in FIG. 2 includes a Random Access Memory (RAM) 214, Read Only Memory (ROM) 216, an I/O adapter 218 for connecting peripheral devices such as disk storage units 220 to the bus 212, a user interface adapter 222 for connecting a keyboard 224, a mouse 226, a speaker 228, a microphone 232, and/or other user interface devices such as a touch screen (not shown) to the bus 212, communication adapter 234 for connecting the workstation to a communication network 235 (e.g., a data processing network) and a display adapter 236 for connecting the bus 212 to a display device 238.

[0017] The workstation may have resident thereon any desired operating system. It will be appreciated that an embodiment may also be implemented on platforms and operating systems other than those mentioned. One embodiment may be written using JAVA, C, and/or C++ language, or other programming languages, along with an object oriented programming methodology. Object oriented programming (OOP) has become increasingly used to develop complex applications.

[0018] Our course, the various embodiments set forth herein may be implemented utilizing hardware, software, or any desired combination thereof. For that matter, any type of logic may be utilized which is capable of implementing the various functionality set forth herein.

[0019] FIG. 3 shows a method 300 for obtaining a reputation associated with a file, in accordance with one embodiment. As an option, the method 300 may be implemented in the context of the architecture and environment of FIGS. 1 and/or 2. Of course, however, the method 300 may be carried out in any desired environment.

[0020] As shown, in operation 301, a file associated with a first computer is identified. In the context of the present description, a file may refer to a text file, a word processing file, a spreadsheet file, a picture file, an executable file, a script file, a library file, a control file, a component of a file, and/or any other collection of data and/or code capable of having a reputation as will soon be set forth. Still yet, the first computer may refer to a client or server computer (e.g. see, for example, computers 102 and 104 of FIG. 1, etc.), and/or any desired device. Even still, the aforementioned association between the file and computer may refer to the fact that the file is stored in memory of the computer, the file is controlled/managed by the computer, and/or any other desired association.

[0021] Of course, the file may be identified in any desired manner. Just by way of example, the file may be identified upon being selected for downloading and/or opening (e.g. during the course of an on-access scan, etc.), during the course of an on-demand scan, and/or by any other technique that results in the identification of the file.

[0022] To this end, a reputation associated with the file stored at a second computer may be obtained. See operation 302. Similar to the first computer, the second computer may refer to a client or server computer (e.g. see, for example, computers 102 and 104 of FIG. 1, etc.), and/or any desired device, as long as the second computer is separate from the first computer. In the context of the present description, the term reputation may refer to any information relating to any characteristic or trait associated with the file. More information regarding one exemplary way the reputation may be obtained in the spirit of the present embodiment will be set forth during reference to FIG. 5.

[0023] In one optional embodiment, the reputation may be obtained utilizing a database identifying a plurality of files and a reputation associated with each of the files. Of course, such database may be situated on any desired computer (e.g. the aforementioned second computer, etc.). In another embodiment, the reputation may even be obtained from a computer that is the same as that associated with the file. Thus, during use, the database is accessible by a computer attempting to download the file, and/or otherwise identifies the same.

[0024] Of course, the database may be generated in any desired manual and/or automated manner. Just by way of example, an Internet-crawling technique may be employed. Still yet, in other embodiments, each file may first be identified at a particular computer during the use thereof, such that a reputation associated with the file may be determined and stored at another computer. More information regarding such ways of building a reputation database will be set forth during reference to FIGS. 4 and 6.

[0025] Again, more illustrative information will now be set forth regarding various optional architectures and features with which the foregoing technique may or may not be implemented, per the desires of the user. It should be strongly noted that the following information is set forth for illustrative purposes and should not be construed as limiting in any manner. Any of the following features may be optionally incorporated with or without the exclusion of other features described.

[0026] FIG. 4 shows a method 400 for generating a reputation database in an automated manner, in accordance with one embodiment. As an option, the method 400 may be implemented in the context of the architecture and environment of FIGS. 1-2. Of course, however, the method 400 may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description.

[0027] As shown, in operation 402, a network (e.g. the Internet, etc.) may be crawled in the search of sites (e.g. web sites, etc.) with files stored in associated therewith. Of course, this may be accomplished in any desired manner. Just by way of example, one or more search agents may search the network for different sites and process the same in the following manner. To this end, a plurality of files associated with a plurality of sites on a network are inspected.

[0028] Specifically, in decision 404, it is first determined whether a site is found. If so, a file stored at the site is retrieved. See operation 406. Such retrieval may be effected by downloading the file to a computer (e.g. see, for example, computers 102 and 104 of FIG. 1, etc.) other than that on which the site resides, for the purpose of executing the following operations. Of course, other embodiments are contemplated whereby such downloading is not necessary and the following operations are performed at the site.

[0029] With continuing reference to FIG. 4, such processing includes the scanning and/or use of the file, as set forth in operation 408. The present scanning may involve the comparison of the file with a plurality of signatures, patterns, etc. that are known to be associated with at least potentially undesirable characteristics. Of course, such undesirable characteristics may be indicative of any at least potentially undesirable code including, but not limited to malware (e.g. viruses, worms, Trojan horses, etc.) spyware, adware, spam, etc. Of course, any other processing may be employed that is capable of identifying at least one undesirable characteristic associated with the file (if it exists).

[0030] In addition to or instead of the aforementioned scanning, the file may also be used to determine whether any undesirable characteristic is exhibited. Such use may take the form of simply opening the file, executing the file in an isolated environment, and/or any other type of use that is capable of prompting the file to exhibit an undesirable characteristic (again, if it exists).

[0031] It should be strongly noted that additional techniques may be employed other than the above scanning and use. Just by way of example, any type of emulation, heuristics, loading, etc. may be employed. Still yet, other techniques may be utilized as a function of a type of the file. For example, in the case of a compressed file (e.g. a file in a ZIP format, etc.), the file may first be decompressed, etc.

[0032] To this end, it may be determined in decision 410 as to whether any undesirable characteristics are exhibited. If so, the file may be identified as having at least a potentially “bad” reputation. On the other hand, if it is determined in decision 410 that undesirable characteristics are not exhibited in association with an instant file, it may be determined in decision 414 as to whether any additional files exist with respect to the current site.

[0033] If it is determined in decision 414 that at least one additional file exists with respect to the current site, the operations 406-410 may be repeated, as necessary. To this end, if each of the files are scanned and/or used, and no undesirable characteristics are exhibited per decision 410, each file (and potentially the entire site) may be identified as having at least a potentially “good” reputation. Conversely, if at least one of the files associated with the site is determined to have the bad reputation, at least the file exhibiting the undesirable characteristic (and/or all of the files of the site) may be designated with such negative reputation. Thus, in one embodiment (shown in FIG. 4), the existence of at least one bad file may result in the entire site (and associated files) as having a bad reputation. Of course, however, in other embodiments, each file may be individually given a good or bad reputation.

[0034] Next, in operation 418, results of the foregoing operations may be stored in a database. In one embodiment, such database may include a remote central database which may or may not be distributed among a plurality of servers, etc. Of course, other embodiments are envisioned where the database is stored locally.

[0035] Of course, the identification of the appropriate reputation may be implemented in any desired manner. Just by way of example, Table 1 illustrates one exemplary data structure that may be used in association with the foregoing database.

[0036]

	TABLE 1

		File name_l	Good_Reputation
		File name_2	Bad_Reputation
		File name_3	Good_Reputation
		File name_4	Bad_Reputation
		File name_5	Good_Reputation

[0037] Such data structure, of course, should not be construed as limiting in any manner. For example, more than two possible reputations may be contemplated, thereby providing more granularity as to file reputation. Further, the files may be identified using additional file-related information including, but not limited to a time stamp, file size, hash (e.g. checksum, etc.), and/or any other desired file attribute.

[0038] With the foregoing database populated, the database may be used in a situation where the file is subsequently opened and/or used, for enhancing security. More information will now be set forth regarding one exemplary method of use of the database in such manner.

[0039] FIG. 5 shows a method 500 for using a reputation database, in accordance with one embodiment. As an option, the method 500 may be implemented in the context of the architecture and environment of FIGS. 1-4. Of course, however, the method 500 may be carried out in any desired environment. Again, the aforementioned definitions may equally apply during the present description.

[0040] As shown, it is determined, in decision 502, whether a file is to be (or has been) downloaded over a network. While a downloading scenario is described herein, it should be noted that the file may be identified in response to any attempt to obtain, open, use, execute, etc. the file. As shown, in decision 502, the method 500 polls until such identification is made.

[0041] Upon it being determined that a file is to be (or has been) downloaded over the network, per decision 502, the file is looked up in a remote database. See operation 504. Such remote database may, in one embodiment, take the form of that set forth during reference to Table 1 above, and may further be generated in accordance with FIG. 4. To accomplish the functionality of the present method 500, an agent may be loaded onto each computer on which protection is desired, where such agent is capable of the present operations as is further equipped with the location of the remote database.

[0042] Once the look-up is complete, it may be determined whether the file has a good or bad rating. See decision 508. If the file has a good rating, the file may simply be opened by the user without further intervention. Note operation 514. Of course, the file may optionally be subjected to supplementary scanning, etc. prior to opening in operation 514.

[0043] On the other hand, if it is determined, in decision 508, that the file has a bad rating, it may then be determined whether a policy associated with the computer, network, and/or user downloading the file is prohibited from accessing files with such bad reputation. See operation 510. If so, the method 500 may be restarted without opening the file. In various embodiments, the policy may be set by an administrator and/or be user-configurable per the desires of the user.

[0044] If, in contrast, the policy does not necessarily prohibit access to files with a bad reputation, the user may be simply notified of the reputation. See operation 512. To this end, the user may make a manual determination as to whether the file is safe to open. In addition to or instead of such notification, additional scanning, etc. may be carried out, for security purposes. Of course, any desired response (or lack thereof) may be employed as function of both the policy and the bad or good reputation.

[0045] By this design, in one example of use, a may user observe, through a rating display interface or the like, that the file being downloaded may have previously done harm to another computer, in which case the user may wish to abort or clean the file before use and/or execution. Still yet, upon determining such condition, the user may be inhibited from completing or using the download via the aforementioned policy, thus providing a way for an enterprise to protect employees with policy-based actions, etc.

[0046] Alternatively, when a good rating is found, the user may be able to proceed in downloading, opening, saving, running, etc. the file. In summary, in the case of a good rating, the user may feel safer using the referenced file; and, in the case of a bad rating, the user may be discouraged or even inhibited from using the referenced file.

[0047] FIG. 6 shows a method 600 for generating a reputation database in a distributed manner, in accordance with one embodiment. As an option, the method 600 may be implemented in the context of the architecture and environment of FIGS. 1-5 and, in particular, be used instead of or in conjunction with the method 400 of FIG. 4, for building a reputation database. Of course, however, the method 600 may be carried out in any desired environment. Yet again, the aforementioned definitions may equally apply during the present description.

[0048] As shown, an initial set of operations 601 may each be carried out utilizing an agent loaded onto a computer where one or more files are being accessed, used, etc. While only one set of operations 601 is shown in FIG. 6, it should be noted that such set of operations 601 may be carried out on a plurality of separate computers. To this end, such set of computers may feed a service provider which, in turn, processes results of such sets of operations 601 during the course of a subsequent set of operations 609, in a manner that will soon be set forth.

[0049] In particular, one or more files are monitored at the one or more computers. Note operation 602. It should be noted that such monitoring may refer to any of the aforementioned processing (e.g. see, for example, operation 408 of FIG. 4, etc.) that is capable of identifying undesirable characteristics. See decision 606.

[0050] If, at any time, any undesirable characteristics are found in association with any one or more files, information relating to such processing may be sent to a service provider. Note operation 608. In one embodiment, such service provider may include MCAFEE, INC. Further, it should be noted that the information may include an identification of the file along with the undesirable characteristics and/or a determination as to whether the file has a good or bad reputation, etc. (depending on where such determination is to take place).

[0051] Thus, in operation 610, the service provider may receive such information from a plurality of different computers for aggregation purposes. By aggregating the information, such information may be compared and/or correlated in order to provide a more certain determination regarding the reputation thereof. See operation 612. Thus, such overall reputation may, in turn, be sent to a remote database. Of course, the computer (e.g. server, etc.) on which the service provider operates may or may not be that on which the database resides.

[0052] Thus, in one example of use, a “community rating system” may be provided to augment or replace the aforementioned automatic download-and-detect method described during reference to FIG. 4. Here, in one embodiment, a software agent running on a computer may indicate a user experience with a downloaded file; if the downloaded file eventually demonstrates undesirable characteristics (e.g. found through experience to contain harmful malware of any type, etc.). In such case, the user is able to automatically or manually submit such findings in a controlled manner to a central service provider and a related network reputation database, thus providing additional indicators that are used to ultimately determine the rating of a given file.

[0053] In one embodiment, terrorism may be countered utilizing the aforementioned technology. According to the U.S. Federal Bureau of Investigation, cyber-terrorism is any “premeditated, politically motivated attack against information, computer systems, computer programs, and data which results in violence against non-combatant targets by sub-national groups or clandestine agents.” A cyber-terrorist attack is designed to cause physical violence or extreme financial harm. According to the U.S. Commission of Critical Infrastructure Protection, possible cyber-terrorist targets include the banking industry, military installations, power plants, air traffic control centers, and water systems. Thus, by optionally incorporating the present technology into the cyber-frameworks of the foregoing potential targets, terrorism may be countered by identifying code as including malware, etc., which may be used to combat cyber-terrorism.

[0054] While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. For example, any of the network elements may employ any of the desired functionality set forth hereinabove. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

Claims

What is claimed is:

1. A method, comprising:

identifying a file associated with a first computer;

obtaining an overall reputation associated with the file stored at a second computer, wherein the overall reputation comprises at least one characteristic associated with the file that includes undesirable code identified through a scanning activity, and wherein the overall reputation is determined by receiving information on the reputation of the file from each of a plurality of computers and aggregating the information received from each of the plurality of computers to produce the overall reputation associated with the file, and wherein the information on the reputation of the file received from each of the plurality of computers is based upon a respective determination of a reputation of the file by each of the plurality of computers; and

identifying a policy, wherein an agent provisioned in the first computer prohibits downloading of the file based on whether the reputation complies with configurable reputation settings provided in the policy, and wherein the policy is configured for indicating that additional scanning is to be carried out based on the reputation of the file.

2. The method of claim 1, wherein the overall reputation associated with the file is determined automatically by inspecting a plurality of files associated with a plurality of sites on a network.

3. The method of claim 2, wherein a plurality of the reputations associated with the plurality of files are stored in a database at the second computer, from which the overall reputation is obtained.

4. The method of claim 1, wherein the overall reputation associated with the file is determined based on an identification of an undesirable characteristic during at least one of scanning and using the file.

5. The method of claim 1, wherein information on the overall reputation associated with the file is identified at a third computer during use of the file.

6. The method of claim 1, wherein the overall reputation is obtained by looking up the overall reputation in a central database.

7. A non-transitory computer-readable medium, comprising one or more instructions that when executed on a processor configure the processor to:

identify a file associated with a first computer;

obtain an overall reputation associated with the file stored at a second computer, wherein the overall reputation comprises at least one characteristic associated with the file that includes undesirable code identified through a scanning activity, and wherein the overall reputation is determined by receiving information on the reputation of the file from each of a plurality of computers and aggregating the information received from each of the plurality of computers to produce the overall reputation associated with the file, and wherein the information on the reputation of the file received from each of the plurality of computers is based upon a respective determination of a reputation of the file by each of the plurality of computers; and

identify a policy, wherein an agent provisioned in the first computer prohibits downloading of the file based on whether the reputation complies with configurable reputation settings provided in the policy, and wherein the policy is configured for indicating that additional scanning is to be carried out based on the reputation of the file.

8. The computer-readable medium of claim 7, wherein the reputation includes at least one of a good reputation and a bad reputation.

9. The computer-readable medium of claim 8, wherein the policy is set by an administrator and indicates that the access to the file with the bad reputation is prohibited based on the policy.

10. The computer-readable medium of claim 7, wherein the policy further indicates that the file should be executed in an isolated environment to determine if any undesirable characteristic is exhibited by the file.

11. The computer-readable medium of claim 7, wherein the policy further indicates that the file should be emulated to determine if any undesirable characteristic is exhibited by the file.

12. The computer-readable medium of claim 7, wherein the overall reputation associated with the file is determined automatically by inspecting a plurality of files associated with a plurality of sites on a network.

13. The computer-readable medium of claim 12, wherein a plurality of the reputations associated with the plurality of files are stored in a database at the second computer, from which the overall reputation is obtained.

14. The computer-readable medium of claim 7, wherein the overall reputation associated with the file is determined based on an identification of an undesirable characteristic during at least one of scanning and using the file.

15. The computer-readable medium of claim 7, wherein information on the overall reputation associated with the file is identified at a third computer during use of the file.

16. The computer-readable medium of claim 7, wherein the file is identified in response to an attempt to download the file over a network.

17. The computer-readable medium of claim 7, wherein the overall reputation is obtained by looking up the overall reputation in a central database.

18. An apparatus, comprising:

a processor operable to execute computer program instructions; and

a memory coupled to the processor and operable to store computer program instructions executable by the processor such that the system is configured to:

identify a file associated with a first computer;

19. The apparatus of claim 18, wherein the overall reputation associated with the file is determined automatically by inspecting a plurality of files associated with a plurality of sites on a network.

20. The apparatus of claim 19, wherein a plurality of the reputations associated with the plurality of files are stored in a database at the second computer, from which the overall reputation is obtained.

21. The apparatus of claim 18, wherein the overall reputation associated with the file is determined based on an identification of an undesirable characteristic during at least one of scanning and using the file.

22. A system, comprising:

a first computer configured to identify a file associated with the first computer; and

a second computer configured to provide an overall reputation associated with the file stored at the second computer to the first computer, wherein the overall reputation comprises at least one characteristic associated with the file that includes undesirable code identified through a scanning activity, and wherein the overall reputation is determined by receiving information on the reputation of the file from each of a plurality of computers and aggregating the information received from each of the plurality of computers to produce the overall reputation associated with the file, and wherein the information on the reputation of the file received from each of the plurality of computers is based upon a respective determination of a reputation of the file by each of the plurality of computers; and

wherein the first computer is further configured to identify a policy, wherein an agent provisioned in the first computer prohibits downloading of the file based on whether the reputation complies with configurable reputation settings provided in the policy, and wherein the policy is configured for indicating that additional scanning is to be carried out based on the reputation of the file.

23. The system of claim 22, wherein the overall reputation associated with the file is determined automatically by inspecting a plurality of files associated with a plurality of sites on a network.

24. The system of claim 23, wherein a plurality of the reputations associated with the plurality of files are stored in a database at the second computer, from which the overall reputation is obtained.

25. The system of claim 22, wherein the overall reputation associated with the file is determined based on an identification of an undesirable characteristic during at least one of scanning and using the file.

Patent Citations (198)

Patent	Date	Inventor	Cited By
US5274819(A)	1993-12-01	Blomfield-Brown	Applicant
US5742763(A)	1998-04-01	Jones	Applicant
US5870559(A)	1999-02-01	Leshem et al.	Applicant
US5892904(A)	1999-04-01	Atkinson et al.	Applicant
US5949419(A)	1999-09-01	Domine et al.	Applicant
US5978917(A)	1999-11-01	Chi	Examiner
US5987610(A)	1999-11-01	Franczek et al.	Applicant
US6018724(A)	2000-01-01	Arent	Applicant
US6065055(A)	2000-05-01	Hughes et al.	Applicant
US6073142(A)	2000-06-01	Geiger et al.	Applicant
US6219786(B1)	2001-04-01	Cunningham et al.	Applicant
US6285999(B1)	2001-09-01	Page	Applicant
US6321334(B1)	2001-11-01	Jerger et al.	Applicant
US6356937(B1)	2002-03-01	Montville et al.	Applicant
US6366912(B1)	2002-04-01	Wallent et al.	Applicant
US6367012(B1)	2002-04-01	Atkinson et al.	Applicant
US6460050(B1)	2002-10-01	Pace et al.	Applicant
US6539430(B1)	2003-03-01	Humes	Applicant
US6606659(B1)	2003-08-01	Hegli et al.	Applicant
US6647400(B1)	2003-11-01	Moran	Applicant
US6658394(B1)	2003-12-01	Khaishgi et al.	Applicant
US6708205(B2)	2004-03-01	Sheldon et al.	Applicant
US6742128(B1)	2004-05-01	Joiner	Applicant
US6748422(B2)	2004-06-01	Morin et al.	Applicant
US6772345(B1)	2004-08-01	Shetty	Applicant
US6785732(B1)	2004-08-01	Bates et al.	Applicant
US6826697(B1)	2004-11-01	Moran	Applicant
US6856963(B1)	2005-02-01	Hurwitz	Applicant
US6886102(B1)	2005-04-01	Lyle	Applicant
US6907533(B2)	2005-06-01	Sorkin et al.	Applicant
US6938003(B2)	2005-08-01	Harpale	Applicant
US7003734(B1)	2006-02-01	Gardner et al.	Applicant
US7024630(B2)	2006-04-01	Himmel et al.	Applicant
US7084760(B2)	2006-08-01	Himberger et al.	Applicant
US7096493(B1)	2006-08-01	Liu	Examiner
US7100122(B2)	2006-08-01	Blaschke et al.	Applicant
US7114177(B2)	2006-09-01	Rosenberg et al.	Applicant
US7136875(B2)	2006-11-01	Anderson et al.	Applicant
US7143139(B2)	2006-11-01	Burbeck et al.	Applicant
US7171470(B2)	2007-01-01	Doyle et al.	Applicant
US7207480(B1)	2007-04-01	Geddes	Applicant
US7216360(B2)	2007-05-01	Nakao et al.	Examiner
US7231395(B2)	2007-06-01	Fain et al.	Applicant
US7254573(B2)	2007-08-01	Burke	Applicant
US7257549(B2)	2007-08-01	Karaoguz et al.	Applicant
US7313691(B2)	2007-12-01	Bantz et al.	Applicant
US7370188(B2)	2008-05-01	Rothman et al.	Applicant
US7380267(B2)	2008-05-01	Arai et al.	Examiner
US7506155(B1)	2009-03-01	Stewart et al.	Applicant
US7562304(B2)	2009-07-01	Dixon et al.	Applicant
US7603718(B2)	2009-10-01	Rounthwaite et al.	Applicant
US7634810(B2)	2009-12-01	Goodman et al.	Applicant
US7694135(B2)	2010-04-01	Rowan et al.	Applicant
US7756930(B2)	2010-07-01	Brahms et al.	Applicant
US7765481(B2)	2010-07-01	Dixon et al.	Applicant
US7809650(B2)	2010-10-01	Bruesewitz et al.	Applicant
US7822620(B2)	2010-10-01	Dixon et al.	Applicant
US7831611(B2)	2010-11-01	Roberts et al.	Applicant
US7831915(B2)	2010-11-01	Averbuch et al.	Applicant
US8065720(B1)	2011-11-01	Ebrahimi et al.	Applicant
US8296664(B2)	2012-10-01	Dixon et al.	Applicant
US8321791(B2)	2012-11-01	Dixon et al.	Applicant
US8429545(B2)	2013-04-01	Dixon et al.	Applicant
US8438499(B2)	2013-05-01	Dixon et al.	Applicant
US2001/0007098(A1)	2001-07-01	Hinrichs et al.	Applicant
US2001/0011284(A1)	2001-08-01	Humpleman et al.	Applicant
US2001/0014164(A1)	2001-08-01	Daniels et al.	Applicant
US2001/0027450(A1)	2001-10-01	Shinoda et al.	Applicant
US2001/0029532(A1)	2001-10-01	Kato et al.	Applicant
US2001/0042931(A1)	2001-11-01	Anderson et al.	Applicant
US2001/0044744(A1)	2001-11-01	Rhoads	Applicant
US2001/0044809(A1)	2001-11-01	Parasnis et al.	Applicant
US2001/0044901(A1)	2001-11-01	Grawrock	Applicant
US2001/0054152(A1)	2001-12-01	Nakao et al.	Examiner
US2001/0056550(A1)	2001-12-01	Lee	Examiner
US2002/0012443(A1)	2002-01-01	Rhoads et al.	Applicant
US2002/0019831(A1)	2002-02-01	Wade	Applicant
US2002/0046041(A1)	2002-04-01	Lang	Applicant
US2002/0052934(A1)	2002-05-01	Doherty	Applicant
US2002/0059364(A1)	2002-05-01	Coulthard et al.	Applicant
US2002/0069129(A1)	2002-06-01	Akutsu et al.	Applicant
US2002/0103801(A1)	2002-08-01	Lyons	Applicant
US2002/0138402(A1)	2002-09-01	Zacharia et al.	Applicant
US2002/0143885(A1)	2002-10-01	Ross	Applicant
US2002/0178381(A1)	2002-11-01	Lee et al.	Applicant
US2002/0180778(A1)	2002-12-01	Proudler	Applicant
US2002/0194483(A1)	2002-12-01	Wenocur et al.	Applicant
US2002/0198950(A1)	2002-12-01	Leeds	Applicant
US2002/0199120(A1)	2002-12-01	Schmidt	Applicant
US2003/0018585(A1)	2003-01-01	Butler et al.	Applicant
US2003/0023878(A1)	2003-01-01	Rosenberg et al.	Applicant
US2003/0055737(A1)	2003-03-01	Pope et al.	Applicant
US2003/0055962(A1)	2003-03-01	Freund et al.	Applicant
US2003/0088577(A1)	2003-05-01	Thurnhofer et al.	Applicant
US2003/0097591(A1)	2003-05-01	Pham et al.	Applicant
US2003/0158888(A1)	2003-08-01	Bjorklund et al.	Applicant
US2003/0172166(A1)	2003-09-01	Judge et al.	Applicant
US2003/0182421(A1)	2003-09-01	Faybishenko et al.	Applicant
US2003/0220912(A1)	2003-11-01	Fain et al.	Applicant
US2004/0006532(A1)	2004-01-01	Lawrence et al.	Applicant
US2004/0059705(A1)	2004-03-01	Wittke et al.	Applicant
US2004/0088369(A1)	2004-05-01	Yeager et al.	Applicant
US2004/0093506(A1)	2004-05-01	Grawrock et al.	Applicant
US2004/0107363(A1)	2004-06-01	Monteverde	Applicant
US2004/0122926(A1)	2004-06-01	Moore et al.	Applicant
US2004/0123117(A1)	2004-06-01	Berger	Applicant
US2004/0123157(A1)	2004-06-01	Alagna et al.	Applicant
US2004/0143753(A1)	2004-07-01	Hernacki et al.	Applicant
US2004/0148281(A1)	2004-07-01	Bates et al.	Applicant
US2004/0153414(A1)	2004-08-01	Khaishgi et al.	Applicant
US2004/0153512(A1)	2004-08-01	Friend	Applicant
US2004/0167980(A1)	2004-08-01	Doyle et al.	Applicant
US2004/0168121(A1)	2004-08-01	Matz	Applicant
US2004/0169678(A1)	2004-09-01	Oliver	Applicant
US2004/0199606(A1)	2004-10-01	Brown et al.	Applicant
US2004/0205173(A1)	2004-10-01	Hall	Applicant
US2004/0205354(A1)	2004-10-01	Gabriel et al.	Applicant
US2004/0210602(A1)	2004-10-01	Hillis et al.	Applicant
US2004/0250115(A1)	2004-12-01	Gemmel et al.	Applicant
US2005/0005111(A1)	2005-01-01	Brebner et al.	Applicant
US2005/0015506(A1)	2005-01-01	Padborg	Applicant
US2005/0022018(A1)	2005-01-01	Szor	Applicant
US2005/0033991(A1)	2005-02-01	Crane	Applicant
US2005/0044423(A1)	2005-02-01	Mellmer et al.	Applicant
US2005/0052998(A1)	2005-03-01	Oliver et al.	Applicant
US2005/0071684(A1)	2005-03-01	Sorkin et al.	Applicant
US2005/0076222(A1)	2005-04-01	Olkin et al.	Applicant
US2005/0091514(A1)	2005-04-01	Fukumoto et al.	Applicant
US2005/0114709(A1)	2005-05-01	Moore et al.	Applicant
US2005/0165680(A1)	2005-07-01	Keeling et al.	Applicant
US2005/0216300(A1)	2005-09-01	Appelman et al.	Applicant
US2005/0216454(A1)	2005-09-01	Diab et al.	Applicant
US2005/0235343(A1)	2005-10-01	Stephens	Applicant
US2005/0240576(A1)	2005-10-01	Piscitello et al.	Applicant
US2005/0251756(A1)	2005-11-01	Tamaki	Applicant
US2005/0256866(A1)	2005-11-01	Lu et al.	Applicant
US2006/0004713(A1)	2006-01-01	Korte et al.	Applicant
US2006/0009994(A1)	2006-01-01	Hogg et al.	Applicant
US2006/0015722(A1)	2006-01-01	Rowan et al.	Applicant
US2006/0041508(A1)	2006-02-01	Pham et al.	Applicant
US2006/0069618(A1)	2006-03-01	Milener et al.	Applicant
US2006/0095404(A1)	2006-05-01	Adelman et al.	Applicant
US2006/0095586(A1)	2006-05-01	Adelman et al.	Applicant
US2006/0106866(A1)	2006-05-01	Green et al.	Applicant
US2006/0106914(A1)	2006-05-01	Plow et al.	Applicant
US2006/0117389(A1)	2006-06-01	Pool	Applicant
US2006/0123478(A1)	2006-06-01	Rehfuss et al.	Applicant
US2006/0174343(A1)	2006-08-01	Duthie et al.	Applicant
US2006/0179157(A1)	2006-08-01	Huang	Applicant
US2006/0212925(A1)	2006-09-01	Shull et al.	Applicant
US2006/0218403(A1)	2006-09-01	Sauve et al.	Applicant
US2006/0235796(A1)	2006-10-01	Johnson et al.	Applicant
US2006/0239430(A1)	2006-10-01	Gue et al.	Applicant
US2006/0242026(A1)	2006-10-01	Crespo et al.	Applicant
US2006/0253458(A1)	2006-11-01	Dixon et al.	Applicant
US2006/0253578(A1)	2006-11-01	Dixon et al.	Applicant
US2006/0253579(A1)	2006-11-01	Dixon et al.	Applicant
US2006/0253580(A1)	2006-11-01	Dixon et al.	Applicant
US2006/0253581(A1)	2006-11-01	Dixon et al.	Applicant
US2006/0253582(A1)	2006-11-01	Dixon et al.	Applicant
US2006/0253583(A1)	2006-11-01	Dixon et al.	Applicant
US2006/0253584(A1)	2006-11-01	Dixon et al.	Applicant
US2006/0265417(A1)	2006-11-01	Amato et al.	Applicant
US2006/0282795(A1)	2006-12-01	Clark et al.	Applicant
US2007/0028291(A1)	2007-02-01	Brennan et al.	Examiner
US2007/0028304(A1)	2007-02-01	Brennan	Examiner
US2007/0039038(A1)	2007-02-01	Goodman et al.	Applicant
US2007/0074125(A1)	2007-03-01	Platt et al.	Applicant
US2007/0083929(A1)	2007-04-01	Sprosts et al.	Applicant
US2007/0088652(A1)	2007-04-01	Firmage et al.	Applicant
US2007/0118898(A1)	2007-05-01	Morgan et al.	Applicant
US2007/0130350(A1)	2007-06-01	Alperovitch et al.	Applicant
US2007/0203884(A1)	2007-08-01	Nichols et al.	Examiner
US2008/0028029(A1)	2008-01-01	Hart	Applicant
US2008/0109473(A1)	2008-05-01	Dixon et al.	Applicant
US2008/0114709(A1)	2008-05-01	Dixon et al.	Applicant
US2008/0134084(A1)	2008-06-01	Clark et al.	Applicant
US2008/0162225(A1)	2008-07-01	Malcolm	Applicant
US2008/0250159(A1)	2008-10-01	Wang et al.	Applicant
US2009/0089287(A1)	2009-04-01	Roberts et al.	Applicant
US2009/0258253(A1)	2009-10-01	Hinoue et al.	Applicant
US2009/0281905(A1)	2009-11-01	Walton	Applicant
US2010/0042931(A1)	2010-02-01	Dixon et al.	Applicant
US2012/0185942(A1)	2012-07-01	Dixon et al.	Applicant
US2012/0311705(A1)	2012-12-01	Dixon et al.	Applicant
US2013/0014020(A1)	2013-01-01	Dixon et al.	Applicant
WO99/49380	1999-09-01		Applicant
WO1/55873	2001-08-01		Applicant
WO1/55905	2001-08-01		Applicant
WO3/049403	2003-06-01		Applicant
WO3/079214	2003-09-01		Applicant
WO2004/061703	2004-07-01		Applicant
WO2005/010649	2005-02-01		Applicant
WO2005/033978	2005-04-01		Applicant
WO2005/043351	2005-05-01		Applicant
WO2005/043416	2005-05-01		Applicant
WO2005/043417	2005-05-01		Applicant
WO2006/020095	2006-02-01		Applicant

Non-Patent Literature (223)

Siteadvisor, http://www.siteadvisor.com/.Applicant
Office Action Summary from U.S. Appl. No. 11/905,330 mailed on Dec. 30, 2009.Applicant
Final Office Action Summary from U.S. Appl. No. 11/342,319 mailed on Jan. 22, 2010.Applicant
Office Action Summary from U.S. Appl. No. 11/342,250 mailed on Feb. 26, 2010.Applicant
Final Office Action Summary from U.S. Appl. No. 11/342,322 mailed on Mar. 1, 2010.Applicant
Final Office Action Summary from U.S. Appl. No. 11/837,067 mailed on Mar. 1, 2010.Applicant
Office Action Summary from U.S. Appl. No. 11/837,050 mailed on Sep. 2, 2009.Applicant
Final Office Action Summary from U.S. Appl. No. 11/342,318 mailed on Sep. 21, 2009.Applicant
Office Action Summary from U.S. Appl. No. 11/342,322 mailed on Oct. 16, 2009.Applicant
Office Action Summary from U.S. Appl. No. 11/342,297 mailed on Dec. 28, 2009.Applicant
Office Action Summary from U.S. Appl. No. 11/342,342 mailed on Jan. 12, 2010.Applicant
Office Action Summary from U.S. Appl. No. 11/342,343 mailed on Jan. 13, 2010.Applicant
Final Office Action Summary from U.S. Appl. No. 11/342,250 mailed on Dec. 2, 2009.Applicant
U.S. Appl. No. 60/588,570, filed Jul. 16, 2004.Applicant
U.S. Appl. No. 60/633,464, filed Dec. 6, 2004.Applicant
“Advertisement,” Dictionary.com, http://dictionary.reference.com/browse/advertisement, Feb. 11, 2010.Applicant
Notice of Allowance from U.S. Appl. No. 11/905,330 mailed on Apr. 30, 2010.Applicant
Final Office Action Summary from U.S. Appl. No. 11/837,050 mailed on Apr. 7, 2010.Applicant
U.S. Appl. No. 11/281,963, filed Nov. 16, 2005.Applicant
Non-Final Office Action Summary from U.S. Appl. No. 11/281,963 mailed on Nov. 13, 2007.Applicant
Non-Final Office Summary from U.S. Appl. No. 11/281,963 mailed on Dec. 2, 2008.Applicant
Final Office Action Summary from U.S. Appl. No. 11/281,963 mailed on Jun. 10, 2008.Applicant
Non-Final Office Summary from U.S. Appl. No. 11/281,963 mailed on Jun. 2, 2009.Applicant
Office Action Summary from U.S. Appl. No. 11/281,963 mailed on Mar. 8, 2010.Applicant
U.S. Appl. No. 11/852,948, filed Sep. 10, 2007.Applicant
Non-Final Office Action Summary from U.S. Appl. No. 11/852,948 mailed on Oct. 7, 2009.Applicant
Non-Final Office Action Summary from U.S. Appl. No. 11/342,297 mailed on Jul. 9, 2008.Applicant
Final Office Action Summary from U.S. Appl. No. 11/342,297 mailed on Mar. 17, 2009.Applicant
Notice of Allowance from U.S. Appl. No. 11/342,297 mailed on May 26, 2010.Applicant
Non-Final Office Action Summary from U.S. Appl. No. 11/342,319 mailed on Sep. 17, 2008.Applicant
Final Office Action Summary from U.S. Appl. No. 11/342,319 mailed on Mar. 16, 2009.Applicant
Non-Final Office Action Summary from U.S. Appl. No. 11/342,319 mailed on Aug. 25, 2009.Applicant
Advisory Action Summary from U.S. Appl. No. 11/342,319 mailed on Apr. 21, 2010.Applicant
Final Office Action Summary from U.S. Appl. No. 11/342,250 mailed on Dec. 16, 2008.Applicant
Advisory Action Summary from U.S. Appl. No. 11/342,250 mailed on Feb. 25, 2009.Applicant
Non-Final Office Action Summary from U.S. Appl. No. 11/342,250 mailed on May 28, 2009.Applicant
Non-Final Office Action Summary from U.S. Appl. No. 11/342,250 mailed on Jun. 20, 2008.Applicant
Final Office Action Summary from U.S. Appl. No. 11/342,343 mailed on Jul. 14, 2010.Applicant
Final Office Action Summary from U.S. Appl. No. 11/342,318 mailed on Aug. 18, 2008.Applicant
Non-Final Office Action Summary from U.S. Appl. No. 11/342,318 mailed on Mar. 26, 2009.Applicant
Non-Final Office Action Summary from U.S. Appl. No. 11/342,318 mailed on Mar. 27, 2008.Applicant
Non-Final Office Action Summary from U.S. Appl. No. 11/342,342 mailed on Jan. 23, 2009.Applicant
Non-Final Office Action Summary from U.S. Appl. No. 11/342,342 mailed on Jan. 24, 2008.Applicant
Advisory Action Summary from U.S. Appl. No. 11/342,342 mailed on Nov. 12, 2008.Applicant
Final Office Action Summary from U.S. Appl. No. 11/342,342 mailed on Jul. 22, 2008.Applicant
Final Office Action Summary from U.S. Appl. No. 11/342,342 mailed on Aug. 20, 2009.Applicant
Non-Final Office Action Summary from U.S. Appl. No. 11/342,320 mailed on May 5, 2008.Applicant
Final Office Action Summary from U.S. Appl. No. 11/342,320 mailed on Dec. 11, 2008.Applicant
Notice of Allowance from U.S. Appl. No. 11/342,320 mailed on Mar. 4, 2009.Applicant
Notice of Allowability from U.S. Appl. No. 11/342,320 mailed on Apr. 27, 2009.Applicant
Non-Final Office Action Summary from U.S. Appl. No. 11/342,322 mailed on Sep. 18, 2008.Applicant
Final Office Action Summary from U.S. Appl. No. 11/342,322 mailed on May 15, 2009.Applicant
Advisory Action Summary from U.S. Appl. No. 11/342,322 mailed on Aug. 10, 2009.Applicant
Non-Final Office Action Summary from U.S. Appl. No. 11/837,067 mailed on Jun. 12, 2009.Applicant
Final Office Action Summary from U.S. Appl. No. 11/837,067 mailed on Dec. 31, 2008.Applicant
Non-Final Office Action Summary from U.S. Appl. No. 11/837,067 mailed on Jul. 12, 2010.Applicant
Non-Final Office Action Summary from U.S. Appl. No. 11/837,067 mailed on Jun. 17, 2008.Applicant
U.S. Appl. No. 11/342,250, filed Jan. 26, 2006.Applicant
U.S. Appl. No. 11/837,050, filed Aug. 10, 2007.Applicant
U.S. Appl. No. 11/342,343, filed Jan. 26, 2006.Applicant
U.S. Appl. No. 11/342,297, filed Jan. 26, 2006.Applicant
U.S. Appl. No. 11/342,318, filed Jan. 26, 2006.Applicant
U.S. Appl. No. 11/342,319, filed Jan. 26, 2006.Applicant
U.S. Appl. No. 11/342,320, filed Jan. 26, 2006.Applicant
U.S. Appl. No. 11/342,322, filed Jan. 26, 2006.Applicant
U.S. Appl. No. 11/342,342, filed Jan. 26, 2006.Applicant
U.S. Appl. No. 12/502,158, filed Jul. 13, 2009.Applicant
U.S. Appl. No. 11/905,330, filed Sep. 28, 2007.Applicant
Non-Final Office Action Summary from U.S. Appl. No. 11/342,322 mailed on Sep. 22, 2010.Applicant
Non-Final Office Action Summary from U.S. Appl. No. 11/342,319 mailed on Sep. 13, 2010.Applicant
Final Office Action Summary from U.S. Appl. No. 11/342,342 mailed on Jul. 26, 2010.Applicant
Non-Final Office Action Summary from U.S. Appl. No. 11/837,050 mailed on Aug. 18, 2010.Applicant
Final Office Action Summary from U.S. Appl. No. 11/342,250 mailed on Sep. 17, 2010.Applicant
Final Office Action Summary from U.S. Appl. No. 11/852,948 mailed on May 26, 2010.Applicant
Notice of Allowance form U.S. Appl. No. 11/342,318, dated Feb. 23, 2010.Applicant
Bowman, W., The Uniform Computer Information Transactions Act: A Well Built Fence or Barbed Wire Around the Intellectual Commons?, LBJ Journal of Public Affairs, Spring 2001, vol. XIII, pp. 80-91, USA; retrieved form http://uts.cc.utexas.edu/˜lbjjpa/2001/bowman.pdf on Feb. 16, 2011.Applicant
Dean et al., DIMACS Workshop on theft in E-Commerce: Content, Identity, and Service, Apr. 14-15, 2005, pp. 1-7, DIMACS Center, CoRE Building, Rutgers University, Piscataway, NJ, USA; retrieved from http://dimacs.rutgers.edu/Workshops/Intellectual/abstracts.html on Feb. 16, 2011.Applicant
International Search Report and Written Opinion from International Application No. PCT/US06/17335, mailed Nov. 29, 2007.Applicant
International Preliminary Report on Patentability from International Application No. PCT/US06/17335, dated Nov. 6, 2007.Applicant
International Search Report and Written Opinion from International Application No. PCT/US06/17333, mailed Aug. 18, 2008.Applicant
International Preliminary Report on Patentability from International Application No. PCT/US2006/017333, dated Mar. 17, 2009.Applicant
International Search Report and Written Opinion from International Application No. PCT/US06/17334, mailed Sep. 25, 2007.Applicant
International Preliminary Report on Patentability from International Application No. PCT/US2006/017334, dated Nov. 6, 2007.Applicant
Response to Non-Final Action dated Apr. 15, 2011 in U.S. Appl. No. 11/342,250 filed on Jul. 15, 2011.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/837,050 filed on Jul. 12, 2011.Applicant
Non-Final Office Action in U.S. Appl. No. 11/837,067 mailed on Jun. 23, 2011.Applicant
Response to Non-Final Office Action dated Apr. 14, 2011 in U.S. Appl. No. 12/502,158 filed on Jul. 14, 2011.Applicant
Response to Final Office Action dated May 15, 2009 in U.S. Appl. No. 11/342,322 filed on Jul. 15, 200.Applicant
Non-Final Office Action in U.S. Appl. No. 11/342,322 mailed on Sep. 2, 2011.Applicant
Non-Final Office Action in U.S. Appl. No. 11/342,319 mailed on Sep. 7, 2011.Applicant
Response to Non-Final Office Action dated Jun. 9, 2011 in U.S. Appl. No. 11/342,343 filed on Sep. 9, 2011.Applicant
Finjan SecureBrowsing™,“Browse fearlessly,” Finjan, Inc. (1996-2007), 2 pages.Applicant
Friendster, Inc. “Welcome to Friendster,” www.friendster.com, Copyright 2002-2005, (2 pages).Applicant
“How PGP works,” copyright 1990-1999 Networks Associates, Inc., available online at http://www.pgpi.org/doc/pgpintro/.Applicant
Response to Non-Final Office Action dated Nov. 13, 2007 in U.S. Appl. No. 11/281,963 filed on Feb. 13, 2008.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/281,963 filed on Sep. 17, 2008.Applicant
Response to Non-Final Office Action mailed Dec. 2, 2008 in U.S. Appl. No. 11/281,963 filed on Mar. 2, 2009.Applicant
Response to Non-Final Office Action dated Jun. 2, 2009 in U.S. Appl. No. 11/281,963 filed on Sep. 2, 2009.Applicant
Notice of Appeal in U.S. Appl. No. 11/281,963 filed on Jul. 8, 2010.Applicant
Appeal Brief in U.S. Appl. No. 11/281,963 filed on Feb. 8, 2011.Applicant
Examiner's Answer to Appellant's Appeal Brief dated Feb. 8, 2011 in U.S. Appl. No. 11/281,963 mailed on Apr. 28, 2011.Applicant
Notice of Appeal in U.S. Appl. No. 11/852,948 filed on Oct. 26, 2010.Applicant
Appeal Brief in U.S. Appl. No. 11/852,948 filed on Feb. 23, 2011.Applicant
Examiner's Answer to Appellant's Feb. 23, 2011 Appeal Brief in U.S. Appl. No. 11/852,948 mailed on May 13, 2011.Applicant
Response to Final Office Action dated Dec. 16, 2008 in U.S. Appl. No. 11/342,250 filed on Feb. 17, 2009.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,250 filed on Mar. 16, 2009.Applicant
Response to Non-Final Office Action dated May 28, 2009 in U.S. Appl. No. 11/342,250 filed on Aug. 28, 2009.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,250 filed on Feb. 2, 2010.Applicant
Non-Final Office Action in U.S. Appl. No. 11/342,250 mailed on Feb. 26, 2010.Applicant
Response to Non-Final Office Action dated Feb. 26, 2010 in U.S. Appl. No. 11/342,250 filed on Jun. 28, 2010.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,250 filed on Feb. 17, 2011.Applicant
Non-Final Office Action in U.S. Appl. No. 11/342,250 mailed on Apr. 15, 2011.Applicant
Response to Non-Final Office Action dated Sep. 2, 2009 in U.S. Appl. No. 11/837,050 filed on Jan. 4, 2010.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/837,050 filed on Jul. 7, 2010.Applicant
Response to Non-Final Office Action dated Aug. 18, 2010 in U.S. Appl. No. 11/837,050 filed on Feb. 28, 2011.Applicant
Final Office Action in U.S. Appl. No. 11/837,050 mailed on May 12, 2011.Applicant
U.S. Appl. No. 11/837,067, filed Aug. 10, 2007.Applicant
Response to Non-Final Office Action dated Jun. 17, 2008 in U.S. Appl. No. 11/837,067 filed on Sep. 17, 2008.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/837,067 filed on Mar. 30, 2009.Applicant
Response to Non-Final Office Action dated Jun. 12, 2009 in U.S. Appl. No. 11/837,067 filed on Nov. 12, 2009.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/837,067 filed on Jun. 1, 2010.Applicant
Response to Non-Final Office Action dated Jul. 12, 2010 in U.S. Appl. No. 11/837,067 filed on Jan. 12, 2011.Applicant
Final Office Action in U.S. Appl. No. 11/837,067 mailed on Apr. 1, 2011.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/837,067 filed on Jun. 1, 2011.Applicant
Response to Non-Final Office Action dated May 5, 2008 in U.S. Appl. No. 11/342,320 filed on Sep. 5, 2008.Applicant
Response to Final Office Action dated Dec. 11, 2008 in U.S. Appl. No. 11/342,320 filed on Feb. 11, 2009.Applicant
312 Amendment in U.S. Appl. No. 11/342,320 filed on Jun. 4, 2009.Applicant
Non-Final Office Action in U.S. Appl. No. 12/502,158 mailed on Apr. 14, 2011.Applicant
Response to Non-Final Office Action dated Mar. 27, 2008 in U.S. Appl. No. 11/342,318 filed on May 22, 2008.Applicant
Pre-Brief Conference Request and Notice of Appeal in U.S. Appl. No. 11/342,318 filed on Nov. 18, 2008.Applicant
Pre-Brief Conference Decision in U.S. Appl. No. 11/342,318 mailed on Dec. 11, 2008.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,318 filed on Feb. 18, 2009.Applicant
Response to Non-Final Office Action dated Mar. 26, 2009 in U.S. Appl. No. 11/342,318 filed on Jun. 26, 2009.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,318 filed on Jan. 21, 2010.Applicant
Response to Non-Final Office Action dated Jan. 24, 2008 in U.S. Appl. No. 11/342,342 filed on Apr. 10, 2008.Applicant
Response to Final Office Action dated Jul. 22, 2008 in U.S. Appl. No. 11/342,342 filed on Sep. 17, 2008.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,342 filed on Nov. 24, 2008.Applicant
Response to Non-Final Office Action dated Jan. 23, 2009 in U.S. Appl. No. 11/342,342 filed on May 26, 2009.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/34,342 filed on Dec. 21, 2009.Applicant
Response to Non-Final Office Action dated Jan. 12, 2010 in U.S. Appl. No. 11/342,342 filed on May 12, 2010.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,342 filed on Jan. 26, 2011.Applicant
Response to Non-Final Office Action dated Sep. 18, 2008 in U.S. Appl. No. 11/342,322 filed on Dec. 18, 2008.Applicant
Notice to Applicant regarding Non-Compliant Amendment in U.S. Appl. No. 11/342,322 mailed on Jan. 16, 2009.Applicant
Response to Notice dated Jan. 16, 2009 in U.S. Appl. No. 11/342,322 filed on Feb. 17, 2009.Applicant
Response to Final Office Action dated May 15, 2009 in U.S. Appl. No. 11/342,322 filed on Jul. 15, 2009.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,322 filed on Aug. 12, 2009.Applicant
Response to Non-Final Office Action dated Oct. 16, 2009 in U.S. Appl. No. 11/342,322 filed on Jan. 19, 2010.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,322 filed on Jun. 1, 2010.Applicant
Response to Non-Final Office Action dated Sep. 22, 2010 in U.S. Appl. No. 11/342,322 filed on Feb. 22, 2011.Applicant
Final Office Action in U.S. Appl. No. 11/342,322 mailed on Mar. 21, 2011.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,322 filed on May 23, 2011.Applicant
Response to Non-Final Office Action dated Jul. 9, 2008 in U.S. Appl. No. 11/342,297 filed on Dec. 9, 2008.Applicant
Notice of Appeal in U.S. Appl. No. 11/342,297 filed on Jun. 17, 2009.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,297 filed on Nov. 17, 2009.Applicant
Response to Non-Final Office Action dated Dec. 28, 2009 in U.S. Appl. No. 11/342,297 filed on Apr. 28, 2010.Applicant
Non-Final Office Action in U.S. Appl. No. 11/342,297 mailed on Sep. 24, 2010.Applicant
Response to Non-Final Office Action dated Sep. 17, 2008 in U.S. Appl. No. 11/342,319 filed on Dec. 17, 2008.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,319 filed on Jun. 16, 2009.Applicant
Response to Non-Final Office Action dated Aug. 25, 2009 in U.S. Appl. No. 11/342,319 filed on Dec. 28, 2009.Applicant
Response to Final Office Action dated Jan. 22, 2010 in U.S. Appl. No. 11/342,319 filed on Mar. 22, 2010.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,319 filed on Apr. 22, 2010.Applicant
Notice of Appeal in U.S. Appl. No. 11/342,319 filed on Feb. 23, 2011.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,319 filed on Apr. 25, 2011.Applicant
Response to Non-Final Office Action dated Jan. 13, 2010 in U.S. Appl. No. 11/342,343 filed on May 13, 2010.Applicant
Notice to Applicant regarding Non-Responsive/Non-Compliant Amendment in U.S. Appl. No. 11/342,343 mailed on May 19, 2010.Applicant
Response to Notice dated May 19, 2010 filed in U.S. Appl. No. 11/342,343 filed on Jun. 11, 2010.Applicant
Non-Final Office Action in U.S. Appl. No. 11/342,343 mailed on Jun. 9, 2011.Applicant
Response to Non-Final Office Action dated Dec. 30, 2009 in U.S. Appl. No. 11/905,330, filed Mar. 30, 2010.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,250 filed on Nov. 30, 2012.Applicant
Notice of Allowance in U.S. Appl. No. 11/837,050 mailed on Nov. 27, 2012.Applicant
Response to Non-Final Office Action dated Jul. 24, 2012 in U.S. Appl. No. 11/342,322 filed on Oct. 24, 2012.Applicant
Response to Non-Final Office Action dated Jul. 24, 2012 in U.S. Appl. No. 11/342,319 filed on Oct. 24, 2012.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,250 filed on Feb. 8, 2012.Applicant
Non-Final Office Action in U.S. Appl. No. 11/342,250 mailed on Feb. 23, 2012.Applicant
Response to Non-Final Office Action dated Nov. 25, 2011 in U.S. Appl. No. 11/837,050 filed on Feb. 24, 2012.Applicant
Final Office Action in U.S. Appl. No. 11/837,050 mailed on Mar. 19, 2012.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/837,067 filed on Jan. 17, 2012.Applicant
Notice of Allowance in U.S. Appl. No. 11/837,067 mailed on Mar. 7, 2012.Applicant
Request for Continued Examination in U.S. Appl. No. 11/837,067 filed on Mar. 23, 2012.Applicant
U.S. Appl. No. 13/431,873, filed Mar. 27, 2012, entitled System Method, and Computer Program Product for Presenting an Indicia of Risk Associated with Search Results within a Graphical User Interface, Inventors, Christopher John Dixon et al.Applicant
Response to Non-Final Office Action dated Nov. 28, 2011 in U.S. Appl. No. 12/502,158 filed on Feb. 27, 2012.Applicant
Response to Non-Final Office Action dated Sep. 22, 2011 in U.S. Appl. No. 11/342,342 filed on Dec. 22, 2011.Applicant
Non-Final Office Action in U.S. Appl. No. 11/342,342 mailed on Mar. 2, 2012.Applicant
Final Office Action in U.S. Appl. No. 11/342,322 mailed on Jan. 26, 2012.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,322 filed on Mar. 26, 2012.Applicant
Response to Non-Final Office Action dated Sep. 7, 2011 in U.S. Appl. No. 11/342,319 filed on Dec. 7, 2011.Applicant
Final Office Action in U.S. Appl. No. 11/342,319 mailed on Jan. 25, 2012.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,319 filed on Mar. 26, 2012.Applicant
Response to Non-Final Office Action dated Feb. 23, 2012 in U.S. Appl. No. 11/342,250 filed on May 14, 2012.Applicant
Final Office Action in U.S. Appl. No. 11/342,250 mailed on Aug. 30, 2012.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/837,050 filed on May 10, 2012.Applicant
Notice of Allowance in U.S. Appl. No. 11/837,050 mailed on Jun. 6, 2012.Applicant
Request for Continued Examination in U.S. Appl. No. 11/837,050 filed on Sep. 6, 2012.Applicant
U.S. Appl. No. 13/568,085, filed Aug. 6, 2012 and entitled “System, Method, and Computer Program Product for Presenting an Indica of Risk Reflecting an Analysis Associated with Search Results within a Graphical User Interface,” Christopher John Dixon et al. inventors.Applicant
Notice of Allowance in U.S. Appl. No. 11/837,067 mailed on Jun. 22, 2012.Applicant
Notice of Allowance in U.S. Appl. No. 12/502,158 mailed on May 30, 2012.Applicant
Request for Continued Examination in U.S. Appl. No. 12/502,158 filed on Aug. 30, 2012.Applicant
Notice of Allowance in U.S. Appl. No. 12/502,158 mailed on Oct. 9, 2012.Applicant
U.S. Appl. No. 13/621,037, filed Sep. 15, 2012 entitled “Indicating Website Reputations during Website Manipulation of User Information”, Inventors Christopher John Dixon et al.Applicant
Response to Non-Final Office Action dated Mar. 2, 2012 in U.S. Appl. No. 11/342,342 filed on Jun. 4, 2012.Applicant
Final Office Action in U.S. Appl. No. 11/342,342 mailed on Jul. 2, 2012.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,342 filed on Oct. 2, 2012.Applicant
Non-Final Office Action in U.S. Appl. No. 11/342,322 mailed on Jul. 24, 2012.Applicant
Non-Final Office Action in U.S. Appl. No. 11/342,319 mailed on Jul. 24, 2012.Applicant
Final Office Action in U.S. Appl. No. 11/342,250 mailed on Nov. 8, 2011.Applicant
Non-Final Office Action in U.S. Appl. No. 11/837,050 mailed on Nov. 25, 2011.Applicant
Response to Non-Final Office Action dated Jun. 23, 2011 in U.S. Appl. No. 11/837,067 filed on Sep. 23, 2011.Applicant
Final Office Action in U.S. Appl. No. 11/837,067 mailed on Nov. 17, 2011.Applicant
Notice of Allowance in U.S. Appl. No. 12/502,158 mailed on Sep. 27, 2011.Applicant
Request for Continued Examination in U.S. Appl. No. 12/502,158 filed on Nov. 7, 2011.Applicant
Non-Final Office Action in U.S. Appl. No. 12/502,158 mailed on Nov. 28, 2011.Applicant
Non-Final Office Action in U.S. Appl. No. 11/342,342 mailed on Sep. 22, 2011.Applicant
Response to Sep. 2, 2011 Non-Final Office Action in U.S. Appl. No. 11/342,322 filed on Dec. 1, 2011.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,343 filed on Jan. 14, 2011.Applicant
Final Office Action in U.S. Appl. No. 11/342,343 mailed on Sep. 26, 2011.Applicant
Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,343 filed on Nov. 28, 2011.Applicant
Examiner Interview Summary in U.S. Appl. No. 11/342,343 mailed on Dec. 5, 2011.Applicant
Final Office Action in U.S. Appl. No. 11/342,319 mailed on Jan. 4, 2013.Applicant
Issue Notification in U.S. Appl. No. 11/837,050 mailed Apr. 3, 2013—Patent No. 8429545.Applicant
Non-Final Office Action in U.S. Appl. No. 13/621,037 mailed Dec. 31, 2012.Applicant
Notice of Publication in U.S. Appl. No. 13/621,037.Applicant
Notice of Allowance in U.S. Appl. No. 11/342,250 mailed on Jan. 10, 2013.Applicant
Final Office Action in U.S. Appl. No. 11/342,322 mailed on Jan. 4, 2013.Applicant

Abstract

Description

Field of the Invention

[0001] The present invention relates to security applications, and more particularly to reputation rating systems.

Background

[0005] There is thus a need for overcoming these and/or other problems associated with the prior art.

Summary

Brief Description of the Drawings

[0007] FIG. 1 illustrates a network architecture, in accordance with one embodiment.

[0008] FIG. 2 shows a representative hardware environment that may be associated with the server computers and/or client computers of FIG. 1, in accordance with one embodiment.

[0009] FIG. 3 shows a method for obtaining a reputation associated with a file, in accordance with one embodiment.

[0010] FIG. 4 shows a method for generating a reputation database in an automated manner, in accordance with one embodiment.

[0011] FIG. 5 shows a method for using a reputation database, in accordance with one embodiment.

[0012] FIG. 6 shows a method for generating a reputation database in a distributed manner, in accordance with another embodiment.

Detailed Description

[0036]

	TABLE 1

		File name_l	Good_Reputation
		File name_2	Bad_Reputation
		File name_3	Good_Reputation
		File name_4	Bad_Reputation
		File name_5	Good_Reputation

Claims

What is claimed is:

1. A method, comprising:

identifying a file associated with a first computer;

2. The method of claim 1, wherein the overall reputation associated with the file is determined automatically by inspecting a plurality of files associated with a plurality of sites on a network.

3. The method of claim 2, wherein a plurality of the reputations associated with the plurality of files are stored in a database at the second computer, from which the overall reputation is obtained.

5. The method of claim 1, wherein information on the overall reputation associated with the file is identified at a third computer during use of the file.

6. The method of claim 1, wherein the overall reputation is obtained by looking up the overall reputation in a central database.

7. A non-transitory computer-readable medium, comprising one or more instructions that when executed on a processor configure the processor to:

identify a file associated with a first computer;

8. The computer-readable medium of claim 7, wherein the reputation includes at least one of a good reputation and a bad reputation.

9. The computer-readable medium of claim 8, wherein the policy is set by an administrator and indicates that the access to the file with the bad reputation is prohibited based on the policy.

11. The computer-readable medium of claim 7, wherein the policy further indicates that the file should be emulated to determine if any undesirable characteristic is exhibited by the file.

15. The computer-readable medium of claim 7, wherein information on the overall reputation associated with the file is identified at a third computer during use of the file.

16. The computer-readable medium of claim 7, wherein the file is identified in response to an attempt to download the file over a network.

17. The computer-readable medium of claim 7, wherein the overall reputation is obtained by looking up the overall reputation in a central database.

18. An apparatus, comprising:

a processor operable to execute computer program instructions; and

a memory coupled to the processor and operable to store computer program instructions executable by the processor such that the system is configured to:

identify a file associated with a first computer;

22. A system, comprising:

a first computer configured to identify a file associated with the first computer; and

23. The system of claim 22, wherein the overall reputation associated with the file is determined automatically by inspecting a plurality of files associated with a plurality of sites on a network.

Patent Citations (198)

Patent	Date	Inventor	Cited By
US5274819(A)	1993-12-01	Blomfield-Brown	Applicant
US5742763(A)	1998-04-01	Jones	Applicant
US5870559(A)	1999-02-01	Leshem et al.	Applicant
US5892904(A)	1999-04-01	Atkinson et al.	Applicant
US5949419(A)	1999-09-01	Domine et al.	Applicant
US5978917(A)	1999-11-01	Chi	Examiner
US5987610(A)	1999-11-01	Franczek et al.	Applicant
US6018724(A)	2000-01-01	Arent	Applicant
US6065055(A)	2000-05-01	Hughes et al.	Applicant
US6073142(A)	2000-06-01	Geiger et al.	Applicant
US6219786(B1)	2001-04-01	Cunningham et al.	Applicant
US6285999(B1)	2001-09-01	Page	Applicant
US6321334(B1)	2001-11-01	Jerger et al.	Applicant
US6356937(B1)	2002-03-01	Montville et al.	Applicant
US6366912(B1)	2002-04-01	Wallent et al.	Applicant
US6367012(B1)	2002-04-01	Atkinson et al.	Applicant
US6460050(B1)	2002-10-01	Pace et al.	Applicant
US6539430(B1)	2003-03-01	Humes	Applicant
US6606659(B1)	2003-08-01	Hegli et al.	Applicant
US6647400(B1)	2003-11-01	Moran	Applicant
US6658394(B1)	2003-12-01	Khaishgi et al.	Applicant
US6708205(B2)	2004-03-01	Sheldon et al.	Applicant
US6742128(B1)	2004-05-01	Joiner	Applicant
US6748422(B2)	2004-06-01	Morin et al.	Applicant
US6772345(B1)	2004-08-01	Shetty	Applicant
US6785732(B1)	2004-08-01	Bates et al.	Applicant
US6826697(B1)	2004-11-01	Moran	Applicant
US6856963(B1)	2005-02-01	Hurwitz	Applicant
US6886102(B1)	2005-04-01	Lyle	Applicant
US6907533(B2)	2005-06-01	Sorkin et al.	Applicant
US6938003(B2)	2005-08-01	Harpale	Applicant
US7003734(B1)	2006-02-01	Gardner et al.	Applicant
US7024630(B2)	2006-04-01	Himmel et al.	Applicant
US7084760(B2)	2006-08-01	Himberger et al.	Applicant
US7096493(B1)	2006-08-01	Liu	Examiner
US7100122(B2)	2006-08-01	Blaschke et al.	Applicant
US7114177(B2)	2006-09-01	Rosenberg et al.	Applicant
US7136875(B2)	2006-11-01	Anderson et al.	Applicant
US7143139(B2)	2006-11-01	Burbeck et al.	Applicant
US7171470(B2)	2007-01-01	Doyle et al.	Applicant
US7207480(B1)	2007-04-01	Geddes	Applicant
US7216360(B2)	2007-05-01	Nakao et al.	Examiner
US7231395(B2)	2007-06-01	Fain et al.	Applicant
US7254573(B2)	2007-08-01	Burke	Applicant
US7257549(B2)	2007-08-01	Karaoguz et al.	Applicant
US7313691(B2)	2007-12-01	Bantz et al.	Applicant
US7370188(B2)	2008-05-01	Rothman et al.	Applicant
US7380267(B2)	2008-05-01	Arai et al.	Examiner
US7506155(B1)	2009-03-01	Stewart et al.	Applicant
US7562304(B2)	2009-07-01	Dixon et al.	Applicant
US7603718(B2)	2009-10-01	Rounthwaite et al.	Applicant
US7634810(B2)	2009-12-01	Goodman et al.	Applicant
US7694135(B2)	2010-04-01	Rowan et al.	Applicant
US7756930(B2)	2010-07-01	Brahms et al.	Applicant
US7765481(B2)	2010-07-01	Dixon et al.	Applicant
US7809650(B2)	2010-10-01	Bruesewitz et al.	Applicant
US7822620(B2)	2010-10-01	Dixon et al.	Applicant
US7831611(B2)	2010-11-01	Roberts et al.	Applicant
US7831915(B2)	2010-11-01	Averbuch et al.	Applicant
US8065720(B1)	2011-11-01	Ebrahimi et al.	Applicant
US8296664(B2)	2012-10-01	Dixon et al.	Applicant
US8321791(B2)	2012-11-01	Dixon et al.	Applicant
US8429545(B2)	2013-04-01	Dixon et al.	Applicant
US8438499(B2)	2013-05-01	Dixon et al.	Applicant
US2001/0007098(A1)	2001-07-01	Hinrichs et al.	Applicant
US2001/0011284(A1)	2001-08-01	Humpleman et al.	Applicant
US2001/0014164(A1)	2001-08-01	Daniels et al.	Applicant
US2001/0027450(A1)	2001-10-01	Shinoda et al.	Applicant
US2001/0029532(A1)	2001-10-01	Kato et al.	Applicant
US2001/0042931(A1)	2001-11-01	Anderson et al.	Applicant
US2001/0044744(A1)	2001-11-01	Rhoads	Applicant
US2001/0044809(A1)	2001-11-01	Parasnis et al.	Applicant
US2001/0044901(A1)	2001-11-01	Grawrock	Applicant
US2001/0054152(A1)	2001-12-01	Nakao et al.	Examiner
US2001/0056550(A1)	2001-12-01	Lee	Examiner
US2002/0012443(A1)	2002-01-01	Rhoads et al.	Applicant
US2002/0019831(A1)	2002-02-01	Wade	Applicant
US2002/0046041(A1)	2002-04-01	Lang	Applicant
US2002/0052934(A1)	2002-05-01	Doherty	Applicant
US2002/0059364(A1)	2002-05-01	Coulthard et al.	Applicant
US2002/0069129(A1)	2002-06-01	Akutsu et al.	Applicant
US2002/0103801(A1)	2002-08-01	Lyons	Applicant
US2002/0138402(A1)	2002-09-01	Zacharia et al.	Applicant
US2002/0143885(A1)	2002-10-01	Ross	Applicant
US2002/0178381(A1)	2002-11-01	Lee et al.	Applicant
US2002/0180778(A1)	2002-12-01	Proudler	Applicant
US2002/0194483(A1)	2002-12-01	Wenocur et al.	Applicant
US2002/0198950(A1)	2002-12-01	Leeds	Applicant
US2002/0199120(A1)	2002-12-01	Schmidt	Applicant
US2003/0018585(A1)	2003-01-01	Butler et al.	Applicant
US2003/0023878(A1)	2003-01-01	Rosenberg et al.	Applicant
US2003/0055737(A1)	2003-03-01	Pope et al.	Applicant
US2003/0055962(A1)	2003-03-01	Freund et al.	Applicant
US2003/0088577(A1)	2003-05-01	Thurnhofer et al.	Applicant
US2003/0097591(A1)	2003-05-01	Pham et al.	Applicant
US2003/0158888(A1)	2003-08-01	Bjorklund et al.	Applicant
US2003/0172166(A1)	2003-09-01	Judge et al.	Applicant
US2003/0182421(A1)	2003-09-01	Faybishenko et al.	Applicant
US2003/0220912(A1)	2003-11-01	Fain et al.	Applicant
US2004/0006532(A1)	2004-01-01	Lawrence et al.	Applicant
US2004/0059705(A1)	2004-03-01	Wittke et al.	Applicant
US2004/0088369(A1)	2004-05-01	Yeager et al.	Applicant
US2004/0093506(A1)	2004-05-01	Grawrock et al.	Applicant
US2004/0107363(A1)	2004-06-01	Monteverde	Applicant
US2004/0122926(A1)	2004-06-01	Moore et al.	Applicant
US2004/0123117(A1)	2004-06-01	Berger	Applicant
US2004/0123157(A1)	2004-06-01	Alagna et al.	Applicant
US2004/0143753(A1)	2004-07-01	Hernacki et al.	Applicant
US2004/0148281(A1)	2004-07-01	Bates et al.	Applicant
US2004/0153414(A1)	2004-08-01	Khaishgi et al.	Applicant
US2004/0153512(A1)	2004-08-01	Friend	Applicant
US2004/0167980(A1)	2004-08-01	Doyle et al.	Applicant
US2004/0168121(A1)	2004-08-01	Matz	Applicant
US2004/0169678(A1)	2004-09-01	Oliver	Applicant
US2004/0199606(A1)	2004-10-01	Brown et al.	Applicant
US2004/0205173(A1)	2004-10-01	Hall	Applicant
US2004/0205354(A1)	2004-10-01	Gabriel et al.	Applicant
US2004/0210602(A1)	2004-10-01	Hillis et al.	Applicant
US2004/0250115(A1)	2004-12-01	Gemmel et al.	Applicant
US2005/0005111(A1)	2005-01-01	Brebner et al.	Applicant
US2005/0015506(A1)	2005-01-01	Padborg	Applicant
US2005/0022018(A1)	2005-01-01	Szor	Applicant
US2005/0033991(A1)	2005-02-01	Crane	Applicant
US2005/0044423(A1)	2005-02-01	Mellmer et al.	Applicant
US2005/0052998(A1)	2005-03-01	Oliver et al.	Applicant
US2005/0071684(A1)	2005-03-01	Sorkin et al.	Applicant
US2005/0076222(A1)	2005-04-01	Olkin et al.	Applicant
US2005/0091514(A1)	2005-04-01	Fukumoto et al.	Applicant
US2005/0114709(A1)	2005-05-01	Moore et al.	Applicant
US2005/0165680(A1)	2005-07-01	Keeling et al.	Applicant
US2005/0216300(A1)	2005-09-01	Appelman et al.	Applicant
US2005/0216454(A1)	2005-09-01	Diab et al.	Applicant
US2005/0235343(A1)	2005-10-01	Stephens	Applicant
US2005/0240576(A1)	2005-10-01	Piscitello et al.	Applicant
US2005/0251756(A1)	2005-11-01	Tamaki	Applicant
US2005/0256866(A1)	2005-11-01	Lu et al.	Applicant
US2006/0004713(A1)	2006-01-01	Korte et al.	Applicant
US2006/0009994(A1)	2006-01-01	Hogg et al.	Applicant
US2006/0015722(A1)	2006-01-01	Rowan et al.	Applicant
US2006/0041508(A1)	2006-02-01	Pham et al.	Applicant
US2006/0069618(A1)	2006-03-01	Milener et al.	Applicant
US2006/0095404(A1)	2006-05-01	Adelman et al.	Applicant
US2006/0095586(A1)	2006-05-01	Adelman et al.	Applicant
US2006/0106866(A1)	2006-05-01	Green et al.	Applicant
US2006/0106914(A1)	2006-05-01	Plow et al.	Applicant
US2006/0117389(A1)	2006-06-01	Pool	Applicant
US2006/0123478(A1)	2006-06-01	Rehfuss et al.	Applicant
US2006/0174343(A1)	2006-08-01	Duthie et al.	Applicant
US2006/0179157(A1)	2006-08-01	Huang	Applicant
US2006/0212925(A1)	2006-09-01	Shull et al.	Applicant
US2006/0218403(A1)	2006-09-01	Sauve et al.	Applicant
US2006/0235796(A1)	2006-10-01	Johnson et al.	Applicant
US2006/0239430(A1)	2006-10-01	Gue et al.	Applicant
US2006/0242026(A1)	2006-10-01	Crespo et al.	Applicant
US2006/0253458(A1)	2006-11-01	Dixon et al.	Applicant
US2006/0253578(A1)	2006-11-01	Dixon et al.	Applicant
US2006/0253579(A1)	2006-11-01	Dixon et al.	Applicant
US2006/0253580(A1)	2006-11-01	Dixon et al.	Applicant
US2006/0253581(A1)	2006-11-01	Dixon et al.	Applicant
US2006/0253582(A1)	2006-11-01	Dixon et al.	Applicant
US2006/0253583(A1)	2006-11-01	Dixon et al.	Applicant
US2006/0253584(A1)	2006-11-01	Dixon et al.	Applicant
US2006/0265417(A1)	2006-11-01	Amato et al.	Applicant
US2006/0282795(A1)	2006-12-01	Clark et al.	Applicant
US2007/0028291(A1)	2007-02-01	Brennan et al.	Examiner
US2007/0028304(A1)	2007-02-01	Brennan	Examiner
US2007/0039038(A1)	2007-02-01	Goodman et al.	Applicant
US2007/0074125(A1)	2007-03-01	Platt et al.	Applicant
US2007/0083929(A1)	2007-04-01	Sprosts et al.	Applicant
US2007/0088652(A1)	2007-04-01	Firmage et al.	Applicant
US2007/0118898(A1)	2007-05-01	Morgan et al.	Applicant
US2007/0130350(A1)	2007-06-01	Alperovitch et al.	Applicant
US2007/0203884(A1)	2007-08-01	Nichols et al.	Examiner
US2008/0028029(A1)	2008-01-01	Hart	Applicant
US2008/0109473(A1)	2008-05-01	Dixon et al.	Applicant
US2008/0114709(A1)	2008-05-01	Dixon et al.	Applicant
US2008/0134084(A1)	2008-06-01	Clark et al.	Applicant
US2008/0162225(A1)	2008-07-01	Malcolm	Applicant
US2008/0250159(A1)	2008-10-01	Wang et al.	Applicant
US2009/0089287(A1)	2009-04-01	Roberts et al.	Applicant
US2009/0258253(A1)	2009-10-01	Hinoue et al.	Applicant
US2009/0281905(A1)	2009-11-01	Walton	Applicant
US2010/0042931(A1)	2010-02-01	Dixon et al.	Applicant
US2012/0185942(A1)	2012-07-01	Dixon et al.	Applicant
US2012/0311705(A1)	2012-12-01	Dixon et al.	Applicant
US2013/0014020(A1)	2013-01-01	Dixon et al.	Applicant
WO99/49380	1999-09-01		Applicant
WO1/55873	2001-08-01		Applicant
WO1/55905	2001-08-01		Applicant
WO3/049403	2003-06-01		Applicant
WO3/079214	2003-09-01		Applicant
WO2004/061703	2004-07-01		Applicant
WO2005/010649	2005-02-01		Applicant
WO2005/033978	2005-04-01		Applicant
WO2005/043351	2005-05-01		Applicant
WO2005/043416	2005-05-01		Applicant
WO2005/043417	2005-05-01		Applicant
WO2006/020095	2006-02-01		Applicant

Non-Patent Literature (223)

Siteadvisor, http://www.siteadvisor.com/.Applicant

Office Action Summary from U.S. Appl. No. 11/905,330 mailed on Dec. 30, 2009.Applicant

Final Office Action Summary from U.S. Appl. No. 11/342,319 mailed on Jan. 22, 2010.Applicant

Office Action Summary from U.S. Appl. No. 11/342,250 mailed on Feb. 26, 2010.Applicant

Final Office Action Summary from U.S. Appl. No. 11/342,322 mailed on Mar. 1, 2010.Applicant

Final Office Action Summary from U.S. Appl. No. 11/837,067 mailed on Mar. 1, 2010.Applicant

Office Action Summary from U.S. Appl. No. 11/837,050 mailed on Sep. 2, 2009.Applicant

Final Office Action Summary from U.S. Appl. No. 11/342,318 mailed on Sep. 21, 2009.Applicant

Office Action Summary from U.S. Appl. No. 11/342,322 mailed on Oct. 16, 2009.Applicant

Office Action Summary from U.S. Appl. No. 11/342,297 mailed on Dec. 28, 2009.Applicant

Office Action Summary from U.S. Appl. No. 11/342,342 mailed on Jan. 12, 2010.Applicant

Office Action Summary from U.S. Appl. No. 11/342,343 mailed on Jan. 13, 2010.Applicant

Final Office Action Summary from U.S. Appl. No. 11/342,250 mailed on Dec. 2, 2009.Applicant

U.S. Appl. No. 60/588,570, filed Jul. 16, 2004.Applicant

U.S. Appl. No. 60/633,464, filed Dec. 6, 2004.Applicant

“Advertisement,” Dictionary.com, http://dictionary.reference.com/browse/advertisement, Feb. 11, 2010.Applicant

Notice of Allowance from U.S. Appl. No. 11/905,330 mailed on Apr. 30, 2010.Applicant

Final Office Action Summary from U.S. Appl. No. 11/837,050 mailed on Apr. 7, 2010.Applicant

U.S. Appl. No. 11/281,963, filed Nov. 16, 2005.Applicant

Non-Final Office Action Summary from U.S. Appl. No. 11/281,963 mailed on Nov. 13, 2007.Applicant

Non-Final Office Summary from U.S. Appl. No. 11/281,963 mailed on Dec. 2, 2008.Applicant

Final Office Action Summary from U.S. Appl. No. 11/281,963 mailed on Jun. 10, 2008.Applicant

Non-Final Office Summary from U.S. Appl. No. 11/281,963 mailed on Jun. 2, 2009.Applicant

Office Action Summary from U.S. Appl. No. 11/281,963 mailed on Mar. 8, 2010.Applicant

U.S. Appl. No. 11/852,948, filed Sep. 10, 2007.Applicant

Non-Final Office Action Summary from U.S. Appl. No. 11/852,948 mailed on Oct. 7, 2009.Applicant

Non-Final Office Action Summary from U.S. Appl. No. 11/342,297 mailed on Jul. 9, 2008.Applicant

Final Office Action Summary from U.S. Appl. No. 11/342,297 mailed on Mar. 17, 2009.Applicant

Notice of Allowance from U.S. Appl. No. 11/342,297 mailed on May 26, 2010.Applicant

Non-Final Office Action Summary from U.S. Appl. No. 11/342,319 mailed on Sep. 17, 2008.Applicant

Final Office Action Summary from U.S. Appl. No. 11/342,319 mailed on Mar. 16, 2009.Applicant

Non-Final Office Action Summary from U.S. Appl. No. 11/342,319 mailed on Aug. 25, 2009.Applicant

Advisory Action Summary from U.S. Appl. No. 11/342,319 mailed on Apr. 21, 2010.Applicant

Final Office Action Summary from U.S. Appl. No. 11/342,250 mailed on Dec. 16, 2008.Applicant

Advisory Action Summary from U.S. Appl. No. 11/342,250 mailed on Feb. 25, 2009.Applicant

Non-Final Office Action Summary from U.S. Appl. No. 11/342,250 mailed on May 28, 2009.Applicant

Non-Final Office Action Summary from U.S. Appl. No. 11/342,250 mailed on Jun. 20, 2008.Applicant

Final Office Action Summary from U.S. Appl. No. 11/342,343 mailed on Jul. 14, 2010.Applicant

Final Office Action Summary from U.S. Appl. No. 11/342,318 mailed on Aug. 18, 2008.Applicant

Non-Final Office Action Summary from U.S. Appl. No. 11/342,318 mailed on Mar. 26, 2009.Applicant

Non-Final Office Action Summary from U.S. Appl. No. 11/342,318 mailed on Mar. 27, 2008.Applicant

Non-Final Office Action Summary from U.S. Appl. No. 11/342,342 mailed on Jan. 23, 2009.Applicant

Non-Final Office Action Summary from U.S. Appl. No. 11/342,342 mailed on Jan. 24, 2008.Applicant

Advisory Action Summary from U.S. Appl. No. 11/342,342 mailed on Nov. 12, 2008.Applicant

Final Office Action Summary from U.S. Appl. No. 11/342,342 mailed on Jul. 22, 2008.Applicant

Final Office Action Summary from U.S. Appl. No. 11/342,342 mailed on Aug. 20, 2009.Applicant

Non-Final Office Action Summary from U.S. Appl. No. 11/342,320 mailed on May 5, 2008.Applicant

Final Office Action Summary from U.S. Appl. No. 11/342,320 mailed on Dec. 11, 2008.Applicant

Notice of Allowance from U.S. Appl. No. 11/342,320 mailed on Mar. 4, 2009.Applicant

Notice of Allowability from U.S. Appl. No. 11/342,320 mailed on Apr. 27, 2009.Applicant

Non-Final Office Action Summary from U.S. Appl. No. 11/342,322 mailed on Sep. 18, 2008.Applicant

Final Office Action Summary from U.S. Appl. No. 11/342,322 mailed on May 15, 2009.Applicant

Advisory Action Summary from U.S. Appl. No. 11/342,322 mailed on Aug. 10, 2009.Applicant

Non-Final Office Action Summary from U.S. Appl. No. 11/837,067 mailed on Jun. 12, 2009.Applicant

Final Office Action Summary from U.S. Appl. No. 11/837,067 mailed on Dec. 31, 2008.Applicant

Non-Final Office Action Summary from U.S. Appl. No. 11/837,067 mailed on Jul. 12, 2010.Applicant

Non-Final Office Action Summary from U.S. Appl. No. 11/837,067 mailed on Jun. 17, 2008.Applicant

U.S. Appl. No. 11/342,250, filed Jan. 26, 2006.Applicant

U.S. Appl. No. 11/837,050, filed Aug. 10, 2007.Applicant

U.S. Appl. No. 11/342,343, filed Jan. 26, 2006.Applicant

U.S. Appl. No. 11/342,297, filed Jan. 26, 2006.Applicant

U.S. Appl. No. 11/342,318, filed Jan. 26, 2006.Applicant

U.S. Appl. No. 11/342,319, filed Jan. 26, 2006.Applicant

U.S. Appl. No. 11/342,320, filed Jan. 26, 2006.Applicant

U.S. Appl. No. 11/342,322, filed Jan. 26, 2006.Applicant

U.S. Appl. No. 11/342,342, filed Jan. 26, 2006.Applicant

U.S. Appl. No. 12/502,158, filed Jul. 13, 2009.Applicant

U.S. Appl. No. 11/905,330, filed Sep. 28, 2007.Applicant

Non-Final Office Action Summary from U.S. Appl. No. 11/342,322 mailed on Sep. 22, 2010.Applicant

Non-Final Office Action Summary from U.S. Appl. No. 11/342,319 mailed on Sep. 13, 2010.Applicant

Final Office Action Summary from U.S. Appl. No. 11/342,342 mailed on Jul. 26, 2010.Applicant

Non-Final Office Action Summary from U.S. Appl. No. 11/837,050 mailed on Aug. 18, 2010.Applicant

Final Office Action Summary from U.S. Appl. No. 11/342,250 mailed on Sep. 17, 2010.Applicant

Final Office Action Summary from U.S. Appl. No. 11/852,948 mailed on May 26, 2010.Applicant

Notice of Allowance form U.S. Appl. No. 11/342,318, dated Feb. 23, 2010.Applicant

Bowman, W., The Uniform Computer Information Transactions Act: A Well Built Fence or Barbed Wire Around the Intellectual Commons?, LBJ Journal of Public Affairs, Spring 2001, vol. XIII, pp. 80-91, USA; retrieved form http://uts.cc.utexas.edu/˜lbjjpa/2001/bowman.pdf on Feb. 16, 2011.Applicant

Dean et al., DIMACS Workshop on theft in E-Commerce: Content, Identity, and Service, Apr. 14-15, 2005, pp. 1-7, DIMACS Center, CoRE Building, Rutgers University, Piscataway, NJ, USA; retrieved from http://dimacs.rutgers.edu/Workshops/Intellectual/abstracts.html on Feb. 16, 2011.Applicant

International Search Report and Written Opinion from International Application No. PCT/US06/17335, mailed Nov. 29, 2007.Applicant

International Preliminary Report on Patentability from International Application No. PCT/US06/17335, dated Nov. 6, 2007.Applicant

International Search Report and Written Opinion from International Application No. PCT/US06/17333, mailed Aug. 18, 2008.Applicant

International Preliminary Report on Patentability from International Application No. PCT/US2006/017333, dated Mar. 17, 2009.Applicant

International Search Report and Written Opinion from International Application No. PCT/US06/17334, mailed Sep. 25, 2007.Applicant

International Preliminary Report on Patentability from International Application No. PCT/US2006/017334, dated Nov. 6, 2007.Applicant

Response to Non-Final Action dated Apr. 15, 2011 in U.S. Appl. No. 11/342,250 filed on Jul. 15, 2011.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/837,050 filed on Jul. 12, 2011.Applicant

Non-Final Office Action in U.S. Appl. No. 11/837,067 mailed on Jun. 23, 2011.Applicant

Response to Non-Final Office Action dated Apr. 14, 2011 in U.S. Appl. No. 12/502,158 filed on Jul. 14, 2011.Applicant

Response to Final Office Action dated May 15, 2009 in U.S. Appl. No. 11/342,322 filed on Jul. 15, 200.Applicant

Non-Final Office Action in U.S. Appl. No. 11/342,322 mailed on Sep. 2, 2011.Applicant

Non-Final Office Action in U.S. Appl. No. 11/342,319 mailed on Sep. 7, 2011.Applicant

Response to Non-Final Office Action dated Jun. 9, 2011 in U.S. Appl. No. 11/342,343 filed on Sep. 9, 2011.Applicant

Finjan SecureBrowsing™,“Browse fearlessly,” Finjan, Inc. (1996-2007), 2 pages.Applicant

Response to Non-Final Office Action dated Nov. 13, 2007 in U.S. Appl. No. 11/281,963 filed on Feb. 13, 2008.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/281,963 filed on Sep. 17, 2008.Applicant

Response to Non-Final Office Action mailed Dec. 2, 2008 in U.S. Appl. No. 11/281,963 filed on Mar. 2, 2009.Applicant

Response to Non-Final Office Action dated Jun. 2, 2009 in U.S. Appl. No. 11/281,963 filed on Sep. 2, 2009.Applicant

Notice of Appeal in U.S. Appl. No. 11/281,963 filed on Jul. 8, 2010.Applicant

Appeal Brief in U.S. Appl. No. 11/281,963 filed on Feb. 8, 2011.Applicant

Examiner's Answer to Appellant's Appeal Brief dated Feb. 8, 2011 in U.S. Appl. No. 11/281,963 mailed on Apr. 28, 2011.Applicant

Notice of Appeal in U.S. Appl. No. 11/852,948 filed on Oct. 26, 2010.Applicant

Appeal Brief in U.S. Appl. No. 11/852,948 filed on Feb. 23, 2011.Applicant

Examiner's Answer to Appellant's Feb. 23, 2011 Appeal Brief in U.S. Appl. No. 11/852,948 mailed on May 13, 2011.Applicant

Response to Final Office Action dated Dec. 16, 2008 in U.S. Appl. No. 11/342,250 filed on Feb. 17, 2009.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,250 filed on Mar. 16, 2009.Applicant

Response to Non-Final Office Action dated May 28, 2009 in U.S. Appl. No. 11/342,250 filed on Aug. 28, 2009.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,250 filed on Feb. 2, 2010.Applicant

Non-Final Office Action in U.S. Appl. No. 11/342,250 mailed on Feb. 26, 2010.Applicant

Response to Non-Final Office Action dated Feb. 26, 2010 in U.S. Appl. No. 11/342,250 filed on Jun. 28, 2010.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,250 filed on Feb. 17, 2011.Applicant

Non-Final Office Action in U.S. Appl. No. 11/342,250 mailed on Apr. 15, 2011.Applicant

Response to Non-Final Office Action dated Sep. 2, 2009 in U.S. Appl. No. 11/837,050 filed on Jan. 4, 2010.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/837,050 filed on Jul. 7, 2010.Applicant

Response to Non-Final Office Action dated Aug. 18, 2010 in U.S. Appl. No. 11/837,050 filed on Feb. 28, 2011.Applicant

Final Office Action in U.S. Appl. No. 11/837,050 mailed on May 12, 2011.Applicant

U.S. Appl. No. 11/837,067, filed Aug. 10, 2007.Applicant

Response to Non-Final Office Action dated Jun. 17, 2008 in U.S. Appl. No. 11/837,067 filed on Sep. 17, 2008.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/837,067 filed on Mar. 30, 2009.Applicant

Response to Non-Final Office Action dated Jun. 12, 2009 in U.S. Appl. No. 11/837,067 filed on Nov. 12, 2009.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/837,067 filed on Jun. 1, 2010.Applicant

Response to Non-Final Office Action dated Jul. 12, 2010 in U.S. Appl. No. 11/837,067 filed on Jan. 12, 2011.Applicant

Final Office Action in U.S. Appl. No. 11/837,067 mailed on Apr. 1, 2011.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/837,067 filed on Jun. 1, 2011.Applicant

Response to Non-Final Office Action dated May 5, 2008 in U.S. Appl. No. 11/342,320 filed on Sep. 5, 2008.Applicant

Response to Final Office Action dated Dec. 11, 2008 in U.S. Appl. No. 11/342,320 filed on Feb. 11, 2009.Applicant

312 Amendment in U.S. Appl. No. 11/342,320 filed on Jun. 4, 2009.Applicant

Non-Final Office Action in U.S. Appl. No. 12/502,158 mailed on Apr. 14, 2011.Applicant

Response to Non-Final Office Action dated Mar. 27, 2008 in U.S. Appl. No. 11/342,318 filed on May 22, 2008.Applicant

Pre-Brief Conference Request and Notice of Appeal in U.S. Appl. No. 11/342,318 filed on Nov. 18, 2008.Applicant

Pre-Brief Conference Decision in U.S. Appl. No. 11/342,318 mailed on Dec. 11, 2008.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,318 filed on Feb. 18, 2009.Applicant

Response to Non-Final Office Action dated Mar. 26, 2009 in U.S. Appl. No. 11/342,318 filed on Jun. 26, 2009.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,318 filed on Jan. 21, 2010.Applicant

Response to Non-Final Office Action dated Jan. 24, 2008 in U.S. Appl. No. 11/342,342 filed on Apr. 10, 2008.Applicant

Response to Final Office Action dated Jul. 22, 2008 in U.S. Appl. No. 11/342,342 filed on Sep. 17, 2008.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,342 filed on Nov. 24, 2008.Applicant

Response to Non-Final Office Action dated Jan. 23, 2009 in U.S. Appl. No. 11/342,342 filed on May 26, 2009.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/34,342 filed on Dec. 21, 2009.Applicant

Response to Non-Final Office Action dated Jan. 12, 2010 in U.S. Appl. No. 11/342,342 filed on May 12, 2010.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,342 filed on Jan. 26, 2011.Applicant

Response to Non-Final Office Action dated Sep. 18, 2008 in U.S. Appl. No. 11/342,322 filed on Dec. 18, 2008.Applicant

Notice to Applicant regarding Non-Compliant Amendment in U.S. Appl. No. 11/342,322 mailed on Jan. 16, 2009.Applicant

Response to Notice dated Jan. 16, 2009 in U.S. Appl. No. 11/342,322 filed on Feb. 17, 2009.Applicant

Response to Final Office Action dated May 15, 2009 in U.S. Appl. No. 11/342,322 filed on Jul. 15, 2009.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,322 filed on Aug. 12, 2009.Applicant

Response to Non-Final Office Action dated Oct. 16, 2009 in U.S. Appl. No. 11/342,322 filed on Jan. 19, 2010.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,322 filed on Jun. 1, 2010.Applicant

Response to Non-Final Office Action dated Sep. 22, 2010 in U.S. Appl. No. 11/342,322 filed on Feb. 22, 2011.Applicant

Final Office Action in U.S. Appl. No. 11/342,322 mailed on Mar. 21, 2011.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,322 filed on May 23, 2011.Applicant

Response to Non-Final Office Action dated Jul. 9, 2008 in U.S. Appl. No. 11/342,297 filed on Dec. 9, 2008.Applicant

Notice of Appeal in U.S. Appl. No. 11/342,297 filed on Jun. 17, 2009.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,297 filed on Nov. 17, 2009.Applicant

Response to Non-Final Office Action dated Dec. 28, 2009 in U.S. Appl. No. 11/342,297 filed on Apr. 28, 2010.Applicant

Non-Final Office Action in U.S. Appl. No. 11/342,297 mailed on Sep. 24, 2010.Applicant

Response to Non-Final Office Action dated Sep. 17, 2008 in U.S. Appl. No. 11/342,319 filed on Dec. 17, 2008.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,319 filed on Jun. 16, 2009.Applicant

Response to Non-Final Office Action dated Aug. 25, 2009 in U.S. Appl. No. 11/342,319 filed on Dec. 28, 2009.Applicant

Response to Final Office Action dated Jan. 22, 2010 in U.S. Appl. No. 11/342,319 filed on Mar. 22, 2010.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,319 filed on Apr. 22, 2010.Applicant

Notice of Appeal in U.S. Appl. No. 11/342,319 filed on Feb. 23, 2011.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,319 filed on Apr. 25, 2011.Applicant

Response to Non-Final Office Action dated Jan. 13, 2010 in U.S. Appl. No. 11/342,343 filed on May 13, 2010.Applicant

Notice to Applicant regarding Non-Responsive/Non-Compliant Amendment in U.S. Appl. No. 11/342,343 mailed on May 19, 2010.Applicant

Response to Notice dated May 19, 2010 filed in U.S. Appl. No. 11/342,343 filed on Jun. 11, 2010.Applicant

Non-Final Office Action in U.S. Appl. No. 11/342,343 mailed on Jun. 9, 2011.Applicant

Response to Non-Final Office Action dated Dec. 30, 2009 in U.S. Appl. No. 11/905,330, filed Mar. 30, 2010.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,250 filed on Nov. 30, 2012.Applicant

Notice of Allowance in U.S. Appl. No. 11/837,050 mailed on Nov. 27, 2012.Applicant

Response to Non-Final Office Action dated Jul. 24, 2012 in U.S. Appl. No. 11/342,322 filed on Oct. 24, 2012.Applicant

Response to Non-Final Office Action dated Jul. 24, 2012 in U.S. Appl. No. 11/342,319 filed on Oct. 24, 2012.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,250 filed on Feb. 8, 2012.Applicant

Non-Final Office Action in U.S. Appl. No. 11/342,250 mailed on Feb. 23, 2012.Applicant

Response to Non-Final Office Action dated Nov. 25, 2011 in U.S. Appl. No. 11/837,050 filed on Feb. 24, 2012.Applicant

Final Office Action in U.S. Appl. No. 11/837,050 mailed on Mar. 19, 2012.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/837,067 filed on Jan. 17, 2012.Applicant

Notice of Allowance in U.S. Appl. No. 11/837,067 mailed on Mar. 7, 2012.Applicant

Request for Continued Examination in U.S. Appl. No. 11/837,067 filed on Mar. 23, 2012.Applicant

U.S. Appl. No. 13/431,873, filed Mar. 27, 2012, entitled System Method, and Computer Program Product for Presenting an Indicia of Risk Associated with Search Results within a Graphical User Interface, Inventors, Christopher John Dixon et al.Applicant

Response to Non-Final Office Action dated Nov. 28, 2011 in U.S. Appl. No. 12/502,158 filed on Feb. 27, 2012.Applicant

Response to Non-Final Office Action dated Sep. 22, 2011 in U.S. Appl. No. 11/342,342 filed on Dec. 22, 2011.Applicant

Non-Final Office Action in U.S. Appl. No. 11/342,342 mailed on Mar. 2, 2012.Applicant

Final Office Action in U.S. Appl. No. 11/342,322 mailed on Jan. 26, 2012.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,322 filed on Mar. 26, 2012.Applicant

Response to Non-Final Office Action dated Sep. 7, 2011 in U.S. Appl. No. 11/342,319 filed on Dec. 7, 2011.Applicant

Final Office Action in U.S. Appl. No. 11/342,319 mailed on Jan. 25, 2012.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,319 filed on Mar. 26, 2012.Applicant

Response to Non-Final Office Action dated Feb. 23, 2012 in U.S. Appl. No. 11/342,250 filed on May 14, 2012.Applicant

Final Office Action in U.S. Appl. No. 11/342,250 mailed on Aug. 30, 2012.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/837,050 filed on May 10, 2012.Applicant

Notice of Allowance in U.S. Appl. No. 11/837,050 mailed on Jun. 6, 2012.Applicant

Request for Continued Examination in U.S. Appl. No. 11/837,050 filed on Sep. 6, 2012.Applicant

U.S. Appl. No. 13/568,085, filed Aug. 6, 2012 and entitled “System, Method, and Computer Program Product for Presenting an Indica of Risk Reflecting an Analysis Associated with Search Results within a Graphical User Interface,” Christopher John Dixon et al. inventors.Applicant

Notice of Allowance in U.S. Appl. No. 11/837,067 mailed on Jun. 22, 2012.Applicant

Notice of Allowance in U.S. Appl. No. 12/502,158 mailed on May 30, 2012.Applicant

Request for Continued Examination in U.S. Appl. No. 12/502,158 filed on Aug. 30, 2012.Applicant

Notice of Allowance in U.S. Appl. No. 12/502,158 mailed on Oct. 9, 2012.Applicant

U.S. Appl. No. 13/621,037, filed Sep. 15, 2012 entitled “Indicating Website Reputations during Website Manipulation of User Information”, Inventors Christopher John Dixon et al.Applicant

Response to Non-Final Office Action dated Mar. 2, 2012 in U.S. Appl. No. 11/342,342 filed on Jun. 4, 2012.Applicant

Final Office Action in U.S. Appl. No. 11/342,342 mailed on Jul. 2, 2012.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,342 filed on Oct. 2, 2012.Applicant

Non-Final Office Action in U.S. Appl. No. 11/342,322 mailed on Jul. 24, 2012.Applicant

Non-Final Office Action in U.S. Appl. No. 11/342,319 mailed on Jul. 24, 2012.Applicant

Final Office Action in U.S. Appl. No. 11/342,250 mailed on Nov. 8, 2011.Applicant

Non-Final Office Action in U.S. Appl. No. 11/837,050 mailed on Nov. 25, 2011.Applicant

Response to Non-Final Office Action dated Jun. 23, 2011 in U.S. Appl. No. 11/837,067 filed on Sep. 23, 2011.Applicant

Final Office Action in U.S. Appl. No. 11/837,067 mailed on Nov. 17, 2011.Applicant

Notice of Allowance in U.S. Appl. No. 12/502,158 mailed on Sep. 27, 2011.Applicant

Request for Continued Examination in U.S. Appl. No. 12/502,158 filed on Nov. 7, 2011.Applicant

Non-Final Office Action in U.S. Appl. No. 12/502,158 mailed on Nov. 28, 2011.Applicant

Non-Final Office Action in U.S. Appl. No. 11/342,342 mailed on Sep. 22, 2011.Applicant

Response to Sep. 2, 2011 Non-Final Office Action in U.S. Appl. No. 11/342,322 filed on Dec. 1, 2011.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,343 filed on Jan. 14, 2011.Applicant

Final Office Action in U.S. Appl. No. 11/342,343 mailed on Sep. 26, 2011.Applicant

Request for Continued Examination and Amendment in U.S. Appl. No. 11/342,343 filed on Nov. 28, 2011.Applicant

Examiner Interview Summary in U.S. Appl. No. 11/342,343 mailed on Dec. 5, 2011.Applicant

Final Office Action in U.S. Appl. No. 11/342,319 mailed on Jan. 4, 2013.Applicant

Issue Notification in U.S. Appl. No. 11/837,050 mailed Apr. 3, 2013—Patent No. 8429545.Applicant

Non-Final Office Action in U.S. Appl. No. 13/621,037 mailed Dec. 31, 2012.Applicant

Notice of Publication in U.S. Appl. No. 13/621,037.Applicant

Notice of Allowance in U.S. Appl. No. 11/342,250 mailed on Jan. 10, 2013.Applicant

Final Office Action in U.S. Appl. No. 11/342,322 mailed on Jan. 4, 2013.Applicant