Description

This curriculum spans the technical and procedural rigor of a multi-phase automotive cybersecurity integration program, comparable to the coordinated efforts seen in OEM-supplier threat modeling, secure architecture rollouts, and compliance-aligned incident response planning across vehicle fleets.

Module 1: Threat Modeling for Vehicle Attack Surfaces

Conducting STRIDE-based threat assessments on ECU communication paths within a CAN FD architecture
Selecting attack vectors to prioritize based on exploit feasibility and safety impact in ISO 21434 risk classification
Mapping supplier-provided component threat models to OEM整车-level threat registers
Integrating threat scenarios from real-world incident databases (e.g., NHTSA recalls, CVE entries) into model assumptions
Documenting trust boundaries between domain controllers and zonal gateways in service-oriented architectures
Updating threat models after hardware changes, such as the addition of a V2X module with public key infrastructure dependencies
Validating threat model completeness using attack trees derived from red team penetration test findings
Coordinating threat modeling activities across Tier 1 suppliers with overlapping software components

Module 2: Secure Communication Protocols in In-Vehicle Networks

Implementing MACsec for high-speed Ethernet backbone links between ADAS and infotainment domains
Configuring and managing symmetric key distribution for SecOC in CAN message authentication
Choosing between TLS and DTLS for OTA update channels based on network reliability and latency constraints
Enforcing mutual authentication between ECUs using IEEE 802.1X with a vehicular RADIUS backend
Designing fallback mechanisms for secure communication during key rollover or certificate expiration events
Segmenting network traffic using VLANs and firewall rules to limit lateral movement after a compromised node
Validating timing behavior of secured messages to ensure real-time deadlines are not violated
Integrating secure logging of communication anomalies into a centralized vehicle security operations platform

Module 3: Hardware Security Modules and Root of Trust

Selecting HSMs that meet ISO 21434 requirements for secure boot and cryptographic operations in microcontrollers
Integrating a hardware-backed keystore for storing OEM and supplier signing keys in production vehicles
Designing secure firmware update workflows that leverage HSM-verified rollback protection
Configuring secure debug interfaces to disable post-production without compromising testability during manufacturing
Managing lifecycle states (e.g., development, production, decommission) in HSMs across vehicle production batches
Performing side-channel resistance testing on HSM implementations used in high-value ECUs
Coordinating HSM key provisioning between OEMs and Tier 1s using secure transfer protocols (e.g., PKCS#11 over TLS)
Implementing secure time sources within the HSM to prevent timestamp manipulation in log and certificate validation

Module 4: Over-the-Air (OTA) Update Security

Designing a dual-signature scheme where both OEM and supplier sign firmware images before deployment
Implementing delta update validation to prevent malicious patch injection during partial updates
Enforcing atomic rollback mechanisms when OTA updates fail or are detected as tampered
Configuring rate limiting and authentication on OTA endpoints to prevent denial-of-service attacks
Validating update package integrity using hash chains anchored in the hardware root of trust
Managing certificate revocation lists for OTA signing keys across a global vehicle fleet
Logging and monitoring failed update attempts as potential indicators of compromise
Coordinating update sequencing across interdependent ECUs to avoid functional incompatibilities

Module 5: Intrusion Detection and Prevention Systems (IDPS) in Vehicles

Deploying signature-based and anomaly-based detection rules on gateway ECUs for CAN and Ethernet traffic
Tuning false positive rates in vehicle IDPS to avoid unnecessary driver alerts or ECU resets
Integrating IDPS alerts with a cloud-based security information and event management (SIEM) system
Defining escalation policies for different alert severities, including safe-mode activation
Updating detection signatures remotely while ensuring authenticity and integrity of rule packages
Collecting and anonymizing network telemetry for offline behavioral analysis without violating privacy regulations
Validating IDPS performance under high-load conditions such as firmware updates or sensor data bursts
Coordinating response actions between IDPS and vehicle immobilization systems during confirmed attacks

Module 6: Supply Chain and Third-Party Component Security

Enforcing SBOM (Software Bill of Materials) requirements for all third-party software components in ECUs
Conducting security audits of supplier development environments and CI/CD pipelines
Verifying cryptographic signing of firmware components from Tier 2 and Tier 3 suppliers
Managing vulnerability disclosure processes with suppliers under contractual SLAs
Implementing runtime isolation for third-party applications in infotainment systems using containerization
Assessing open-source library risks using automated scanning tools integrated into build systems
Requiring evidence of secure coding practices (e.g., MISRA compliance) in supplier deliverables
Establishing secure communication channels for exchanging security-critical data with suppliers

Module 7: Vehicle-to-Everything (V2X) Security Architecture

Configuring certificate management systems for V2X pseudonyms to balance privacy and traceability
Implementing IEEE 1609.2 security services for securing WAVE-based message exchanges
Designing roadside unit (RSU) authentication workflows using PKI hierarchies managed by trusted authorities
Handling certificate revocation in V2X networks with intermittent connectivity using CRL and CRLI distribution
Evaluating latency impact of signature verification on safety-critical V2V messages such as emergency braking alerts
Securing V2X communication stacks against replay attacks using timestamp and sequence number validation
Integrating V2X threat intelligence into the vehicle’s IDPS for coordinated response to spoofed messages
Testing V2X security mechanisms under jamming and spoofing conditions in controlled environments

Module 8: Compliance and Audit Readiness for Automotive Cybersecurity

Documenting evidence for UNECE WP.29 R155 and R156 regulatory audits across development and production phases
Maintaining a cybersecurity management system (CSMS) with defined roles, processes, and escalation paths
Preparing for third-party audits by organizing access to threat models, test reports, and incident logs
Mapping internal security controls to ISO/SAE 21434 process requirements for gap analysis
Generating audit trails for key security events such as ECU reprogramming or certificate updates
Implementing version-controlled repositories for all security artifacts with access logging
Conducting internal penetration tests and red team exercises to validate control effectiveness before audits
Updating compliance documentation in response to changes in vehicle architecture or regulatory updates

Module 9: Incident Response and Forensics in Automotive Systems

Designing secure logging mechanisms that survive ECU resets and power cycles for forensic analysis
Establishing secure channels for transmitting forensic data from vehicles to OEM response centers
Defining data minimization policies to comply with privacy laws during incident data collection
Creating vehicle-specific playbooks for containment, such as isolating compromised ECUs via gateway rules
Preserving chain of custody for ECU memory dumps during physical forensic investigations
Coordinating with law enforcement and regulatory bodies during high-impact cybersecurity incidents
Reconstructing attack timelines using correlated logs from multiple ECUs and backend systems
Conducting post-incident reviews to update threat models and prevent recurrence across vehicle lines