RunSafe CEO to address U.S. connected vehicle compliance 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 tighter federal software-origin requirements and growing pressure to prove supply-chain security across software-defined vehicles.

Why it matters: - Automakers and Tier-1 suppliers are under growing pressure to prove where vehicle software comes from and whether foreign-adversary-linked components are present. - The BIS Connected Vehicle Rule raises the stakes for software-defined vehicles by turning compliance into an ongoing lifecycle process, not a one-time review. - Consumer concern is high: 65% of drivers in the 2025 Connected Car Cyber Safety & Security Index said remote hacking of a vehicle is possible, and 77% called third-party components a severe cyber risk.

What happened: - RunSafe Security said Founder and CEO Joseph M. Saunders will deliver a solo keynote at the Automotive Cybersecurity Summit 2026. - The session is scheduled for July 29-30, 2026, at the DoubleTree Suites by Hilton Hotel Detroit Downtown - Fort Shelby in Detroit. - Saunders will discuss the Bureau of Industry and Security’s Connected Vehicle Rule and how OEMs and Tier-1 suppliers can respond.

The details: - The keynote is titled “Meeting U.S. Connected Vehicle Rule Origin Requirements.” - Saunders plans to outline technical ways to map code provenance faster and produce automated, compliance-ready software bills of materials, or SBOMs. - The session will also cover how manufacturers can remove foreign-adversary-linked components from complex, multi-tier supply chains. - RunSafe Security says its memory relocation technology protects embedded systems against runtime exploits without requiring code rewrites. - The company also says build-time SBOMs can capture components that binary analysis and scanning can miss. - RunSafe says many software composition analysis tools are strongest at detecting open-source packages but have limited visibility into proprietary or commercial components. - The company says build-time SBOMs record which source files, libraries and toolchains contributed to the final output while that information is still available. - RunSafe says that timing matters in automotive software because static linking and aggressive optimization can remove identifying signals. - Press credentials and media coordination are available through Kari Ritacco at RedIron PR, +1 703-928-9996.

Between the lines: - The event positions RunSafe in the middle of a fast-moving policy shift where software provenance is becoming a regulatory issue, not just a security best practice. - Detroit is a strategic stage for the message because the city sits at the center of the U.S. auto industry and the transition to software-defined vehicles. - The emphasis on SBOMs and code provenance suggests compliance teams will need better visibility into supplier software stacks, not just perimeter defenses.

What's next: - Saunders is available for one-on-one interviews, technical briefings and on-camera commentary during the summit. - RunSafe expects the discussion to focus on local and global economic impacts of the U.S. Connected Vehicle regulations. - The summit will give OEMs, suppliers and policy experts a chance to compare compliance approaches as federal requirements tighten.