What it is
ISO 26262 is a family of standards for functional safety in road vehicles. It addresses hazards caused by malfunctioning safety-related electrical and electronic systems, including their interactions. Functional safety means managing the risk that a malfunction could harm people.
Its central idea is a safety lifecycle: identify hazards, define safety goals, allocate requirements, develop and verify the solution, and maintain safety through production, operation, service and decommissioning. A safety case connects the argument that safety has been achieved with supporting evidence.
Who it applies to
The standard concerns safety-related E/E systems in series-production road vehicles, excluding mopeds. Vehicle manufacturers, system suppliers, software developers and semiconductor suppliers contribute different parts of the safety work.
Scope follows the vehicle function and its hazards, rather than controller size. An HPC, zone controller or small LIN node can receive safety requirements. Conversely, being installed in a vehicle does not automatically make every component safety-related.
ISO 26262 is a technical standard; its use can be required by customer agreements. It does not itself grant vehicle type approval.
What it covers
Work starts with an item definition describing the function, boundaries, interfaces and operating context. Hazard analysis and risk assessment (HARA) considers hazardous events using severity, exposure and controllability. It establishes safety goals and their Automotive Safety Integrity Levels (ASILs).
ASILs run from A to D, with D demanding the greatest rigor. An ASIL describes the integrity required for a safety goal and derived requirements; it is not a general quality rating for an ECU.
| Activity | Practical result |
|---|---|
| Safety concepts | Functional and technical requirements allocated to the design |
| System, hardware and software development | Architecture, implementation, analyses and verification evidence |
| Safety management and supporting processes | Plans, traceability, change control and supplier coordination |
| Confirmation and release activities | Independent scrutiny where required and an evidence-based release decision |
The standard addresses systematic faults, such as incorrect requirements, and random hardware failures. Hardware analysis considers architectural metrics and probabilistic failure evaluation. Software work emphasizes disciplined development, verification and control of interference.
How it fits with other documents
ISO 26262 adapts the functional-safety approach of IEC 61508 to road vehicles. ISO 21448, commonly called SOTIF, addresses hazards associated with functional insufficiencies and reasonably foreseeable misuse. ISO/SAE 21434 addresses automotive cybersecurity engineering; safety and security teams must coordinate where their concerns interact.
AUTOSAR can support implementation of safety mechanisms and software architecture. Using AUTOSAR, a qualified component or a supplier safety manual does not establish vehicle-level compliance by itself: integration must satisfy the allocated requirements and assumptions.
In practice
Consider a zone controller supplying a safety-relevant actuator. The team first establishes which malfunction could create a hazardous event. It then derives requirements for power control, fault detection and the required reaction.
A watchdog reset or power shutdown is suitable only if it supports the safety concept. Some functions require continued operation or a controlled transition. Detection and reaction must complete within the relevant fault tolerant time interval.
Daily work therefore includes tracing requirements, checking supplier assumptions, analyzing shared power and computing resources, testing fault reactions and reviewing changes. Evidence must show that the integrated vehicle function meets its safety goals, including when a component fails.