Contents
Tracker
Standards & regulations
Every regulation, standard and specification the wiki relies on — one page each, with its status, what it covers and which disciplines must know it. Summaries only: paid standards are never reproduced.
Show topics for
65 documents
Regulations
EU Cyber Resilience Act Horizontal cybersecurity requirements for products with digital elements The EU Cyber Resilience Act sets cybersecurity duties for products with digital elements placed on the Union market; type-approved vehicles are excluded, while many aftermarket devices and some supplier products are still covered. EU · Free / public GB 44496-2024 General technical requirements for software update of vehicles GB 44496-2024 is China's mandatory national standard for how a vehicle software update must behave so the change stays controlled, explained to the user, and safe. SAC (China) · Free / publicVERIFY UN R155 Uniform provisions concerning the approval of vehicles with regard to cyber security and cyber security management system UN R155 requires vehicle manufacturers to manage cybersecurity throughout the vehicle lifecycle and demonstrate that each vehicle type is protected against cyber threats. UNECE · Free / public UN R156 Uniform provisions concerning the approval of vehicles with regard to software update and software updates management system UN R156 requires vehicle manufacturers to manage software updates through controlled processes and demonstrate that vehicles can receive updates safely and securely. UNECE · Free / public
Standards
FIPS 180-4 (SHS) Secure Hash Standard (SHS) The Secure Hash Standard defines SHA-1 and the SHA-2 family, including SHA-256 and SHA-512, which vehicles use to fingerprint software, certificates, and other data. NIST · Free / publicVERIFY FIPS 186-5 (DSS) Digital Signature Standard (DSS) FIPS 186-5 is NIST’s Digital Signature Standard: the approved methods for creating and checking RSA, ECDSA, and EdDSA signatures (including Ed25519) so a receiver can detect tampering and confirm who signed. NIST · Free / publicVERIFY FIPS 197 (AES) Advanced Encryption Standard (AES) FIPS 197 is the NIST standard that defines AES, the symmetric block cipher with a 128-bit block and keys of 128, 192, or 256 bits. NIST · Free / publicVERIFY FIPS 198-1 (HMAC) The Keyed-Hash Message Authentication Code (HMAC) HMAC (FIPS 198-1) lets two parties who share a secret key detect a changed message and reject a tag made by anyone who lacks that key. NIST · Free / publicVERIFY FIPS 202 (SHA-3) SHA-3 Standard: Permutation-Based Hash and Extendable-Output Functions FIPS 202 is NIST's public definition of the SHA-3 hash functions and the SHAKE extendable-output functions, which turn a message into a cryptographic fingerprint. NIST · Free / publicVERIFY FIPS 203 (ML-KEM) Module-Lattice-Based Key-Encapsulation Mechanism Standard FIPS 203 defines ML-KEM, the NIST post-quantum way for two parties to establish a shared secret over a public channel. NIST · Free / publicVERIFY FIPS 204 (ML-DSA) Module-Lattice-Based Digital Signature Standard FIPS 204 is NIST's standard for ML-DSA, a post-quantum digital signature used to show that software, a certificate, or another message was signed by a trusted private key and has not been altered. NIST · Free / publicVERIFY FIPS 205 (SLH-DSA) Stateless Hash-Based Digital Signature Standard FIPS 205 defines SLH-DSA, a post-quantum digital signature based on hash functions that does not require the signer to store changing secret state between signatures. NIST · Free / publicVERIFY IEEE 1003.1 (POSIX) Portable operating system interface, including the PSE51 real-time profile POSIX (IEEE 1003.1) is the standard operating-system interface that keeps application source portable across Unix-like systems, with the smaller PSE51 real-time profile as the minimum AUTOSAR Adaptive expects. IEEE / The Open Group · Free / publicVERIFY IEEE 1609.2 Wireless Access in Vehicular Environments — Security services for applications and management messages IEEE 1609.2 defines how vehicles and roadside devices protect exchanged messages using digital signatures, encryption, and certificates. IEEE · PaidVERIFY IEEE 802.1AE (MACsec) Media Access Control (MAC) Security IEEE 802.1AE, known as MACsec, protects Ethernet traffic against tampering and impersonation, with optional encryption to hide its contents. IEEE · Free / publicVERIFY IEEE 802.1AS (gPTP) Timing and synchronization for time-sensitive applications IEEE 802.1AS defines how networked devices share a common sense of time so that sensors, controllers, and other time-sensitive functions can coordinate their work. IEEE · Free / publicVERIFY IEEE 802.1DG-2025 Time-Sensitive Networking profile for automotive in-vehicle Ethernet communications IEEE 802.1DG selects Ethernet networking features and settings that help vehicle data arrive within predictable time limits. IEEE · Paid IEEE 802.1Qav / 802.1Qbv Credit-based shaper and enhancements for scheduled traffic IEEE 802.1Qav and 802.1Qbv define ways to control Ethernet transmission so time-sensitive vehicle traffic can share links with other data while meeting engineered timing requirements. IEEE · Free / publicVERIFY IEEE 802.1X (MKA) Port-based network access control and MACsec Key Agreement IEEE 802.1X controls which devices may communicate on an Ethernet network and defines MKA, the protocol that manages keys for MACsec protection. IEEE · Free / publicVERIFY IEEE 802.3 automotive PHYs Automotive Ethernet physical layers: 100BASE-T1, 1000BASE-T1, 2.5–10GBASE-T1 and optical IEEE 802.3 automotive PHY specifications define how Ethernet data travels over single-pair copper cables or optical fibre inside a vehicle. IEEE · Free / publicVERIFY IEEE 802.3cg (10BASE-T1S) Physical layer specifications and management parameters for 10 Mb/s operation and associated power delivery over a single balanced pair of conductors IEEE 802.3cg defines Ethernet communication at 10 Mb/s over one wire pair, including 10BASE-T1S for connecting small devices on a shared automotive network. IEEE · Paid ISO 11898 Road vehicles — Controller area network (CAN) ISO 11898 defines how CAN controllers and transceivers exchange messages reliably on vehicle networks using Classical CAN, CAN FD and CAN XL. ISO · Paid ISO 11992 Road vehicles — Interchange of digital information on electrical connections between towing and towed vehicles ISO 11992 defines how a truck and its trailer exchange digital information for braking, running gear, other equipment, and diagnostics. ISO · PaidVERIFY ISO 13400 (DoIP) Road vehicles — Diagnostic communication over Internet Protocol (DoIP) ISO 13400 defines how diagnostic tools find a vehicle and exchange diagnostic messages with its electronic control units over IP networks, typically using Ethernet. ISO · PaidVERIFY ISO 14229 (UDS) Road vehicles — Unified diagnostic services (UDS) ISO 14229 defines the diagnostic requests and responses that tools use to inspect, troubleshoot, control and reprogram vehicle electronic control units. ISO · PaidVERIFY ISO 15118-20 Road vehicles — Vehicle to grid communication interface — Part 20: 2nd generation network layer and application layer requirements ISO 15118-20 defines how an electric vehicle and charging equipment communicate to authorize charging, coordinate power transfer, and support bidirectional energy flow. ISO · PaidVERIFY ISO 15765-2 (ISO-TP) Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 2: Transport protocol and network layer services ISO 15765-2, commonly called ISO-TP, defines how diagnostic messages are carried over CAN, including messages too large to fit in a single CAN frame. ISO · PaidVERIFY ISO 16750-2 Road vehicles — Environmental conditions and testing for electrical and electronic equipment — Part 2: Electrical loads ISO 16750-2 defines electrical supply stresses and tests used to check whether vehicle electronics can withstand conditions such as voltage drops, overvoltage and reversed connections. ISO · PaidVERIFY ISO 17978 (SOVD) Road vehicles — Service-oriented vehicle diagnostics (SOVD) ISO 17978 defines a common diagnostic interface that lets tools inspect and service vehicle computers, their software applications, and traditional electronic control units. ISO · Paid ISO 17987 (LIN) Road vehicles — Local Interconnect Network (LIN) ISO 17987 defines how low-cost sensors, actuators and their controlling ECU communicate over a Local Interconnect Network (LIN) in a vehicle. ISO · PaidVERIFY ISO 21448 (SOTIF) Road vehicles — Safety of the intended functionality ISO 21448 helps engineers address unsafe vehicle behavior caused by limitations in a function’s design or performance, even when nothing has failed. ISO · Paid ISO 24089 Road vehicles — Software update engineering ISO 24089 explains how organisations should plan, prepare and manage vehicle software updates throughout the vehicle life cycle. ISO · PaidVERIFY ISO 26262 Road vehicles — Functional safety ISO 26262 defines how automotive teams manage the risk of harm caused by malfunctioning electrical and electronic systems throughout a vehicle’s lifecycle. ISO · Paid ISO/PAS 8800 Road vehicles — Safety and artificial intelligence ISO/PAS 8800 explains how engineers build evidence that AI used in road vehicles is acceptably safe throughout development and operation. ISO · Paid ISO/SAE 21434 Road vehicles — Cybersecurity engineering ISO/SAE 21434 defines how automotive teams manage cybersecurity risks throughout a vehicle’s lifecycle. ISO/SAE · Paid NIST SP 800-186 Recommendations for Discrete Logarithm-Based Cryptography: Elliptic Curve Domain Parameters NIST SP 800-186 defines recommended elliptic curves, including P-256 and P-384, that engineers use as mathematical building blocks for public-key cryptography. NIST · Free / publicVERIFY NIST SP 800-208 Recommendation for Stateful Hash-Based Signature Schemes NIST SP 800-208 explains how to use quantum-resistant digital signatures whose security depends on carefully tracking which signing keys have already been used. NIST · Free / publicVERIFY NIST SP 800-38 series Block cipher modes of operation: CBC/CTR, CMAC, CCM, GCM and XTS The NIST SP 800-38 series explains how to use block ciphers such as AES to encrypt data, authenticate messages, or combine both protections. NIST · Free / publicVERIFY NIST SP 800-57 Part 1 Recommendation for Key Management: Part 1 – General NIST SP 800-57 Part 1 explains how to choose, protect, use, replace, and retire the cryptographic keys that keep systems secure. NIST · Free / publicVERIFY RFC 5280 Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile RFC 5280 defines how digital certificates and revocation lists are structured and checked so systems can decide which public keys to trust. IETF · Free / publicVERIFY RFC 7748 Elliptic Curves for Security RFC 7748 defines X25519 and X448, two cryptographic functions that let communicating systems establish a shared secret over an untrusted network. IETF · Free / publicVERIFY RFC 8446 (TLS 1.3) The Transport Layer Security (TLS) Protocol Version 1.3 RFC 8446 defines TLS 1.3, a protocol that authenticates communicating endpoints and protects the data exchanged between them. IETF · Free / publicVERIFY RFC 9147 (DTLS 1.3) The Datagram Transport Layer Security (DTLS) Protocol Version 1.3 DTLS 1.3 protects datagram communication, typically over UDP, against eavesdropping and tampering while allowing packets to be lost or arrive out of order. IETF · Free / publicVERIFY RFC 9325 Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) RFC 9325 explains how to configure TLS and DTLS so that encrypted connections also provide dependable authentication and protection against known attacks. IETF · Free / publicVERIFY SAE J1939 Serial control and communications heavy duty vehicle network SAE J1939 is a family of standards that gives electronic controllers in trucks, buses, and other heavy-duty equipment a common way to exchange operating data and diagnostic information. SAE · PaidVERIFY
Industry specifications
Arm ARM (A-profile) Arm Architecture Reference Manual for A-profile architecture The Arm Architecture Reference Manual for A-profile is the rulebook for how Cortex-A application processors execute instructions, take exceptions, and separate privileged and secure software. Arm · Free / publicVERIFY ARM IHI 0070 (SMMU) Arm System Memory Management Unit Architecture Specification Arm's specification for the System Memory Management Unit (SMMUv3), the block that translates and protects memory accesses from devices other than the CPU on an application processor. Arm · Free / publicVERIFY ASAM SOVD Service-oriented vehicle diagnostics ASAM SOVD is the specification for a web-style diagnostic API that lets testers reach high-performance computers and other service-oriented vehicle software, while classic control units stay on UDS. ASAM · PaidVERIFY AUTOSAR Adaptive Platform Adaptive Platform execution management, state management, and operating system interface The Adaptive Platform's Execution Management, State Management, and operating-system interface define how applications on a high-performance ECU are started, stopped, and grouped into states on a POSIX operating system. AUTOSAR · Free / publicVERIFY AUTOSAR Classic Platform Classic Platform layered architecture, runtime, operating system, and basic software The AUTOSAR Classic Platform is the standard layered software architecture for microcontroller ECUs, covering application components, the runtime environment, the operating system, and basic software. AUTOSAR · Free / public AUTOSAR communication & SOME/IP (Foundation protocols) Communication stack, Communication Management, and SOME/IP foundation protocols These AUTOSAR specifications define how a Classic ECU moves signals and PDUs, how an Adaptive ECU offers and calls services, and how SOME/IP carries and discovers those services on IP. AUTOSAR · Free / publicVERIFY AUTOSAR E2E protection End-to-end communication protection AUTOSAR end-to-end protection puts a counter, a data identifier, and a CRC in the payload so the receiver can tell when safety-related data was corrupted, repeated, lost, reordered, or confused with another signal. AUTOSAR · Free / publicVERIFY AUTOSAR network & mode management Network management and ECU mode management AUTOSAR's network and mode specifications define how Classic ECUs keep a bus awake, coordinate partial wake-up, and return the controller to sleep. AUTOSAR · Free / publicVERIFY AUTOSAR SecOC & crypto stack Secure onboard communication, cryptographic services, and secure hardware extensions AUTOSAR’s secure-communication and crypto specifications define how ECUs authenticate onboard messages and call standard cryptographic services, including keys kept in secure hardware. AUTOSAR · Free / publicVERIFY CiA specifications CAN in Automation specifications CiA specifications are the CAN in Automation documents for building devices on CAN, CAN FD, and CAN XL, including CANopen profiles, physical-layer recommendations, and CANsec, used together with ISO 11898. CiA · Members / paidVERIFY COVESA VSS Vehicle Signal Specification COVESA's Vehicle Signal Specification is an open, shared tree of named vehicle data so services and APIs use the same path and meaning for the same fact. COVESA · Free / publicVERIFY Devicetree Specification Devicetree Specification The Devicetree Specification defines the tree-shaped hardware description that firmware passes to an operating system so drivers can discover the CPUs, memory, and peripherals on a board. devicetree.org · Free / publicVERIFY GlobalPlatform TEE APIs Trusted Execution Environment Client API and Internal Core API These GlobalPlatform specifications define how ordinary software talks to trusted applications that keep cryptographic operations and confidential data inside a hardware-isolated trusted execution environment. GlobalPlatform · Free / publicVERIFY LIN 2.2A LIN Specification Package, Revision 2.2A LIN 2.2A defines how inexpensive automotive sensors and actuators communicate over a shared, centrally scheduled bus. LIN Consortium · Free / publicVERIFY OASIS VIRTIO Virtual I/O Device (VIRTIO) Specification VIRTIO defines standard virtual devices so an operating system inside a virtual machine can use services such as networking and storage through compatible drivers. OASIS · Free / publicVERIFY OMG DDS Data Distribution Service (DDS) and DDS Interoperability Wire Protocol DDS defines how applications publish and subscribe to shared, typed data, while DDSI-RTPS defines how compatible implementations exchange that data over a network. OMG · Free / publicVERIFY OPEN Alliance specifications Interoperability, test and conformance specifications for automotive Ethernet OPEN Alliance specifications help engineers build and test automotive Ethernet components and networks that work reliably together. OPEN Alliance · Free / publicVERIFY SPDX / CycloneDX Software bill of materials formats (SPDX and CycloneDX) SPDX and CycloneDX are public formats for sharing a machine-readable inventory of software components, helping automotive teams track dependencies, licenses, and security exposure. Linux Foundation / OWASP · Free / publicVERIFY TCG TPM 2.0 TPM 2.0 Library Specification, Part 1: Architecture TPM 2.0 Part 1 explains how a Trusted Platform Module protects keys and secrets, controls their use, and provides evidence about a computer’s measured software state. TCG · Free / publicVERIFY Uptane Uptane Standard for Design and Implementation Uptane defines how vehicles check that software updates come from trusted sources and are authorized for the intended electronic control unit. Uptane · Free / publicVERIFY
No topics match.
VERIFY = status not yet confirmed by the editor against the primary source.