Why it matters
Diagnostics can reprogram ECUs, change configuration and actuate outputs. Historically protected by simple “seed/key” algorithms that were often reverse-engineered, diagnostic access became a favourite attack path.
What modern secure diagnostics looks like
- Authentication with certificates or backend-issued tokens (UDS 0x29), tied to a person or tool.
- Roles: workshops, OEM engineers and production have different rights.
- Gateway enforcement: requests reach internal ECUs only after authentication.
- Logging of privileged sessions.
Example flow: authentication details depend on the configured method, and failed authentication or authorization prevents protected service access.
Example successful unidirectional certificate exchange: role mapping depends on configuration, and each protected service still requires authorization.
Best practices
- Retire seed/key for sensitive services; keep it only where compatibility demands, with unique secrets.
- Issue short-lived credentials from a backend.
- Balance security with legitimate independent-repair access requirements.
Common pitfalls
- One global secret for all vehicles of a model.