Software Security for the Connected Car

In 2012, the OnStar system built into GM vehicles was used at the request of police to shut down a stolen car as it was being pursued. This incident and others made it clear that if the police can break into a car, so can thieves and other hackers. And while connectivity and data are the currency of our age, capitalizing on them in the automotive sector comes with significant risk. While internal and external vehicle networks are more pervasive than ever before, they also broaden the attack surface of connected cars and place an additional burden of safety and security on automakers and Tier 1s. In response, automotive OEMs are increasingly requiring developers to prove that their software meets the highest standards for security as well as safety.

In this webinar, attendees will learn how isolation techniques and security measures from the embedded industry can be leveraged to protect modern vehicles from unwanted code or malicious attack. Best practices are explained, technology examples provided, and questions answered. We’ll discuss how automotive security breaches can be introduced through failures in software quality, and we’ll cover specific processes that will show attendees how to:

  • Avoid dangerous coding practices
  • Choose and apply secure coding standards quickly and cost-effectively
  • Develop understandable and maintainable code
  • Thoroughly test code using automated tools
  • Prove that software security practices are being followed throughout the development lifecycle
  • Develop secure code while meeting cost and schedule demands

Please fill out the form below to view the webinar