JOHN ANDREW SCARROW
Pilots at 18 St, Redmond, WA

5671445, Sep 23, 1997

Aug 2, 1995

8/510437

Stephen David Gluyas - Berlin NJ
Joseph A. Horanzy - Philadelphia PA
John L. Scarrow - Redmond WA

OKI America, Inc. - Hackensack NJ

G06F 1300

395873

A data transmission system transmits data from a first device to an interface device at a continuous rate and includes a first device for storing data and for transmitting data at a first data output rate. An interface device outputs data at a second data output rate different from the first data output rate. A preload buffer initially receives a predetermined amount of data from the first device and stores the initially received data. The preload buffer also transmits at least a portion of the initially received data at a third data output rate. The preload buffer receives additional data from the first device as the initially received data is transmitted from the preload buffer. A first buffer and a second buffer of generally equal size are sized to receive a single block of data from the preload buffer. The size of the single block of data is less than the predetermined amount of output data initially received and stored in the preload buffer. The first buffer first receives a block of data from the preload buffer and then transmits the block of data to the interface device.

2010000, Jan 7, 2010

Apr 16, 2008

12/103713

Geoff Hulten - Lynwood WA, US
Steve Rehfuss - Bellevue WA, US
Ron Franczyk - Redmond WA, US
Christopher A. Meek - Kirkland WA, US
John Scarrow - Sammamish WA, US
Andrew Newman - Redmond WA, US

MICROSOFT CORPORATION - Redmond WA

G06F 21/22

713156, 726 24, 726 22, 713188

The claimed subject matter is directed to the use of an application reputation service to assist users with minimizing their computerized machines' exposure to and infection from malware. Specifically, the claimed subject matter provides a method and system of an application reputation service that contains the reputations for elements that are known to be non-malicious as well as those known to be malicious.One embodiment of the claimed subject matter is implemented as a method to determine the reputation of an element (e.g., an application). When a user attempts to install or execute a new application, the Application Reputation Service is queried by the user's machine with a set of identities for the element. The Application Reputation Service determines the reputation of the application by referencing a knowledge base of known reputations and returns an indication (e.g., an overall rating, or a flag) of how safe that application would be to install and run on the user's computer.

8146151, Mar 27, 2012

Feb 27, 2008

12/037936

Geoff Hulten - Lynnwood WA, US
John Scarrow - Sammamish WA, US
Ivan Osipkov - Bothell WA, US
Kristofer N. Iverson - Redmond WA, US

Microsoft Corporation - Redmond WA

G06F 7/04

726 16

Safe file transmission and reputation lookup. As a part of the safe file transmission and reputation lookup methodology, a data file that is to be made available to a data file receiver is accessed and it is determined whether the data file needs to be provided a protective file. The data file is wrapped in a protective file to create a non-executing package file. Access is provided to the non-executing package file where the associated data file is prevented from being executed until data file reputation information is received.

7870609, Jan 11, 2011

Jun 29, 2007

11/772099

Geoffrey J. Hulten - Lynnwood WA, US
John L. Scarrow - Sammamish WA, US
Eliot C. Gillum - Mountain View CA, US
Kumar S. Srivastava - Redmond VA, US
Anatoliy Panasyuk - Bellevue WA, US
Ivan Osipkov - Kirkland WA, US

Microsoft Corporation - Redmond WA

G06F 11/00, G06F 12/14

726 22, 726 25

Functionality is described for addressing a threat to the security of a user device that utilizes a network-accessible service. The functionality operates by assessing the likelihood that the user device is infected by the undesirable item. When the user device makes a request to access the network-accessible service, the functionality can interact with the user device in a manner that is governed by the assessed likelihood that the user device is infected by the undesirable item.

2012016, Jun 28, 2012

Mar 5, 2012

13/412299

Geoff Hulten - Lynnwood WA, US
John Scarrow - Sammamish WA, US
Ivan Osipkov - Bothell WA, US
Kristofer N. Iverson - Redmond WA, US

Microsoft Corporation - Redmond WA

G06F 21/00

726 22

A method of safe file transmission and reputation lookup is provided. As a part of the safe file transmission and reputation lookup methodology, a data file that is to be made available to a data file receiver is accessed and it is determined whether the data file needs to be provided a protective file. The data file is wrapped in a protective file to create a non-executing package file. Access is provided to the non-executing package file where the associated data file is prevented from being executed until data file reputation information is received.

2012006, Mar 15, 2012

Sep 13, 2010

12/880363

Ritika Virmani - Seattle WA, US
Ryan C. Colvin - Bothell WA, US
Elliott Jeb Haber - Fall City WA, US
Warren G. Stevens - Redmond WA, US
Jane T. Kim - Seattle WA, US
Jess S. Holbrook - Seattle WA, US
Sarah J. Bowers - Snohomish WA, US
John L. Scarrow - Sammamish WA, US
Jeffrey R. McKune - Sammamish WA, US

MICROSOFT CORPORATION - Redmond WA

G06F 15/16

709219

A Web browser of a computing device downloads or otherwise obtains a file. File information identifying the file is obtained and is sent to a remote reputation service. Client information identifying aspects of the computing device can also optionally be sent to the remote reputation service. In response to the file information (and optionally client information), a reputation indication for the file is received from the remote reputation service. A user interface for the Web browser to present at the computing device is determined, based at least in part on the reputation indication, and presented at the computing device.

2011024, Oct 6, 2011

Apr 2, 2010

12/753841

Shawn D. Loveland - Sammamish WA, US
Geoffrey J. Hulten - Lynnwood WA, US
John L. Scarrow - Sammamish WA, US

MICROSOFT CORPORATION - Redmond WA

G06F 21/22, G06F 15/16

726 6, 709203

Access to some aspect of a service may be limited until a user has invested in performing some amount of computation. Legitimate users typically have excess cycles on their machines, which can be used to perform computation at little or no cost to the user. By contrast, computation is expensive for for-profit internet abusers (e.g., spammers). These abusers typically use all of their computing resources to run “bots” that carry out their schemes, so computation increases the abuser's cost by forcing him or her to acquire new computing resources or to rent computer time. Thus, the providers of free services (e.g., web mail services, blogging sites, etc.), can allow newly registered users to use some limited form of the service upon registration. However, in order to make more extensive use of the service, the user can be asked to prove his legitimacy by investing in some amount of computation.

2011014, Jun 16, 2011

Dec 14, 2009

12/637673

Ameya S. Bhatawdekar - Issaquah WA, US
Kristofer N. Iverson - Redmond WA, US
Elliott J. Haber - Fall City WA, US
John L. Scarrow - Sammamish WA, US
Chad W. Mills - Redmond WA, US

Microsoft Corporation - Redmond WA

G06F 21/00, G06F 15/173

709238, 726 26

A reputation based redirection service is usable to build URL wrappers for un-trusted and unknown URLs. Such URL wrappers can be used to protect Web users by, for example, redirecting traffic to interstitial Web pages. Additionally, reputation decisions can be made by the service to further protect users from malicious URLs.

8429743, Apr 23, 2013

Dec 23, 2008

12/342981

Shawn Loveland - Sammamish WA, US
Geoffrey J Hulten - Lynnwood WA, US
Elliott Jeb Haber - Fall City WA, US
John L. Scarrow - Sammamish WA, US

Microsoft Corporation - Redmond WA

G06F 21/00

726 22, 709200, 705 7, 711161

Online risk mitigation techniques are described. In an implementation, a service is queried for a reputation associated with an object from an online source in response to selection of the object. A backup of a client that is to receive the object is stored prior to obtaining the object when the reputation does not meet a threshold reputation level.