Automotive Safety Standards
ISO 26262, ISO 21448 (SOTIF),
ISO/SAE 21434
ISO 26262 Overview
• • Introduced in 2011 (updated in 2018)
• • Ensures functional safety in
electrical/electronic systems in road vehicles
• • Applies to all lifecycle phases: concept to
decommissioning
ISO 26262 Key Components
• • Hazard Analysis and Risk Assessment (HARA)
• • Automotive Safety Integrity Levels (ASIL A-D)
• • Functional safety concept and technical
safety concept
• • Verification and validation methods
ISO 26262 Application Example
• • Example: Electronic Stability Control (ESC)
systems
• • Applied by: Bosch, Continental
• • Ensures the ESC reacts properly in
emergency scenarios
ISO 26262 Non-Compliance Impact
• • Increased risk of system failures
• • Legal consequences in case of accidents
• • Loss of consumer trust and OEM liability
ISO 21448 (SOTIF) Overview
• • Published in 2019
• • Addresses risks not caused by system
malfunctions
• • Focuses on intended functionality (e.g.,
sensors misinterpreting data)
ISO 21448 Key Components
• • Hazard identification from functional
insufficiencies
• • Design validation and testing for unknown
scenarios
• • Mitigation measures for limitations in
perception systems
ISO 21448 Application Example
• • Example: Autonomous Emergency Braking
(AEB)
• • Applied by: Tesla, Waymo
• • Ensures safety despite challenging sensor
inputs
ISO 21448 Non-Compliance Impact
• • Potential for accidents despite functional
systems
• • Regulatory penalties
• • Negative public perception and recalls
ISO/SAE 21434 Overview
• • Published in 2021
• • Focuses on cybersecurity for road vehicles
• • Covers the full lifecycle: concept,
development, operation
ISO/SAE 21434 Key Components
• • Threat analysis and risk assessment (TARA)
• • Cybersecurity goals and concept
• • Incident response and updates
ISO/SAE 21434 Application
Example
• • Example: In-vehicle communication
networks
• • Applied by: Toyota, BMW
• • Protection against hacking of telematics
systems
ISO/SAE 21434 Non-Compliance
Impact
• • Increased vulnerability to cyberattacks
• • Compromised vehicle safety
• • Legal action and data breach penalties

Automotive_Safety_Standards_Presentation.pptx

  • 1.
    Automotive Safety Standards ISO26262, ISO 21448 (SOTIF), ISO/SAE 21434
  • 2.
    ISO 26262 Overview •• Introduced in 2011 (updated in 2018) • • Ensures functional safety in electrical/electronic systems in road vehicles • • Applies to all lifecycle phases: concept to decommissioning
  • 3.
    ISO 26262 KeyComponents • • Hazard Analysis and Risk Assessment (HARA) • • Automotive Safety Integrity Levels (ASIL A-D) • • Functional safety concept and technical safety concept • • Verification and validation methods
  • 4.
    ISO 26262 ApplicationExample • • Example: Electronic Stability Control (ESC) systems • • Applied by: Bosch, Continental • • Ensures the ESC reacts properly in emergency scenarios
  • 5.
    ISO 26262 Non-ComplianceImpact • • Increased risk of system failures • • Legal consequences in case of accidents • • Loss of consumer trust and OEM liability
  • 6.
    ISO 21448 (SOTIF)Overview • • Published in 2019 • • Addresses risks not caused by system malfunctions • • Focuses on intended functionality (e.g., sensors misinterpreting data)
  • 7.
    ISO 21448 KeyComponents • • Hazard identification from functional insufficiencies • • Design validation and testing for unknown scenarios • • Mitigation measures for limitations in perception systems
  • 8.
    ISO 21448 ApplicationExample • • Example: Autonomous Emergency Braking (AEB) • • Applied by: Tesla, Waymo • • Ensures safety despite challenging sensor inputs
  • 9.
    ISO 21448 Non-ComplianceImpact • • Potential for accidents despite functional systems • • Regulatory penalties • • Negative public perception and recalls
  • 10.
    ISO/SAE 21434 Overview •• Published in 2021 • • Focuses on cybersecurity for road vehicles • • Covers the full lifecycle: concept, development, operation
  • 11.
    ISO/SAE 21434 KeyComponents • • Threat analysis and risk assessment (TARA) • • Cybersecurity goals and concept • • Incident response and updates
  • 12.
    ISO/SAE 21434 Application Example •• Example: In-vehicle communication networks • • Applied by: Toyota, BMW • • Protection against hacking of telematics systems
  • 13.
    ISO/SAE 21434 Non-Compliance Impact •• Increased vulnerability to cyberattacks • • Compromised vehicle safety • • Legal action and data breach penalties