Sécurité des implémentations pour la cryptographie
Cryptography is the cornerstone of digital security. Its use allows us to build complex systems which security relies on well-known difficult problems.
However those proofs, obtained in theoretic models, can be undermined by actual implementations. Bad configurations, coding errors or side-channel information can threaten the security of systems even if they are cryptographically proven secure.
This class aims at underlining the complexity of correctly using cryptography in real life. Different cryptographic implementation vulnerabilities are presented together with good practices that can limit them. To this goal, all aspects of a secure system design are addressed. It starts from the system level and goes down to the tricky details of cryptographic primitive implementations.
Some introductive slides.
Printable version of the class slides.
The final grade will mix the results of
- 1/3 a lab report (TP 1) that should be sent before the 05.01.2021
- 2/3 a written exam on the 19.01.2021 from 8:15 to 10:15
\Following are some details about the writen exam.
- It is an individual exam.
- Slides or any note from course or labs is prohibited.
- The exam contains a knowledge questions and a code review part.
- The knowledge part will be a list of multiple-choice and short-answer questions..
- The code review part will be similar to the labs (TP 1 and 2).
In order to be able to enjoy the lab please ensure that you have access to a desktop/laptop that fulfills the following requirements.
- You are allowed to open serial port to communicate with USB devices.
- Python 3 is installed with its package serial, numpy and matplotlib.
CM 1 (17.11.2020)
System requirements and architecture
CM 2 (24.11.2020)
Product interface and architecture
CM 3 (30.11.2020)
CM 4 (01.12.2020)
CM 5 (05.01.2021)
Local (noninvasive) security
TP 3 (06.01.2021)
Exploiting processing time
CM 6 (12.01.2021)
Local (invasive) security
TP 4 (13.01.2021)
Exploiting power consumption
TP 5 (20.01.2021)
Exploiting fault injection
(same statement as for TP 4)