Skip to content

Session 2 | Stage 2 | Dr Ken Tindell | CryptoCAN Encrypted messaging on CAN bus

Blue TeamSecure Our Streets26 minAdvancedOpen on YouTube ↗

Examines session 2 | Stage 2 | Dr Ken Tindell | CryptoCAN Encrypted messaging on CAN bus and evaluates key implications for security practitioners.

Summary

## Why Encrypt CAN?

Dr. Ken Tindell (CTO, Kynetix) argues that Controller Area Network was never designed for confidentiality, yet vehicles increasingly need authenticated, encrypted in-vehicle messaging. Mainstream IT crypto stacks rarely fit CAN's tight timing and bandwidth limits.

## CryptoCAN Design

CryptoCAN adapts automotive SHE (Security Hardware Extension) concepts, including separate authentication and encryption keys, secure key loading, and software HSM emulation. On a Cortex-M0, AES operations run in roughly 13 microseconds with only a few kilobytes of code and ROM tables.

## Message Authentication

Authentication uses CMAC via SHE generate/verify APIs. Verify-only key permissions prevent endpoints that only check messages from forging MACs. Tindell details bit-truncation checks and why sender and verifier roles must remain distinct on constrained ECUs.

## Practical Impact

The talk shows that meaningful CAN security is achievable without bolting on enterprise TLS. Done correctly, embedded crypto can meet real-time automotive requirements while raising the bar against bus injection and tampering.

Related talks