Program Overview
As vehicles become hyper-connected, electric, autonomous, and software-centric, cybersecurity is now a critical safety and business priority. This program gives participants a fast-track, industry-relevant understanding of in-vehicle networks, threat surfaces, real cyber-attack case studies, and secure design practices. Through hands-on simulations and scenario-based discussions, participants learn how modern automotive systems—from ECUs and CAN networks to V2X and telematics—must be secured end-to-end, aligned with ISO/SAE 21434 and global OEM standards.
Features
- Understand in-vehicle network architecture and major cybersecurity vulnerabilities
- Identify and analyse common automotive threat vectors using real-world case examples
- Apply secure design principles (cryptography, secure communication, secure ECU/firmware practices)
- Map cybersecurity requirements to ISO/SAE 21434 and build a basic vehicle cybersecurity checklist
Target audiences
- Automotive engineers (electronics, mechatronics, embedded systems)
- Cybersecurity analysts
- R&D, Quality, and Vehicle Programs teams
- IT/OT security teams in OEMs, Tier-1, Tier-2 suppliers
Curriculum
- 5 Sections
- 33 Lessons
- 1 Day
Expand all sectionsCollapse all sections
- Automotive Cybersecurity Landscape & Fundamentals5
- 1.1Evolution of vehicle electronics → connected → SDVs (software-defined vehicles)
- 1.2Why cybersecurity matters: safety, privacy, compliance, brand risk
- 1.3Overview of in-vehicle network architecture: ECUs, gateways, CAN, LIN, FlexRay, Ethernet
- 1.4Regulatory environment overview: ISO/SAE 21434, UNECE WP.29, global OEM policies
- 1.5Introduction to Vehicle Threat Surfaces
- Vehicle Networks & Attack Vectors9
- 2.1How vehicle networks work: message frames, arbitration, bus communication
- 2.2How hackers exploit CAN/LIN vulnerabilities
- 2.3Emerging risks with EVs, ADAS, OTA updates, and telematics systems
- 2.4Case study 1: Jeep Cherokee hack (Uconnect)
- 2.5Case Study 2: Tesla remote-control exploits
- 2.6Case Study 3: Keyless entry relay attacks
- 2.7Case Study 4: Telematics data breaches in fleets
- 2.8Supply chain risks: compromised ECU, firmware injection, counterfeit chips
- 2.9Red flags: how vulnerabilities typically enter OEM/Tier-1 development cycles
- Secure Vehicle Design: Hardware, Software & Communication8
- 3.1Secure ECU architecture & secure boot
- 3.2Role of cryptography in automotive systems (lightweight crypto, key mgmt.)
- 3.3Secure CAN & emerging secure Ethernet
- 3.4Secure OTA updates & firmware validation practices
- 3.5Threat modelling for automotive systems (STRIDE, HEAVENS model)
- 3.6Testing & validation: penetration testing, fuzzing, anomaly detection
- 3.7What good looks like: global OEM security-by-design examples
- 3.8Case breakdowns:How Toyota secures ECU firmware; How Tesla handles OTA & telemetry security; How Bosch/Continental manage ECU supplier security processes
- Emerging Challenges: V2X, EV Security, ADAS & Cloud Backend6
- 4.1V2V & V2X security risks
- 4.2Cybersecurity requirements for EV charging ecosystem
- 4.3ADAS LiDAR/Radar spoofing
- 4.4Cloud data, telematics platforms & backend cybersecurity
- 4.5Data privacy considerations (location, driving patterns, identity data)
- 4.6What India needs to prepare for: connected-infrastructure vulnerabilities
- Capstone Project & Simulation5
- 5.1Mini Case 1: Threat modelling for a vehicle’s CAN network
- 5.2Mini Case 2: Analyse a sample cyber-incident (payload manipulation)
- 5.3Mini Case 3: Draft a basic cybersecurity checklist aligned with ISO/SAE 21434
- 5.4Mini Case 4: Build a 10-point mitigation roadmap for a hypothetical new EV model
- 5.5Tools: Sample CAN logs; Threat modelling template; Cybersecurity checklist template; Incident-response flow; Capstone: Secure design review of a sample vehicle subsystem; Templates: Threat modelling sheets, ECU security checklist, supplier audit format
Instructor
