Master’s in IoT Cybersecurity Engineering
Online master's programme of 1,900 hours in IoT cybersecurity engineering, structured in 12 modules covering IoT attack surface and threat modelling, embedded cryptography, hardware security, secure boot and firmware, secure communications, device identity, cloud security, device security assessment, detection and response, regulation and secure development, with an assigned technical tutor.
Take the controls.
Run a real engineering trade-off from this programme. Move the sliders, watch the model react in real time and beat the challenge.
What you will be able to do
Identify the attack surface and model threats in IoT systems.
Apply cryptography suited to resource-constrained devices.
Implement hardware security and secure boot mechanisms.
Protect device communications and identity.
Assess device security through controlled testing.
Apply European product cybersecurity regulations.
Design an IoT product that remains secure throughout its lifecycle.
Who it's for
- IoT cybersecurity engineers securing devices from silicon to cloud.
- Product security analysts assessing connected products.
- Secure firmware developers implementing secure boot, TLS and OTA.
- Cybersecurity compliance consultants preparing clients for the Cyber Resilience Act.
- Device security auditors running penetration tests on IoT products.
- PSIRT managers handling vulnerabilities and disclosure.
- Engineering or science graduates aiming to work in consumer electronics.
What you'll work with
- ETSI EN 303 645 (cybersecurity for consumer IoT)
- Regulation (EU) 2024/2847 (Cyber Resilience Act)
- EN 18031-1 (RED cybersecurity requirements for internet-connected radio equipment)
- IEC 62443-4-2 (technical security requirements for IACS components)
- NIST IR 8259A (IoT device cybersecurity capability core baseline)
- ISO/IEC 27001 (information security management systems)
- PSA Certified (security certification framework for IoT chips and devices)
- OWASP ISVS (IoT Security Verification Standard)
- Wireshark
- binwalk
- Ghidra
- MCUboot
- OpenSSL
12 modules · 1900 h
1.1Components of an IoT ecosystem1.2Attack vectors on device, network and cloud1.3OWASP IoT Top 10 list1.4Historical incidents and botnets such as Mirai1.5Attacker motivations and profiles1.6STRIDE threat modelling applied to IoT1.7Risk analysis in connected products1.8Security requirements by design1.9CWE vulnerability taxonomy1.10Case study: threat model of an IP camera
2.1AES symmetric encryption and modes of operation2.2Elliptic curve cryptography2.3Hash functions and MAC codes2.4Random number generation2.5ASCON lightweight cryptography2.6Cryptographic accelerators in microcontrollers2.7Side-channel attacks: principles2.8Secure key management2.9Post-quantum cryptography for IoT2.10Practical: ECDSA signing with mbedTLS on a microcontroller
3.1Hardware root of trust3.2Secure elements, TPM and SIM3.3TrustZone trusted execution environments3.4Protection of JTAG and SWD debug ports3.5Physically unclonable functions3.6Protection against physical tampering3.7Fault injection: defensive framework3.8Hardware supply chain security3.9Assessment with PSA Certified3.10Lab: configuring TrustZone-M on a Cortex-M33
4.1Secure boot chain4.2MCUboot and verified U-Boot bootloaders4.3Image signing and encryption4.4Rollback protection4.5Secure OTA updates4.6Firmware partitioning and isolation4.7Memory protection with MPU4.8Secure development in C and MISRA4.9Static analysis of embedded code4.10Practical: secure boot with MCUboot
5.1TLS 1.3 and DTLS on constrained devices5.2Mutual authentication with certificates5.3Security in MQTT and CoAP5.4OSCORE and EDHOC5.5BLE security and pairing5.6Security in Zigbee, Thread and Matter5.7LoRaWAN security5.8Security in cellular IoT networks5.9Network segmentation for devices5.10Lab: MQTT over TLS with mutual authentication
6.1Unique device identity6.2Public key infrastructure for IoT6.3Secure factory provisioning6.4Zero-touch enrolment6.5Credential rotation and revocation6.6Secure fleet management6.7EST and SCEP protocols6.8Credentials in eSIM and iSIM6.9End of life and secure erasure6.10Workshop: private PKI for a sensor fleet
7.1Shared responsibility model7.2Access policies on IoT platforms7.3API protection7.4Security of device twins7.5Logging and auditing7.6Detection of anomalous behaviour7.7Security of edge containers7.8Personal data protection7.9Secure service configuration7.10Practical: policy review in AWS IoT Core
8.1IoT penetration testing methodology8.2Firmware analysis with binwalk8.3Firmware emulation8.4Network traffic analysis8.5Testing radio interfaces8.6Testing companion mobile apps8.7Review of default configuration8.8Findings report and CVSS severity8.9Responsible vulnerability disclosure8.10Lab: firmware analysis in a controlled environment
9.1Fleet security monitoring9.2IoT intrusion detection systems9.3Secure logging on devices9.4Event correlation in SIEM9.5Incident response on devices9.6Forensic analysis of IoT devices9.7Patch management at scale9.8Threat intelligence9.9Mandatory incident notification9.10Case study: responding to a botnet in a fleet
10.1ETSI EN 303 645 standard10.2RED cybersecurity requirements10.3Cyber Resilience Act obligations10.4IEC 62443 series in industrial IoT10.5NIST IR 8259 and device profile10.6PSA and SESIP certification10.7EUCC European certification scheme10.8Security labelling programmes10.9Manufacturer responsibility after sale10.10Workshop: gap analysis against EN 303 645
11.1Secure development maturity model11.2Traceable security requirements11.3Security-focused design review11.4Software bill of materials (SBOM)11.5Open-source dependency management11.6Integrating security into CI/CD11.7Firmware fuzz testing11.8Vulnerability and CVE management11.9Security support throughout the product's lifetime11.10Practical: DevSecOps pipeline for firmware
12.1Definition of the IoT product12.2Threat and risk modelling12.3Proposed security architecture12.4Implementation of controls12.5Security assessment of the prototype12.6Regulatory compliance analysis12.7Vulnerability management plan12.8Conclusions on IoT security12.9Master's Thesis report12.10Master's Thesis: defence before a panel
How you'll learn
100% online training on the SEIUM campus, with downloadable material, recorded classes and an assigned technical tutor. No fixed timetables: you progress at your own pace within each intake, so the programme fits around your job.
Each module combines theory, guided reading of the original standard and applied exercises. The working software is Wireshark, binwalk, Ghidra, MCUboot and OpenSSL, in free, academic or evaluation versions. Testing is studied through real procedures: firmware and traffic analysis on lab devices, implementing secure boot and TLS communications, and conformity assessment against ETSI EN 303 645. Assessment is continuous by module, plus the final Master's Thesis.
Standards covered: ETSI EN 303 645, Regulation (EU) 2024/2847, EN 18031-1, IEC 62443-4-2, NIST IR 8259A, ISO/IEC 27001, PSA Certified, OWASP ISVS.
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
- A university degree in engineering, science or architecture, or equivalent demonstrable professional experience.
- An internet connection and a computer capable of running the programme's 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 Wireshark, binwalk, Ghidra, MCUboot and OpenSSL, 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's 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 Power Quality Engineering and Active Filters
Online master's programme of 1,900 hours in power quality and active filter engineering, structured in 12 modules covering harmonics, voltage dips, flicker, measurement to IEC 61000-4-30,…
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…
Master’s in Advanced GNSS and Resilient PNT Engineering
Online master's programme of 1,900 hours in advanced GNSS and resilient PNT engineering: 12 modules covering GNSS systems and receivers, precise positioning, augmentation and integrity, GNSS…
More in Electronics, Embedded Systems & Telecom
All Electronics, Embedded Systems & Telecom programmes → · How to apply · Fees & financing · Scholarships