RunSafe CEO to Brief automakers on U.S. connected vehicle compliance in Detroit

RunSafe Security 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 is aimed at OEMs and suppliers facing new software-origin and SBOM requirements as U.S. vehicle cybersecurity rules tighten.

Why it matters: - Automakers and suppliers are facing new federal compliance pressure as software-defined vehicles add more code, more third-party components and more supply-chain risk. - Consumer concern is high: a 2025 Connected Car Cyber Safety & Security Index found 65% of drivers believe remote vehicle hacking is possible and 77% view third-party components as a severe cyber risk. - The BIS Connected Vehicle Rule could force the industry to treat compliance as a continuous process instead of a one-time audit.

What happened: - RunSafe Security said Founder and CEO Joseph M. Saunders will lead a solo keynote at the Automotive Cybersecurity Summit 2026 in Detroit. - 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, 525 W Lafayette Blvd, Detroit, Michigan 48226. - The audience includes automotive OEMs, Tier-1 suppliers, security engineers and transportation policy experts.

The details: - Saunders plans to address the Bureau of Industry and Security Connected Vehicle Rule and the software-origin restrictions tied to it. - The presentation will cover technical approaches to map code provenance quickly, generate automated compliance-ready Software Bills of Materials and remove foreign-adversary-linked components from multi-tier supply chains. - RunSafe says its memory relocation technology can help protect embedded systems against runtime exploits without requiring code rewrites. - RunSafe also says build-time SBOMs can capture components that binary analysis and scanning miss. - The company says many software composition analysis tools are built for open-source detection and offer limited visibility into proprietary or commercial components. - RunSafe says build-time SBOMs record source files, libraries and toolchains during the build itself, which can matter for BIS compliance when static linking and optimization obscure identifying signals. - Press credentials and interview requests can be coordinated through Kari Ritacco at RedIron PR, +1 703-928-9996.

Between the lines: - The event positions RunSafe’s technology around a new regulatory pain point, not just general cybersecurity. - The compliance message also reflects a broader shift in automotive security from perimeter defense to supply-chain provenance and software traceability. - The focus on build-time SBOMs suggests the biggest challenge may be proving what is inside vehicle software, not just finding known vulnerabilities.

What's next: - Saunders is available for one-on-one interviews, technical briefings and on-camera commentary during the summit. - The discussion is likely to sharpen attention on how OEMs and suppliers document software origins ahead of stricter connected vehicle enforcement. - The Detroit session could become a reference point for how the auto industry interprets BIS compliance in practice.