PMU V3: Secure Bitstream Loader

Getting Started

1. Checkout the repository

git clone --recursive [email protected]:lnis-uofu/FPGA_Secured_Bitstream.git
cd FPGA_Secured_Bitstream

2. Setup the environment variables in a csh/tcsh shell

source setup_enc.csh

Introduction

The Programmign Management Unit will serve as a macro that can be placed near a FPGA to handle bitstream loading. While the primary functonalty of the PMU is to load a bitstream into an FPGA Core it will also incoroporate some hardware security and data integrity features. This is in reponse to the need for OpenFPGA to be able to incoporate some hardware security IPs to its FPGA design framework. As of today the PMU version 3 is capable of 8 instructions for loading a bistream with the options of using AES encription and/or SHA authentication. The FSM contained in this macro intreprets a serially encoded "pmu header" that is appened to a plaintext bitstream, ciphertext bitstream, or cipher key. This version of the PMU also features some testing features encure accurate loading of the correct bitsteam to the FPGA core. With that, the final version of the PMU will resembel a RISC-V core that incorporates all the features of the previous PMU versions as well as other features such as programming multiple FPGA configuration chains and post fabrication updates.

Programming Management Unit: PMU

Version 3

PMU V3 consists of a JTAG Tap Controller, PMU FSM, with SHA and AES interfaces. Version 3 incoportates AES for bitstream encryption and SHA for bitstream data integrity and user authentication. Since PMU version 3 was implemented as a test chip the hierarchial overview of the test chip is shown in Figure 2 and mored detailed organizatioin of the blocks within the PMU are presented later in the README.

PMU Instructions/Encoding Scheme

Since the PMU is capable of using AES and SHA separately or combined, it creates the need for several encoding schemes. For example, if you want to load a bitstream without utilizing any of the PMUs security features, the instruction header can be reduced to only contain the instruction. This is to avoid any extra informationi being left in the bitstream, which could include information like public/private key combinitations for asymetric cipher blocks. Since almost all 7 instructions have a unique encoding format, each instruction will be listed here with the appropriate bitstream encoding mechanisms. The names of the instructions reflect their operation can be categorized as: loading a key, loading a bitstream, or pushing the bitstream from the fpga core. With that AES or SHA engines can be used to improve the security achieved in each category. For example the PMU can load a key without AES or SHA and then use both cipher cores when loading the bitstream to ensure its authenticy and protect the plain text bitstream. Then using the "push bitstream" instruction the user can read out the plaintext value loaded into the FPGA core. This instructions is solely for testing purposes and would not be implemented in anything but a testchip. Instruction binary values chosen such that the done resemble and common brute force attacks like sending a string of alternating values. ie. '10101'.

INSTRUCTIONS

LOAD_KEY & LOAD_BITSTREAM

These instructions utilize the PMU to move data to the FPGA and key storage without the use of AES of SHA.

LOAD_KEY_SHA & LOAD_BITSTREAM_SHA

Employs sha256 to verifiy the user and the integrity of the key/bitstream data.

LOAD_BITSTREAM_AES

Bitstream data is encoded with aes128 only and is decrypted on the fly at FPGA configuration.

LOAD_BITSTREAM_SHA_AES

This instruction uses both encipherment approaches to encode and authenticate the bitstream data.

PUSH_BITSTREAM

Testing feature to move the contents of the FPGA core to and output of the PMU such that the data in the configuration chain can be observed externally.

Note on Key Storage

Due to the limitations of the skywater130 pdk PMU v3 uses registers to store the AES key. Ideally this key would be stored in a custom 128b ePROM/FLASH write only memory or the another key manage approach would be to utilize a rolling AES key as has been done in Xillinx FPGAs. From a hardware security perspective cipher key storage is considered one of the biggest weaknesses of a system. However, the scope of the project ends at key management techniques as this aspect of the design could be left to another research project.

Scripts

Included there is a python script used to generate the bitstream with the encoding scheme and. This python script can be used as a temlplate to generate similar encdoded bitstreams. This script is called in the pmu/testbench directory by make to support verilog testbenchs and generate a unique encoded bitstream for each instruction. The user needs to define the bitstream and aes/sha keys in the scripts/inputs files.

Testing

Information about testing is here in the testbench/README.md file.

Dependencies

TO-DO

• Unit Testing
• Dependencies

Acknoledgements

• MAC_unit_systolic: Repository Organization
• JTAG: JTAG implementation from OpenCores
• AES: AES-128b
• SHA: SHA-256b