Intel Corporation

Symantec Corporation

David W Grawrock

James A Sutton, Ii

Willard M Wiseman

Robert J Greiner

Ioannis T Schoinas

Linda J Rankin

Kushagra V Vaid

John H Wilson

Mazin S Yousif

Ned M Smith

Clifford D Hall

Ernie F Brickell

Michael A Kozuch

Gilbert A Neiger

David I Poisner

Shawn Lohstroh

Vedvyas Shanbhogue

Jesse R Walker

Francis X Mckeen

Geoffrey S Strongin

Lawrence O Smith

Ken Reneris

Ravi S Subramaniam

Shawn R Lohstroh

William D McDonnal

Millind Mittal

Richard A Uhlig

Shreekant S Thakkar

Howard C Herbert

Roger A Golliver

Derrick Chu Lin

Steven L Grobman

Kirk D Brannock

Carl M Ellison

Robert T George

Bradley Gene Burgess

Andy Glew

Narendar Bahadur Sahgal

Joe R Gruber

William E Sobel

Andrew F Glew

Alok Kumar

Geoffrey Cooper

David Johnston

Bruce Querbach

Tieyu Zheng

Keshavan K Tiruvallur

Mark B Trobough

Joseph Frank Cihula

Chinna B Prudvi

Yuriy Bulygin

David Ott

Hermann Gartler

Madhukar Tallam

Vui Yong Liew

Alberto J Martinez

Matthew D Wood

James A Sutton

Kuo-Lang Tseng

Ashok N Kabadi

Samie B Samaan

Keith A Drescher

Jay Joseph Nejedlo

Mukesh Kataria

Lyle E Cool

James J Grealish

Russell J Wunderlich

Ramesh Thomas

Cameron W Cotrill

Abhijit Davare

Brian Meyer

David Champagne

Priyadarsan Patra

Kevin E Jones

William Penner

Ridvan A Sahan

Rahima K Mohammed

Arun R Ramadorai

Wee Hoo Cheah

Yuen Tat Lee

Kapila B Udawatta

John L Baudrexl

Christian E Iovin

Paul R Spear

Kip C Killpack

Loren James McConnell

Kyle Markley

Sarat Kompalli

Corey Malone

Matthew L King

Williard M Wiseman

Travis K Goff

Evan J Halprin

Jiun Long Foo

Minal B Patel

Aneet Chopra

Selvakumar Raja Gopal

Paul Puttonen

Neil Dobler

Nagib Z Hakim

In one embodiment, a domain controller (a) quarantines unknown devices at a first quarantine point at a first layer of a multi-layer communication model; (b) communicates with a domain name system (DNS) service to self-allocate and register a domain name with the DNS service; (c) receives a provisioning request for a first device via an access point, wherein the access point comprises a second quarantine point at a second layer of the multi-level communication model; (d) verifies a device type of the first device with the DNS service; and (e) responsive to that verification, provisions the first device into the domain. The domain controller may also send a provisioning response to the access point to enable the first device to be removed from the second quarantine point, to enable the first device to communicate with the domain controller. Other embodiments are described and claimed.

System, apparatus and method for scalable internet of things (IOT) device on-boarding with quarantine capabilities

In one embodiment, a domain controller includes a quarantine logic to quarantine unknown devices from unrestricted network access. The quarantine logic comprises a first quarantine point at a first layer of a multi-layer communication model. The domain controller also includes: a first logic to communicate with a domain name system (DNS) service to self-allocate and register a domain name with the DNS service, the domain name associated with a domain to be managed by the domain controller; a second logic to manage a group of devices of the domain; and a third logic to receive a provisioning request for a first device via an access point that comprises a second quarantine point at a second layer of the multi-level communication model. The second layer is a lower layer than the first layer, and the second quarantine point is more restrictive than the first. Other embodiments are described and claimed.

System, apparatus and method for scalable internet of things (IoT) device on-boarding with quarantine capabilities

Technologies for device commissioning include a rendezvous server to receive, from a buyer device, a request to transfer ownership of a compute device to the buyer device. The rendezvous server verifies the provenance of the compute device based on a block chain and establishes a secure session with the compute device in response to verification of the provenance. The block chain identifies each transaction associated with ownership of the compute device.

Technologies for device commissioning

In one embodiment, a domain controller includes: a quarantine logic to quarantine unknown devices from unrestricted network access, the quarantine logic comprising a first quarantine point at a first layer of a multi-layer communication model; a first logic to communicate with a domain name system (DNS) service to self-allocate and register a domain name with the DNS service, the domain name associated with a domain to be managed by the domain controller; a second logic to manage a group of devices of the domain; and a third logic to receive a provisioning request for a first device via an access point, wherein the access point comprises a second quarantine point at a second layer of the multi-level communication model. Other embodiments are described and claimed.

