2008 International Conference on Field Programmable Logic and Applications 2008
DOI: 10.1109/fpl.2008.4629951
|View full text |Cite
|
Sign up to set email alerts
|

Secure FPGA configuration architecture preventing system downgrade

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
13
0

Year Published

2009
2009
2024
2024

Publication Types

Select...
3
3
1

Relationship

1
6

Authors

Journals

citations
Cited by 22 publications
(13 citation statements)
references
References 6 publications
0
13
0
Order By: Relevance
“…• Only the freshest updates must be allowed to prevent an attacker from reusing old updates [46]. We have already shown that our design flow can ensure integrity, authenticity, and confidentiality for SWIP.…”
Section: A Software Updatementioning
confidence: 99%
See 1 more Smart Citation
“…• Only the freshest updates must be allowed to prevent an attacker from reusing old updates [46]. We have already shown that our design flow can ensure integrity, authenticity, and confidentiality for SWIP.…”
Section: A Software Updatementioning
confidence: 99%
“…Then, the server generates a challenge for which the remote server must be able to generate an appropriate response for authentication. Next, the SWIP is encrypted and packaged in such a way to ensure integrity, authenticity, confidentiality, and freshness [46]. This must be performed in such a way to minimize storage, computational overhead, and transmission overhead [47].…”
Section: A Software Updatementioning
confidence: 99%
“…Motivated by this, Badrignans et al [11] proposed additions to the hard-coded configuration logic in order to prevent replay of old bitstreams. They use a nonce in the authentication process, in addition to a mechanism for alerting the developer of its failure.…”
Section: Related Workmentioning
confidence: 99%
“…Several security architectures have been proposed for satellites to remotely manage their hardware configuration from the ground station [16], and for purposes of key distribution [17] and management [18], [19], [20]. All of those works make use of cryptographic primitives such as hash functions to achieve their goals, but none of them considers the harsh environment surrounding spacecrafts and more specifically the resistance to SEUs.…”
Section: Related Workmentioning
confidence: 99%