A+Augmenter la taille du texteA-Réduire la taille du texteImprimer le documentEnvoyer cette page par mailPartagez cet articleFacebookTwitterLinked InGoogle+Viadeo
Number of hours
Lectures : 9.0
Tutorials : 9.0
ECTS : 1.5
Being able to understand the threats and vulnerabilities
What actions to avoid / limit
Guide to good practice
Security Policy / Audit
Contact Sébastien VIARDOT
The module is largely based on the assignments to be made, consisting of fault analysis, the responses needed to limit the impacts (anticipation and reaction), and propose experiments to implement them.
The topics covered in the framed sessions are :
Introduction to the course, legal warning, assignments presentation.
Lab : Docker and vagrant, and setting up a security challenge
Hardware flaw, illustration via meltdown and spectrum (if not otherwise processed)
Network failures and good practices
WEB security lab
Having taken the following courses (or equivalent) is recommended:
Operating System Design Project - Foundations
Operating system and concurrent programming
Security of systems and networks
CONTINUOUS CONTROL (CC): Evaluation type: Work to be done (alone or in pairs) on a vulnerability analysis and an experiment + Peer evaluation. A total of 2 works to be done and 6 peer reviews to be done.
NORMAL SESSION: No written examination in limited time in normal session, evaluation in continuous control.
RETRIEVAL SESSION (E2): Type of examination: Work equivalent to render individually on the analysis of a new vulnerability + written or oral following the number of students catching up. Specific room: Duration: 2h if it is a writing, 1h if it is an oral. Authorized documents: none Prohibited documents (eg books, all documents): all