Cyber Resilience Act Explained: What It Means for the Automotive Industry

With the rapid rise of products utilizing AI, IoT, and connected technology, there has been growing concern across all industries of the cybersecurity risks associated with embedded technology. In response, in December 2024, the European Union put into force the Cyber Resilience Act (CRA), aiming to raise the baseline for security for all digital products and solutions sold in the EU.

Though the regulation originated in Europe, its impact will be global, as today’s interconnected market and supply chain crosses borders. Here’s a closer look at the CRA, why it matters, and its implications on the world’s automotive sector.

What is the Cyber Resilience Act?

The CRA is a legal framework that outlines cybersecurity requirements for products (both hardware and software) with digital elements sold within the European Union. The CRA casts a much wider net than requiring cybersecurity for traditional IT systems, covering everything from smart watches, refrigerators, to agricultural vehicles. In fact, the regulation not only applies to the products themselves, but the full lifecycle of IoT and digital products.

The objective of the CRA is to improve consumer safety, build trust in the digital marketplace, and ensure that manufacturers are held accountable for the security of their products. With this overarching regulation, the hope is that the CRA will foster more transparency for the digital ecosystem, ultimately encouraging innovation while still protecting both businesses and consumers from emerging cyber threats.

The CRA mandates a “security-by-design” approach, which means that companies must integrate cybersecurity from design through the end-of-life (EOL). It also requires vulnerability management and updates, along with compliance and documentation.

Key Implications for Industries Utilizing Connectivity

More and more industries are implementing connected technologies into their supply chain, which means the CRA targets a wide range of industries, including defense, IT infrastructure, and robotics/smart factory, to name a few.

Healthcare & Medical Devices: Many healthcare products now boast connectivity and dedicated user support. Products like remote monitoring tools, smart implants, and other medical devices must secure processed data and ensure device integrity.

Smart Manufacturing: Factories often use IoT and smart automation to optimize their factory lines. Networks and real-time operations must protect against cyberattacks that could disrupt industrial processes.

Space & Defense Systems: Satellites and mission-critical technologies must use robust protection to safeguard against cyber threats and protect sensitive operations for national security.

Agricultural Machinery: Like connected vehicles, agricultural transport is becoming much more connected and software-driven, meaning vehicles like autonomous tractors and sensor-based farming equipment must comply with the CRA as well.

CRA: More than the Law

The CRA represents more than just regulation within the EU. It signals a global shift towards mandatory cybersecurity standards for connected solutions, including all types of vehicles. Early preparation will be key, as manufacturers must utilize security-by-design principles from the development stage of all products.

The CRA introduces a risk-based product classification system, allowing a transition period until December 2027 for full compliance.

CRA timeline infographic

A lack of cybersecurity resilience increases likelihood of a cyber attack, which can not only lead to operational disruption and financial loss within a company’s supply chain and sales funnel, but can also result in legal ramifications. Non-compliance will result in fines of up to €15 million or 2.5% of global turnover and potential EU market bans, which could also result in a lack of brand awareness or worse, negative brand image.

Why the Automotive Industry Should Care

While most automotive vehicles are excluded from the CRA due to the overlapping nature of the CRA regulations with existing regulations (like the WP.29 R155 and EU General Safety Regulation, GSR), certain automotive components like digital components, aftermarket software, andconnected services, as well as vehicles not covered under R155 (like construction or agricultural vehicles) are still subject to the CRA.

