Google Inc.

Timothy Jay Chen

Scott David Johnson

Marius P Schilder

Derek L Martin

Eunchan Kim

Michael Stefano Fritz Schaffner

Benjamin Charles Serebrin

Behnoosh Hariri

Christopher Gori

Ali Abdelhadi

Harrison Pham

Miguel Angel Osorio Lozano

Ziv Hershman

Miguel Angel Osorio

Mark Hayter

Dominic Rizzo

Thomas Edward Roberts

Trevor Scott Bunker

Konstantin Yakovlev

Zifan Xiang

Thomas Fahrni

Remi Wesley Ogundokun

Michael Kaeser

Lars Krüger

Lara Scheidegger

Beixi Li

Barak Ben Noon

William Joshua Billingham

Stephan Burkhardt

Rupert James Swarbrick

Gregory Andrew Chadwick

Philipp Wagner

This document describes systems and techniques for deriving identity and root keys for embedded systems. In aspects, a boot process and key manager of an embedded system may implement a secure or trusted boot process for embedded systems in which code of next-level boot loader or software image is verified using root keys or other protected information before execution of the boot process is passed to the next stage in the boot process. Alternatively or additionally, the key manager may enable sealing and attestation of various levels of root and identity keys to enable respective verification of software or hardware throughout a life cycle of a device to prevent unauthorized access to protected or private code of an embedded system. By so doing, the described aspects may enable an embedded system with a secure boot process and robust identity and root key management system.

Deriving identity and root keys for embedded systems

Techniques are described herein for providing people suggestions in collaborative online text editors. A method includes: receiving user interface input that corresponds to a document in a document editing application; automatically parsing the received user interface input to identify a name included in the user interface input; in response to identifying the name included in the user interface input, providing an option to create a link in the document between the name and a corresponding contact in a contact store; receiving additional user interface input that indicates acceptance of the option to create the link in the document; and in response to receiving the additional user interface input, automatically creating the link in the document between the name and the corresponding contact in the contact store.

People suggestion in collaborative online text editors

An integrated circuit chip can provide protection with registers of a register file. A processor can be part of general or security-oriented (e.g., root-of-trust (RoT)) circuitry. In described implementations, the processor includes multiple register blocks for storing multiple register values. The processor also includes multiple integrity blocks for storing multiple integrity codes. A respective integrity block is associated with a respective register block. The respective integrity block can store a respective integrity code that is derived from a respective register value that is stored in the respective register block. The integrity code can enable detection or correction of one or more corrupted bits in the register value. An integrity controller of the processor can monitor the register value regularly or in response to an access by an execution unit. The controller can take a protective action if corruption is detected. This enables information protection to extend to processor execution units.

Register file protection

An IC chip can provide silicon root of trust (RoT) functionality. In described implementations, the IC chip includes a processor, an interconnect, and multiple peripheral devices. These comportable circuit components are designed to facilitate interoperability and consistent, expected communications for security circuitry. Each peripheral device includes an interface that adheres to a common framework for interacting with the processor and with other peripheral devices. The interface includes an interconnect interface coupling the peripheral device to the interconnect and an inter-device interface coupling the peripheral device to at least one other peripheral device. The peripheral device is realized based on a peripheral device design code that indicates inter-device signaling in accordance with an inter-device scheme of an interface specification. Manufacturers fabricate the peripheral device, based on the design code, to be physically and logically coupled to another peripheral device in a predictable manner. This fosters more-robust and reliable security circuitry.

Peripheral device comportability with security circuitry

A skin graft tool can cut a skin graft at a desired thickness and width, as desired. A skin punch is provided to cut a perimeter around the area of the skin to be cut for the graft, and a fenestrator tool is provided to fenestrate the cut graft skin material prior to applying to a graft site.

Skin graft harvester

Identity and root keys derivation scheme for embedded devices

