The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Jun. 08, 2010
Filed:
Apr. 18, 2006
Srinivas Mantripragada, Cupertino, CA (US);
Tim Garnett, Boston, MA (US);
Derek Bruening, Troy, NY (US);
Vladimir Kiriansky, Cambridge, MA (US);
Bharath Chandramohan, Sunnyvale, CA (US);
James Brink, Oakland, CA (US);
Saman P. Amarasinghe, Waltham, MA (US);
Sandy Wilbourn, Palo Alto, CA (US);
Srinivas Mantripragada, Cupertino, CA (US);
Tim Garnett, Boston, MA (US);
Derek Bruening, Troy, NY (US);
Vladimir Kiriansky, Cambridge, MA (US);
Bharath Chandramohan, Sunnyvale, CA (US);
James Brink, Oakland, CA (US);
Saman P. Amarasinghe, Waltham, MA (US);
Sandy Wilbourn, Palo Alto, CA (US);
VMware, Inc., Palo Alto, CA (US);
Abstract
Protected software, such as an application and/or DLL, is monitored by protective software to guard against attacks, while distinguishing spurious, benign events from attacks. In a 1-touch approach, the protected software is monitored in a testing environment to detect spurious, benign events caused by, e.g., incompatibility or interoperability problems. The spurious events can be remediated in different ways, such as by applying a relaxed security policy. In a production mode, or 0-touch mode, when the protected software is subject to attacks, the corresponding remediation can be applied when the spurious events are again detected. Security events which occur in production mode can also be treated as benign when they occur within a specified time window. The applications and/or DLLs can further be classified according to whether they are known to have bad properties, known to be well-behaved, or unknown. Appropriate treatment is provided based on the classification.