Vehicles are complex digital ecosystems, and with more and more technology being embedded into the architecture, compliance will also become more complex. While the details of the CRA are still being worked out, the automotive industry will have to move quickly, as the impacts of the regulation will be wide-ranging. Manufacturers and suppliers can begin by aligning with existing guidelines for cybersecurity resilience in vehicles:

   •  Standard and Regulation Compliance: Automotive manufacturers will have to ensure that they comply with the existing regulations like UNR-155 and GSR, and are recommended to follow standards like ISO/SAE 21434 when it comes to vehicle architecture and connected platforms.

 •  Secure OTA Updates: Manufacturers can ensure that their Over-the-Air (OTA) capabilities are secure and efficient, and ensure that vulnerabilities are patched in real-time.

 •  Regular testing: Testing current architecture for vulnerabilities can be a great starting point to analyze where mitigation is needed.

 •  V2X security and Security Credential Management Systems: While a Security Credential Management System (SCMS) isn’t explicitly required by the CRA, it can support compliance by demonstrating security best practices.

AUTOCRYPT has been closely involved in cybersecurity regulatory compliance from the early stages, focusing on practical, optimized solutions for manufacturers and suppliers. Our expertise in automotive and IT cybersecurity empowers our partners to seamlessly meet regulatory requirements while strengthening their product reliability, market competitiveness, and maintain a positive brand image.

To learn more about the CRA, click here. To contact our team about how your company can get started with CRA compliance, contact global@autocrypt.io.

Post-Quantum Cryptography, and the Future of Automotive Cybersecurity 

As of late, there’s been a lot of worried and concerned discussion regarding quantum computing. There are concerns that once quantum computers become available, all IT systems will collapse and be hacked; some blockchain enthusiasts worry that cryptocurrencies will become obsolete; governments worry that national security systems may be compromised. Are these valid concerns? In today’s blog, we’ll explore what quantum computers are and what we can do to manage concerns about the future.  

What is Quantum Computing?

The modern-day computer uses “bits” as the basic unit, while quantum computers use “qubits.” The key difference is the way that qubits exist. For example, a bit can be a 0 or a 1, but a qubit can be a 0, 1, or both at the same time. Imagine a spinning coin. While spinning, a coin can be both heads and tails. In quantum mechanics, this is called the principle of superposition, and this superposition allows for quantum computers to process many possibilities simultaneously.  

Another interesting property of qubits is entanglement. When qubits are “entangled,” the state of one qubit is directly related to the state of another. This means that if a qubit changes its state, it will instantly affect the other. This phenomenon of qubits enables quantum computers to perform complex calculations far more quickly than a computer using bits, which processes information in a linear, sequential manner.  

Quantum computers are still in the early stages of development, and larger tech companies have already begun to create and use quantum computers for research and experimentation. Many experts will say that the quantum computers available today have a relatively small number of qubits and are susceptible to errors. However, some are optimistic that the technology will achieve more accuracy and broader use very soon. 

What is Post-Quantum Cryptography (PQC)?

While quantum computing holds great promise for solving more complex problems, it also presents a great risk. If misused, quantum computers could, in theory, break encryption methods that secure sensitive data like personal communications, banking transactions, and even confidential government data.  

This is why the development of Post-Quantum Cryptography is crucial to safeguard against this potential threat.  

Post-quantum cryptography (PQC), in simple terms, refers to cryptographic algorithms that are secure even in quantum computing environments. Unlike the traditional cryptographic systems we use today, such as RSA or ECDSA, PQC algorithms rely on mathematical structures that quantum computers are less likely to break, such as lattice-based, hash-based, code-based, or multivariate polynomial-based.

Developing PQC for different use cases is essential because if we wait until quantum computing reaches supremacy, it could quickly render current cryptographic systems obsolete, leaving data vulnerable. The transition to PQC should begin now, as preparing for a quantum future will require proactive effort to ensure cybersecurity frameworks remain intact and resilient.  

PQC Standardization and Regulatory Development

In 2016, the National Institute of Standards and Technology (NIST) launched a competition to standardize PQC. Researchers from all over the world submitted algorithms and through several rounds, 82 proposals were reviewed and in 2022 four algorithms were chosen: SPHINCS+, CRYSTALS-DILITHIUM, CRYSTALS-KYBER, and FALCON. They are incorporating these standards into the Federal Information Processing Standards (FIPS) document, and additional rounds will likely select new algorithms for digital signatures or other uses.  

