International (ISO/TC 22/SC 32); adopted as GB/T 34590 (China, MOD), BS ISO 26262 and others

ISO 26262:2018

245 controls. 245 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

245 controls 245 frameworks share controls with it International (ISO/TC 22/SC 32); adopted as GB/T 34590 (China, MOD), BS ISO 26262 and others verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
ISO-26262-2-5Overall safety management0
ISO-26262-2-6Safety management during the concept and product development0
ISO-26262-2-7Safety management after release for production0
ISO-26262-2-8Safety culture0
ISO-26262-2-9Confirmation measures0
ISO-26262-3-5Item definition132
ISO-26262-3-6Initiation of the safety lifecycle0
ISO-26262-3-7Hazard analysis and risk assessment (HARA)119
ISO-26262-3-8Functional safety concept1
ISO-26262-4-10Functional safety assessment1
ISO-26262-4-5Initiation of product development at the system level0
ISO-26262-4-6Specification of the technical safety requirements0
ISO-26262-4-7System design0
ISO-26262-4-8Item integration and testing0
ISO-26262-4-9Safety validation0
ISO-26262-5-10Hardware integration and verification0
ISO-26262-5-5Initiation of product development at the hardware level0
ISO-26262-5-6Specification of hardware safety requirements0
ISO-26262-5-7Hardware design0
ISO-26262-5-8Evaluation of the hardware architectural metrics0
ISO-26262-5-9Evaluation of safety goal violations due to random hardware failures0
ISO-26262-6-10Software integration and testing0
ISO-26262-6-11Verification of software safety requirements0
ISO-26262-6-5Initiation of product development at the software level0
ISO-26262-6-6Specification of software safety requirements0
ISO-26262-6-7Software architectural design0
ISO-26262-6-8Software unit design and implementation0
ISO-26262-6-9Software unit testing0
ISO-26262-7-5Production3
ISO-26262-7-6Operation, service (maintenance and repair)0
ISO-26262-7-7Decommissioning0
ISO-26262-8-10Documentation1
ISO-26262-8-11Confidence in the use of software tools0
ISO-26262-8-12Qualification of software components0
ISO-26262-8-13Qualification of hardware components0
ISO-26262-8-14Proven in use argument0
ISO-26262-8-5Interfaces within distributed developments0
ISO-26262-8-6Specification and management of safety requirements0
ISO-26262-8-7Configuration management45
ISO-26262-8-8Change management38
ISO-26262-8-9Verification1
ISO-26262-9-5Requirements decomposition with respect to ASIL tailoring0
ISO-26262-9-6Criteria for coexistence of elements0
ISO-26262-9-7Analysis of dependent failures0
ISO-26262-9-8Safety analyses0
ISO26262-2.5Safety Management Overall0
ISO26262-2.6Project Dependent Safety Management0
ISO26262-3.5Item Definition0
ISO26262-3.6Hazard Analysis and Risk Assessment1
ISO26262-3.7Functional Safety Concept1
ISO26262-4.6Technical Safety Concept0
ISO26262-4.7System and Item Integration and Testing0
ISO26262-4.8Safety Validation0
ISO26262-5.6Hardware Safety Requirements0
ISO26262-5.7Hardware Design0
ISO26262-5.8Evaluation of Hardware Architectural Metrics0
ISO26262-5.9Evaluation of Safety Goal Violations Due to Random Hardware Failures0
ISO26262-6.10Software Integration and Verification0
ISO26262-6.6Software Safety Requirements0
ISO26262-6.7Software Architectural Design0
ISO26262-6.8Software Unit Design and Implementation0
ISO26262-6.9Software Unit Verification0
ISO26262-7.5Production3
ISO26262-7.6Operation, Service, and Decommissioning0
ISO26262-8.11Confidence in the Use of Software Tools0
ISO26262-8.12Qualification of Software Components0
ISO26262-8.6Specification and Management of Safety Requirements0
ISO26262-9.5Requirements Decomposition with Respect to ASIL Tailoring0
ISO26262-9.7Safety Analyses0
11:44 A semiconductor component and its partitioning0
11:4.14.1 How to consider semiconductor components1
11:4.104.10 Interfaces within distributed developments1
11:4.114.11 Confirmation measures1
11:4.124.12 Clarification on hardware integration and verification1
11:4.24.2 Dividing a semiconductor component in parts0
11:4.34.3 About hardware faults, errors and failure modes1
11:4.44.4 About adapting a semiconductor component safety analysis to system level3
11:4.54.5 Intellectual Property (IP)1
11:4.64.6 Base failure rate for semiconductors1
11:4.74.7 Semiconductor dependent failure analysis2
11:4.84.8 Fault injection0
11:4.94.9 Production and Operation1
11:55 Specific semiconductor technologies and use cases0
11:5.15.1 Digital components and memories1
11:5.25.2 Analogue/mixed signal components1
11:5.35.3 Programmable logic devices0
11:5.45.4 Multi-core components1
11:5.55.5 Sensors and transducers1
12:1010 Safety validation0
12:10.4.110.4.1 Safety validation environment1
12:10.4.210.4.2 Specification of safety validation1
12:10.4.310.4.3 Execution of safety validation0
12:10.4.410.4.4 Evaluation0
12:55 General topics for adaptation for motorcycles0
12:66 Safety culture1
12:77 Confirmation measures: general (types, independency and authority)1
12:88 Hazard analysis and risk assessment0
12:8.4.18.4.1 Initiation of the hazard analysis and risk assessment0
12:8.4.28.4.2 Situation analysis and hazard identification1
12:8.4.38.4.3 Classification of hazardous events1
12:8.4.48.4.4 Determination of safety goals1
12:8.4.58.4.5 Verification0
12:99 Vehicle integration and testing0
12:9.2.19.2.1 Vehicle integration0
12:9.2.29.2.2 Test goals and test methods during vehicle testing1
2:55 Overall safety management0
2:5.4.25.4.2 Safety culture1
2:5.4.35.4.3 Management of safety anomalies regarding functional safety2
2:5.4.45.4.4 Competence management2
2:5.4.55.4.5 Quality management system1
2:5.4.65.4.6 Project-independent tailoring of the safety lifecycle2
2:66 Project dependent safety management0
2:6.4.106.4.10 Confirmation reviews1
2:6.4.116.4.11 Functional safety audit1
2:6.4.126.4.12 Functional safety assessment3
2:6.4.136.4.13 Release for production1
2:6.4.26.4.2 Roles and responsibilities in safety management2
2:6.4.36.4.3 Impact analysis at the item level2
2:6.4.46.4.4 Reuse of an existing element2
2:6.4.56.4.5 Tailoring of the safety activities2
2:6.4.66.4.6 Planning and coordination of the safety activities2
2:6.4.76.4.7 Progression of the safety lifecycle1
2:6.4.86.4.8 Safety case1
2:6.4.96.4.9 Confirmation measures1
2:77 Safety management regarding production, operation, service and decommissioning0
2:7.4.27.4.2 Responsibilities, planning and required processes for production, operation, service and decommissioning1
3:55 Item definition2
3:66 Hazard analysis and risk assessment0
3:6.4.16.4.1 Initiation of the hazard analysis and risk assessment1
3:6.4.26.4.2 Situation analysis and hazard identification2
3:6.4.36.4.3 Classification of hazardous events3
3:6.4.46.4.4 Determination of safety goals2
3:6.4.56.4.5 Management of variances of T&B in hazard analysis and risk assessment0
3:6.4.66.4.6 Verification1
3:77 Functional safety concept0
3:7.4.27.4.2 Derivation of functional safety requirements2
3:7.4.37.4.3 Safety validation criteria1
3:7.4.47.4.4 Verification of the functional safety concept1
4:55 General topics for the product development at the system level0
4:66 Technical safety concept0
4:6.4.26.4.2 Safety mechanisms2
4:6.4.36.4.3 System architectural design2
4:6.4.46.4.4 Safety analyses and avoidance of systematic failures2
4:6.4.56.4.5 Measures for control of random hardware failures during operation2
4:6.4.66.4.6 Allocation to hardware and software1
4:6.4.76.4.7 Hardware-software interface (HSI) specification1
4:6.4.86.4.8 Production, operation, service and decommissioning1
4:6.4.96.4.9 Verification1
4:77 System and item integration and testing0
4:7.4.17.4.1 Specification of integration and test strategy1
4:7.4.27.4.2 Hardware-software integration and testing2
4:7.4.37.4.3 System integration and testing1
4:7.4.47.4.4 Vehicle integration and testing1
4:88 Safety validation0
4:8.4.18.4.1 Safety validation environment1
4:8.4.28.4.2 Specification of safety validation2
4:8.4.38.4.3 Execution of safety validation2
4:8.4.48.4.4 Evaluation1
5:1010 Hardware integration and verification2
5:55 General topics for the product development at the hardware level0
5:66 Specification of hardware safety requirements2
5:77 Hardware design0
5:7.4.17.4.1 Hardware architectural design1
5:7.4.27.4.2 Hardware detailed design1
5:7.4.37.4.3 Safety analyses1
5:7.4.47.4.4 Verification of hardware design2
5:7.4.57.4.5 Production, operation, service and decommissioning1
5:88 Evaluation of the hardware architectural metrics2
5:99 Evaluation of safety goal violations due to random hardware failures0
5:9.4.29.4.2 Evaluation of Probabilistic Metric for random Hardware Failures (PMHF)2
5:9.4.39.4.3 Evaluation of Each Cause of safety goal violation (EEC)1
5:9.4.49.4.4 Verification review0
6:10.410.4 Software integration and verification2
6:11.411.4 Testing of the embedded software2
6:5.45.4 General topics for the product development at the software level3
6:6.46.4 Specification of software safety requirements2
6:7.47.4 Software architectural design2
6:8.48.4 Software unit design and implementation2
6:9.49.4 Software unit verification2
7:55 Planning for production, operation, service and decommissioning2
7:66 Production1
7:77 Operation, service and decommissioning2
8:10.410.4 Documentation management3
8:1111 Confidence in the use of software tools0
8:11.4.211.4.2 Validity of predetermined Tool Confidence Level or qualification1
8:11.4.311.4.3 Software tool compliance with its evaluation criteria or its qualification1
8:11.4.411.4.4 Planning of usage of a software tool1
8:11.4.511.4.5 Evaluation of a software tool by analysis2
8:11.4.611.4.6 Qualification of a software tool1
8:11.4.711.4.7 Increased confidence from use1
8:11.4.811.4.8 Evaluation of the tool development process1
8:11.4.911.4.9 Validation of the software tool1
8:1212 Qualification of software components0
8:12.4.212.4.2 Specification of software component qualification2
8:12.4.312.4.3 Verification of qualification of a software component1
8:1313 Evaluation of hardware elements0
8:13.4.213.4.2 Evaluation of class I hardware elements1
8:13.4.313.4.3 Evaluation of class II hardware elements1
8:13.4.413.4.4 Evaluation of class III hardware elements0
8:1414 Proven in use argument0
8:14.4.214.4.2 Proven in use credit2
8:14.4.314.4.3 Minimum information on candidate1
8:14.4.414.4.4 Analysis of modifications to the candidate1
8:14.4.514.4.5 Analysis of field data2
8:15.415.4 Interfacing an application that is out of scope of ISO 262621
8:16.416.4 Integration of safety-related systems not developed according to ISO 262621
8:55 Interfaces within distributed developments0
8:5.4.15.4.1 Application of requirements1
8:5.4.25.4.2 Supplier selection criteria2
8:5.4.35.4.3 Initiation and planning of distributed development1
8:5.4.45.4.4 Execution of distributed development1
8:5.4.55.4.5 Functional safety assessment activities in distributed developments1
8:66 Specification and management of safety requirements0
8:6.4.16.4.1 Specification of safety requirements1
8:6.4.26.4.2 Attributes and characteristics of safety requirements3
8:6.4.36.4.3 Management of safety requirements3
8:7.47.4 Configuration management2
8:88 Change management0
8:8.4.18.4.1 Planning and initiating change management1
8:8.4.28.4.2 Change requests1
8:8.4.38.4.3 Change request analysis3
8:8.4.48.4.4 Change request evaluation2
8:8.4.58.4.5 Implementing and documenting the change2
8:99 Verification0
8:9.4.19.4.1 Verification planning3
8:9.4.29.4.2 Verification specification2
8:9.4.39.4.3 Verification execution and evaluation2
9:55 Requirements decomposition with respect to ASIL tailoring2
9:66 Criteria for coexistence of elements2
9:77 Analysis of dependent failures1
9:88 Safety analyses1
PART-1ISO 26262-1:2018 Vocabulary0
PART-10ISO 26262-10:2018 Guidelines on ISO 26262 (informative)0
PART-11ISO 26262-11:2018 Guidelines on application of ISO 26262 to semiconductors0
PART-12ISO 26262-12:2018 Adaptation of ISO 26262 for motorcycles0
PART-2ISO 26262-2:2018 Management of functional safety0
PART-3ISO 26262-3:2018 Concept phase0
PART-4ISO 26262-4:2018 Product development at the system level0
PART-5ISO 26262-5:2018 Product development at the hardware level0
PART-6ISO 26262-6:2018 Product development at the software level0
PART-7ISO 26262-7:2018 Production, operation, service and decommissioning0
PART-8ISO 26262-8:2018 Supporting processes0
PART-9ISO 26262-9:2018 ASIL-oriented and safety-oriented analyses0
SERIESISO 26262:2018: the series and its parts0
STATUSEdition status: the second edition and what would lift the build0

Tell me when ISO 26262:2018 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

  • Description of business operations
  • Sensitive information inventory and classification
  • Cybersecurity risk management objectives statement
  • Cybersecurity programme description
  • Item definition document
  • Boundary diagram

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

What this page is

A control-level reference for ISO 26262:2018, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition