If you've ever run an SBOM tool on a C/C++ codebase and gotten results that felt wrong, you're not imagining it. Teams evaluating tools like Black Duck, Syft, Trivy, and FOSSA on embedded projects routinely find that outputs are incomplete, inconsistent, or so noisy...
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
What’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
Questions to Ask When Evaluating SBOM Tools for Embedded C/C++
If you're running a proof of concept on Software Bill of Materials (SBOM) tooling for C/C++, you've probably already discovered that vendor demos don't tell you much. Tools that look capable in a sales presentation frequently fall apart when pointed at a real embedded...
The FDA Is Asking for VEX with SBOMs: Here’s Why That Matters
Key Takeaways: The FDA is asking medical device manufacturers to submit VEX (Vulnerability Exploitability eXchange) files alongside SBOMs in some premarket cybersecurity submissions. VEX artifacts document whether known vulnerabilities in SBOM-listed components are...



