Secured Data Transmission - UDS Diagnostics

0x84 Secured Data Transmission Overview

0x84 Wrapping UDS Payload with CMAC/AEAD

  Normal UDS request (0x22 ReadDID):
  ┌──────┬─────────┐
  │ 0x22 │ DID     │  (plaintext)
  └──────┴─────────┘

  Secured UDS request (0x84 wrapping 0x22):
  ┌──────┬──────────────┬──────────────────────────────────┬────────────┐
  │ 0x84 │ SignatureLen  │ Encrypted/Signed UDS payload     │ Signature  │
  │      │ + algorithm  │ (AES-128-GCM ciphertext)         │ (CMAC/tag) │
  └──────┴──────────────┴──────────────────────────────────┴────────────┘

  Security options (OEM-configured):
  ├── Signature only (integrity + authenticity; no confidentiality)
  ├── Encryption only (confidentiality; no integrity for metadata)
  └── AEAD (encryption + authentication tag): AES-128-GCM recommended

  Use case: protect sensitive calibration data or seed-key exchange from
  eavesdropping or replay attacks on the diagnostic bus

When to Use 0x84 vs TLS

Scenario	0x84 Secured Data	TLS (DoIP)
CAN bus (no IP)	Only option for CAN-based diagnostic security	Not applicable
DoIP/Ethernet	Rarely used (TLS covers entire TCP session)	Preferred: TLS 1.3 on TCP 13400
Partial payload protection	Possible: protect specific DIDs only	All-or-nothing per TCP session
Legacy tool support	Harder: tool must support 0x84 stack	TLS is standard; widely supported

TLS 1.3 as the Preferred Alternative on Ethernet

💡 TLS over DoIP vs 0x84

For Ethernet-connected ECUs, TLS 1.3 on the DoIP TCP connection is simpler and more secure than 0x84: it protects all UDS traffic transparently, handles key exchange and certificate validation automatically, and is universally supported by diagnostic tools. Service 0x84 is primarily relevant for CAN-only ECUs that need selective payload protection without upgrading to Ethernet transport. For new platform development on DoIP, mandate TLS 1.3 with mutual authentication and skip 0x84 implementation.

Summary

Service 0x84 fills the gap between session-level TLS (available on DoIP/Ethernet only) and completely unprotected CAN diagnostic traffic. For CAN-connected high-security ECUs (gateway, TCU), 0x84 with AES-128-GCM provides both confidentiality and integrity for specific UDS exchanges. For DoIP ECUs, TLS 1.3 is the correct answer — it is standardised, tool-supported, and covers all diagnostic traffic without per-service overhead. The driving factor for 0x84 adoption is CAN-based deployment without Ethernet connectivity.

🔬 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.