Adapting ISO/SAE 21434 for Effective Cyber
Risk Management in Modern Vehicles
• Engineering and Project Management
• [Insert Date]
Research Motivation
• - Growing digitization and connectivity in
modern vehicles
• - Rising incidents of cyberattacks in the
automotive sector
• - Need for a robust cybersecurity framework
• - Regulatory and market pressures
Research Objectives
• - Examine ISO/SAE 21434 applicability
• - Assess standard adaptation for better risk
management
• - Explore implementation challenges and best
practices
• - Develop a risk framework aligned with
ISO/SAE 21434
Research Questions
• - How well does ISO/SAE 21434 address
cybersecurity threats?
• - What are its adoption and implementation
limitations?
• - How can it be adapted for evolving threats?
• - What can be learned from industry case
studies?
Theoretical Background
• - Overview of ISO/SAE 21434
• - Key Concepts:
• • Threat Analysis and Risk Assessment (TARA)
• • Cybersecurity Goals & Claims
• • Lifecycle-based Security Approach
• - Importance of risk-based thinking
Industry and Technological Context
• - Modern vehicle systems: ECUs, CAN, ADAS,
V2X
• - Cybersecurity for functional safety
• - Regulations: UNECE WP.29, GDPR, NHTSA
• - Impact of AI and OTA updates
PESTEL Analysis
• - Political: Regulations and compliance
• - Economic: Cost of non-compliance
• - Social: User trust and privacy
• - Technological: Evolving threats
• - Environmental: Lifecycle management
• - Legal: Cyber laws and standards
Case Studies
• - Jeep Cherokee Hack (2015)
• - Tesla OTA vulnerability
• - ISO/SAE 21434 adoption by OEMs
• - Lessons: Proactive vs. reactive security
Research Methodology
• - Approach: Qualitative case study &
framework analysis
• - Sources: Whitepapers, standards, interviews
• - Analysis: Gap identification, standard
mapping
Key Findings
• - ISO/SAE 21434 is a strong base, needs
adaptation
• - Challenges: Scalability, supply chain
integration
• - Cybersecurity must span the vehicle lifecycle
• - Cross-industry collaboration is key
Proposed Framework / Recommendations
• - Enhanced TARA with real-time monitoring
• - Vendor cybersecurity assurance plans
• - Standardized threat/vulnerability databases
• - Lifecycle cybersecurity KPIs and auditing
Conclusion & Future Work
• - ISO/SAE 21434 is vital but not standalone
• - Needs dynamic, risk-based adaptation
• - Future: AI threat intelligence, predictive
analytics
• - Continuous collaboration and regulatory
updates

ISO_SAE_21434_Cyber_Risk_Presentation (1).pptx

  • 1.
    Adapting ISO/SAE 21434for Effective Cyber Risk Management in Modern Vehicles • Engineering and Project Management • [Insert Date]
  • 2.
    Research Motivation • -Growing digitization and connectivity in modern vehicles • - Rising incidents of cyberattacks in the automotive sector • - Need for a robust cybersecurity framework • - Regulatory and market pressures
  • 3.
    Research Objectives • -Examine ISO/SAE 21434 applicability • - Assess standard adaptation for better risk management • - Explore implementation challenges and best practices • - Develop a risk framework aligned with ISO/SAE 21434
  • 4.
    Research Questions • -How well does ISO/SAE 21434 address cybersecurity threats? • - What are its adoption and implementation limitations? • - How can it be adapted for evolving threats? • - What can be learned from industry case studies?
  • 5.
    Theoretical Background • -Overview of ISO/SAE 21434 • - Key Concepts: • • Threat Analysis and Risk Assessment (TARA) • • Cybersecurity Goals & Claims • • Lifecycle-based Security Approach • - Importance of risk-based thinking
  • 6.
    Industry and TechnologicalContext • - Modern vehicle systems: ECUs, CAN, ADAS, V2X • - Cybersecurity for functional safety • - Regulations: UNECE WP.29, GDPR, NHTSA • - Impact of AI and OTA updates
  • 7.
    PESTEL Analysis • -Political: Regulations and compliance • - Economic: Cost of non-compliance • - Social: User trust and privacy • - Technological: Evolving threats • - Environmental: Lifecycle management • - Legal: Cyber laws and standards
  • 8.
    Case Studies • -Jeep Cherokee Hack (2015) • - Tesla OTA vulnerability • - ISO/SAE 21434 adoption by OEMs • - Lessons: Proactive vs. reactive security
  • 9.
    Research Methodology • -Approach: Qualitative case study & framework analysis • - Sources: Whitepapers, standards, interviews • - Analysis: Gap identification, standard mapping
  • 10.
    Key Findings • -ISO/SAE 21434 is a strong base, needs adaptation • - Challenges: Scalability, supply chain integration • - Cybersecurity must span the vehicle lifecycle • - Cross-industry collaboration is key
  • 11.
    Proposed Framework /Recommendations • - Enhanced TARA with real-time monitoring • - Vendor cybersecurity assurance plans • - Standardized threat/vulnerability databases • - Lifecycle cybersecurity KPIs and auditing
  • 12.
    Conclusion & FutureWork • - ISO/SAE 21434 is vital but not standalone • - Needs dynamic, risk-based adaptation • - Future: AI threat intelligence, predictive analytics • - Continuous collaboration and regulatory updates