In April 2024, the European Commission published a recommendation for member states to develop a strategy for implementing PQC, which would define clear goals and timelines for the implementation. This has led several workstreams and think tanks to actively participate in developing and implementing PQC into the European digital infrastructure.  

In 2022, the U.S. passed the “Quantum Computing Cybersecurity Preparedness Act,” which included a federal mandate for federal agencies to transition to PQC. The NSA announced that by 2035, all national security systems should implement PQC.  

In South Korea, the transition to PQC is being actively addressed by the National Intelligence Service and the Ministry of Science and ICT. They released their roadmap for transitioning to quantum-resistant cryptographic systems in 2020, and the roadmap was designed to span over a 15-year period, setting the goal of fully integrating PQC by 2035. 

PQC in Automotive Cybersecurity

The global implementation of PQC roadmaps is ongoing, and use cases can vary across governments and organizations, but one of the most important areas is the automotive industry. As modern vehicles are increasingly becoming software-centric, vehicle architecture is becoming increasingly sophisticated, integrating advanced connectivity features like OTA updates and V2X communications. These advancements enable smarter and more convenient mobility but also create a myriad of cybersecurity challenges if the vehicle architecture is breached, as many of the cryptographic methods were designed for more traditional computing environments.  

However, though regulations and standards do not yet mandate its implementation, manufacturers, suppliers, and solution providers in the industry have already begun to explore and evaluate PQC implementation:  

  • NXP Semiconductors is developing quantum-resistant firmware updates for vehicle applications 
  • Vodafone is testing PQC-secured VPNs, which is focused more on network security, but the company states it could be extended to connected vehicle applications 
  • LG U+ showcased its PQC-based applications like secure digital keys and infotainment systems at CES 2023, and continues to develop quantum-resistant technology for network and cellular applications 

As with traditional IT systems, once quantum computing reaches supremacy, vehicle systems could be vulnerable to attacks. Transition to PQC before quantum computing reaches practical implementation is crucial, as many worry that bad actors could already be stockpiling encrypted automotive data, waiting for quantum computing to enable them to decrypt, a long-term attack strategy known as “Harvest Now, Decrypt Later” (HNDL). 

Preparing for the Post-Quantum Future

While there’s no way to know when quantum computers will reach practical supremacy, one thing is clear: the transition to PQC is no longer a theoretical need but an urgent necessity, especially invehicle applications.  

However, transitioning to PQCbased solutions comes with its own set of challenges. PQC algorithms require a greater amount of computational power, which can be a concern for existing automotive hardware. This is why early testing, standardization, and collaboration will prove to be invaluable for realistic integration.  

The dilemma is not whether we should implement PQC but how quickly we can make it a reality. The automotive sector has a lot of work to do, and security solutions providers like AUTOCRYPT are on track to ensure that the transition happens efficiently and securely. 

 


To stay informed about the latest news on mobility tech and software-defined vehicles, read our blog for more technology insights or subscribe to AUTOCRYPT’s monthly newsletter.

Exploring Maneuver Sharing and Coordinating Service (MSCS) in Autonomous Driving

Autonomous driving is advancing rapidly, with self-driving cars being tested in urban mobility, highways, and logistics. Have you ever wondered how these vehicles communicate to navigate safely? Unlike human drivers, who rely on signals and intuition, autonomous vehicles use data-sharing systems. This blog examines the limitations of cooperative driving systems and introduces Maneuver Sharing in Autonomous Driving through the Maneuver Sharing and Coordinating Service (MSCS) as a solution to improve vehicle communication, safety, and efficiency.

Current cooperative autonomous driving systems rely on Basic Safety Messages (BSMs) within Vehicle-to-Everything (V2X) communication. Each vehicle regularly transmits BSM data, sharing essential information such as speed, position, and heading with surrounding vehicles. This allows vehicles to assess potential collision risks and respond accordingly.

