Powered by Smartsupp


Enhancing Automotive Safety and Security: The Role of TARA and ELM Automotive Compliance


 

Introduction

In the rapidly evolving automotive industry, the integration of advanced technologies has brought about significant improvements in vehicle performance and user experience. However, these advancements also introduce new challenges, particularly in the realms of cybersecurity and functional safety. 

To address these challenges, the establishment of robust frameworks and standards is essential. Among these, the Threat Analysis and Risk Assessment (TARA) and the IBM Engineering Lifecycle Management (ELM) Automotive Compliance framework play pivotal roles in ensuring that vehicles are both safe and secure.

Understanding Key Standards in Automotive Safety and Cybersecurity

The automotive industry follows essential standards to ensure both safety and cybersecurity across the design, development, and lifecycle of vehicles. Here’s a user-friendly breakdown of the main standards:

1. UNECE WP.29/R155 – Cybersecurity Management Requirement

  • What it is: This regulation requires car manufacturers and their suppliers to create a Cyber Security Management System (CSMS). The CSMS is essential for identifying and managing cybersecurity risks throughout the vehicle's design, development, and production stages.
  • Why it matters: Compliance is crucial for legal approval in regions that enforce this regulation. Manufacturers need this to sell vehicles in those markets.
  • Timeline: It’s been mandatory since July 2022 for all new vehicle models, and from July 2024, it applies to all newly produced vehicles.

2. ISO/SAE 21434 – Cybersecurity in Product Development

  • What it is: This standard provides detailed guidelines on how manufacturers should handle cybersecurity during the development process, supporting the requirements of UNECE R155.
  • Why it matters: It ensures a systematic approach to identifying and managing cybersecurity risks, which helps manufacturers comply with R155.
  • Focus: It covers cybersecurity practices that must be embedded within product development processes to protect automotive systems from cyber threats.

3. ASPICE (Automotive SPICE) – Process Improvement and Maturity

  • What it is: ASPICE is a framework for assessing and improving processes in automotive software and systems engineering.
  • Why it matters: It guides manufacturers in developing products with a focus on cybersecurity and functional safety, ensuring consistent quality and safety in automotive development.
  • Application: Used to evaluate the maturity of a company’s processes and helps align with industry best practices.

4. ISO 26262 – Functional Safety Standard

  • What it is: This safety standard sets out requirements for engineering processes in automotive systems, focusing on the safety aspects of software, hardware, and system design.
  • Why it matters: By following ISO 26262, manufacturers can prioritize safety throughout the product lifecycle, reducing risks to drivers and passengers.
  • Focus: It ensures that safety-related components in vehicles are designed to perform reliably and safely under various conditions.

5. HARA (Hazard Analysis and Risk Assessment)

  • What it is: HARA is a systematic approach designed to identify, evaluate, and mitigate risks associated with electrical and electronic systems in vehicles. It plays a crucial role in the concept phase of the ISO 26262 safety lifecycle, guiding the development of safety measures to prevent or control potential hazards.
  • Why it matters: 
    • Structured Risk Management: HARA provides a clear framework for systematically identifying and addressing potential hazards, ensuring that all possible risks are considered during the development process.
    • Resource Allocation: Engineers save time performing HARA because they can rely on a pre-defined template compliant to ISO 26262. Also, teams benefit from improved consistency because of the pre-defined HARA format and automized ASIL Value calculation
    • Compliance and Standardization: Adhering to HARA and ISO 26262 ensures that automotive manufacturers meet international safety standards, facilitating global market access and consumer trust.
  • Focus: The goal of HARA is to identify and evaluate potential hazards that may occur in an automotive system due to malfunctions in electrical and electronic (E/E) systems. This involves linking each identified risk to a corresponding safety requirement.

The Role of TARA in Cybersecurity

Threat Analysis and Risk Assessment (TARA) is a critical component of the cybersecurity framework within the ELM Automotive Compliance. TARA involves systematically identifying potential threats to automotive systems and assessing the associated risks. This process is essential for developing effective mitigation strategies and ensuring that both safety and security are prioritized during the design and development phases.

1. Proactive Risk Identification: TARA enables organizations to identify potential threats early in the development process. By understanding the types of attacks that could target their systems, manufacturers can design countermeasures that effectively mitigate these risks.

2. Informed Decision-Making: The insights gained from TARA inform decision-making throughout the product lifecycle. By understanding the risk landscape, organizations can allocate resources more effectively and prioritize security measures that address the most critical vulnerabilities.

3. Continuous Improvement: TARA is not a one-time activity; it is an ongoing process that evolves as new threats emerge and technologies advance. This continuous assessment allows organizations to adapt their cybersecurity strategies and maintain a robust defense against potential attacks.

