Intel® Stratix® 10 Device Security User Guide

Download
ID 683642
Date 11/09/2021
Public

A newer version of this document is available. Customers should click here to go to the newest version.

Document Table of Contents
Document Table of Contents x
1. Intel Stratix 10 Device Security Overview 2. Authentication and Authorization 3. AES Bitstream Encryption 4. Device Provisioning 5. Advanced Features 6. Intel® Stratix® 10 Device Security User Guide Archives 7. Document Revision History for Intel® Stratix® 10 Device Security User Guide
1. Intel Stratix 10 Device Security Overview x
1.1. Commitment to Product Security
2. Authentication and Authorization x
2.1. Creating a Signature Chain 2.2. Signing a Configuration Bitstream
2.1. Creating a Signature Chain x
2.1.1. Creating Authentication Key Pairs on the Local Filesystem 2.1.2. Creating Authentication Key Pairs in SoftHSM 2.1.3. Creating the Signature Chain Root Entry 2.1.4. Creating a Signature Chain Public Key Entry
2.2. Signing a Configuration Bitstream x
2.2.1. Quartus Key File Assignment 2.2.2. Co-Signing SDM Firmware 2.2.3. Configuring Bitstream Signing Using the quartus_sign Command 2.2.4. Verifying Configuration Bitstream Signature Chains
3. AES Bitstream Encryption x
3.1. Creating the AES Root Key 3.2. Quartus Encryption Settings 3.3. Encrypting a Configuration Bitstream
3.3. Encrypting a Configuration Bitstream x
3.3.1. Configuration Bitstream Encryption Using the Programming File Generator Graphical Interface 3.3.2. Configuration Bitstream Encryption Using the Programming File Generator Command Line Interface 3.3.3. Partially Encrypted Configuration Bitstream Generation Using the Command Line Interface 3.3.4. Partial Reconfiguration Bitstream Encryption
4. Device Provisioning x
4.1. Using SDM Provision Firmware 4.2. Authentication Root Key Provisioning 4.3. Programming Key Cancellation ID Fuses 4.4. Security Setting Fuse Provisioning 4.5. AES Root Key Provisioning 4.6. Converting Owner Root Key, AES Root Key Certificates, and Fuse files to Jam STAPL File Formats
4.5. AES Root Key Provisioning x
4.5.1. AES Root Key Compact Certificate 4.5.2. Intrinsic ID® PUF AES Root Key Provisioning 4.5.3. Black Key Provisioning
4.5.2. Intrinsic ID® PUF AES Root Key Provisioning x
4.5.2.1. Intrinsic ID PUF Enrollment 4.5.2.2. Wrapping the AES Root Key 4.5.2.3. Programming Helper Data and Wrapped Key to QSPI Flash Memory 4.5.2.4. Querying Intrinsic ID PUF Activation Status 4.5.2.5. Location of the PUF in Flash Memory
4.5.3. Black Key Provisioning x
4.5.3.1. Black Key Provisioning Options
5. Advanced Features x
5.1. Secure Debug Authorization 5.2. HPS Debug Certificates 5.3. Platform Attestation 5.4. Physical Anti-Tamper 5.5. Using Design Security Features with Remote System Update
5.4. Physical Anti-Tamper x
5.4.1. Anti-Tamper Responses 5.4.2. Anti-Tamper Detection 5.4.3. Anti-Tamper Lite Intel® FPGA IP
5.4.3. Anti-Tamper Lite Intel® FPGA IP x
5.4.3.1. Release Information
1. Intel Stratix 10 Device Security Overview
2. Authentication and Authorization
3. AES Bitstream Encryption
4. Device Provisioning
5. Advanced Features
6. Intel® Stratix® 10 Device Security User Guide Archives
7. Document Revision History for Intel® Stratix® 10 Device Security User Guide

4.5.2.2. Wrapping the AES Root Key

You generate the IID PUF wrapped AES root key (.wkey) file by sending a signed certificate to the SDM.

You can use the Intel® Quartus® Prime Programmer to automatically generate, sign, and send the certificate to wrap your AES root key, or you may use the Intel® Quartus® Prime Programming File Generator to generate an unsigned certificate. You sign the unsigned certificate using your own tools or the Quartus signing tool. You then use the Programmer to send the signed certificate and wrap your AES root key. The signed certificate may be used to program all devices that can validate the signature chain.

Figure 7. Wrapping the AES Key Using the Intel® Quartus® Prime Programmer
  1. You may generate the IID PUF wrapped AES root key (.wkey) with the Programmer using the following arguments:
    • The .qky file containing a signature chain with AES root key certificate permission
    • The private .pem file for the last key in the signature chain
    • The .qek file holding the AES root key
    • The 16-byte initialization vector (iv) 
    quartus_pgm -c 1 -m jtag --qky_file=aes0_sign_chain.qky \
--pem_file=aes0_sign_private.pem --qek_file=aes.qek \
--iv=1234567890ABCDEF1234567890ABCDEF -o "ei;aes.wkey;1SX280LH2"
  2. Alternatively, you may generate an unsigned IID PUF wrapping AES root key certificate with the Programming File Generator using the following arguments: 
    quartus_pfg --ccert -o ccert_type=IID_PUF_WRAPPED_AES_KEY \
-o qek_file=aes.qek --iv=1234567890ABCDEF1234567890ABCDEF unsigned_aes.ccert
  3. You sign the unsigned certificate with your own signing tools or the quartus_sign tool using the following command: 
    quartus_sign --family=stratix10 --operation=sign \
--qky=aes0_sign_chain.qky --pem=aes0_sign_private.pem \
unsigned_aes.ccert signed_aes.ccert
  4. You then use the Programmer to send the signed AES certificate and return the wrapped key (.wkey) file: 
    quarts_pgm -c 1 -m jtag --ccert_file=signed_aes.ccert \
-o "ei;aes.wkey;1SX280LH2"
    Note: The i operation is not necessary if you previously loaded the provision firmware helper image, for example, to enroll the PUF.
Level Two Title

Did you find the information on this page useful?

Characters remaining:

Feedback Message