Google Inc.

Adobe, Inc.

Adrian L Ludwig

Curtis Gerald Condra

Nicholas Neil Kralevich, Iv

Kenneth Root

Alexander James Faaborg

Richard G Cannings

Curtis Gerald Condra, Iv

Sebastian Johannes Porst

Colin Cross

Tal Dayan

Charles E Gotlieb

Randall Sarafa

Maya Ben Ari

Robert J Greenwalt, Iii

Mayank Dutt Upadhyay

Winthrop Lyon Saville, Iii

Jake Hamby

Nico Falliere

Joseph Benjamin Gruver

Jonathan Bruce Larimer

Peter Valchev

Richard Cannings

Mayank Upadhyay

Nicholas Kralevich

Nicholas Neil Kralevich Iv

A user-provided keystore may be utilized in a boot process to verify a boot image as disclosed herein. A device may be determined to be in a locked or verified state. A selected keystore may be determined to not verify against a first key such as a root key. A user may provide a keystore to a device. The system may display a prompt to the user which asks whether the user would like to continue to boot or not, if the system determines that the keystore does not verify against the first key. The user may respond to the prompt by indicating a desire to continue booting. The system may determine that the boot image verifies against the keystore and finish booting the device. Thus, the prompt may alert the user to a threat to the integrity of the boot process or device.

Verifying boot process of electronic device

Systems and techniques are provided for dynamic authorization. A signal may be received from a sensor. A concept may be determined from the signal. The concept may be a location of a computing device, an action being performed with the computing device, an identity of a user of the computing device, or a temporal context for the computing device. A current pattern may be determined from the concept. The current pattern may be matched to a stored pattern. The stored pattern may be associated with a security outcome. The security outcome may be sent to be implemented. A security message may displayed indicating the security outcome and part of the stored pattern that was matched to the current pattern. The security outcome may be causing presentation of an authentication prompt or not causing presentation of an authentication prompt.

Dynamic authorization

A method for updating configuration information includes, in a computing device including a processor, memory, and an operating system, initiating an update to at least one configuration setting of the computing device. The update may be downloaded from at least one update data source. The update may include configuration update data and configuration update metadata. The update may be verified by comparing the configuration update metadata with metadata associated with a current version of the at least one configuration setting. The update may be installed if it is verified. The update to the at least one configuration setting may be installed based on an intent from an unsecure component of the computing device. The unsecure component may include content consuming application installed on the device, a component of a computing platform of the device, and/or an update-seeker application installed on the device.

Configuration file updater

Verified boot

A device includes at least one processor, a messaging service operable by the at least one processor to determine whether an outgoing message is a likely premium message, and a user interface module operable by the at least one processor to responsive to determining that outgoing message is the likely premium message, output, for display, a prompt for confirmation to send the outgoing message to a likely premium code, and receive an indication of input detected within the prompt for confirmation. The module is further operable by the at least one processor to selectively send, based at least in part on the received indication of the user input, the outgoing message to the likely premium code.

Premium messaging challenges

A method may include, in a computing device including a processor, memory, an operating system, and at least one installed application, detecting an attempted exploitation of at least one known vulnerability associated with the device. The attempted exploitation may be logged. At least one remedial action may be performed on the device based on the logged attempted exploitation. The known vulnerability may be associated with the operating system and/or the at least one installed application. The at least one known vulnerability may include one or more of at least one known coding flaw in the operating system or in the at least one installed application, at least one known weakness in a protocol running on the computing device, a known family of coding flaws in the operating system or in the at least one installed application, an unauthorized triggering of premium SMS services, and/or triggering of a hostile misconfiguration.

Software exploit detection

An application distribution server may be operable to perform an application distribution process for an application, where the application distribution process may comprise a plurality of phases. The plurality of phases may comprise, in sequence, a developer account creation phase, a risk assessment phase, an application upload phase, an application publication phase, an application promotion phase and an application download phase. The application distribution server may detect, at each of the plurality of phases, whether a particular behavior corresponding to use of the application to distribute undesirable software may occur. In instances when an occurrence of the particular behavior is detected at a certain phase in the application distribution process, the application distribution server may continue, utilizing a trap system, one or more subsequent phases after the certain phase for the application, without communicating information on the detection of the occurrence of the particular behavior.

Using a honeypot workflow for software review

The present disclosure provides a system and method for a mobile device to run an application that requires one or more permissions. The mobile device may comprise a screen and a processor. The one or more permissions may be displayed graphically on the screen prior to the application being installed by the processor.

Grouping and ranking of application permissions

Systems, methods, routines and/or techniques for time delay on services (e.g., verification services) that detect undesirable content are described. In some embodiments, a flexible verification service prevents users (e.g., hackers) from using the verification service 'as an oracle' to predict whether the user's application or software program will be detected by the verification service. The verification service, after receiving a verification request from a client device, may delay or prevent the communication of a verification response to the client device. The verification service may evaluate a verification request to determine a level of risk associated with the request. The verification service may communicate an initial response to the client device that submitted the verification request. The verification service may eventually communicate the verification response to the client device, for example, after a period of delay.

Detecting undesirable content

A system and method attempts to access a portable electronic document using different methods depending on whether the user attempting access is in front of, or behind, a firewall.

System and method for providing document security, access control and automatic identification of recipients

Growing community of inventors

Atherton, CA, United States of America

Adrian L Ludwig