The curriculum spans the technical and organizational practices found in multi-year automotive cybersecurity programs, covering threat modeling, secure architecture, and regulatory compliance activities comparable to those conducted across OEMs and Tier 1 suppliers during vehicle development and post-deployment operations.
Module 1: Threat Modeling and Risk Assessment for Vehicle Systems
- Conducting STRIDE-based threat modeling on electronic control units (ECUs) to identify spoofing and tampering risks in CAN bus communications.
- Selecting attack vectors for inclusion in risk matrices based on exploit feasibility and potential safety impact, such as remote access via telematics units.
- Integrating ISO/SAE 21434 requirements into threat assessment workflows for new vehicle platforms.
- Assigning CVSS scores to identified vulnerabilities in infotainment systems while accounting for limited attacker access conditions.
- Facilitating cross-functional workshops with safety and systems engineering teams to align on acceptable risk thresholds.
- Documenting assumptions about attacker capabilities (e.g., physical access vs. over-the-air) for use in penetration testing scoping.
Module 2: Secure Vehicle Network Architecture Design
- Implementing domain segregation between powertrain, chassis, and infotainment networks using zone-based firewalls and gateways.
- Configuring VLANs and rate limiting on Ethernet backbones to prevent broadcast flooding attacks in high-speed vehicle networks.
- Designing secure update paths for OTA firmware that isolate critical ECUs from non-critical communication channels.
- Evaluating placement of intrusion detection systems (IDS) at key network junctions without introducing unacceptable latency.
- Selecting cryptographic protocols for inter-ECU communication based on processing constraints of legacy microcontrollers.
- Defining rules for diagnostic access over DoIP to prevent unauthorized reprogramming of safety-critical modules.
Module 3: Secure Software Development Lifecycle (S-SDLC) Integration
- Enforcing mandatory static application security testing (SAST) in CI/CD pipelines for infotainment application builds.
- Mapping third-party library dependencies in Android Automotive OS and monitoring for CVEs in open-source components.
- Requiring threat modeling outputs as gate deliverables before software enters integration testing.
- Implementing secure coding standards for C/C++ used in ECU firmware, including buffer overflow mitigations.
- Conducting architecture risk analysis during design reviews for new telematics applications.
- Managing patch backporting processes for long-lifecycle vehicle software across multiple model years.
Module 4: Cryptographic Key Management and PKI Implementation
- Designing hierarchical certificate authorities for vehicle-to-everything (V2X) communications with revocation mechanisms.
- Provisioning hardware security modules (HSMs) in manufacturing to inject unique cryptographic keys into ECUs.
- Implementing certificate lifecycle management for millions of vehicles with automated renewal and revocation.
- Choosing elliptic curve cryptography parameters that balance security and performance on resource-constrained ECUs.
- Defining key rotation policies for session keys used in secure diagnostic sessions.
- Securing over-the-air update signing keys with multi-person control and air-gapped storage.
Module 5: Supply Chain and Third-Party Risk Management
- Requiring Tier 1 suppliers to provide Software Bill of Materials (SBOM) for all delivered ECU software.
- Auditing supplier development environments for compliance with secure coding and access control standards.
- Enforcing contractual clauses for vulnerability disclosure timelines and patch delivery commitments.
- Validating security test results from suppliers using independent penetration testing labs.
- Mapping data flows from third-party cloud services (e.g., navigation, voice assistants) to onboard systems.
- Assessing risks of shared components across vehicle platforms when a supplier discloses a widespread vulnerability.
Module 6: Intrusion Detection and Anomaly Monitoring Systems
- Developing behavioral baselines for CAN message frequency and timing to detect ECU impersonation.
- Deploying lightweight host-based IDS agents on Android-based infotainment systems without degrading UX.
- Correlating alerts from vehicle IDS with cloud-based threat intelligence for fleet-wide attack pattern detection.
- Configuring alert thresholds to minimize false positives from legitimate diagnostic tool usage.
- Designing secure data pipelines to transmit IDS events to backend security operations centers.
- Implementing response actions such as ECU isolation or session termination upon confirmed intrusion detection.
Module 7: Incident Response and Forensic Readiness for Connected Vehicles
- Establishing secure logging mechanisms on ECUs with write-once storage to preserve forensic evidence.
- Defining data preservation protocols for vehicles involved in cybersecurity incidents during warranty repairs.
- Creating playbooks for responding to ransomware attacks targeting infotainment systems.
- Coordinating with law enforcement on data access procedures for vehicle forensic imaging.
- Simulating recall scenarios triggered by widespread exploitation of a critical vulnerability.
- Archiving firmware versions and configuration data to support root cause analysis during investigations.
Module 8: Regulatory Compliance and Cybersecurity Governance
- Mapping internal cybersecurity controls to UN R155 and R156 requirements for type approval in multiple regions.
- Establishing a cybersecurity management system (CSMS) with documented roles, responsibilities, and audit trails.
- Preparing evidence packages for audits by regulatory bodies, including risk assessment records and test results.
- Updating cybersecurity policies to reflect evolving threats and new vehicle connectivity features.
- Reporting cybersecurity incidents to national authorities within mandated timeframes under regional regulations.
- Conducting annual top-down risk assessments to validate the effectiveness of the organization’s cybersecurity posture.