Infographic: Auto Software Security

we have come a long way since karl benz patented and developed what would become known as the modern automobile. the rise of driver-assist technology, internet connectivity, control-by-wire functionality, and other innovations means a greater reliance on software to carry out all types of functions — not just traditionally safety-critical systems. in fact, today’s car has more lines of code than a jet fighter. but with so much software being integrated along several tiers of the automotive supply chain, how do we ensure that the car as a system is safe, secure, and reliable?

automotive software survey

we asked software development professionals during a recent webinar a few questions about the perceptions of software quality in the automotive industry. the results not only provide insights about the perception of software quality ownership within the industry, but they also point to a lack of consensus amongst peers.

how does your organization determine functional safety requirements for the supply chain?

50% of respondents said that they rely on a certificate of compliance from suppliers. the other 50% said that policies that define testing protocols, including coverage, determine the functional safety requirements.

when is a hardware or software component considered done?

69% of respondents said that they consider a component finished when internal tests show 0% failure, versus 23% of respondents who said that passing government certifications means that the component is finished. only 8% said that a component is only finished when processes defined in standards, such as misra, are followed.

who owns functional safety for an automotive hardware component that contains software?

57% of respondents said that ultimately the manufacturer that assembles and sells the vehicle is responsible for the functional safety of all software-containing components. 35% of respondents said that functional safety is owned by the supplier of the hardware/software, whereas only 7% said that it’s the responsibility of the architects/programmers who design and create the code.

automotive software quality risks and what you can do to mitigate them

the following infographic identifies the growing surface area that cars of the not-too-distant future, as well as cars on the road today, expose that could be exploited by malicious hackers.