Contents
Safety & security

Automotive Cryptography

The building blocks behind SecOC, secure boot, signed updates, TLS and V2X — hashes, MACs, AES, RSA and elliptic curves, certificates and the hardware that keeps keys safe — explained for engineers who are not cryptographers.

Topics in this area

Area overview

Start here

Almost every security mechanism in a vehicle reduces to a few cryptographic questions:

Question Building block Typical vehicle use
Has the data changed? Hash function (SHA-256) Software image checksums, measured boot
Did a trusted partner send it? MAC (AES-CMAC, HMAC) SecOC on CAN and Ethernet
Did the manufacturer release it? Digital signature (ECDSA, RSA) Secure boot, signed OTA packages
Can anyone else read it? Encryption (AES-GCM, AES-CTR) Encrypted update packages, TLS, MACsec
How do two parties agree on a key? Key agreement (ECDH) TLS handshakes, key provisioning
Who is this key holder? Certificates and PKI (X.509) Backend connections, V2X, diagnostics authentication

The algorithms are public and well studied. In practice the weak points are keys (how they are generated, stored, distributed and rotated), randomness, implementation (side channels, misuse of modes) and lifecycle — a vehicle must stay secure for 15 years or more, which is why crypto agility and post-quantum migration matter.

How to read this area

Start with the basics, then the families of algorithms, then how keys and certificates are managed, and finally the hardware that protects them. Every article in the wiki that uses cryptography shows a cryptography box listing what is used, which algorithm and where the key lives.

Latest Cryptography news

All news →

No news on this topic yet.