However, BSMs alone cannot convey the intent behind a vehicle’s movements. As shown in the graph below, a BSM provides only fundamental status data without explaining why a vehicle is moving in a certain way.

Basic Safety Messages within V2X

In other words, while BSMs enable cooperative autonomous driving, they lack the capability to communicate driving intentions. If vehicles could understand the purpose behind each movement in advance, particularly in emergency situations, driving safety and efficiency would significantly improve.

Real-World Scenario: The Need for MSCS

To illustrate this, let’s define two key entities:

  • HV (Host Vehicle): The vehicle transmitting its movement intention.
  • RV (Remote Vehicle): The vehicle receiving the movement information.

Now, consider a different scenario: What if the HV had already informed nearby RVs of its intent to change lanes in advance? In that case, the RV could adjust its route ahead of time, leading to a smoother and safer driving experience.

The same idea applies beyond driving. In any situation, whether at work, in school, or during teamwork, understanding someone’s intentions before they act allows for better planning, coordination, and overall efficiency.

What is MSCS?

To overcome the limitations of BSMs, the Maneuver Sharing and Coordinating Service (MSCS) offers a smarter approach to cooperative driving.

MSCS enhances V2X communication by enabling vehicles to share their intended maneuvers. Understanding the purpose behind a vehicle’s movement enables better analysis and response, enhancing overall road safety and efficiency.

Unlike traditional BSM-based driving, which reacts to real-time data, MSCS enables proactive decision-making by considering the planned maneuvers of surrounding vehicles. This advancement leads to a smoother and more coordinated driving experience.

Autonomous Maneuver Sharing in SAE J3186 standards

MSCS operates in compliance with SAE J3186 standards, which defines its primary use cases as:

  1. Cooperative Lane Change
  2. Cooperative Lane Merge

These scenarios demonstrate how MSCS enables smoother lane changes and merges by allowing vehicles to communicate their intended movements. Through MSCS, vehicles notify one another and cooperate to execute maneuvers safely.

It is important to note that MSCS is designed to function based on vehicle intent and follows two distinct communication protocols:

  1. General Vehicle Protocol: Requires mutual negotiation through request and response interactions.
  2. Emergency Vehicle Protocol: Prioritizes emergency vehicles (e.g., ambulances, police cars) without requiring negotiation from surrounding vehicles.

In general, standard vehicles (following the General Vehicle Protocol) must yield to emergency vehicles (following the Emergency Vehicle Protocol). This ensures that special-purpose vehicles can operate efficiently without mutual negotiation.

By implementing MSCS, vehicles can share movement intentions, enabling others to adapt proactively. This results in safer, more efficient, and cooperative autonomous driving.

MSCS and MSCM

Next, let’s differentiate between MSCS and MSCM to explore the operational aspects of MSCS.

  • MSCS (Maneuver Sharing and Coordinating Service): The overall system that enables maneuver coordination
  • MSCM (Maneuver Sharing and Coordinating Message): The message exchanged between vehicles to communicate movement intent

The graph below illustrates the structure of MSCM:

Structure of Maneuver Sharing and Coordinating Service (MSCM)

In MSCS, a Maneuver represents a coordinated movement involving multiple vehicles, while a Sub-Maneuver refers to the individual actions each vehicle takes to carry out that Maneuver.

The Executing Vehicle (HV) initiates the Maneuver request and identifies surrounding Affected Vehicles, which receive MSCM messages to coordinate movement. HV must obtain agreement from Affected Vehicles unless it is an emergency vehicle.

MSCM Data Structure

MSCM Data Structure

MSCM messages contain key data components, including the MSCM Type, which classifies messages into one of eight types:

Autonomous Maneuver Sharing: MSCM Type

Additionally, each Maneuver in MSCM consists of multiple Sub-Maneuvers, structured as follows:

Sub-Maneuvers Data

