Intel Corporation

Mateusz Bronk

Arkadiusz Berent

Piotr Zmijewski

Krystian Matusiewicz

Various examples relate to apparatuses, methods, and computer programs for executing an executable, and to a method for distributing software or firmware. An apparatus for executing an executable comprises interface circuitry, machine-readable instructions, and processing circuitry for executing the machine-readable instructions to identify, for the executable, a trigger to activate or deactivate a noise injection mode during execution of the executable, the noise injection mode being suitable for introducing noise during execution of the executable, and activate or deactivate the noise injection mode based on the identified trigger.

Apparatuses, methods and computer programs for executing an executable, and method for distributing software or firmwares

A system and method of authenticating a development environment include receiving, by one or more processors associated with a source code repository, a development profile from a development environment. Sending the development profile to a trusted profile verifier to be registered as a trusted development profile. Receiving a pending source file commit request, where the pending source file commit request includes source code files and a current development profile. Facilitating verification of whether the current development profile matches the trusted development profile. When it is verified that the current development profile matches the trusted development profile, accepting the source code files.

Trusted profile of a developer and development environment to protect software supply chain

A method comprises generating, during a software build process conducted in a trusted build environment, a trusted log comprising a plurality of records of actions performed during the software build process and a plurality of identifiers of tools used to perform the actions, aggregating the plurality of records of actions and the plurality of identifiers into a build certificate file, generating a digital signature to be applied to the build certificate, and publishing the build certificate in association with one or more build artifacts generated by the software build process.

Protecting software supply chain using secure log generated in a trusted build environment

The disclosed embodiments enable applying production nature to a software signature post-build (or even post-release), where the signature type is determined by the existence of a production-signed intermediate CA certificate—either hosted in the cloud (for pure release immutability), or re-ingested into the package (if certain modification are allowed). This allows a so-called deferred issuance of the product release. Even if the CA certificate is to be reinserted into the package, this modification likely affects only the delivery shell (e.g., installer) and may not require format-specific binary changes of, possibly heterogeneous, artifacts therein.

Method, system and apparatus for delayed production code signing for heterogeneous artifacts

Methods, apparatus, systems and articles of manufacture are disclosed to facilitate distributed data backup. An example apparatus includes a controller to detect a trigger event for a distributed backup mode; and, in response to detection of the trigger event, trigger the distributed backup mode. When in the distributed backup mode, the controller of the example apparatus is to identify one or more receiving devices within communication range of the apparatus available to receive a data backup from the apparatus. The example apparatus includes a data distributor to distribute data from the apparatus among the one or more receiving devices. The controller of the example apparatus is to confirm receipt of the distributed data by the one or more receiving devices.

Methods and apparatus to facilitate distributed data backup

Various aspects are related to a traffic management system that may include: a token issuer associated with a first traffic-managing infrastructure, a token collector associated with a vehicle, and a token verifier associated with a second traffic-managing infrastructure, wherein the token issuer is configured to issue one or more tokens, wherein the token collector is configured to collect the one or more tokens when the vehicle is in a vicinity of the first traffic-managing infrastructure and send the one or more collected tokens to the token verifier when the vehicle is in a vicinity of the second traffic-managing infrastructure, wherein the token verifier is configured to trigger a control of the second traffic-managing infrastructure based on the one or more collected tokens.

Traffic management system, components of a distributed traffic management system, prioritization/load-distribution system, and methods thereof

Technologies for securely exchanging sensor information include an in-vehicle computing system of a vehicle to establish a trusted execution environment and a secure communication channel between the trusted execution environment and a corresponding trusted execution environment of a coordination server. A private key is bound to the trusted execution environment of the in-vehicle computing system. The in-vehicle computing system confirms the authenticity of the coordination server, receives sensor data generated by a sensor of the vehicle, and generates an attestation quote based on the trusted execution environment of the in-vehicle computing system. The in-vehicle computing system further transmits, to the coordination server over the secure communication channel, the sensor data, the attestation quote, and a cryptographically-signed communication signed with the private key.

Securely exchanging vehicular sensor information

An embodiment includes a method executed by at least one processor of a member computing node comprising: establishing a communication channel with a verifier computing node, the member computing node and the verifier computing node each coupled to a respective charging coil; determining a group of devices approved for charging with the verifier computing node; determining the member computing node is a member of the group of devices; authenticating the member computing node to the verifier computing node; in response to authenticating the member computing node to the verifier computing node, inductively charging the member computing node based on a magnetic field produced by the verifier computing node. Other embodiments are described herein.

Growing community of inventors

Gdansk, Poland

Mateusz Bronk