Master'sElectronics, Embedded Systems & Telecom Applications open

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.

Duration1900 h
ModeOnline
LanguageEnglish
Start datesSet by the faculty
AwardSEIUM Institute diploma
Virtual lab · try it before you enrol

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.

SIM · LIVE ●
Learning outcomes

What you will be able to do

01

Identify the attack surface and model threats in IoT systems.

02

Apply cryptography suited to resource-constrained devices.

03

Implement hardware security and secure boot mechanisms.

04

Protect device communications and identity.

05

Assess device security through controlled testing.

06

Apply European product cybersecurity regulations.

07

Design an IoT product that remains secure throughout its lifecycle.

Profile

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.
Standards & tools

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
Syllabus

12 modules · 1900 h

  1. 1.1Components of an IoT ecosystem
  2. 1.2Attack vectors on device, network and cloud
  3. 1.3OWASP IoT Top 10 list
  4. 1.4Historical incidents and botnets such as Mirai
  5. 1.5Attacker motivations and profiles
  6. 1.6STRIDE threat modelling applied to IoT
  7. 1.7Risk analysis in connected products
  8. 1.8Security requirements by design
  9. 1.9CWE vulnerability taxonomy
  10. 1.10Case study: threat model of an IP camera
  1. 2.1AES symmetric encryption and modes of operation
  2. 2.2Elliptic curve cryptography
  3. 2.3Hash functions and MAC codes
  4. 2.4Random number generation
  5. 2.5ASCON lightweight cryptography
  6. 2.6Cryptographic accelerators in microcontrollers
  7. 2.7Side-channel attacks: principles
  8. 2.8Secure key management
  9. 2.9Post-quantum cryptography for IoT
  10. 2.10Practical: ECDSA signing with mbedTLS on a microcontroller
  1. 3.1Hardware root of trust
  2. 3.2Secure elements, TPM and SIM
  3. 3.3TrustZone trusted execution environments
  4. 3.4Protection of JTAG and SWD debug ports
  5. 3.5Physically unclonable functions
  6. 3.6Protection against physical tampering
  7. 3.7Fault injection: defensive framework
  8. 3.8Hardware supply chain security
  9. 3.9Assessment with PSA Certified
  10. 3.10Lab: configuring TrustZone-M on a Cortex-M33
  1. 4.1Secure boot chain
  2. 4.2MCUboot and verified U-Boot bootloaders
  3. 4.3Image signing and encryption
  4. 4.4Rollback protection
  5. 4.5Secure OTA updates
  6. 4.6Firmware partitioning and isolation
  7. 4.7Memory protection with MPU
  8. 4.8Secure development in C and MISRA
  9. 4.9Static analysis of embedded code
  10. 4.10Practical: secure boot with MCUboot
  1. 5.1TLS 1.3 and DTLS on constrained devices
  2. 5.2Mutual authentication with certificates
  3. 5.3Security in MQTT and CoAP
  4. 5.4OSCORE and EDHOC
  5. 5.5BLE security and pairing
  6. 5.6Security in Zigbee, Thread and Matter
  7. 5.7LoRaWAN security
  8. 5.8Security in cellular IoT networks
  9. 5.9Network segmentation for devices
  10. 5.10Lab: MQTT over TLS with mutual authentication
  1. 6.1Unique device identity
  2. 6.2Public key infrastructure for IoT
  3. 6.3Secure factory provisioning
  4. 6.4Zero-touch enrolment
  5. 6.5Credential rotation and revocation
  6. 6.6Secure fleet management
  7. 6.7EST and SCEP protocols
  8. 6.8Credentials in eSIM and iSIM
  9. 6.9End of life and secure erasure
  10. 6.10Workshop: private PKI for a sensor fleet
  1. 7.1Shared responsibility model
  2. 7.2Access policies on IoT platforms
  3. 7.3API protection
  4. 7.4Security of device twins
  5. 7.5Logging and auditing
  6. 7.6Detection of anomalous behaviour
  7. 7.7Security of edge containers
  8. 7.8Personal data protection
  9. 7.9Secure service configuration
  10. 7.10Practical: policy review in AWS IoT Core
  1. 8.1IoT penetration testing methodology
  2. 8.2Firmware analysis with binwalk
  3. 8.3Firmware emulation
  4. 8.4Network traffic analysis
  5. 8.5Testing radio interfaces
  6. 8.6Testing companion mobile apps
  7. 8.7Review of default configuration
  8. 8.8Findings report and CVSS severity
  9. 8.9Responsible vulnerability disclosure
  10. 8.10Lab: firmware analysis in a controlled environment
  1. 9.1Fleet security monitoring
  2. 9.2IoT intrusion detection systems
  3. 9.3Secure logging on devices
  4. 9.4Event correlation in SIEM
  5. 9.5Incident response on devices
  6. 9.6Forensic analysis of IoT devices
  7. 9.7Patch management at scale
  8. 9.8Threat intelligence
  9. 9.9Mandatory incident notification
  10. 9.10Case study: responding to a botnet in a fleet
  1. 10.1ETSI EN 303 645 standard
  2. 10.2RED cybersecurity requirements
  3. 10.3Cyber Resilience Act obligations
  4. 10.4IEC 62443 series in industrial IoT
  5. 10.5NIST IR 8259 and device profile
  6. 10.6PSA and SESIP certification
  7. 10.7EUCC European certification scheme
  8. 10.8Security labelling programmes
  9. 10.9Manufacturer responsibility after sale
  10. 10.10Workshop: gap analysis against EN 303 645
  1. 11.1Secure development maturity model
  2. 11.2Traceable security requirements
  3. 11.3Security-focused design review
  4. 11.4Software bill of materials (SBOM)
  5. 11.5Open-source dependency management
  6. 11.6Integrating security into CI/CD
  7. 11.7Firmware fuzz testing
  8. 11.8Vulnerability and CVE management
  9. 11.9Security support throughout the product's lifetime
  10. 11.10Practical: DevSecOps pipeline for firmware
  1. 12.1Definition of the IoT product
  2. 12.2Threat and risk modelling
  3. 12.3Proposed security architecture
  4. 12.4Implementation of controls
  5. 12.5Security assessment of the prototype
  6. 12.6Regulatory compliance analysis
  7. 12.7Vulnerability management plan
  8. 12.8Conclusions on IoT security
  9. 12.9Master's Thesis report
  10. 12.10Master's Thesis: defence before a panel
