SSYS2
Sécurité avancée des SI d'entreprise: operating-system security, isolation, access control, and hardening practice.
Instructor: Daniel De Almeida Braga
Term: Master 2 RSSI
Location: CyberSchool, Universite de Rennes
Time: 54 hours (18h lectures + 12h supervised work + 24h labs)
Course Description
This course trains future security managers and engineers to reason about the security mechanisms provided by modern operating systems and enterprise platforms. It connects system internals with operational policy: authentication, access control, mandatory confinement, storage protection, application isolation, and container deployment.
The module follows a defense-in-depth approach. Each topic introduces the protection goal, the underlying mechanism, its limitations, and the operational tradeoffs involved in deploying it on Linux or Windows systems.
At the end of this module, you should be able to:
- Present the various protection mechanisms implemented on both OSes.
- Understand the limits of defenses, what they protect against and how to configure them effectively.
- Learn how to deploy security policies on a system.
- Prepare students to identify and respond to security vulnerabilities and threats in both OS.
Prerequisites
- Unix basics.
- Windows basics.
- Introductory computer security, including cryptography and access control.
Teaching Language
French, with material in English.
Schedule
| Topic | Materials |
|---|---|
| Course organization Course goals, structure, and expectations. | |
| Operating-system security foundations OS security model, kernel/user boundaries, threat surfaces, and defense in depth. | |
| Authentication Identity, local and network authentication, credential handling, and Kerberos concepts. | |
| Access control Linux and Windows access-control models, permissions, privileges, and audit-oriented configuration. | |
| Linux security modules Mandatory access control with SELinux and AppArmor, policy reasoning, and deployment constraints. | |
| Data security Storage protection, backups, availability, confidentiality, and integrity mechanisms. | |
| Application security Process isolation, software confinement, and practical application hardening. | |
| Container security Container isolation, deployment assumptions, and security limits in containerized environments. |