Integrating Cybersecurity and Functional Safety

IBM's ELM Automotive Compliance framework emphasizes the importance of integrating cybersecurity and functional safety. This integration is achieved through a lifecycle approach that considers both aspects at every stage of product development. By aligning the requirements of ISO 26262 with the cybersecurity measures outlined in ISO/SAE 21434, organizations can create a comprehensive strategy that enhances the safety and security of their vehicles.

Product development plan with each phase, including introductory, organizational and project lifecycles

1.) Product development plan

1. Unified Compliance Framework: The ELM Automotive Compliance framework addresses multiple standards, ensuring that both cybersecurity and functional safety are considered throughout the product development lifecycle. This unified approach allows organizations to meet regulatory requirements while ensuring the safety and security of automotive systems.

 

2. Collaboration Across Teams: Integrating cybersecurity and functional safety requires collaboration between different teams within an organization. By fostering communication and cooperation between safety engineers and cybersecurity experts, manufacturers can develop solutions that address both safety and security concerns effectively.

 

3. Enhanced Consumer Trust: By prioritizing both cybersecurity and functional safety, manufacturers can enhance consumer trust in their products. As consumers become increasingly aware of the importance of cybersecurity in vehicles, demonstrating a commitment to these standards can differentiate manufacturers in a competitive market.

In the Assets module you can Create assets, set asset category, associate related

2.) Asset identification

 

Tara module allow you to identify damage scenarios for cybersecurity properties, associate scenarios with assets....

3.) Last two steps of Asset identification

 

To assess impact - insert a

4.) Assess stakeholder impact

 

Use the TARA calculator to compute overall impact  for each damage scenario

5.) Impact Rating

 

1. Create new threat scenarios 2, Link them to damage scenarios they can potentially cause

6.) Identify threat scenarios

Create new attack paths and link them to threat scenarios, calculate attack feasibility

7.) Create attack paths

Use TARA calculator to calculate risk values using attack path feasibilities and damage scenario impacts

8.) Overall Risk Assessment

View reports including traceability, TARA and Process exception

9.) TARA Reports

What can IBM and Softacus do for you?

With IBM's tools, achieving ISO 26262 certification is straightforward. The IBM Jazz Platform offers a range of options to monitor your progress and secure your compliance maturity level.

The IBM ELM Solution for Automotive Engineering – ISO-26262 provides a collection of best practices designed to support organizations in creating products that align with the ISO-26262 functional safety standard. This solution covers key areas defined by ISO-26262, including functional safety management, conceptual design, systems engineering, and software development. It facilitates a gradual adoption of processes, practices, and tools, helping to accelerate the value gained from process improvement efforts.

Conclusion

In conclusion, the integration of TARA and the ELM Automotive Compliance framework is essential for enhancing the safety and security of modern vehicles. By establishing a robust Cyber Security Management System (CSMS) and prioritizing both cybersecurity and functional safety, automotive manufacturers can navigate the complexities of the evolving landscape while ensuring compliance with regulatory standards. As the industry continues to advance, the commitment to these principles will be crucial in building safer, more secure vehicles for the future.

Softacus Services

We, in Softacus, are experts when it comes to consulting and service delivery of IBM software products and solutions in your business. We help our clients to improve visibility and transparency when licensing and managing commercial software, providing measurable value while increasing efficiency and accountability and we are providing services in different areas (see Softacus Services).
IBM ELM extensions developed by Softacus are free of charge for the customers who ordered IBM ELM licenses via Softacus or for the customers who ordered any of our services. If you are interested in any of our IBM ELM extensions, you found a bug or you have any enhancement request, please let us know at info@softacus.com.

Image

Softacus AG

Löwenstrasse 20
8001 Zürich
Switzerland
E-Mail: info@softacus.com
Tel.: +41 43 5087081
Fax: +41 43 344 6075 

VAT: CHE-108.817.809 MWST
D-U-N-S® Number 486800618

Image

Softacus GmbH

Westendstrasse 28
60325 Frankfurt am Main
Germany
E-Mail: info@softacus.com
Tel.: +49 69 34876544
Fax: +49 69 5830 35709

VAT: DE301903892
D-U-N-S® Number 313482703

Image

Softacus s.r.o.

Křídlovická 351/47A
603 00 Brno
Czech Republic
E-Mail: info@softacus.com
Tel.: +420 530333482
Fax: +41 43 344 6075

VAT: CZ07286333
D-U-N-S® Number 496165108

Image

Softacus s.r.o.

Tatranské nám. 3
058 01 Poprad
Slovakia
E-Mail: info@softacus.com
Tel: +421 911 083 612
Fax: +41 43 344 6075

VAT: SK2121388148
D-U-N-S® Number  2121388148

Offcanvas

Cookie Policy