Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Monday September 11 2017, @06:14AM   Printer-friendly
from the you-can't-make-this-stuff-up dept.

A trade magazine, http://www.todaysmotorvehicles.com/article/5-myths-about-connected-cars/ ran this article by Shaun Kirby, Cisco Consulting CTO, "5 Myths About Connected Cars". Haven't read anything this funny all year, some clips include:

Myth: Securing connected cars requires breakthroughs in security technology.

Fact: Connected cars are extremely complex, with many sensors, computers, and networks, along with an ever-growing list of features. Fortunately, technologies already exist that have proven effective in securing some of the largest enterprise information technology (IT) infrastructures. Existing technologies are well equipped to keep drivers and their data safe now and into the future.

...and this one, the punch line at the end had me rolling in the aisle:

Myth: Automakers are responsibile for securing connected cars.

Fact: The vehicle manufacturer is just one link in the security chain. Multiple tiers of suppliers, dealerships, developers of aftermarket devices and services, regulatory bodies, and other industries creating devices and services that interact with connected cars are all responsible for keeping cars and drivers safe and secure.

It is especially important for third parties who provide connected car applications to have secure infrastructures. For instance, a mall operator installing vehicle-to-infrastructure units to guide heavy traffic to optimal parking spots will need to ensure that all the proper security controls are in place.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 1, Interesting) by Anonymous Coward on Monday September 11 2017, @12:04PM (1 child)

    by Anonymous Coward on Monday September 11 2017, @12:04PM (#566201)

    Thank you, + mods well deserved. I have a couple of older cars and both have turned on the check engine light, one several times over the years. As the annual state inspection rolls around, I start to get nervous, will it stay off long enough to pass another year? How much will it cost this time? If the light is on for a one-time anomaly (like a mis-fire) and I "clear all codes" using a cheap OBD reader, will it stay off long enough to pass? (usually not)

    Once it was just the gas cap seal (evaporative emissions) -- which visibly looked and felt the same as the replacement, but the new cap didn't trigger the light. Another time there were 20+ codes thrown, turned out to be a working battery that couldn't maintain enough voltage (while cranking) to keep one of the computers happy.

    I'd love to run a pre-OBD car, but here we have lots of salt on the roads in winter. Older cars were not rustproofed like newer cars (including galvanized sheet metal and stainless exhaust systems) and there are very few of those cars left. Most of the older cars I see are only used in summer.

    My bicycle works great for shorter errands. As others have noted, one easy way to keep a car a long time is to not use it very much...

    Starting Score:    0  points
    Moderation   +1  
       Interesting=1, Total=1
    Extra 'Interesting' Modifier   0  

    Total Score:   1  
  • (Score: 2) by bob_super on Monday September 11 2017, @07:07PM

    by bob_super (1357) on Monday September 11 2017, @07:07PM (#566332)

    Places like Paris have started banning cars that are too old from entering the city altogether (not that anyone should ever drive in Paris).
    If your car is too old to have computers, it's also polluting more than a battalion of newer cars. That's not a bad excuse.

    If you want your car to be safe, just clip the antennas and don't connect your phone to it. Connected cars are an idiocy; the easy answer is to air-gap.

    Spurious error codes? Yeah, they suck. But most error codes do save you hours, of tying to figure out from your non-techie S.O., whether it was a "ping" or a "pop" before the engine croaked.