Cars are becoming more and more connected, and therefore vulnerable to the increasing cyber-attacks from the outside. This could severely threaten the safety of passengers and the public. However, the existing standards do not address the unique cybersecurity challenges in automotive engineering, e.g. safety, long life-cycle and use of embedded controllers. Thus, a uniformed guidelines and standards for automotive security need to be established.
ISO/SAE 21434 “Road vehicles – Cybersecurity engineering” is the future automotive security standard. It is important for the automotive product development and all related processes.
The ISO/SAE 21434 will define common terminologies across the global automotive supply chain and drive industry consensus on key cybersecurity issues. It sets minimum criteria for vehicle cybersecurity engineering and provides a governance reference to point to for engineering quality.
Scope of ISO/SAE 21434
The new ISO/SAE 21434 safeguards the entire development process and lifecycle of a road vehicle and promotes “security by design”. Following the V-model, it includes requirements engineering, design, specification, implementation, test and operation.
The ISO/SAE 21434 is therefore a process-oriented standard and helps define a structured process to ensure cybersecurity along the lifecycle. It will not prescribe specific cybersecurity technology, solutions or remediation methods.
We support in establishing a state-of-the-art cybersecurity process where we perform the following activities:
Analyze existing processes with respect to security relevance.
Identify gaps in current process and close with a tailored cybersecurity process.
Moderate and facilitate continuous workshops for reviews and implementation of the security process.
Focus on how cybersecurity requirements are identified and maintained throughout the life-cycle
Perform competitive analysis and maintain knowledge of emerging technologies in both the automotive and consumer electronics field
Develop suitable security roadmap (near-term, mid-term and long-term focus) as it relates to Security and Safety Features
In case of safety-critical products, and where an effective Functional Safety culture and infrastructure is available, we align the process with ISO 26262. This makes best possible benefit of existing competence and organization, thus allowing an efficient introduction of cybersecurity process.
Vector SecurityCheck with threat and risk analysis (TARA), security concept, prioritized proposals and initial methodical instructions
Methodology and tool support for security-oriented tests and resilience
Process assessments for your suppliers
Awareness training on cybersecurity and ISO/SAE 21434 for managers and developers
Training and coaching for managers and developers for the effective implementation of ISO/SAE 21434 across the life-cycle
Interim Safety and Security Manager
Security analyses and security concept for end-to-end safeguards
Development and specification of security requirements based on threat scenarios and Automotive Common Criteria
Assets are agreed, and each asset is analyzed with respect to potential attacks, the effect of the attack and the resulting threat. Each threat is classified according to a security level. The first step in this work package is to analyze the security items in scope of the security engineering process.
Develop concepts and solutions around related Cybersecurity incidents reported in industry and research organizations.
Analyze ECUs, find potential security weakness and report back in order to find new requirements, testing or processes which can be updated to avoid future risk. Storyboards, use cases, proof-of-concept demonstrations, specifications and requirements development experience
Analyze security concept and attack schemes
For each threat with a high security level security goals are derived. Security goals can be summarized as high-level security requirements.
Each security goal is then further refined into functional and technical security requirements which help to achieve the security goal. This step answers to the questions of “How?” and provides concrete answers for the implementation.
Additional to that, if already the initial concept documents are available, a preliminary gap analysis can be performed where it is assessed if the system requirements specification covers the related security aspects based on the security requirements or not.