ISO 26262:2018 — Functional Safety for Road Vehicles
ISO 26262:2018 (2nd edition) is the international standard for functional safety of electrical and electronic (E/E) systems in road vehicles. It addresses hazards caused by malfunctioning behaviour of E/E safety-related systems. Defines Automotive Safety Integrity Levels (ASIL A-D) based on hazard analysis. Covers the full safety lifecycle from concept through decommissioning. 12 parts covering management, system/hardware/software development, production, and field monitoring. The foundational automotive safety standard.
Framework summaries on this platform are AI-assisted interpretations for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (8)
Part 2: Management of Functional Safety
| Code | Title |
|---|---|
| ISO-26262-2-5 | Overall safety management |
| ISO-26262-2-6 | Safety management during the concept and product development |
| ISO-26262-2-7 | Safety management after release for production |
| ISO-26262-2-8 | Safety culture |
| ISO-26262-2-9 | Confirmation measures |
Part 3: Concept Phase
| Code | Title |
|---|---|
| ISO-26262-3-5 | Item definition |
| ISO-26262-3-6 | Initiation of the safety lifecycle |
| ISO-26262-3-7 | Hazard analysis and risk assessment (HARA) |
| ISO-26262-3-8 | Functional safety concept |
Part 4: Product Development at the System Level
| Code | Title |
|---|---|
| ISO-26262-4-10 | Functional safety assessment |
| ISO-26262-4-5 | Initiation of product development at the system level |
| ISO-26262-4-6 | Specification of the technical safety requirements |
| ISO-26262-4-7 | System design |
| ISO-26262-4-8 | Item integration and testing |
| ISO-26262-4-9 | Safety validation |
Part 5: Product Development at the Hardware Level
| Code | Title |
|---|---|
| ISO-26262-5-10 | Hardware integration and verification |
| ISO-26262-5-5 | Initiation of product development at the hardware level |
| ISO-26262-5-6 | Specification of hardware safety requirements |
| ISO-26262-5-7 | Hardware design |
| ISO-26262-5-8 | Evaluation of the hardware architectural metrics |
| ISO-26262-5-9 | Evaluation of safety goal violations due to random hardware failures |
Part 6: Product Development at the Software Level
| Code | Title |
|---|---|
| ISO-26262-6-10 | Software integration and testing |
| ISO-26262-6-11 | Verification of software safety requirements |
| ISO-26262-6-5 | Initiation of product development at the software level |
| ISO-26262-6-6 | Specification of software safety requirements |
| ISO-26262-6-7 | Software architectural design |
| ISO-26262-6-8 | Software unit design and implementation |
| ISO-26262-6-9 | Software unit testing |
Part 7: Production, Operation, Service and Decommissioning
| Code | Title |
|---|---|
| ISO-26262-7-5 | Production |
| ISO-26262-7-6 | Operation, service (maintenance and repair) |
| ISO-26262-7-7 | Decommissioning |
Part 8: Supporting Processes
| Code | Title |
|---|---|
| ISO-26262-8-10 | Documentation |
| ISO-26262-8-11 | Confidence in the use of software tools |
| ISO-26262-8-12 | Qualification of software components |
| ISO-26262-8-13 | Qualification of hardware components |
| ISO-26262-8-14 | Proven in use argument |
| ISO-26262-8-5 | Interfaces within distributed developments |
| ISO-26262-8-6 | Specification and management of safety requirements |
| ISO-26262-8-7 | Configuration management |
| ISO-26262-8-8 | Change management |
| ISO-26262-8-9 | Verification |
Part 9: ASIL-Oriented and Safety-Oriented Analyses
| Code | Title |
|---|---|
| ISO-26262-9-5 | Requirements decomposition with respect to ASIL tailoring |
| ISO-26262-9-6 | Criteria for coexistence of elements |
| ISO-26262-9-7 | Analysis of dependent failures |
| ISO-26262-9-8 | Safety analyses |
Maps to 589 other frameworks
Frequently Asked Questions
What is ISO 26262:2018 — Functional Safety for Road Vehicles?
ISO 26262:2018 — Functional Safety for Road Vehicles is a compliance framework from International (ISO) with 8 domains and 45 controls. ISO 26262:2018 (2nd edition) is the international standard for functional safety of electrical and electronic (E/E) systems in road vehicles. It addresses hazards caused by malfunctioning behaviour of E/E safety-related systems. Defines Automotive Safety Integrity Levels (ASIL A-D) based on hazard analysis. Covers the full safety lifecycle from concept through decommissioning. 12 parts covering management, system/hardware/software development, production, and field monitoring. The foundational automotive safety standard. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
How many controls does ISO 26262:2018 — Functional Safety for Road Vehicles have?
ISO 26262:2018 — Functional Safety for Road Vehicles has 45 controls organised across 8 domains. The largest domains are Part 8: Supporting Processes (10 controls), Part 6: Product Development at the Software Level (7 controls), Part 4: Product Development at the System Level (6 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
What frameworks does ISO 26262:2018 — Functional Safety for Road Vehicles map to?
ISO 26262:2018 — Functional Safety for Road Vehicles maps to 589 other compliance frameworks. The top mapping partners are Azure Security Benchmark (9% coverage), C5 (Germany) (9% coverage), CAIQ (CSA) (9% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I get started with ISO 26262:2018 — Functional Safety for Road Vehicles compliance?
Start your ISO 26262:2018 — Functional Safety for Road Vehicles compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about ISO 26262:2018 — Functional Safety for Road Vehicles requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 45 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 692 frameworks.
Get Started Free →Free forever — no credit card required