RunSafe’s 2025 Connected Car Cyber Safety & Security Index

Download the Report

Download RunSafe’s 2025 Connected Car Cyber Safety & Security Index

This year’s automotive cybersecurity report reveals that consumers view cybersecurity as a must-have and a purchase driver that can make or break brand loyalty.

Connected cars are computers on wheels, containing over 100 million lines of code and requiring strong cybersecurity, just like any other device you own. 

Increasingly, consumers are aware of the dangers of cyber vulnerabilities in their vehicle’s software and the life-and-death implications of a successful hack. However, the industry has yet to respond with the transparency and security measures today’s drivers demand.

RunSafe Security’s 2025 Connected Car Cyber Safety & Security Index reveals consumers’ biggest areas of concern, from software supply chain anxiety to physical safety, and the standards they expect auto manufacturers and software suppliers to live up to.

Key Findings At-a-Glance:

  • 65% of consumers believe remote hacking is possible
  • 79% said protecting physical safety is more important than protecting personal data
  • 87% said a car brand that offers strong cybersecurity and privacy would influence their purchase decision (35% would pay more)
  • 28% are not confident their car is protected from hackers
  • 34% believe the vehicle manufacturer should be held responsible if a cyberattack on a car causes an accident

Verification IconWhat’s Inside the Report:

  • Insight into consumers’ awareness and sentiment toward connected vehicle cyber threats
  • The paradox of Over-the-Air Updates for long-term security
  • Why third-party technology, especially AI, is causing software supply chain anxiety
  • Who consumers hold responsible for automotive attacks
  • How security is driving brand perception and a justification for premium pricing
  • Industry implications and takeaways for automotive manufacturers and suppliers

Check Out Our Latest Blog Posts

Navigating Third-Party Software Risk: Best Practices for 2026

Navigating Third-Party Software Risk: Best Practices for 2026

Most of the code running in your product probably isn't code you wrote. Open source libraries, vendor SDKs, and firmware components all become part of your attack surface the moment they're compiled into your build. Third-party software risk is the potential for...

read more
3 SBOM Generation Methods: Binary vs Build-Time vs Source Code

3 SBOM Generation Methods: Binary vs Build-Time vs Source Code

Your SBOM is only as useful as it is accurate, and the method you use for Software Bill of Materials (SBOM) generation determines the level of accuracy you will receive. SBOM generation method determines whether an SBOM captures what developers declared, what scanners...

read more