This invention pertains generally to computer security, and more specifically to selectively revoking heuristic exemptions for content with digital signatures.
Heuristic detection is commonly used by security software to check for and detect malicious code (e.g., viruses, worms, Trojan horses, etc.) Security software often exempts applications with Digital Signatures from heuristic detection. This is a good policy, as it both reduces false positives and allows trusted third party applications to bypass heuristic detection without requiring interaction with the publisher of the security software.
However, sometimes a digital signature provider provides signatures to entities which the security software publisher does not trust. This can occur because the signature authority made a mistake, or because the signature provider and the security software publisher have different standards as to what constitutes a trusted party. For example, digital signatures are granted to some companies that have been known to distribute commercial spyware applications. In this case, it would not be appropriate to grant a blanket heuristic detection exemption to files from such a company. On the other hand, the company may ship applications that do not contain spyware, so it is also not appropriate to assume that all files from such a company are known to be a threat.
It would be desirable to be able to revoke the exemption given to applications with digital signatures where desired, without presupposing that files originating from an entity with a revoked exemption comprise a threat per se.
Applications with valid digital signatures are, by default, exempted from heuristic detection. However, there are cases where this exemption is not warranted (for example, where the company distributing the application has been known to distribute commercial spyware or adware). For this reason, digital signatures are examined for specified attributes indicating that an exemption is not appropriate. If the specified attributes are not present in a digital signature, the associated application will be exempt from heuristic detection. However, where the specified attributes are present in a signature, the signed application is subject to heuristic detection just like a non-signed application. This does not mean the application is automatically treated as being malicious, but simply that the application is scrutinized to check for malicious behavior.
The features and advantages described in this summary and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.
The Figures depict embodiments of the present invention for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the invention described herein.
As illustrated in
When examining the digital signature 103, the exemption manager 105 can check for any given signature attribute 109 (or combination of attributes 109). In other words, as explained in greater detail in conjunction with
Turning now to
As illustrated in
It is to be understood that the specified attributes 109 can represent any characteristics which are believed to indicate a need to subject content 101 to heuristic detection. The specific attributes 109 to use are a design variable, which can be set and modified (e.g., “at the factory” and/or via dynamic updates) by the publisher of the security software. In some embodiments, these attributes 109 can also be specified and/or edited by users of the security software and/or by trusted third parties.
As will be understood by those familiar with the art, the invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. Likewise, the particular naming and division of the portions, modules, agents, managers, components, functions, procedures, actions, layers, features, attributes, methodologies and other aspects are not mandatory or significant, and the mechanisms that implement the invention or its features may have different names, divisions and/or formats. Furthermore, as will be apparent to one of ordinary skill in the relevant art, the portions, modules, agents, managers, components, functions, procedures, actions, layers, features, attributes, methodologies and other aspects of the invention can be implemented as software, hardware, firmware or any combination of the three. Of course, wherever a component of the present invention is implemented as software, the component can be implemented as a script, as a standalone program, as part of a larger program, as a plurality of separate scripts and/or programs, as a statically or dynamically linked library, as a kernel loadable module, as a device driver, and/or in every and any other way known now or in the future to those of skill in the art of computer programming. Additionally, the present invention is in no way limited to implementation in any specific programming language, or for any specific operating system or environment. Furthermore, it will be readily apparent to those of ordinary skill in the relevant art that where the present invention is implemented in whole or in part in software, the software components thereof can be stored on computer readable media as computer program products. Any form of computer readable medium can be used in this context, such as magnetic or optical storage media. Additionally, software portions of the present invention can be instantiated (for example as object code or executable images) within the memory of any programmable computing device. Accordingly, the disclosure of the present invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.
Number | Name | Date | Kind |
---|---|---|---|
6367012 | Atkinson et al. | Apr 2002 | B1 |
7650409 | Cain et al. | Jan 2010 | B2 |
20030074581 | Hursey et al. | Apr 2003 | A1 |
20030154409 | Morota et al. | Aug 2003 | A1 |
20040107345 | Brandt et al. | Jun 2004 | A1 |
20040153644 | McCorkendale et al. | Aug 2004 | A1 |
20060218637 | Thomas et al. | Sep 2006 | A1 |
20070157321 | Errico et al. | Jul 2007 | A1 |
20080141332 | Treinen | Jun 2008 | A1 |
20080263659 | Alme | Oct 2008 | A1 |
20090182818 | Krywaniuk | Jul 2009 | A1 |
20090287653 | Bennett | Nov 2009 | A1 |
20120260304 | Morris et al. | Oct 2012 | A1 |