Building Automotive Security on Internet Standards: In-Car Service Authentication with DNSSEC, DANE, and DANCE

Introduction to the show: ident: Security Radio. Generated commentary on the latest security and cryptography papers.

Nadia: We're looking at the paper: "Building Automotive Security on Internet Standards".

Elias: Here's the gist of the paper. This paper proposes authenticating and authorizing in-vehicle services by integrating DNSSEC, DANE, and DANCE with automotive middleware to decouple cryptographic authentication from service deployment for scalable security management.

Nadia: How it works The core of the approach decouples the cryptographic authentication of the service from that of the service deployment with the help of DNSSEC, thereby largely simplifies key management<ref:2506.13261#pg2>.

Elias: The proposal authenticates in-vehicle services by certificates that are solely generated by the service suppliers but published on deployment via DNSSEC TLSA records solely signed by the OEM<ref:2506.13261#pg5>.

Nadia: This leverages well-established Internet standards to ensure interoperability with various current and future protocols, allowing for scalable management of credentials for millions of connected vehicles at well-established security levels<ref:2506.13261#pg5>.

Title and authors: Nadia: We're talking about how this paper, Building Automotive Security on Internet Standards: In-Car Service Authentication with DNSSEC, DANE, and DANCE, proposes a way to use established Internet standards for in-car security. It’s about using DNSSEC to tie service authentication to the deployment process.

Elias: They are essentially proposing that the software supplier signs their product and provides a certificate, but then the OEM signs the deployment of that certificate using its own credentials in a DNSSEC TLSA record.

Priya: So what does that mean for someone just listening? It sounds complicated. Is it like they’re replacing all the old security methods with something simpler?

Nadia: It’s not about replacing everything, but rather building a layer of trust on top of existing Internet standards. They are leveraging DNSSEC, which is already a well-known system for data integrity and authenticity online.

Elias: They use DANE and DANCE to build on that DNSSEC foundation to store and sign these keys in specific records called TLSA records. This establishes a chain of trust from the root zone down to the specific service endpoint within the DNS hierarchy.

The paper's summary: Nadia: So, what does this whole process actually achieve according to their summary? It boils down to deriving automotive security requirements directly from that DNSSEC ecosystem.

Elias: They show how they derive those requirements by looking at the DNS structure and how DANE and DANCE work together to bind a certificate to a named service endpoint.

Priya: And what does this binding actually do for the vehicle itself? Does it make things more reliable when you're on the road?

Nadia: It gives the vehicle an offline way to verify security credentials because they can cache a delegated DNSSEC zone inside the car. This means you can check those credentials without needing an active Internet connection.

Elias: That addresses mid-term scenarios, allowing for verification even when connectivity is down. They are also integrating name-based service discovery and invocation using new SVCB records in DNS for publish-subscribe systems.

The paper's improvements: Nadia: The paper points out a few key improvements they made to the concept of building this security layer on top of Internet standards. It’s about making it practical.

Elias: One major improvement is decoupling the cryptographic authentication from the service deployment, which they say largely simplifies key management across a multi-supplier ecosystem.

Priya: That decoupling sounds important for managing different suppliers, right? What else do they suggest that makes this scheme more robust against real threats?

Nadia: They show that by using name-based authorization, subscribers can verify the presence of a DNSSEC-secured TLSA record matching an exact name to implicitly authorize the publisher. That means fine-grained policies without needing extra infrastructure.

Elias: And they address security analysis using the STRIDE threat model, looking at Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, and Elevation of privilege against specific automotive attack scenarios.

Conclusion: Nadia: So to wrap up this discussion on Building Automotive Security on Internet Standards: In-Car Service Authentication with DNSSEC, DANE, and DANCE. The main thing is that they successfully use established Internet standards for a robust credential lifecycle management system in the automotive world.

Elias: They managed to reduce dependence on locally stored credentials for all interacting parties while still allowing offline operability through that local DNSSEC resolver setup. It’s feasible for authenticating and authorizing services in a realistic in-vehicle setting.

Priya: From a measurement view, the analysis showed that even with service setup times ranging from one point three seconds to three point three seconds across different scenarios, the individual service setup time stayed well below the two hundred milliseconds requirement. That’s measurable performance data they reported.

Nadia: It really suggests that this DNSSEC-based authentication and authorization scheme is a workable approach for securing automotive services in an actual in-vehicle environment. It opens up future research into performance using dedicated hardware and post-quantum cryptography, and also suggests extending this to other local networks like industrial control systems or smart home environments.

Elias: They confirm that this DNSSEC-based authentication and authorization scheme is feasible for authenticating and authorizing automotive services in a realistic invehicle setting. It’s a solid foundation built on existing internet protocols.