In conclusion, there are 8 types of protocols for each Maneuver in MSCM.

MSCS Operational Process

To understand the operation of MSCS, let’s examine how it functions in standard vehicles. The system follows three sequential stages:

  1. Awareness State
  2. Maneuver Negotiation State
  3. Maneuver Execution State

MSCS Operational Process

  1. Awareness State
    • This is the preliminary stage of MSCS operation
    • While vehicles are aware of their surroundings via BSM, they have not initiated MSCS yet
    • Only MSCM Type 0 messages (intention notifications) can be sent in this stage
  2. Maneuver Negotiation State
    • Vehicles begin negotiating the execution of a Maneuver
    • Emergency vehicles skip this step, as negotiation is not required
    • MSCM Types 1-3 are used to request and confirm Maneuvers, while Types 4-5 handle cancellations
  3. Maneuver Execution State
    • Vehicles execute the approved Maneuver
    • The HV and RV reach a mutual agreement and act accordingly
    • MSCM Type 7 messages confirm execution, and the Maneuver concludes when all Sub-Maneuvers are completed.

In conclusion, Maneuver Sharing and Coordinating Service (MSCS) represents a significant advancement in autonomous driving, allowing vehicles to communicate their movement intentions and not just their basic status. By enhancing Vehicle-to-Everything (V2X) communication, MSCS improves safety, coordination, and efficiency on the road. Unlike traditional systems that react to real-time data, MSCS enables proactive decision-making, particularly in complex scenarios like lane changes or merges.

With protocols that prioritize emergency vehicles and ensure smooth coordination, MSCS creates a structured environment for vehicles to work together seamlessly. This proactive approach helps prevent collisions, reduces traffic congestion, and leads to safer, more efficient roads. As autonomous vehicles continue to evolve, MSCS will be at the forefront of shaping a future where roads are not only safer but also smarter, bringing us closer to a fully integrated, autonomous transportation system.

 


To stay informed about the latest news on mobility tech and software-defined vehicles, read our blog for more technology insights or subscribe to AUTOCRYPT’s monthly newsletter.

Taking Charge with the Transition to SDVs: Autocrypt’s presence in Europe, an interview with Joohwa Sarah Lee

The automotive industry is going through a period of transformation: with electrification, automation, and software becoming the stars of the show, the traditional automotive industry in Europe has been through the ups and downs of trying to keep up with the Joneses. Established car manufacturers have realized that to navigate the transformations, quickly implementing and introducing new technologies to build innovative business models will be key.  

joohwa sarah lee autocrypt svp
Joohwa Sarah Lee, SVP of AutoCrypt Technologies GmbH

Anticipating these changes, Autocrypt established its European subsidiary back in 2021, and has been working with its European partners and customers to ensure that new innovations go hand-in-hand with secure, resilient environments. And as we head into 2025, we sat down with Joohwa Sarah Lee, who leads Autocrypt’s European business, to discuss the current landscape in Europe, Autocrypt’s strategies, and what we can expect moving forward.

Q: Sarah, could you tell us a bit about yourself, and what you do? 

Hello – I’m Joohwa Sarah Lee, SVP at Autocrypt Technologies. I’ve been in the automotive space for nearly two decades now, first as an R&D engineer at a major German automotive manufacturer, gaining extensive experience in vehicle thermal management systems, HVAC and battery systems.  

My background is in mechanical engineering and computational science engineering (CSE), but I’ve really enjoyed being a part of all areas of the automotive business, from open innovation to even tech scouting, collaborating with internal development departments. At Autocrypt, I’ve been working with creating innovative partnerships with manufacturers and suppliers, and especially highlighting to them the importance of regulatory compliance in the current automotive landscape. 

Q: Wow, your experience is quite extensive in the automotive industry – what got you interested in this industry in the first place? 