Methodology, software & labs

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.

Assigned technical tutor:every module ends with a deliverable that your tutor marks individually.
Standards-based learning:guided reading of ETSI EN 303 645, Regulation (EU) 2024/2847 and EN 18031-1 applied to real cases, not as a theoretical annex.
Industry software:Wireshark, binwalk, Ghidra, MCUboot and OpenSSL, in free, academic or evaluation versions.
Master's Thesis with defence:A secure IoT product, from threat modelling and security architecture to implemented controls, prototype assessment and regulatory compliance, defended before a panel.
Flexible format:100% online, no fixed timetables, compatible with full-time work.
Capstone project

Build it end to end

Your final project follows the real engineering workflow, step by step, reviewed by your tutor.

Product and threats
Define the IoT product and model its threats and risks.
Security architecture
Propose a security architecture covering hardware, firmware, communications and cloud.
Controls implementation
Implement the security controls on a prototype.
Assessment and compliance
Assess the prototype's security and analyse its regulatory compliance.
Master's Thesis
Define the vulnerability management plan and present the project, defended before a panel.
Career opportunities

Where this takes you

IoT Cybersecurity EngineerProduct Security AnalystSecure Firmware DeveloperCybersecurity Compliance ConsultantDevice Security AuditorPSIRT Manager
Admissions & scholarships

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.

FAQ

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.

Master’s in IoT Cybersecurity EngineeringEnrol
Scroll to Top
SEIUM – Institute of Advanced Engineering
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.