MACS Service Reports - 2016 - NOV5
ETI
Figure 4: The underdash J1962 VCI (left) is little security and is easily hacked. Both the SVI model (center) was developed before the ExVe model (right).
Both have stringent security protocols all users must successfully pass before being granted access to the vehicle. Note that the SVI concept specifies that the
aftermarket and automakers jointly control and monitor access to vehicles. Note that unlike the SVI, ExVe specifies only automakers control and monitor
access to vehicles.
or eight-wire based, which allows faster and higher data volumes to be transferred. Other automotive markets have moved
beyond two-wire. We're lagging.
"The auto industry in the United States needs to get in step
with what's happening here in other industries and in the rest
of the world," continued Potter. "Too often, when meeting with
automakers, suppliers and others about wanting access to vehicles, the one thing that is always thrown back in our faces is,
'That will be unsecure.' That's closed-minded. It's critical to go
beyond our business cultures and past practices to wherever the
information and know-how we need is, whether it's for Ethernet, security, encryption, artificial intelligence or other needs we
have."
- Globally, the industry is headed toward managed ITS; this
includes service repair shops and suppliers. Security and encryption design is being done right in the international ITS
community today. This past summer, the 2016 CONVERGE
meeting in Berlin showcased the new ISO 21217:2014 standard, which describes open standards communications architecture and the use of reference security protocols to safeguard ITS nodes, such as vehicles, control centers, shops and
traffic signals, based on the principles of bounded, secured
and managed domains. This new ISO standard is far superior to what we have domestically today. It's know-how we
need.
"ETI member firms build the automotive tools, equipment,
devices and third-party service repair information products
that bridge automakers and service repair facilities," Potter said.
"Our customers are in both groups, and we've enjoyed an open,
honest collaboration with them. We realize automakers have
been behind the curve regarding vehicle security and encryption, for which solutions are complicated and expensive. On the
other hand, the global IT and ITS communities are well ahead
of the auto industry in the areas of security and encryption. We
need to use our relationship with them to grow our capability."
"That's why we've been telling automakers for a few years
now: 'Get rid of your individual proprietary systems. They add
unnecessary complexity to servicing vehicles, and frankly aren't
as good as those developed and in use today by the ITS and IT
industries.' We've urged automakers to adopt the new robust
systems developed by these two communities, which use stateof-the-art security and encryption mechanisms and employ
standardized but more sophisticated and secure vehicle interfaces. They work, and that serves everybody's interests. After all,
we're all in the security business now."
Potter cited two examples:
* The International Consumer Electronics Show (CES) -
The Las Vegas CES is a multi-industry show where knowhow has traction. Just a few years ago, no one in the automotive repair industry attended it. Yet it is where telematics,
connectivity and other emerging technologies this industry
now needs were already being discussed and successfully
implemented years ago. Some, but not enough of stakeholders attend now to grow knowledge, expertise and relationships with IT experts from Apple, Google, Amazon, NVIDIA
and other tech giants that we can leverage. They have shown
the value of using open and proven industry standards and
methods, rather than traditional proprietary means, to build
more secure, encrypted and standardized vehicle access for
all legitimate stakeholders. Simply put, doing things a dozen
different ways isn't user-friendly, and often, it's confusing
and less secure.
* Intelligent Transportation Systems (ITS) Plenary Meetings
November 2016
5
MACS Service Reports
Table of Contents for the Digital Edition of MACS Service Reports - 2016
MACS Service Reports - 2016 - JAN1
MACS Service Reports - 2016 - JAN2
MACS Service Reports - 2016 - JAN3
MACS Service Reports - 2016 - JAN4
MACS Service Reports - 2016 - JAN5
MACS Service Reports - 2016 - JAN6
MACS Service Reports - 2016 - JAN7
MACS Service Reports - 2016 - JAN8
MACS Service Reports - 2016 - FEB1
MACS Service Reports - 2016 - FEB2
MACS Service Reports - 2016 - FEB3
MACS Service Reports - 2016 - FEB4
MACS Service Reports - 2016 - FEB5
MACS Service Reports - 2016 - FEB6
MACS Service Reports - 2016 - FEB7
MACS Service Reports - 2016 - FEB8
MACS Service Reports - 2016 - MAR1
MACS Service Reports - 2016 - MAR2
MACS Service Reports - 2016 - MAR3
MACS Service Reports - 2016 - MAR4
MACS Service Reports - 2016 - MAR5
MACS Service Reports - 2016 - MAR6
MACS Service Reports - 2016 - MAR7
MACS Service Reports - 2016 - MAR8
MACS Service Reports - 2016 - APR1
MACS Service Reports - 2016 - APR2
MACS Service Reports - 2016 - APR3
MACS Service Reports - 2016 - APR4
MACS Service Reports - 2016 - APR5
MACS Service Reports - 2016 - APR6
MACS Service Reports - 2016 - APR7
MACS Service Reports - 2016 - APR8
MACS Service Reports - 2016 - MAY1
MACS Service Reports - 2016 - MAY2
MACS Service Reports - 2016 - MAY3
MACS Service Reports - 2016 - MAY4
MACS Service Reports - 2016 - MAY5
MACS Service Reports - 2016 - MAY6
MACS Service Reports - 2016 - MAY7
MACS Service Reports - 2016 - MAY8
MACS Service Reports - 2016 - JUN1
MACS Service Reports - 2016 - JUN2
MACS Service Reports - 2016 - JUN3
MACS Service Reports - 2016 - JUN4
MACS Service Reports - 2016 - JUN5
MACS Service Reports - 2016 - JUN6
MACS Service Reports - 2016 - JUN7
MACS Service Reports - 2016 - JUN8
MACS Service Reports - 2016 - JUL1
MACS Service Reports - 2016 - JUL2
MACS Service Reports - 2016 - JUL3
MACS Service Reports - 2016 - JUL4
MACS Service Reports - 2016 - JUL5
MACS Service Reports - 2016 - JUL6
MACS Service Reports - 2016 - JUL7
MACS Service Reports - 2016 - JUL8
MACS Service Reports - 2016 - AUG1
MACS Service Reports - 2016 - AUG2
MACS Service Reports - 2016 - AUG3
MACS Service Reports - 2016 - AUG4
MACS Service Reports - 2016 - AUG5
MACS Service Reports - 2016 - AUG6
MACS Service Reports - 2016 - AUG7
MACS Service Reports - 2016 - AUG8
MACS Service Reports - 2016 - SEP1
MACS Service Reports - 2016 - SEP2
MACS Service Reports - 2016 - SEP3
MACS Service Reports - 2016 - SEP4
MACS Service Reports - 2016 - SEP5
MACS Service Reports - 2016 - SEP6
MACS Service Reports - 2016 - SEP7
MACS Service Reports - 2016 - SEP8
MACS Service Reports - 2016 - OCT1
MACS Service Reports - 2016 - OCT2
MACS Service Reports - 2016 - OCT3
MACS Service Reports - 2016 - OCT4
MACS Service Reports - 2016 - OCT5
MACS Service Reports - 2016 - OCT6
MACS Service Reports - 2016 - OCT7
MACS Service Reports - 2016 - OCT8
MACS Service Reports - 2016 - NOV1
MACS Service Reports - 2016 - NOV2
MACS Service Reports - 2016 - NOV3
MACS Service Reports - 2016 - NOV4
MACS Service Reports - 2016 - NOV5
MACS Service Reports - 2016 - NOV6
MACS Service Reports - 2016 - NOV7
MACS Service Reports - 2016 - NOV8
MACS Service Reports - 2016 - DEC1
MACS Service Reports - 2016 - DEC2
MACS Service Reports - 2016 - DEC3
MACS Service Reports - 2016 - DEC4
MACS Service Reports - 2016 - DEC5
MACS Service Reports - 2016 - DEC6
MACS Service Reports - 2016 - DEC7
MACS Service Reports - 2016 - DEC8
https://www.nxtbook.com/nxtbooks/macs/servicereports_2022
https://www.nxtbook.com/nxtbooks/macs/servicereports_2021
https://www.nxtbook.com/nxtbooks/macs/servicereports_2020
https://www.nxtbook.com/nxtbooks/macs/servicereports_2019
https://www.nxtbook.com/nxtbooks/macs/servicereports_2018
https://www.nxtbook.com/nxtbooks/macs/servicereports_2017
https://www.nxtbook.com/nxtbooks/macs/servicereports_2016
https://www.nxtbook.com/nxtbooks/macs/servicereports_2015
https://www.nxtbookmedia.com