In some implementations, a method includes receiving user input indicating a request to create a task and presenting a visual representation of the task. The method can also include receiving user input indicating an assignment of the task to an assignee, sending, to a second application, a first notification indicating the task and the assignment of the task to the assignee. It can further include receiving, from the second application, a second notification indicative of a change to a status of the task, and modifying the visual representation of the task to graphically illustrate the change in the status of the task in the user interface of the first application.

Embedded tasks in collaborative productivity suite

Systems, apparatuses, and methods for improving security of a silicon-based system by creating a glitch-resistant process for executing a software code block on the silicon-based system are disclosed. An example method may begin by marking the software code block as non-executable. Second, intent to execute the software code block is registered with a staging register. Third, the software code block is compressed into a compression constant. Fourth, the compression constant is compared with a first predetermined value using two comparators. Fifth, responsive to the comparators providing a true result after comparison, the software code block is marked as executable to allow the software code block to execute. In another aspect, the example method may be repeated for n>1 iterations, and in each iteration i, an ith software code block is compressed into an ith compression constant that is compared to an ith predetermined value.

Secure code jump and execution gating

An IC chip can provide silicon root of trust (RoT) functionality. In described implementations, the IC chip includes a processor, an alert handler, and multiple peripheral devices, which generate alert indications. The alert handler processes the alert indications, which have security implications. The alert handler includes multiple alert receiver modules to communicate with the multiple peripheral devices. The alert handler also includes a controller, multiple accumulation units, multiple escalation timers, and multiple escalation sender modules. These components can be organized into a hierarchy of increasing escalation severity. In operation, the controller classifies an alert and flexibly implements an adaptable alert handler path that is established through the escalation components responsive to the classification and based on a source of the alert. A path can conclude with an escalation sender module commanding an escalation handler to implement a security countermeasure. The flexible paths can therefore handle different types of alerts.

Alert handling

This document includes techniques, apparatuses, and systems related to an interface for revision-limited memory, which can improve various computing aspects and performance. In aspects, confidentiality, integrity, and availability may be ensured while increasing the performance of revision-limited memory. In this example, the techniques also enable the digital computing device to interact with information related to the revision-limited memory.

Interface for revision-limited memory

Systems, apparatuses, and methods for improving security of a silicon-based system by creating a glitch-resistant process for executing a software code block on the silicon-based system are disclosed. An example method may begin by marking the software code block as non-executable. Second, intent to execute the software code block is registered with a staging register. Third, the software code block is compressed into a compression constant. Fourth, the compression constant is compared with a first predetermined value using two comparators. Fifth, responsive to the comparators providing a true result after comparison, the software code block is marked as executable to allow the software code block to execute. In another aspect, the example method may be repeated for n&#x3e;1 iterations, and in each iteration i, an ith software code block is compressed into an ith compression constant that is compared to an ith predetermined value.

A semiconductor chip device include device state fuses that may be used to configure various device states and corresponding security levels for the semiconductor chip as it transitions from wafer manufacturing to provisioned device. The device states and security levels prevent the semiconductor chip from being accessed and exploited, for example, during manufacturing testing. A secure boot flow process for a semiconductor chip over its lifecycle is also disclosed. The secure boot flow may start at the wafer manufacturing stage and continue on through the insertion of keys and firmware.

Secure device state apparatus and method and lifecycle management

Systems, apparatuses, and methods for signing, and verifying the signature of, code to be executed by a target device. An example method of determining a verification hash of a code image to be executed by a target device comprises receiving a header and code image, determining an image hash based on metadata and the code image, determining a fuses hash based on values of hardware fuses of the target device, determining an information hash based on information stored in memory, determining a verification hash based on the image hash, the fuses hash, and the information hash, verifying the verification hash against a code signature in the header, obtaining an unlock constant based on the verification hash, comparing the unlock constant with a stored predetermined value to unlock a memory region of the target device, and executing the code in the code image on the target device.

Growing community of inventors

Pleasanton, CA, United States of America

Timothy Jay Chen