Developer Guide

  • 10/27/2020
  • Public Content

Intel® EPID 1.1 Provisioning Sample

This sample demonstrates how to use Intel® DAL for implementing the Intel® Enhanced Privacy ID (Intel® EPID) provisioning on a platform, meaning, to concatenate the Intel EPID group ID currently stored on the platform into the full Intel EPID algorithm's relevant data. For more information on Intel DAL security, see the Security Guidelines.
This sample is applicable for API level 4 and above.
Note: Before running the sample, make sure the server is running. To run the server, locate the SDK installation on your disk and double-click
. Then run the project.
When the platform is produced, the following are burned into it:
  • Intel EPID public group ID
  • Specific platform private key
All of the Intel EPID group members share the same Intel EPID group ID. Each platform has a unique private key.
Those two things are not enough to enable using Intel EPID for security functions (e.g., for signing and SIGMA). To use the Intel EPID feature, you need to perform the provisioning step on the platform. This step provides the platform with all the required signed data and saves the data to the flash memory.
On a real platform, provisioning is performed only once unless a new image is burned on the platform. In emulation, provisioning only needs to be performed once, unless the clear flash data checkbox is selected and the emulation is restarted.
The data is given to a platform according to its Intel EPID group ID, so the provisioning data is the same for all the Intel EPID group members. The provisioning data that the platform receives from the server is signed by Intel. The provisioning data consists of a certificate and mathematical parameters that are read from the files transferred from the server.
The files' content is signed. The last 64 bytes of each file are the signature. When the firmware receives the data, it verifies that the data was signed by Intel, decrypts the data, and saves it.
Intel EPID provisioning is a one-time process. Once the provisioning has been performed, the new stored data is used in the relevant crypto usages, such as the Intel EPID signing process and SIGMA algorithms.
The Intel EPID provisioning process is performed automatically by Intel® Capability Licensing Service version 1.47.715.0 and later (Intel Capability Licensing Service runs on the client machine as part of the Intel® Management Engine (Intel® ME) \ Intel® Trusted Execution Engine (Intel® TXE) software package).

Sample Flow

  1. The trusted application indicates whether the Intel EPID provisioning process was already performed on the platform. If the platform was not yet provisioned, you can proceed to the next steps.
  2. The trusted application provides the host application with the trusted application's platform Intel EPID group ID, thereby proving its membership in the specific Intel EPID group. When forwarded to the server, this will allow it to obtain the full provisioning data from the server.
  3. The host application sends the platform Intel EPID group ID to the server.
  4. The server generates the provisioning data, including the certificate and the mathematical parameters according to the platform Intel EPID group ID, and sends it to the host application, which forwards the information to the trusted application.
  5. The trusted application performs the Intel EPID provisioning process on the current platform, using the provisioning data it received.

Product and Performance Information


Performance varies by use, configuration and other factors. Learn more at