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

5.1. Secure Debug Authorization

To enable Secure Debug Authorization, the debug owner needs to generate an authentication key pair and use the Intel® Quartus® Prime Pro Programmer to generate a device information file for the device that runs the debug image: 
quartus_pgm -c 1 -m jtag -o “ei;device_info.txt;1SX280HH1” --dev_info
The debug owner transfers the generated authenticated public key and device information to the device owner. The device owner uses the quartus_sign tool or the reference implementation to append a conditional public key entry to a signature chain intended for debug operations using the public key from the debug owner, the necessary authorizations, the device information text file, and applicable further restrictions. 
quartus_sign --family=Stratix10 --operation=append_key \ 
--previous_pem=debug_chain_private.pem --previous_qky=debug_chain.qky \ 
--permission=0x6 --cancel=1 \ 
--dev_info=device_info.txt --restriction=”1,2,17,18” \  
debug_authorization_public_key.pem secure_debug_auth_chain.qky
The device owner sends the full signature chain back to the debug owner, who uses the signature chain and their private key to sign the debug image. 
quartus_sign --family=Stratix10 --operation=sign \ 
--qky=secure_debug_auth_chain.qky --pem=debug_authorization_private_key.pem \
unsigned_debug_design.rbf authorized_debug_design.rbf
The debug owner can then program the securely authorized debug design. 
quartus_pgm -c 1 -m jtag -o “p;authorized_debug_design.rbf”

The device owner may revoke the secure debug authorization by canceling the explicit key cancellation ID assigned in the secure debug authorization signature chain.

Level Two Title

Did you find the information on this page useful?

Characters remaining:

Feedback Message