Master’s in Firmware Security Engineering
Online master's programme of 1,900 hours in firmware security engineering. 12 modules covering embedded architecture, secure boot, applied cryptography, secure OTA updates, secure development, security testing, physical attack countermeasures, vulnerability management and compliance with the Cyber Resilience Act, IEC 62443-4 and ETSI EN 303 645, with an assigned technical tutor.
Take the controls.
Run a real engineering trade-off from this field. Move the sliders, watch the model react in real time and beat the challenge.
What you will be able to do
Analyse the threats to an embedded device from the design stage.
Design secure boot chains with a hardware root of trust.
Apply cryptography suited to resource-constrained devices.
Implement signed, robust OTA updates.
Apply secure development practices and static analysis.
Verify product security and manage its vulnerabilities.
Prepare compliance documentation for the Cyber Resilience Act.
Who it's for
- Firmware security engineers who want to broaden their expertise across the full product lifecycle.
- Embedded systems engineers taking on security responsibilities.
- Product security managers preparing for the Cyber Resilience Act.
- Industrial cybersecurity auditors working with IEC 62443.
- Automotive cybersecurity engineers applying ISO/SAE 21434 and UNECE R155/R156.
- Product certification specialists.
- Engineering or science graduates seeking to move into the automotive sector.
What you'll work with
- Regulation (EU) 2024/2847 (Cyber Resilience Act for products with digital elements)
- IEC 62443-4-1 and 62443-4-2 (secure product development and component security requirements)
- ETSI EN 303 645 (cybersecurity for consumer IoT)
- ISO/SAE 21434 (road vehicle cybersecurity engineering)
- NIST SP 800-193 (platform firmware resiliency)
- UNECE R155 and R156 (vehicle cybersecurity and software updates)
- Common Criteria, ISO/IEC 15408 (IT security evaluation)
- Ghidra
- Yocto Project
- MCUboot
- Cppcheck
- Wireshark
12 modules · 1900 h
1.1Microcontrollers and SoCs1.2Flash, ROM and RAM memories1.3Boot process and loader chain1.4Peripherals and debug interfaces1.5Real-time operating systems1.6Embedded Linux1.7IoT device firmware1.8Firmware in automotive and industry1.9Firmware lifecycle1.10Workshop: architecture map of a device
2.1Threat model of a device2.2Physical and logical attack surface2.3Hardware root of trust2.4Code confidentiality and integrity2.5On-device key management2.6Principle of least privilege2.7Security by design2.8Product security requirements2.9Regulations applicable to connected products2.10Practical: threat analysis of an IoT sensor
3.1Secure boot and signature verification3.2Chain of trust at boot3.3Secure elements and TPM3.4Secure key storage3.5Measured boot and attestation3.6UEFI Secure Boot3.7Revocation of compromised keys3.8Version anti-rollback3.9Boot verification testing3.10Lab: verified boot on a development board
4.1Symmetric and asymmetric algorithms4.2Hash functions and signatures4.3Random number generators4.4Cryptography with limited resources4.5Hardware cryptographic accelerators4.6Key lifecycle management4.7Public key infrastructure for devices4.8Common implementation errors4.9Validation of cryptographic modules4.10Practical: signing and verifying an image
5.1OTA update architectures5.2Package signing and encryption5.3A/B partitions and recovery5.4Pre-installation verification5.5Secure distribution of updates5.6Device fleet management5.7UNECE R156 requirements5.8Version traceability5.9Update robustness testing5.10Lab: OTA channel with signature verification
6.1MISRA C and CERT C coding standards6.2Secure memory management6.3Static code analysis6.4Peer code review6.5Dependency management and SBOM6.6Reproducible builds6.7Compiler protections6.8Continuous integration with security controls6.9Development security documentation6.10Practical: static analysis of an embedded project
7.1Product security test plan7.2Robustness testing and defensive fuzzing7.3Verification of security requirements7.4Assessment of debug interfaces7.5Binary analysis for verification purposes7.6Device communications testing7.7Emulation environments7.8Management of findings and fixes7.9Evidence for certification7.10Lab: laboratory verification campaign
8.1Types of physical attacks on hardware8.2Protection of JTAG and SWD ports8.3Side-channel countermeasures8.4Fault-injection countermeasures8.5Memory protection and code readout protection8.6Tamper detection8.7Board design with security criteria8.8Evaluation of countermeasures8.9Balancing cost and protection8.10Case study: review of a product's countermeasures
9.1PSIRT and product incident management9.2Coordinated vulnerability disclosure9.3CVEs and customer communication9.4Prioritisation and remediation9.5Support throughout the product lifetime9.6Monitoring third-party components9.7Notification obligations9.8Response metrics9.9Lessons learned9.10Practical: a company's PSIRT procedure
10.1Cyber Resilience Act (EU) 2024/284710.2ETSI EN 303 645 for consumer IoT10.3IEC 62443-4-1 and 4-2 in industry10.4ISO/SAE 21434 in automotive10.5Common Criteria and protection profiles10.6European certification schemes10.7Conformity assessment10.8Required technical documentation10.9Working with evaluation laboratories10.10Case study: regulatory compliance matrix
11.1Firmware in connected vehicles11.2Connected medical devices11.3Industrial control systems11.4Energy infrastructure11.5Avionics and space systems11.6Consumer electronics11.7Sector-specific requirements11.8Documented real-world cases11.9Technology trends11.10Workshop: comparison of sector requirements
12.1Device selection and scope12.2Product threat model12.3Proposed security architecture12.4Secure boot and update12.5Security verification plan12.6Regulatory compliance analysis12.7Vulnerability management plan12.8Assessment of costs and residual risks12.9Master's Thesis report12.10Master's Thesis: defence before a panel
How you'll learn
Training is 100% online on the SEIUM campus, with downloadable material, recorded classes and an assigned technical tutor. There are no fixed timetables: you progress at your own pace within the intake, so it fits around your job.
Each module combines theory, guided reading of the original standard and applied exercises. The working software is Ghidra, Yocto Project, MCUboot, Cppcheck and Wireshark, in free, academic or evaluation versions. Work is based on real procedures: development boards, firmware emulation environments and product verification campaigns. Assessment is continuous per module, plus the final Master's Thesis.
Standards covered: Regulation (EU) 2024/2847 (Cyber Resilience Act), IEC 62443-4-1 and 62443-4-2, ETSI EN 303 645, ISO/SAE 21434, NIST SP 800-193, UNECE R155 and R156, Common Criteria (ISO/IEC 15408).
Build it end to end
Your final project follows the real engineering workflow, step by step, reviewed by your tutor.
Where this takes you
Requirements
- University degree in engineering, science or architecture, or equivalent demonstrable professional experience.
- Internet connection and a computer capable of running the programme software.
- English sufficient to read technical standards.
Ready to start?
Send your application today. Our admissions team replies within 72 hours with your study plan and funding options.
Frequently asked questions
The programme totals 1,900 hours over 12–14 months. You set your own pace within each intake, and your tutor helps you plan the workload around your job.
You work with Ghidra, Yocto Project, MCUboot, Cppcheck and Wireshark, using free, academic or evaluation versions. Your tutor indicates the free alternative wherever one exists.
A SEIUM Institute diploma, awarded on passing the continuous assessment and the Master's Thesis. It is SEIUM's own qualification, not an official state degree; its recognition depends on the programme completed and the regulations of each country.
Yes. Modules passed in a course or postgraduate diploma in the same area are recognised in the higher programme. Ask about the recognition policy when you enrol.
A university degree in engineering, science or architecture (or equivalent professional experience), a computer able to run the programme software, and English sufficient to read technical standards.
Start dates are set by SEIUM's faculty for each intake. Our admissions team will confirm the next available date when you apply.
Related programmes
Master’s in Predictive Maintenance
Online master's programme of 1,900 hours in predictive maintenance — vibration and acoustic analysis, models and deployment in the plant. 12 modules covering maintenance strategies, vibration…
Master’s in Middleware and Real-Time Communication
Online master's programme of 1,900 hours in middleware and real-time communication (DDS/RTPS, ROS 2, SOME/IP, OPC UA, TSN and PTP): 12 modules covering distributed real-time systems,…
Master’s in Precision Power Supply and Power Integrity Engineering
Online master's programme of 1,900 hours in precision power and power integrity engineering. 12 modules covering power architectures, low-noise linear regulators, switching converters, loop stability, power…
More in Electronics, Embedded Systems & Telecom
All Electronics, Embedded Systems & Telecom programmes → · How to apply · Fees & financing · Scholarships