I’ve always been interested in cars, even as a child. I remember as a child growing up in Korea, I saw a Ferrari F50 for the first time – its lines and color were so striking, it’s embedded in my memory. When I was trying to figure out what to study at university I vacillated for a while between automotive design and Engineering. I’m glad I chose the latter, but even more glad that engineering brought me to work in the automotive industry. Though I’m interested in a lot of different areas, be it engineering or business or recruiting, I don’t believe I’ll ever stray from the automotive sector. 

Q: You’ve had quite a career in the automotive sector: What would you say has been the biggest change you’ve seen in the industry? 

The transition from internal combustion engines (ICE) to electric vehicles has most likely been the biggest change in the history of the industry. I’m based in Germany, and this is a country where until the mid-2010s, the country’s ICE technology was world-class due to its decadeslong history in engine research and innovation. German manufacturers have been slower to adopt EV technology, which allowed for other competitors to push their way into the market. Despite those challenges, though, the European market remains one of the largest and most important, so it’s exciting to see governments looking to boost innovation through policy and regulatory support. This will play a crucial role in keeping Europe’s automotive leadership alive.  

Q: What is the biggest challenges facing the industry as we move forward? 

Along with electrification, the transition from traditional architecture to software-driven vehicles is going to be a challenge for legacy manufacturers, compared to the newer EV manufacturers. The shift from a distributed structure to domain and zonal architecture requires a lot of research, time, and human resources. While a lot of OEMs agree that transitioning to SDVs is the right move, it’s difficult to change architectures that they have maintained for decades.  

Q: So what can they do? 

Ultimately, SDVs are the right move, but we have to talk numbers. With SDVs, manufacturers can definitely expect higher profitability. Take Tesla, for example. They achieved a 22% operational profit margin in 2022 through their subscription models such as FSD. Vehicle and user apps and APIs have become a critical factor when it comes to consumer purchasing decisions – a McKinsey report said that 50% of EV buyers said that they consider connectivity features a major priority when it comes to a new vehicle purchase.  

SDVs also contribute to cost savings in development. Simulations and virtual testing not only cost less, they are much more efficient in terms of development and prototyping. Furthermore, after SOP, software updates will be far less costly than a hardware change. Ultimately, SDVs aren’t just a technological trend but will be an essential strategy for manufacturers in the current era of autonomous and electric vehicles.  

Q: How have you seeing the growing importance of security in the automotive industry? 

The demand for security is rapidly increasing, which is why I saw joining Autocrypt as a major opportunity. Automotive security will be in demand, more than ever, as software-defined vehicles become the norm. This isn’t just in Korea or Europe, it’s a global phenomenon. A good example is the Indian market, where the AIS-189 regulation will be implemented as of October 2027. The regulation is based on UNR-155, and similarly requires a cybersecurity management system. This means that Indian OEMs and parts suppliers are urgently demanding security testing solutions, especially in the area of PKI. This is really exciting for me, as we really get to open doors to collaborating with different manufacturers and suppliers all over the world.  

Q: What’s the next step for AUTOCRYPT in Europe (and maybe beyond)?

Europe was and continues to be a key player in the global automotive market. We’ll definitely focus on strengthening our partnerships with European OEMs and Tier-1 suppliers, and continue establishing our reputation as a leading player in vehicle cybersecurity. AUTOCRYPT has decades of experience in securing vehicles, and that puts us in the perfect place to address the unique challenges posed by the transition to SDVs. 

But the automotive market isn’t limited to a single region. As vehicles are manufactured and sold to other regions, there’s going to be more and more hoops that manufacturers and suppliers need to jump through. I’m looking forward to guiding our partners and customers through regulation compliance and providing the necessary approvals and systems in place to make it an efficient and seamless process.  

Q: Any final thoughts? 

There’s a lot of changes in the automotive market right now. Vehicle software, artificial intelligence, and cybersecurity will be at the core of this new era and it’s critical for manufacturers to begin implementing some changes. Companies equipped with solutions to deal with changes (whether technological, regulatory, etc.) will have a significant edge in addressing the growing demand from consumers and regulatory bodies for advanced, intelligent automobiles.  

