RunSafe Security CEO to address U.S. connected vehicle rule at Detroit summit

RunSafe Security Founder and CEO Joseph M. Saunders will speak at the Automotive Cybersecurity Summit 2026 in Detroit on July 29-30 about the Bureau of Industry and Security's Connected Vehicle Rule. The session comes as automakers and suppliers face new compliance demands tied to software origin tracking, SBOMs and supply-chain security.

Why it matters: - Automakers and suppliers are facing tighter federal compliance expectations for software-defined vehicles. - The BIS Connected Vehicle Rule raises the stakes for software origin tracking, supply-chain visibility and ongoing compliance programs. - Consumer concern is already high. A 2025 Connected Car Cyber Safety & Security Index found 65% of drivers believe remote vehicle hacking is possible, and 77% see third-party components as a severe cyber risk.

What happened: - RunSafe Security said Founder and CEO Joseph M. Saunders will lead a solo keynote at the Automotive Cybersecurity Summit 2026. - The session is titled "Meeting U.S. Connected Vehicle Rule Origin Requirements." - The summit runs July 29-30, 2026, at the DoubleTree Suites by Hilton Hotel Detroit Downtown - Fort Shelby in Detroit. - Saunders will address OEMs, Tier-1 suppliers, security engineers and transportation policy experts.

The details: - Saunders will discuss the Bureau of Industry and Security Connected Vehicle Rule and software origin restrictions. - The presentation will focus on how automakers can move compliance from a point-in-time check to a continuous lifecycle process. - RunSafe says the talk will cover technical methods to map code provenance, generate automated compliance-ready Software Bills of Materials, and remove foreign-adversary-linked components from multi-tier supply chains. - RunSafe Security describes its platform as using patented memory relocation techniques to harden embedded systems against runtime exploits without code rewrites. - RunSafe also says build-time SBOMs can capture components missed by binary analysis and standard scanning tools. - The company says build-time SBOMs record source files, libraries and toolchains during the build process, which is important when static linking and optimization reduce identifying signals in automotive software.

Between the lines: - The message is aimed at a market that must balance speed, software complexity and regulatory compliance. - The emphasis on build-time SBOMs suggests that post-build scanning alone may not be enough for the automotive compliance model RunSafe is targeting. - The focus on foreign-adversary-linked components shows how the connected vehicle debate now intersects with national security and supply-chain risk.

What's next: - Saunders will be available for one-on-one interviews, technical discussions and on-camera commentary during the summit. - Press credentials can be coordinated through Kari Ritacco at RedIron PR, +1 703-928-9996. - The Detroit event will likely surface how OEMs and suppliers plan to adapt to the new connected vehicle requirements before model year production lines move further into compliance cycles.

The bottom line: - RunSafe is using the Detroit summit to position software provenance, SBOMs and embedded security as core tools for connected vehicle compliance.