Cybersecurity Considerations for In-Vehicle Infotainment Systems

Today, new car buyers are focusing more on the “digital cockpit ecosystem experience” than on traditional features such as horsepower and fuel economy. The automotive industry has made it a priority to deliver this experience, including fully connected in-vehicle infotainment (IVI) systems that include touchscreen displays, voice commands, and integrated information and entertainment features.

What is an in-car infotainment system?

More and more end consumers want to be fully connected to their "digital ecosystem" experience. The "smart cockpit" is the core of the in-vehicle infotainment system and is becoming a key differentiator for OEMs and their car brands.

In-vehicle infotainment (IVI) is the combination of vehicle systems used to provide vehicle occupants with an audio/visual interface and control elements—touchscreen displays, button panels, voice commands, etc.

Here is a snapshot of the components or modules that make up the “Smart Cockpit”:

1. User Interface: What the driver and passengers see and interact with on screens, either by touch or with knobs and dials.

2. Head Unit: This includes the display, housing, circuit boards, CD/DVD player, radio, and multiple processors (collectively referred to as the vehicle's head unit). It is also the interface for all physical inputs to the vehicle, such as the sound system and/or external cameras.

3. Operating System (OS): As the heart of the infotainment system, the OS controls access to the processor, memory, storage, and display in the head unit.

4. Application Framework Module: Manages everything from the Spotify app to navigation and interaction with the system, such as text-to-speech and voice commands. It controls all app functionality and which apps can appear in the console.

5. Mobile Integration: Enables the vehicle to connect to a wide range of smartphones and devices. Support for Wi-Fi, Bluetooth and plug-and-play programs such as Google Play's Mirror Link, Apple CarPlay and Android Auto allows modified versions of your phone's media and apps to be imported into the screen.

6. Automotive platform: A software bridge between the application framework and the operating system that supports multimedia, video, navigation, audio, radio, acoustics, software updates, cloud services, etc.
   According to a recent analysis by industry research firm Frost & Sullivan, the "connected car" will constitute nearly 86% of the global automotive market by 2025. In the same year, the IVI market is expected to reach $42.7 billion.

However, IVI systems themselves, as well as third-party applications, also create many vulnerability threat points for cybercriminals. OEMs and Tier 1 suppliers of IVI systems to the automotive industry must work to ensure that the embedded code in these systems meets safety and security-critical standards. Doing so can help avoid recall costs and impact on business reputation.

Cyberattacks pose serious risk to in-vehicle infotainment systems

In-vehicle infotainment has come a long way in just a few years, and is expected to continue to rapidly evolve as emerging technologies such as AI, ML, and AR enter the automotive space as standard integrations into these embedded “digital cockpit” systems. While IVI systems are currently used to provide information and entertainment, they will soon play a larger role as the primary communication component for all functions within the vehicle. Users can see more information through AR and 3D navigation and alerts, interactive traffic and hazard warnings, and communication methods with other vehicles on the road.

As IVI systems add more functionality and connectivity every year, developers managing over-the-air software updates must consider the myriad attack surfaces and potential vulnerabilities of in-vehicle networks.
Because IVI systems connect to the internet and run operating systems using Android, RTOS, Linux, QNX, and Windows Embedded Automotive, as well as USB connections, Bluetooth, and Wi-Fi, there are many ways for hackers to find these entry points and exploit vulnerabilities in the code, which could impact user privacy and security.

Up to 90% of software security issues are caused by coding errors. That’s why it’s important to ensure that failure scenarios don’t occur. However, code quality is still not as good as it should be for many IVI systems, leading to buggy and cumbersome IVIs in new cars. Developers looking to improve code quality and in-vehicle infotainment cybersecurity should use coding standards and static analysis tools as part of cybersecurity and quality-first best practices.

Importance of Coding Standards for In-Vehicle Infotainment Systems

It can be said that a connected vehicle is a computer on four wheels that is connected to the Internet through its IVI system. Since the IVI system is part of the in-vehicle network, it may create many vulnerable threat points for hackers, who may be able to control the driver's smartphone and access personal data, manipulate vehicle safety-critical system functions, or make system update programs. Therefore, IVI system development practices must adhere to coding standards and guidelines.

Two recent initiatives that are expected to benefit IVI systems are the ISO/SAE 21434 standard and the United Nations Economic Commission for Europe (UNECE) WP.29 regulation. Together, these standards will prepare the automotive industry to ensure the safety of the next generation of connected cars.

The ISO/SAE 21434 standard builds on its predecessor, ISO 26262, which did not cover software development or subsystems. ISO/SAE 21434 focuses on the cybersecurity risks inherent in automotive electronics design and development. The automotive software security standard provides a structured process to ensure that cybersecurity considerations are incorporated throughout the lifecycle of automotive products.

Unlike ISO/SAE 21434, WP.29 regulations require OEMs to be responsible for managing cybersecurity risks throughout the supply chain.

How IVI Cybersecurity Breaches Affect OEMs

OEMs and their Tier 1 suppliers need to take steps to avoid the negative impact of vulnerabilities in their IVI embedded software, as attacks could threaten the privacy and safety of drivers and their passengers. Cybersecurity incidents can be costly and time-consuming, and may result in vehicle recalls, ultimately impacting profits, reputational losses, and organizational productivity.

Software glitches in IVI systems frequently lead to recalls. A recent MSN.com survey of the least reliable family cars put the latest generation of vehicles at the top of the list, with 57 percent of vehicles experiencing malfunctions, including 33 percent affected by IVI issues.

Software glitches in infotainment systems can lead to recalls due to safety and security issues. For example, a glitch could allow a driver to browse the internet and watch TV while driving. A software glitch could also cause a car's screen to go dark in cold weather.

Even if the malfunction is not obvious, malicious actors could exploit this type of vulnerability in software to shut down critical functions that affect safety and security.

Ensuring that the codes in your IVI system meet the necessary standards and compliance requirements can help avoid recall costs and impacts on your business reputation and profitability.

Why SAST is critical for in-vehicle infotainment software code

Static Application Security Testing (SAST) software testing methodology examines and analyzes the coding and design conditions of application source code, bytecode, and binary files to discover security vulnerabilities in IVI system software. The working mechanism behind SAST is a static analysis tool that checks for design and coding flaws.

Ideal for enterprise DevOps and DevSecOps, Klocwork is the industry-leading static analysis and SAST tool for source code designed in C, C++, C#, Java, JavaScript, Python, and Kotlin. In addition, 9 of the 10 top automotive component manufacturers rely on Perforce static analysis tools to help ensure the security and compliance of their automotive software.