We’ll continue to see amazing changes in the next few years, and as the European (and global) automotive industry transitions to SDVs, AUTOCRYPT already has developed many of the solutions that are or will be required for the new market. Leveraging these capabilities and expanding our business opportunities is my goal, and I’m optimistic about our future here! 


Many thanks to Joohwa Sarah Lee for the interview. For more insights, follow her on her personal Linkedin page.

Hardware-in-the-Loop Simulation: What it means for ECU testing

With rapid advancements in autonomous driving technologies and various convenience features, vehicles now offer a wide array of functionalities. However, as modern vehicles rely on an increasing number of ECUs, HILS ECU Testing has become essential for validating and optimizing software performance before deployment. By simulating real-world driving conditions, HILS ensures that ECUs function reliably before integration into actual vehicles.

This isn’t simply a braggart outfitting of a vehicle. The numerous features offered by modern-day vehicles simply cannot be managed by a single ECU. Multiple ECUs must work together using complex interconnections to delivery seamless, safe functionality

For example, an automatic climate control system operates with the collaboration of several ECUs; one may be managing temperature sensors, while another runs airconditioning, windows, and heaters, and so on. This is a simple example, but for more complex features, dozens of ECUs may be required to perform a single function in perfect unison.

Difficulties in Testing

When adding a new feature to a vehicle, it is essential to test and validate the software of the ECUs because unlike hardware defects, software defects often remain undetected during the product development stage, making them difficult to address. Unlike hardware issues, these defects can cause unpredictable and potentially life-threatening outcomes. However, directly testing functions on actual vehicles can be equally risky, so traditionally, prototypes resembling the network environment of a vehicle are used to test functions by combining the relevant ECUs.

However, testing in a network environment is costly due to the exponential increase in the complexity of ECUs and software in recent years.

For example, luxury models like the Mercedes-Benz S-Class, BMW 7 Series, and Hyundai Genesis can be equipped with hundreds of ECUs. Testing a single vehicle function requires assembling a prototype model, a process that is both costly and time-consuming. Instead, automakers increasingly rely on HILS ECU Testing to simulate real-world conditions before deploying physical prototypes. Moreover, luxury sedans often contain over 20 million lines of software code—approximately three times the amount of code found in a large aircraft.

Therefore, assembling and testing hundreds of ECUs for every new feature adds considerable cost and time for manufacturers and suppliers. Testing a single function could mean creating a unique testing environment for all related ECUs, which would vary by vehicle model.

HILS Testing

This is where HILS (Hardware-in-the-Loop Simulation) comes in. HILS is a testing technique used to verify the functionality of developed products by simulating their actual operational environment.

In vehicle testing, HILS serves as a simulation system for various ECU functionalities. HILS makes it possible to test everything from individual ECUs to integrated network systems for all driving scenarios before ever testing on an actual vehicle.

Instead of combining physical ECUs into a prototype, HILS testing uses simulations. The testing environment consists of three main components:

  1. Test Input Generator: Generates and provides input values for the test. Tools like fuzzers are included in this component
  2. Target ECU: The specific ECU to be tested
  3. HILS: A virtual controller that mathematically models the vehicle environment and simulates the actual movements of controllers. When needed, real actuators can be connected for experimentation.

In the example provided by below by AUTOCRYPT, you can see how the test process works. The Target ECU is connected to the HILS system, which receives test input values generated by the Fuzzer. The output from the HILS system verifies the functionality of the ECU, eliminating the need to physically assemble all related ECUs for testing. Only the ECU to be tested needs to be connected to the HILS environment.

HILS ECU Testing for Automotive Software - autocrypt

HILS Advantages

