OBD-II Secure Diagnostic Port Access to in-Vehicle Networks
J3273
This Task Force under the Data Link Connector Vehicle Security Committee will review and memorialize starting with an Information Report the status at the time of publication of secure diagnostic access to in-vehicle networks.
The TF will consider expanding the diagnostic scope beyond the Data Link Connector (DLC) / OBD-II port to encompass all diagnostic access whether physically wired, or wireless. With the introductions of battery electric vehicles (BEVs), the TF should review and consider various off-board communication diagnostics (e.g., connections to battery pack). If diagnostic data or information is eventually moved to other wired or wireless ports, or “links” in the future, then a more generalized process may be considered. The TF may consider Terms & Definitions to be memorialized and will concentrate on what is especially meant by “wireless” and/or “wireless diagnostic” etc.
One potential result could be a summary of possible recommendations and/or guidance for diagnostic communications once “wireless’ becomes more prevalent. However, any possible recommendations, etc. created is expected to be technology neutral.
Also, this Information Report will encompass passenger cars and light-, medium-, and heavy-duty trucks, unless otherwise noted.
Rationale: This Task Force under the Data Link Connector Vehicle Security Committee will review and memorialize in an Information Report the status of secure diagnostic access to in-vehicle networks.
Currently, On-Board Diagnostic regulations (OBD-II) require passenger cars and light-, medium-, and heavy-duty trucks to provide a Diagnostic Connector, which conforms to existing SAE J-docs (e.g., J1962, J1979, etc.) to support communication of diagnostic information to off-board devices. This includes but is not limited to 3rd party access to vehicle maintenance. Legislated diagnostic information is required to be communicated in a timely fashion to the off-board devices. Many vehicle manufacturers also provide access to enhanced diagnostic information and vehicle systems/subsystems via this connector.
Work will build on the existing J3138 and other SAE J-docs (e.g., J3101, J3005, etc.) and will concentrate on the ‘security’ for ‘diagnostic access’ and not necessarily on access to other vehicle data just ‘diagnostics’. Generalized vehicle ‘data access’ would be out-of-scope.
