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:
Apr. 12, 2011
Filed:
Feb. 28, 2006
Karen Elizabeth Corby, Seattle, WA (US);
Mark Alcazar, Seattle, WA (US);
Viresh Ramdatmisier, Seattle, WA (US);
Ariel Jorge Kirsman, Bellevue, WA (US);
Andre A. Needham, Redmond, WA (US);
Akhilesh Kaza, Sammamish, WA (US);
Raja Krishnaswamy, Redmond, WA (US);
Jeff Cooperstein, Bellevue, WA (US);
Charles W Kaufman, Sammamish, WA (US);
Chris Anderson, Redmond, WA (US);
Venkata Rama Prasad Tammana, Kirkland, WA (US);
Aaron R Goldfeder, Tampa, FL (US);
John Hawkins, Duvall, WA (US);
Karen Elizabeth Corby, Seattle, WA (US);
Mark Alcazar, Seattle, WA (US);
Viresh Ramdatmisier, Seattle, WA (US);
Ariel Jorge Kirsman, Bellevue, WA (US);
Andre A. Needham, Redmond, WA (US);
Akhilesh Kaza, Sammamish, WA (US);
Raja Krishnaswamy, Redmond, WA (US);
Jeff Cooperstein, Bellevue, WA (US);
Charles W Kaufman, Sammamish, WA (US);
Chris Anderson, Redmond, WA (US);
Venkata Rama Prasad Tammana, Kirkland, WA (US);
Aaron R Goldfeder, Tampa, FL (US);
John Hawkins, Duvall, WA (US);
Microsoft Corporation, Redmond, WA (US);
Abstract
Described is a technology including an evaluation methodology by which a set of privileged code such as a platform's API method may be marked as being security critical and/or safe for being called by untrusted code. The set of code is evaluated to determine whether the code is security critical code, and if so, it is identified as security critical. Such code is further evaluated to determine whether the code is safe with respect to being called by untrusted code, and if so, is marked as safe. To determine whether the code is safe, a determination is made as to whether the first set of code leaks criticality, including by evaluating one or more code paths corresponding to one or more callers of the first set of code, and by evaluating one or more code paths corresponding to one or more callees of the first set of code.