|Publication number||US7346611 B2|
|Application number||US 11/104,201|
|Publication date||Mar 18, 2008|
|Filing date||Apr 12, 2005|
|Priority date||Apr 12, 2005|
|Also published as||US20060230290|
|Publication number||104201, 11104201, US 7346611 B2, US 7346611B2, US-B2-7346611, US7346611 B2, US7346611B2|
|Original Assignee||Webroot Software, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (31), Non-Patent Citations (8), Referenced by (8), Classifications (11), Legal Events (5)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present application is related to the following commonly owned and assigned applications: application Ser. No. 10/956,578, entitled System and Method for Monitoring Network Communications for Pestware; application Ser. No. 10/956,573, entitled System and Method For Heuristic Analysis to Identify Pestware, application Ser. No. 10/956,574, entitled System and Method for Pestware Detection and Removal, and application Ser. No. 11/104,202, filed herewith, entitled System and Method for Directly Accessing Data From a Data Storage Medium each of which is incorporated by reference in their entirety.
A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.
The present invention relates to computer system management. In particular, but not by way of limitation, the present invention relates to systems and methods for controlling pestware or malware.
Personal computers and business computers are continually attacked by trojans, spyware, and adware, collectively referred to as “malware” or “pestware.” These types of programs generally act to gather information about a person or organization—often without the person or organization's knowledge. Some pestware is highly malicious. Other pestware is non-malicious but may cause issues with privacy or system performance. And yet other pestware is actual beneficial or wanted by the user. Wanted pestware is sometimes not characterized as “pestware” or “spyware.” But, unless specified otherwise, “pestware” as used herein refers to any program that collects and/or reports information about a person or an organization and any “watcher processes” related to the pestware.
Software is available to detect pestware, but scanning a system for pestware typically requires a system to look at files stored in a data storage device (e.g., disk) on a file by file basis. This process of scanning files is frequently time consuming, and as a consequence, users must wait a substantial amount of time to find out the results of a system scan. Even worse, some users elect not to perform a system scan because they do not want to, or cannot, wait for a scan to be completed. Accordingly, current software is not always able to scan and remove pestware in a convenient manner and will most certainly not be satisfactory in the future.
Exemplary embodiments of the present invention that are shown in the drawings are summarized below. These and other embodiments are more fully described in the Detailed Description section. It is to be understood, however, that there is no intention to limit the invention to the forms described in this Summary of the Invention or in the Detailed Description. One skilled in the art can recognize that there are numerous modifications, equivalents and alternative constructions that fall within the spirit and scope of the invention as expressed in the claims.
Embodiments of the present invention include methods for scanning files of a protected computer for pestware. One embodiment is configured to identify a location of each of a plurality of files in at least one file storage device of the protected computer and store a list of the location of each of the plurality of files. The list of the plurality of files is then sorted by the location of each of the plurality of files so as to generate a sorted list of files. The files are then accessed in accordance with their position in the sorted list of files so as to retrieve information from each of the plurality of files in an order determined by the location of the files in the file storage device. The retrieved information from each of the plurality of files is then analyzed so as to determine whether any of the plurality of files are potential pestware files.
In another embodiment the invention may be characterized as a system for managing pestware. In this embodiment, a pestware detection module is configured to detect pestware on a protected computer, which includes a file storage device and a program memory. The system also includes a sweep speedup module configured to identify a location of each of a first file, a second file and a third file in the file storage device of the protected computer, and retrieve information from each of the first file, the second file and the third file in an order determined by the respective locations of the first file, the second file and the third file in the file storage device. The pestware detection module in this emboidiment is configured to analyze the retrieved information from each of the first file, the second file and the third file so as to determine whether each of the first file, the second file and the third file is a potential pestware file. These and other embodiments are described in more detail herein.
Various objects and advantages and a more complete understanding of the present invention are apparent and more readily appreciated by reference to the following Detailed Description and to the appended claims when taken in conjunction with the accompanying Drawings where like or similar elements are designated with identical reference numerals throughout the several views and wherein:
According to several embodiments, the present invention decreases the amount of time required to retrieve information from files stored in a computer system's storage device (e.g., hard drive).
In prior art computer systems, when a file is accessed (e.g., to retrieve information from the files), the computer's operating system is typically utilized to access the file. The operating system, however, typically performs several logistical operations before and/or while accessing a particular file. For example, before a typical operating system accesses a file, the operating system checks to make sure that accessing the file does not violate any established security provisions. In addition, the operating system must make sure the file is not already in use, and if it is, the operating system typically denies access to the file. And once the operating system does access a file, it flags the file so that it cannot be subsequently accessed while it is in use.
Although these logistical operations may be unnoticeable when just a few files are accessed, when several files are accessed, the logistical operations, in aggregate, take a substantial amount of time to carry out, and as a consequence, become very noticeable to the user.
In addition, when a user desires to perform a general scan of a collection of files (e.g., for pestware), prior art scanning software typically utilizes the operating system to enumerate (i.e., identify) each file in the collection of files to be scanned. Once the files are enumerated, the prior art scanning software then accesses, utilizing the operating system, each enumerated file, file by file, in the order the files are enumerated by the operating system.
Unfortunately, the order in which typical operating systems enumerate files may be determined by the directory tree that the files are organized by instead of the physical location of the files in the computer system's file storage device. In the context of a disk drive for example, the order in which files are enumerated may have very little, if any, relation to the location of the files on the disk. As a consequence, the head of a disk dive may have to move across opposite ends of the disk surface to access two files that were juxtaposed in the list of files enumerated by the operating system.
Although the time it takes the head to jump between two disparate locations on a disk surface to access two enumerated files may be insignificant, when several enumerated files (e.g., several hundred or thousand files) are accessed, the amount of time required for the disk heads to traverse the disk surface, in aggregate, is substantial.
Referring first to
As shown, the storage device 106 provides storage for a collection of N files 124, which includes a pestware file 126. The storage device 106 is described herein in several implementations as hard disk drive for convenience, but this is certainly not required, and one of ordinary skill in the art will recognize that other storage media may be utilized without departing from the scope of the present invention. In addition, one of ordinary skill in the art will recognize that the storage device 106, which is depicted for convenience as a single storage device, may be realized by multiple (e.g., distributed) storage devices.
As shown, an anti-spyware application 112 includes a detection module 114, a shield module 116, a removal module 118 and a sweep speedup module 120, which are implemented in software and are executed from the memory 104 by the CPU 102. In addition, an operating system 122 is also depicted as running from memory 104.
The software 112 can be configured to operate on personal computers (e.g., handheld, notebook or desktop), servers or any device capable of processing instructions embodied in executable code. Moreover, one of ordinary skill in the art will recognize that alternative embodiments, which implement one or more components (e.g., the anti-spyware 112) in hardware, are well within the scope of the present invention.
In the present embodiment, the operating system 122 is not limited to any particular type of operating system and may be operating systems provided by Microsoft Corp. under the trade name WINDOWS (e.g., WINDOWS 2000, WINDOWS XP, and WINDOWS NT). Additionally, the operating system may be an open source operating system such operating systems distributed under the LINUX trade name. For convenience, however, embodiments of the present invention are generally described herein with relation to WINDOWS-based systems. Those of skill in the art can easily adapt these implementations for other types of operating systems or computer systems.
In accordance with some embodiments of the present invention, the sweep speedup module 120 expedites the scanning of the N files 124 for pestware (e.g., the pestware file 126) in the data storage device 106 by scanning the files 124 according to their physical location in the data storage device 106 instead of the order the files are enumerated by the operating system. In this way, the time required for the mechanism(s) within the file storage device (e.g., a disk head) to access each file is substantially reduced.
In other embodiments, as discussed further with reference to
In yet other embodiments, the sweep speedup module 120 both directly accesses the data storage device 106 to locate and identify files in the data storage device 120 and accesses the files according to their location in the data storage device so as to further expedite the scanning of the N files 124 for any pestware.
Referring next to
As shown, a listing of the names and locations of the N files 124 is then saved (Block 208), and the stored listing of the N files 124 is sorted by the physical location of the N files 124 (Block 210). In the case where the physical storage device 106 is a disk drive, for example, the N files 124 are sorted by the cluster numbers of the files.
After the N files 124 are sorted so as to generated a sorted listing of the N files 124, information is retrieved from each of the N files 124, file-by-file, in accordance with the sorted listing (Block 212). For example, information may be retrieved from the N files 124 by accessing them in a sequential manner starting at either the top or the bottom of the sorted list. In this way, each file that is accessed is in close proximity to the file previously accessed. As a consequence, the time required to retrieve information from the N files 124 is substantially reduced relative to accessing the N files 124 in accordance with the location of the N files 124 in the directory tree. After information is retrieved from each of the N files 124, the information is analyzed to determine whether each file is potentially a pestware file, and the scanning processes is ended after information from each of the N files 124 is analyzed (Blocks 214 and 216). It should be recognized, that the information received from each file may be analyzed (Block 214) while information from other files is being retrieved (Block 212) so as to expedite the entire process of retrieving and analyzing information from the N files 124.
In several embodiments, the detection module 114, it is responsible for detecting pestware or pestware activity on the protected computer 100 based upon the information received from the N files 124. In one embodiment for example, the detection module compares a representation of known pestware files (e.g., a cyclical redundancy code (CRC) of a portion of the pestware file) with a representation (e.g., CRC) of a portion of each of the N files 124. In one variation, only 500 Bytes of information are retrieved from each of the N files 124 and a CRC of the 500 Bytes of information retrieved from each file is compared with the known pestware definitions. If the 500 Bytes of retrieved information indicates the file is a potential pestware file, then a more thorough analysis (e.g., an analysis of the entire file) is conducted. In this way, the comparison of each file with definitions of pestware files is expedited.
Pestware and pestware activity can also be detected by the shield module 116, which generally runs in the background on the computer system. Shields can generally be divided into two categories: those that use definitions to identify known pestware and those that look for behavior common to pestware. This combination of shield types acts to prevent known pestware and unknown pestware from running or being installed on a protected computer.
In many cases, the detection and shield modules (114 and 116) detect pestware by matching files on the protected computer with definitions of pestware, which are collected from a variety of sources. For example, a host computers, protected computers and other systems can crawl the Web to actively identify pestware. These systems often download programs and search for exploits. The operation of these exploits can then be monitored and used to create pestware definitions. Various techniques for detecting pestware are disclosed in the above-identified and related application entitled: System and Method for Monitoring Network Communications for Pestware.
Referring next to
After the file table for a collection of the N files 124 is located, the file table is accessed, while circumventing the operating system (Block 306), and the file table is read so as to identify names, locations and other attributes of the files (e.g., file size, compression flags and encryption flags) of the collection of the N files 124 in the file storage device 106 (Block 308). In some embodiments, the entire file structure of the collection of the N files 124 built and stored so that the location of every one of the N files 124 is known. Thus, the steps identified in Blocks 304, 306 and 308 may be utilized to generate the listing of names and locations, discussed with reference to Block 208 of
After the names and locations of the N files 124 are identified (Block 308), information from each of the N files 124 is retrieved, while circumventing the operating system, until each of the N files 124 has been accessed (Blocks 310 and 312). This information may be utilized, as previously discussed, to identify pestware (e.g., the pestware 126) among the N files 124 (Block 214).
It should be recognized that the processes depicted in
In conclusion, the present invention provides, among other things, a system and method for managing pestware. Those skilled in the art can readily recognize that numerous variations and substitutions may be made in the invention, its use and its configuration to achieve substantially the same results as achieved by the embodiments described herein. Accordingly, there is no intention to limit the invention to the disclosed exemplary forms. Many variations, modifications and alternative constructions fall within the scope and spirit of the disclosed invention as expressed in the claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5623600||Sep 26, 1995||Apr 22, 1997||Trend Micro, Incorporated||Virus detection and removal apparatus for computer networks|
|US6069628||May 14, 1997||May 30, 2000||Reuters, Ltd.||Method and means for navigating user interfaces which support a plurality of executing applications|
|US6073241||Aug 29, 1996||Jun 6, 2000||C/Net, Inc.||Apparatus and method for tracking world wide web browser requests across distinct domains using persistent client-side state|
|US6092194||Nov 6, 1997||Jul 18, 2000||Finjan Software, Ltd.||System and method for protecting a computer and a network from hostile downloadables|
|US6154844||Dec 22, 1997||Nov 28, 2000||Finjan Software, Ltd.||System and method for attaching a downloadable security profile to a downloadable|
|US6167520||Jan 29, 1997||Dec 26, 2000||Finjan Software, Inc.||System and method for protecting a client during runtime from hostile downloadables|
|US6310630||Dec 12, 1997||Oct 30, 2001||International Business Machines Corporation||Data processing system and method for internet browser history generation|
|US6397264||Nov 1, 1999||May 28, 2002||Rstar Corporation||Multi-browser client architecture for managing multiple applications having a history list|
|US6460060||Jan 26, 1999||Oct 1, 2002||International Business Machines Corporation||Method and system for searching web browser history|
|US6480962||Apr 18, 2000||Nov 12, 2002||Finjan Software, Ltd.||System and method for protecting a client during runtime from hostile downloadables|
|US6535931||Dec 13, 1999||Mar 18, 2003||International Business Machines Corp.||Extended keyboard support in a run time environment for keys not recognizable on standard or non-standard keyboards|
|US6611878||Nov 8, 1996||Aug 26, 2003||International Business Machines Corporation||Method and apparatus for software technology injection for operating systems which assign separate process address spaces|
|US6633835||Jan 11, 2002||Oct 14, 2003||Networks Associates Technology, Inc.||Prioritized data capture, classification and filtering in a network monitoring environment|
|US6667751||Jul 13, 2000||Dec 23, 2003||International Business Machines Corporation||Linear web browser history viewer|
|US6701441||Jun 25, 2002||Mar 2, 2004||Networks Associates Technology, Inc.||System and method for interactive web services|
|US6785732||Sep 11, 2000||Aug 31, 2004||International Business Machines Corporation||Web server apparatus and method for virus checking|
|US6804780||Mar 30, 2000||Oct 12, 2004||Finjan Software, Ltd.||System and method for protecting a computer and a network from hostile downloadables|
|US6813711||Jan 4, 2000||Nov 2, 2004||Samsung Electronics Co., Ltd.||Downloading files from approved web site|
|US6829654||Jun 23, 2000||Dec 7, 2004||Cloudshield Technologies, Inc.||Apparatus and method for virtual edge placement of web sites|
|US6965968||Feb 27, 2003||Nov 15, 2005||Finjan Software Ltd.||Policy-based caching|
|US7058822||May 17, 2001||Jun 6, 2006||Finjan Software, Ltd.||Malicious mobile code runtime monitoring system and methods|
|US20030217287||May 14, 2003||Nov 20, 2003||Ilya Kruglenko||Secure desktop environment for unsophisticated computer users|
|US20040030914||Aug 9, 2002||Feb 12, 2004||Kelley Edward Emile||Password protection|
|US20040034794||Aug 21, 2003||Feb 19, 2004||Yaron Mayer||System and method for comprehensive general generic protection for computers against malicious programs that may steal information and/or cause damages|
|US20040064736||Aug 25, 2003||Apr 1, 2004||Wholesecurity, Inc.||Method and apparatus for detecting malicious code in an information handling system|
|US20040080529||Oct 24, 2002||Apr 29, 2004||Wojcik Paul Kazimierz||Method and system for securing text-entry in a web form over a computer network|
|US20040143763||Apr 6, 2004||Jul 22, 2004||Radatti Peter V.||Apparatus and methods for intercepting, examining and controlling code, data and files and their transfer in instant messaging and peer-to-peer applications|
|US20040187023||Jan 30, 2004||Sep 23, 2004||Wholesecurity, Inc.||Method, system and computer program product for security in a global computer network transaction|
|US20040225877||Mar 3, 2004||Nov 11, 2004||Zezhen Huang||Method and system for protecting computer system from malicious software operation|
|US20050138433||Dec 23, 2003||Jun 23, 2005||Zone Labs, Inc.||Security System with Methodology for Defending Against Security Breaches of Peripheral Devices|
|US20060085528 *||Oct 1, 2004||Apr 20, 2006||Steve Thomas||System and method for monitoring network communications for pestware|
|1||Codeguru, Hooking The Keyboard, by Anoop Thomas, Dec. 13, 2001, 6 pgs.|
|2||Codeguru, Managing Low-Level Keyboard Hooks With The Windows API for VB .Net, by Paul Kimmel, Apr. 18, 2004, 10 pgs.|
|3||Codeguru, Three Ways to Inject Your Code Into Another Process, by Robert Kuster, Aug. 4, 2003, 22 pgs.|
|4||DevX.com, Intercepting Systems API Calls, by Seung-Woo Kim, May 13, 2004, 6 pgs.|
|5||Illusive Security, Wolves In Sheep's Clothing: malicious DLLs Injected Into trusted Host Applications, Author Unknown, http://home.arcor.de/scheinsicherheit/dll.htm 13 pgs.|
|6||Microsoft.com, How To Subclass A Window in Windows 95, Article ID 125680, Jul. 11, 2005, 2 pgs.|
|7||MSDN, by Kyle Marsh, Jul. 29, 1993, 15 pgs.|
|8||PCT Search Report, PCT/US05/34874, Jul. 5, 2006, 7 Pages.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7565695||Apr 12, 2005||Jul 21, 2009||Webroot Software, Inc.||System and method for directly accessing data from a data storage medium|
|US8065664 *||Aug 7, 2006||Nov 22, 2011||Webroot Software, Inc.||System and method for defining and detecting pestware|
|US20060230291 *||Apr 12, 2005||Oct 12, 2006||Michael Burtscher||System and method for directly accessing data from a data storage medium|
|US20080052679 *||Aug 7, 2006||Feb 28, 2008||Michael Burtscher||System and method for defining and detecting pestware|
|US20080172387 *||Jan 16, 2007||Jul 17, 2008||Olaf Manczak||Speeding up traversal of a file system tree|
|US20100115619 *||Nov 3, 2008||May 6, 2010||Michael Burtscher||Method and system for scanning a computer storage device for malware incorporating predictive prefetching of data|
|US20110219002 *||Mar 5, 2010||Sep 8, 2011||Mcafee, Inc.||Method and system for discovering large clusters of files that share similar code to develop generic detections of malware|
|US20140188949 *||Jan 3, 2013||Jul 3, 2014||Dell Products L.P.||Methods and systems for supply chain assurance of information handling system code|
|U.S. Classification||707/737, 707/823, 707/952, 707/999.003, 707/781, 707/752|
|Cooperative Classification||Y10S707/99933, Y10S707/952, G06F21/562|
|Apr 12, 2005||AS||Assignment|
Owner name: WEBROOT SOFTWARE, INC., COLORADO
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BURTSCHER, MICHAEL;REEL/FRAME:016471/0494
Effective date: 20050405
|Aug 31, 2011||FPAY||Fee payment|
Year of fee payment: 4
|Sep 13, 2012||AS||Assignment|
Owner name: WEBROOT INC., COLORADO
Free format text: CHANGE OF NAME;ASSIGNOR:WEBROOT SOFTWARE, INC.;REEL/FRAME:028953/0917
Effective date: 20111219
|Jan 6, 2015||AS||Assignment|
Owner name: WELLS FARGO BANK, NATIONAL ASSOCIATION, COLORADO
Free format text: SECURITY INTEREST;ASSIGNOR:WEBROOT INC.;REEL/FRAME:034742/0085
Effective date: 20141223
|Sep 2, 2015||FPAY||Fee payment|
Year of fee payment: 8