Master’s in ISO 21434 and UNECE R155/R156 (CSMS/SUMS)
Online master's programme of 1,900 hours in automotive cybersecurity to ISO/SAE 21434 and UNECE R155/R156. 12 modules covering CSMS, TARA, secure architecture, cryptography, testing, vulnerability management, SUMS and type-approval audits, 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
Interpret the requirements of UNECE R155, R156 and ISO/SAE 21434.
Implement a cybersecurity management system within the organisation.
Carry out a threat analysis and risk assessment (TARA).
Design a secure vehicle architecture with appropriate cryptography.
Plan cybersecurity verification and testing.
Manage vulnerabilities, incidents and software updates.
Prepare the documentation for audit and type-approval.
Who it's for
- Automotive cybersecurity engineers.
- CSMS managers.
- TARA analysts.
- Vehicle penetration testing engineers.
- Software update management (SUMS) managers.
- Cybersecurity type-approval auditors.
- Engineering or science graduates seeking to enter vehicle manufacturers.
What you'll work with
- ISO/SAE 21434 (road vehicle cybersecurity engineering)
- UN Regulation No. 155 (CSMS)
- UN Regulation No. 156 (SUMS)
- ISO 24089 (software updates in road vehicles)
- Regulation (EU) 2019/2144 (general safety type-approval)
- ISO 26262 (functional safety)
- ISO/IEC 27001 (information security management)
- Vector CANoe
- Ansys medini analyze
- Wireshark
- Python (Scapy)
- Burp Suite
12 modules
1.1UNECE R155 and its scope of application1.2UNECE R156 and update management1.3Relationship with type-approval1.4ISO/SAE 21434 as the state of the art1.5Obligations of the manufacturer and the supply chain1.6Application timeline in the European Union1.7Audits by the type-approval authority1.8Consequences of non-conformity1.9Relationship with ISO 26262 and SOTIF1.10Complete regulatory map of the project
2.1Scope and governance of the CSMS2.2Policies, roles and responsibilities2.3Processes across the whole life cycle2.4Supplier and interface management2.5Staff competence and training2.6Configuration and version management2.7Indicators and management review2.8Evidence required by the auditor2.9Preparing for the initial audit2.10Workshop: documentary framework of a CSMS
3.1Identification of assets to be protected3.2Threat scenarios and attack trees3.3Impact assessment: safety, operational, financial and privacy3.4Attack feasibility and methods3.5Determination of the risk level3.6Treatment decision: avoid, reduce, share or accept3.7Cybersecurity goals and requirements3.8Traceability from risk to requirement3.9Review and maintenance of the TARA3.10Case study: TARA of a telematics unit
4.1Domain segmentation and trust zones4.2Gateways and control of flows between networks4.3Attack surface and its reduction4.4Principles of least privilege and defence in depth4.5Secrets management and secure storage4.6Secure elements and HSMs in automotive4.7Message authentication on CAN: SecOC4.8Ethernet protection: MACsec, TLS and IPsec4.9In-vehicle intrusion detection4.10Workshop: hardening an E/E architecture
5.1Symmetric primitives and their embedded use5.2Digital signatures and certificates in the vehicle5.3Public key infrastructure for a fleet5.4Key provisioning in the factory and in aftersales5.5Rotation, revocation and expiry5.6Random number generation on MCUs5.7Performance and real-time cost5.8Side-channel resistance5.9Crypto-agility and post-quantum readiness5.10Lab: certificate chain for an ECU
6.1Level-based test strategy6.2Functional testing of security mechanisms6.3Static analysis and code review6.4Fuzzing of interfaces and protocols6.5Penetration testing on the bench and in the vehicle6.6Hardware testing and physical access6.7Acceptance criteria and coverage6.8Management and closure of findings6.9Reports for the authority6.10Lab: fuzzing campaign on UDS
7.1Monitoring of sources and advisories7.2Triage and exploitability assessment7.3Response teams and escalation7.4Communication with the authority and the customer7.5Coordinated disclosure with researchers7.6Emergency patching and temporary mitigations7.7Incident logging and lessons learned7.8Response time metrics7.9Incident drills7.10Workshop: response exercise for a critical vulnerability
8.1R156 requirements for the SUMS8.2RXSWIN software identification8.3Impact assessment of each update8.4Compatibility with the current type-approval8.5Security of the OTA campaign8.6Consent, user information and vehicle conditions8.7Rollback and handling of update failures8.8Version records per vehicle8.9Updates in aftersales and the workshop8.10Lab: OTA campaign plan
9.1Cybersecurity interface agreements9.2Allocation of responsibilities with suppliers9.3Contractual requirements and evidence9.4Software bill of materials (SBOM)9.5Third-party and open-source components9.6Supplier maturity assessment9.7Second-party audits9.8Change management for supplied components9.9End of support and obsolescence9.10Workshop: drafting a CIA with a supplier
10.1Monitoring of the fleet in service10.2Security telemetry and privacy10.3Secure diagnostics and workshop access10.4Management of vehicles out of support10.5Second life and change of ownership10.6Secure erasure of personal data10.7Spare parts and non-original parts10.8Decommissioning and dismantling10.9Residual obligations of the manufacturer10.10Case study: end-of-support policy
11.1Preparation of the type-approval file11.2CSMS and SUMS evidence per vehicle11.3Relationship between the type file and projects11.4Interviews and sampling during the audit11.5Non-conformities and action plans11.6Periodic surveillance and renewal11.7Type-approval extensions11.8Coordination between authorities in different countries11.9Errors that delay a type-approval11.10Mock audit
12.1Definition of the vehicle and its architecture12.2Complete TARA of the chosen system12.3Cybersecurity concept and derived requirements12.4Design of countermeasures and their justification12.5Verification plan and results12.6Update plan and RXSWIN12.7R155 and R156 audit file12.8Residual risk analysis12.9Report and defence before a panel12.10Master's Thesis: final review with the tutor
How you'll learn
A 100% online programme on the SEIUM campus, with downloadable materials, recorded classes and an assigned technical tutor. There are no fixed timetables: you progress at your own pace within each intake, so it fits around your job.
Each module combines theory, guided reading of the original standard and applied exercises. The working software is Vector CANoe, Ansys medini analyze, Wireshark, Python (Scapy) and Burp Suite, in free, academic or evaluation versions. Testing is studied through real procedures for TARA analysis of an architecture, penetration testing of in-vehicle networks and CSMS audits. Assessment is continuous by module, plus the final Master's Thesis.
Standards covered: ISO/SAE 21434, UN Regulation No. 155, UN Regulation No. 156, ISO 24089, Regulation (EU) 2019/2144, ISO 26262 and ISO/IEC 27001.
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'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 will work with Vector CANoe, Ansys medini analyze, Wireshark, Python (Scapy) and Burp Suite. Free, academic or evaluation versions are used, and your tutor indicates the free alternative where 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 Event, Thermal and Multispectral Camera Engineering
Online master's programme of 1,900 hours in event, thermal and multispectral camera engineering, structured in 12 modules covering unconventional image sensors, event-data processing, infrared thermography, multispectral…
Master’s in Vulnerable Road User Detection and Urban Safety Engineering
Online master's programme of 1,900 hours in vulnerable road user detection and urban safety, structured in 12 modules covering sensing, detection and intention prediction of pedestrians…
Master’s in Runtime Monitoring Engineering
Online master's programme of 1,900 hours in runtime monitoring engineering, structured in 12 modules covering runtime verification with temporal logic, perception, planning and ODD monitoring, safe…
More in Autonomous, ADAS & Software-Defined Vehicle
All Autonomous, ADAS & Software-Defined Vehicle programmes → · How to apply · Fees & financing · Scholarships