Techniques for implementing public key infrastructure using blockchains are described. An apparatus may receive, from a introducee principal, a proof-of-work. The apparatus may combine the proof-of-work with an identifier of the introducee principal. The apparatus may generate an introduction of the introducee principal. The introduction may include signing, using an asymmetric private key assigned to the apparatus, the combination of the proof-of-work and the identifier of the introducee principal. The apparatus may publish the introduction of the introducee principal to a blockchain.

Public key infrastructure using blockchains

Cloud container resource binding and tasking using keys is generally described herein. An example device to bind and perform tasks using cloud-based resource may include a container to claim tasks to be performed and to select and bind to a resource based on capabilities of the resource and requirements of the tasks.

Cloud container resource binding and tasking using keys

An apparatus and method is described herein for providing a test, validation, and debug architecture. At a target or base level, hardware hooks (Design for Test or DFx) are designed into and integrated with silicon parts. A controller may provide abstracted access to such hooks, such as through an abstraction layer that abstracts low level details of the hardware DFx. In addition, the abstraction layer through an interface, such as APIs, provides services, routines, and data structures to higher-level software/presentation layers, which are able to collect test data for validation and debug of a unit/platform under test. Moreover, the architecture potentially provides tiered (multiple levels of) secure access to the test architecture. Additionally, physical access to the test architecture for a platform may be simplified through use of a unified, bi-directional test access port, while also potentially allowing remote access to perform remote test and debug of a part/platform under test. In essence, a complete test architecture stack is described herein for test, validation, and debug of electronic parts, devices, and platforms.

Test, validation, and debug architecture

A method and apparatus for initiating secure operations in a microprocessor system is described. In one embodiment, one initiating logical processor initiates the process by halting the execution of the other logical processors, and then loading initialization and secure virtual machine monitor software into memory. The initiating processor then loads the initialization software into secure memory for authentication and execution. The initialization software then authenticates and registers the secure virtual machine monitor software prior to secure system operations.

System and method for execution of a secured environment initialization instruction

Technologies for secure presence assurance include a computing device having a presence assertion circuitry that receives an input seed value and generates a cryptographic hash based on the received input seed value. The computing device further verifies the integrity of the presence assertion circuitry based on the generated cryptographic hash.

Technologies for secure presence assurance

In one embodiment of the present invention, a method includes verifying a master processor of a system; validating a trusted agent with the master processor if the master processor is verified; and launching the trusted agent on a plurality of processors of the system if the trusted agent is validated. After execution of such a trusted agent, a secure kernel may then be launched, in certain embodiments. The system may be a multiprocessor server system having a partially or fully connected topology with arbitrary point-to-point interconnects, for example.

Launching a secure kernel in a multiprocessor system

Technologies for monitoring protected functionality of an integrated circuit device include an integrated circuit device having a protected function module. The protected function module includes a modifiable security device. When the protected function module is activated or powered up, an attribute of the modifiable security device is irreversibly modified. The integrated circuit device may be a processor, and the protected function module may be a debug module of the processor. The modifiable circuit device may be an oscillator. The frequency of the oscillator may change when the oscillator is powered due to oscillator aging. The integrated circuit device may be included in a computing device. The integrated circuit device may expose data indicative of the attribute of the modifiable security device to firmware or software of the computing device. The data may be exposed through a cryptographically signed, firmware-readable memory space. Other embodiments are described and claimed.

Technologies for protected hardware function monitoring and forensics

An embodiment provides a level of assurance regarding correct operation of software. An embodiment creates baseline and real-time measurements of software and compares the measurements to determine whether the software is operating correctly. An application provider may include 'tracing elements' in target software application. While producing the application the trace elements are detected and provide trace events, which collectively provide a 'baseline trace' indicating proper application execution. The provider supplies the application and the baseline trace to a user. The user operates the application in real-time to produce a &#x201c;real-time trace&#x201d; based on the application still having trace elements that produce trace events (which collectively form the &#x201c;real-time&#x201d; trace). A comparator compares the baseline and real-time traces. If the traces are within a pre-determined range of each other the user has a level of assurance the software is operating correctly. Other embodiments are included herein.

System and method for determining correct execution of software based on baseline and real time trace events

Growing community of inventors

Aloha, OR, United States of America

David W Grawrock