Safety and security guides
What functional safety and cybersecurity mean for in-vehicle messages: E2E counters and CRCs, authenticated messages with SecOC, ISO 26262, ISO/SAE 21434 and UN R155 and R156.
4 guides Read them in this order
- AUTOSAR E2E protection on CAN: counters, CRCs and Data IDs explained How AUTOSAR end-to-end protection works on CAN messages. Profiles 1, 2, 11 and 22 bit by bit, the Data ID modes, what the receiver checks, and the larger profiles for CAN FD and Ethernet. Python code that reproduces the example values in the AUTOSAR specification.
- SecOC explained: authenticated CAN messages with MACs and freshness values How AUTOSAR Secure Onboard Communication protects CAN and CAN FD messages against manipulation and replay. The authenticator, freshness values, truncation, Profile 1 (24-bit CMAC, 8-bit freshness), the payload cost, and a tested Python sender and receiver.
- ISO 26262 for CAN and test engineers: what functional safety means for messages What ISO 26262 asks of in-vehicle communication, in practical terms. ASIL determination from severity, exposure and controllability, how safety goals become requirements on CAN messages, E2E protection, timeouts and safe states, hardware metrics, tool qualification, and how SOTIF differs.
- ISO/SAE 21434, UN R155 and R156 explained for CAN and ECU engineers What the vehicle cybersecurity regulations UN R155 and R156 require, how ISO/SAE 21434 and ISO 24089 support them, how a TARA works step by step with a CAN example, and what changes in daily work on messages, diagnostics and software updates.