Skills
Securing an application from the design stage
Injection, authentication, session handling, access rights, secrets: most application incidents come from a small number of well-known families. Handling them at design time costs a few hours; handling them after a breach costs a reputation.
Security written into the code
An application is secured where it is written. Validating input at the edge of the system, separating authentication from authorisation, keeping secrets out of the repository, logging what matters without exposing personal data: these moves are made at the same time as the code, and they then hold on their own. The programme teaches them as design habits, then tests them through code review and the offensive blocks of the same curriculum.
- Validate input and neutralise injection at the system's boundaries
- Set up authentication and verifiable role-based permissions
- Manage secrets and keys outside the code repository
- Run a security-oriented code review on an existing project
The exact measure
You design an application with its security guarantees written down, and verify them through review and testing. Volumes, credits and certified outlets, recomputed from the official catalogue.
- teaching blocks
- 4
- of taught instruction
- 740 h
- credits in total
- 74
- professional qualifications concerned
- 3
Catalogue rule: one credit is twenty-five hours of work, ten of them taught.
- Cybersecurity programme — Bac+5 level
- 340 (46 %)
- Computer Science programme — Bac+3 level
- 260 (35 %)
- Web and Mobile Development
- 140 (19 %)
The modules that carry it
A cross-curricular module spread over several years reads « Years 1 to 3 »: it runs alongside the whole programme rather than a single term.
| Teaching block | Programme | Taught hours | Year |
|---|---|---|---|
| Application security | Cybersecurity programme — Bac+5 level | 120 h | Year 1 |
| Security fundamentals | Cybersecurity programme — Bac+5 level | 220 h | Year 1 |
| Software engineering | Computer Science programme — Bac+3 level | 260 h | Year 3 |
| Deployment | Web and Mobile Development | 140 h | Year 2 |
Which positions it leads to
At levels 6 and 7, professional experience is part of the entry requirements.
| Professional qualification | Target occupation | Level | Taught volume |
|---|---|---|---|
| Chief Information Security Officer | CISO | 7 · Expert and executive | 700 h |
| Application Developer | experienced developer | 5 · Senior technician and supervisor | 800 h |
| Development Team Lead | lead developer, technical team manager | 6 · Manager and professional | 800 h |
Which programme takes you there
The same professional act can be reached by several routes. Compare volume, duration and amount.
| Programme | Level | Duration | Fees |
|---|---|---|---|
| Cybersecurity programme — Bac+5 level | Master's degree | 2 years | 7 500 000 GNF per year |
| Computer Science programme — Bac+3 level | Bachelor's degree | 3 years | 5 400 000 GNF per year |
| Web and Mobile Development | Bachelor's degree | 2 years | 5 200 000 GNF per year |
Explore next
- Digital forensicsDigital forensics at IHETC: trace preservation, timeline reconstruction, log analysis and a defensible incident report. 180 taught hours in cybersecurity.
- Data governanceData governance at IHETC: ownership, access rights, retention periods, sovereignty and compliance. Teaching blocks, taught hours and roles.
- Security managementInformation security management at IHETC: governance, risk, compliance and standards frameworks. Taught hours, programmes and target qualifications.
- Framing AI use casesFraming artificial intelligence use cases at IHETC: identification, expected value, available data, governance and adoption. Blocks and target roles.
- User researchUser research at IHETC: interviews, observation, usability testing and reporting. 200 taught hours in user experience design.
- Information architectureInformation architecture at IHETC: site structure, labelling, navigation, card sorting and findability testing. 180 taught hours in user experience design.