KiviCore GmbH

Protecting the FPGA bitstream may not protect the complete boot chain. Bootloaders, firmware and applications can introduce additional trust boundaries. How far does your chain of trust extend?

The Cyber Resilience Act puts software integrity on the product agenda. For FPGA-based systems, that raises a practical question: How do you establish trust from hardware to application? See where secure boot fits into the architecture.

Protecting the FPGA bitstream is only the beginning. A secure product needs a chain of trust that extends from a trusted starting point to the software that ultimately runs on the device. See how secure boot works across the complete boot chain.

What happens if your embedded system starts software it cannot trust? Secure boot establishes trust before execution from the first trusted component to the application. See where vulnerabilities can enter the boot chain.

Secure Boot should fit your system not force your system to fit the bootloader. Choose KiviBoot Tiny for a compact software-based implementation or KiviBoot Fast to accelerate cryptographic operations in FPGA hardware. One Secure Boot architecture. Different performance and resource profiles.

Planning Secure Boot for an embedded Linux system? KiviBoot-Linux is being developed to extend the chain of trust from the Root of Trust through the bootloader to the Linux system.