JULY- SEPT 2022Autobusiness outlook 19CAN gateway that bridges into firmware, a proprietary ADAS system that operates more or less independently, etc. What is more, the number of credible vendors for any specific subsystem can be counted on the fingers of one hand. As a result, even though a modern vehicle is truly "a computer on wheels", on some fundamental level that computer has the same capabilities regardless of which manufacturer produced your vehicle. I have found out first-hand that the path around this present state is lengthy, difficult, and expensive. This is inconsistent with the natural cadence and expectations of modern software development and results in siloed, rigid solutions and business models.To enable broader innovation we need smaller, well-defined functional modules that can be mixed and matched without lengthy negotiation and large NREs, ECU-level interfaces that are based on open standards, and software frameworks and platforms that encourage experimentation rather than lead to vendor lock-in. We need to build an ecosystem that is similar to the one that Android created for smartphones: open-source interfaces, reference designs, and a widely available software platform that fosters a thriving and efficient community of suppliers and OEMs.In my current role I lead product security at Zoox--one of the foremost autonomous vehicle companies (did I mention we are hiring?). Strengthening our internal cybersecurity R&D organization, keeping track of emerging standards, and bringing in vendors who can augment our efforts are all part of the job.What makes the work most interesting--and keeps me up at night occasionally--is the need to chart our cybersecurity roadmap across a largely unknown risk landscape and juggle perceptions about cybersecurity held by both traditional computer security vendors and automotive security specialists (our needs as an innovator in the field are almost always different from what is available off-the-shelf or pitched to us from either side; we are effectively at the cutting edge of building converged cybersecurity infrastructure, integrating the IT, OT--operational technology, and Product security domains).I would encourage suppliers of Automotive Engineering Services to try and see things from the perspective of OEMs that need to balance functionality, safety, and security for a complicated BOM that contains tens (or hundreds) of ECUs and even more major software dependencies as well as operationalize the technology--far beyond building and selling individual products.Embedding any new and unproven components--hardware or software--in the critical path is rarely something that we would consider prudent so you should think about how to be flexible by offering a variety of low-risk integration points, dispel concerns about lock-in for your solution by leveraging open-source software, and clearly express the long-term value that you are providing to the finished product as well as to OEM processes. I am excited about the path ahead and about being part of the evolution of the automotive value chain over the coming years!You can find my posts about technology on LinkedIn--reach out and share your thoughts!
< Page 9 | Page 11 >