| Attack Surface | Threat | ISO/SAE 21434 TARA Category |
|---|---|---|
| OBD-II port | Physical access; ECU firmware replacement | Physical tampering |
| Telematics (4G/5G) | Remote code execution; backend compromise | Network attack |
| Bluetooth/WiFi | Key fob relay attack; infotainment compromise | Wireless attack |
| USB/CD media | Malware via media update; infotainment bridge to safety network | Physical media |
| V2X (C-V2X) | Spoofed infrastructure messages (false traffic light) | External data injection |
| OTA update channel | Malicious update package; update rollback | Supply chain attack |
Threat Model for Modern Vehicles
Security Zone Architecture
Vehicle Security Zones (UNECE R155)
Zone 1: External (Untrusted)
┌──────────────────────────────────────────────────┐
│ OBD-II port │ Bluetooth │ WiFi │ USB │
│ V2X receiver │ Cloud API │ 4G/5G │ │
└──────────────────┬───────────────────────────────┘
│ Firewall / IDS
Zone 2: Infotainment (Low Trust)
┌──────────────────▼───────────────────────────────┐
│ IVI HMI │ Navigation │ App Store │ Media │
└──────────────────┬───────────────────────────────┘
│ Security Gateway (IDPS + Firewall)
Zone 3: Vehicle (Medium Trust)
┌──────────────────▼───────────────────────────────┐
│ Gateway ECU │ BCM │ HVAC │ Body functions │
└──────────────────┬───────────────────────────────┘
│ Hardware Security Module gate
Zone 4: Safety-Critical (High Trust)
┌──────────────────▼───────────────────────────────┐
│ EPS │ AEB │ ESC/ABS │ Airbag │ Zone ECUs │
└──────────────────────────────────────────────────┘
Zone 4 → Zone 3 only via authenticated, validated signalCryptographic Architecture
YAMLcrypto_architecture.yaml
# Vehicle cryptographic architecture per ISO/SAE 21434
crypto_services:
secure_boot:
algorithm: ECDSA P-256
key_storage: HSM (EVITA Full)
verification: every boot before RTOS start
ota_update_signing:
algorithm: Ed25519
key_length: 256-bit
standard: UPTANE (dual-key: Director + Image repo)
rollback_protection: anti-rollback counter in HSM
can_message_auth:
algorithm: CMAC-AES-128
standard: AUTOSAR CAN-SEC / CANsec (future)
key_derivation: per-ECU symmetric key from HSM
vehicle_identity:
certificate: X.509 per vehicle (provisioned at factory)
ca: OEM PKI root CA
use: TLS 1.3 for V2C communication; DoIP authSummary
Security zone design is the architectural response to UNECE Regulation R155, which requires OEMs to implement a Cyber Security Management System (CSMS) and demonstrate that vehicle cybersecurity was systematically engineered. The four-zone model (external, infotainment, vehicle, safety-critical) maps directly to trust levels: no message from Zone 1 should reach Zone 4 without being validated by the security gateway. The critical design principle is asymmetric trust: safety-critical ECUs (Zone 4) should never accept configuration or data directly from the infotainment domain (Zone 2), even if the infotainment request appears legitimate. The only path from Zone 2 to Zone 4 should be via the authenticated and filtered security gateway.
🔬 Deep Dive — Core Concepts Expanded
This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.
Key principles to reinforce:
- Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
- Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
- Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.
🏭 How This Topic Appears in Production Projects
- Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
- Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
- Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.
⚠️ Common Mistakes and How to Avoid Them
- Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
- Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
- Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
- Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.
📊 Industry Note
Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.