Skip to content

How do we address the security issues introduced by the use of aftermarket ECUs? #200

@jhdalek55

Description

@jhdalek55

First introduced at our industry workshop in May, this issue opens discussion on the complicated topic of how the use of aftermarket equipment and services impacts security systems. Aftermarket companies refurbish and reuse equipment following end-of-life support from OEMs. This means introducing ECUs to a vehicle that the OEM has no control over. In addition, because aftermarket suppliers may not have access to the original design, they often reverse engineer the parts to figure out how it works. Such an approach perhaps keeps these suppliers from being able to glean all relevant design information about the ECU.

This is admittedly a broad topic. When introduced at the workshop, several specific points were raised that could each be broken into separate issues:

  • How do we deal with aftermarket ECUs that do not have their own Primary? Can they leverage an OEMs Director repository?
  • If an aftermarket ECU does have its own Primary, is each capable of controlling a mutually exclusive set of
  • Could ownership of Director be delegated to a third party or owner?

I'm opening up this issue so we can begin a dialogue on these and other issues.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions