2018
DOI: 10.1109/tc.2016.2646367
|View full text |Cite
|
Sign up to set email alerts
|

Bitstream Fault Injections (BiFI)–Automated Fault Attacks Against SRAM-Based FPGAs

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
36
0

Year Published

2018
2018
2023
2023

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 44 publications
(36 citation statements)
references
References 18 publications
0
36
0
Order By: Relevance
“…Moreover, virtualization techniques for FPGAs need to provide security not only for network and memory access but also for the compute substrate itself, as it opens up to new types of attacks. For example, a malicious bitstream can potentially damage an FPGA [85] or crash the system until power cycle reset [86] or perform a side channel attack [87], [88]. To mitigate these types of attacks, FPGA specific solutions need to be designed (e.g., a configuration controller to identify and block malicious bitstreams).…”
Section: Trends and Future Directionsmentioning
confidence: 99%
“…Moreover, virtualization techniques for FPGAs need to provide security not only for network and memory access but also for the compute substrate itself, as it opens up to new types of attacks. For example, a malicious bitstream can potentially damage an FPGA [85] or crash the system until power cycle reset [86] or perform a side channel attack [87], [88]. To mitigate these types of attacks, FPGA specific solutions need to be designed (e.g., a configuration controller to identify and block malicious bitstreams).…”
Section: Trends and Future Directionsmentioning
confidence: 99%
“…If no proper integrity checking mechanism is implemented for the encrypted bitstreams, bitstreams are vulnerable to fault injections as well, as the adversary can flip any arbitrary bits of the bitstream to inject a fault into the computation of the application [80]. Moreover, BBRAMs and eFuses of SRAM-based FPGAs, as well as flash memory of CPLDs and flash-based FPGAs could be vulnerable to semi-and fully-invasive attacks [88].…”
Section: Problem Statementmentioning
confidence: 99%
“…The power-up configuration process associated with fielded systems first determines whether the external bitstream includes an encrypted-bitstream indicator, and if so, decrypts the bitstream using cipher block chaining (CBC) mode of AES. To prevent fault injection attacks [5], Xilinx authenticates configuration data as it is loaded. In particular, a 256-bit keyed hashed message authentication code (HMAC) of the bitstream is computed, using SHA-256 to detect tamper and to authenticate the sender of the bitstream.…”
Section: Overview Of a Secure Boot Under Xilinxmentioning
confidence: 99%
“…For example, a technique that manipulates cryptographic components embedded in the bitstream as a strategy to extract secret keys is described in [4]. A fault injection attack on an FPGA bitstream is described in [5] to accomplish the same goal, where faulty cipher texts are generated by fault injection and then used to recover the keys. A hardware Trojan insertion strategy is described in [6] that is designed to weaken FPGA-embedded cryptographic engines.…”
Section: Introductionmentioning
confidence: 99%