The auto industry will very quickly have to learn from the aviation industry in terms of integrating all these diverse information systems safely and securely. One difference is that cars are way more accessible than planes to be tampered with and hence the security systems will most likely have to be seriously hardened.
EDIT: please take "integrate" to mean to properly place each system on its own space and then surface the necessary APIs in a secure fashion. Of course physical separation of entertainment and car systems is the logical step, and it comes from the aviation industry.
There is no justifiable reason for these things to be integrated at all. Yes, it saves the mfr some $$, but people can DIE because of this stupidity.
As recent events have shown, the aviation industry hasn't integrated these systems securely - they're just harder to get to so it took a while before people started discovering their flaws - http://www.cnn.com/2015/05/17/us/fbi-hacker-flight-computer-...
Secure integration is not possible - the only right way for companies as inept as legacy auto makers to do this is for the systems to be separated.
Unfortunately the aviation industry has apparently been making the same mistake.
It has been obvious for at least a decade, to anyone paying attention, that if you create a path between a critical system and untrusted systems, you will not, in practice, be able to prove that the former is secure, nor anticipate all the sorts of attack it could be subject to. Why, then, does this mistake continue to be repeated, year after year? I imagine the explanation must include large doses of both ignorance and hubris - the Dunning-Kruger effect with teeth.
EDIT: please take "integrate" to mean to properly place each system on its own space and then surface the necessary APIs in a secure fashion. Of course physical separation of entertainment and car systems is the logical step, and it comes from the aviation industry.