What is it about?
Many modern electronic devices, from cars to satellites to data centers, rely on a special kind of computer chip called an FPGA. Unlike ordinary chips, an FPGA can be rewired by loading a configuration file, much like installing software, which makes it flexible but also creates unique security risks: if attackers steal or tamper with that file, they can copy a company's design or hide malicious functions inside it. Newer "system-on-chip" FPGAs also include a full processor on the same chip, which adds convenience but opens even more doors for attackers. This article reviews more than a decade of research on how these chips can be attacked, from power-consumption snooping to laser fault injection, and how those attacks can be prevented. It then organizes this knowledge into a step-by-step strategy that engineers can follow to identify the threats that matter for their product and choose the right defenses.
Featured Image
Photo by Yannick Pipke on Unsplash
Why is it important?
FPGAs are increasingly deployed in places where security failures have serious consequences: cloud computing platforms, telecommunications, industrial control, medical devices, and defense systems. Yet the built-in protections offered by manufacturers, such as encryption and authentication, have repeatedly been broken by researchers, and the newer system-on-chip FPGAs are too complex for any single off-the-shelf protection to cover. What makes this work unique is that it goes beyond cataloguing attacks: it rates each attack vector by how much time, expertise, and equipment an attacker realistically needs, and it provides a ready-made threat model specifically adapted to system-on-chip FPGAs. This gives developers a practical, prioritized starting point for securing their designs, something previous surveys did not offer, and it is timely as these devices spread into systems that must operate unattended for years without physical protection or easy security updates.
Perspectives
Working on this survey made it clear to me how wide the gap is between traditional IT cybersecurity, which is a mature discipline, and the security of embedded hardware like FPGAs, where developers are often left to fend for themselves. The most striking lesson was that even sophisticated manufacturer security features have been repeatedly defeated, so real security comes from a methodical, threat-driven design process rather than from any single feature. My hope is that this article serves as both a reference and a starting point: that developers use the threat model to reason about their own products, and that manufacturers move toward more open, scrutinizable designs so the research community can help find weaknesses before attackers do.
Alexandre Proulx
Universite Laval
Read the Original
This page is a summary of: A Survey on FPGA Cybersecurity Design Strategies, ACM Transactions on Reconfigurable Technology and Systems, March 2023, ACM (Association for Computing Machinery),
DOI: 10.1145/3561515.
You can read the full text:
Contributors
The following have contributed to this page
