Why it exists
The Ethernet backbone carries the vehicle’s most important traffic. Without protection, a compromised node could read or inject frames on any link it reaches.
What the options are
| Mechanism | Layer | Protects | Typical use |
|---|---|---|---|
| MACsec | Link (L2) | Each hop, all traffic, in hardware | Backbone links between zones and HPCs |
| IPsec | Network (L3) | End to end, IP traffic | Tunnels between ECUs |
| TLS / DTLS | Transport | End to end, per connection | Services, backend connections |
| SecOC | PDU | Selected messages, across mixed buses | Control messages |
Simplified layout: SecTAG includes the MACsec EtherType, tag and ICV lengths depend on configuration, and preamble and FCS are omitted.
How to choose
MACsec protects everything on a link with little software effort but ends at every switch. TLS protects a connection end to end but costs CPU. Many architectures combine MACsec on the backbone with TLS for backend and SecOC for messages that cross into CAN.
Best practices
- Decide per traffic class, guided by the TARA.
- Automate key agreement (MKA) and plan for key updates.
Common pitfalls
- Assuming encryption equals authentication of the application — a compromised endpoint still sends valid traffic.