Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 18 submissions in the queue.
posted by cmn32480 on Sunday July 24 2016, @01:46PM   Printer-friendly
from the not-just-locking-the-doors-anymore dept.

The Automotive Information Sharing and Analysis Center has published an executive summary of their Automotive Cybersecurity Best Practices.

From the summary

As vehicles become increasingly connected and autonomous, the security and integrity of automotive systems is a top priority for the automotive industry. The Proactive Safety Principles released in January 2016 demonstrate the automotive industry's commitment to collaboratively enhance the safety of the traveling public. The objective of the fourth Principle, "Enhance Automotive Cybersecurity," is to explore and employ ways to collectively address cyber threats that could present unreasonable safety or security risks. This includes the development of best practices to secure the motor vehicle ecosystem.

Unfortunately the public executive overview is somewhat content free and refers to NIST documents on security practices but something is better than nothing. It's been six years since the publication of Experimental Security Analysis of a Modern Automobile and five years since Comprehensive Experimental Analyses of Automotive Attack Surfaces . In those research papers compsci students splay open the control system of a car through standard security analysis techniques such as fuzzing. My favorite technique they used was to install custom software into the QNX powered OnStar device then use it to bridge between the body bus and the bus that handles the engines, brakes, steering, etc. Very clever indeed.

How does the community feel about the poorly secured two ton (metric or imperial, you pick) rolling robot that the modern vehicle has become?


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: 2) by melikamp on Sunday July 24 2016, @04:19PM

    by melikamp (1886) on Sunday July 24 2016, @04:19PM (#379429) Journal

    Direct link to pdf, if you want to avoid javascript: http://www.automotiveisac.com/assets/img/executive-summary.pdf [automotiveisac.com]

    Security has been marketed as safety for everyone against dangers to everyone. But it's been twisted. Sometimes security changed to security for vendors against their own customers.

    I agree, this is exactly the case here. From the customer's point of view, being able to understand and control the software is absolutely necessary for any kind of security evaluation, let alone assurance, but free/libre software is simply not on the table. This is all about security of auto manufacturers from lawsuits, and nothing else. Any resulting safety of passengers, other drivers, and pedestrians is just a nifty side-effect they can keep pointing to, while they are trying to "sell" us a car with software which we cannot analyze, control, or modify.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2