While it does not completely eliminate the need for prototype vehicles, simulated testing is generally more cost-effective than creating physical products. It reduces the number of prototype vehicles, and shortens the time and manpower spent on test benches.

HILS also provides a significant advantage in conducting dangerous tests, such as wire breaks, sensor failures, or crash simulations. It is equally effective during the development of control algorithms when the actual components for testing may not yet exist. Furthermore, the ability to conduct tests anytime, anywhere, adds a practical advantage.

HILS ECU testing is not simply at its conceptual stage. The automotive industry has already recognized the importance of HILS testing – in fact, ISO 26262, the international standard for functional safety in vehicles, outlines software validation stages throughout a vehicle’s lifecycle, and recommends HILS testing during unit and integration testing.

For instance, Hyundai Motor Group’s vehicle software development process emphasizes HILS testing in the fifth stage of their V-cycle process, highlighting the growing importance of integrated HILS testing in new vehicle development as automotive control software becomes increasingly complex.

According to Wards Auto, the word “software” was first mentioned in a recall in 1994, and since then attribution to software for recall incidents has risen to 15% by 2023. While, software defects are inevitable as automotive software becomes heavier and more complex, this means conducting comprehensive software testing in advance is that much more essential.

HILS plays a critical role in this process by enabling flexible, unrestricted testing, which also aids in rapid response to software defects. Unlike physical tests, which are hindered by the time and cost of prototype production, HILS allows for swift simulation-based defect analysis and response.

To learn more about how AUTOCRYPT utilizes HILS in its fuzz testing solution, click here.

To learn more about AUTOCRYPT’s use of HILS in its fuzz testing solution and other automotive testing services, contact global@autocrypt.io.

Infographic: 2024 Year in Review

This year has been a remarkable journey for AUTOCRYPT, filled with innovation, meaningful collaborations, and impactful achievements. We are incredibly grateful to our investors, partners, clients, readers, and visitors for your unwavering support in 2024!

As we prepare to step into 2025, we’re excited about the opportunities and challenges that lie ahead. Here’s to another year of growth, innovation, and success—together!

Merry Christmas and Happy New Year!

Below is a recap of AUTOCRYPT’s key milestones and accomplishments in 2024.

Infographic 2024 Year in Review Autocrypt

Download PDF

(Accessibility version below)

New solutions

2024 has been the year of innovation and growth for AUTOCRYPT. We introduced 4 new groundbreaking solutions designed to address critical challenges in the automotive cybersecurity sector.

AutoCryptⓇ CSTP – Automotive cybersecurity testing platform for regulatory compliance

AutoCryptⓇ CLS – C-ITS local station for V2I communication

AutoCryptⓇ ASL – Adaptive security library for AUTOSAR platforms

AutoCryptⓇ RODAS – Remote driving assistance system for autonomous vehicles

Awards and certifications

This year, our efforts were recognized with several prestigious certifications and awards:

Designated as a Vehicle Type Approval Technical Service Provider for UN R155/156

Received Top Innovator Award at the 2024 CLEPA Innovation Awards

Partnerships

Collaboration fuels innovation, and this year, we forged impactful partnerships that strengthen our solutions and expand our reach:

VinCSS

Cohda Wireless

MicroNova

Bayanat

Emobi

Events

We participated in several impactful events, connecting with industry leaders and showcasing our innovations:

  1. CES 2024
  2. ITF Summit 2024
  3. VDI ELIV
  4. AutoTech Detroit 2024
  5. Automotive Testing Expo Europe
  6. International VDI Conference
  7. ITS World Congress Dubai
  8. Car Connectivity Consortium

and more…

Resources

This year, we published a range of resources to guide and inform our industry peers:

The Rise of Chinese Software-Defined Vehicles

UNECE Regulation 155: Key Vehicle Components to Focus on for Regulatory Compliance

Public Key Infrastructure: Use Cases in the Automotive Industry

Robotaxis in the Spotlight: Market Trends, Technology, and Disengagement Analysis