Bill Boldt Sr. Business Development Manager, Security BlackberryCerticom
Due to high profile hacks on cars, it is hard to argue that without security you can have safety. So, security is emerging as perhaps the most important factor in the evolution of the connected autonomous car. Cars are the most software intensive systems in the universe with far more lines of code than even a state of the art jet fighter. By being such complex digital systems they have become prime targets for attack, and that is where cryptographic countermeasures come in.
Connecting the dots – in the emerging software-defined world safety increasingly comes from security and security comes from cryptography. Robust cryptographic security implementation is how you increase trust, and when it comes to a car every system must be trusted: inside the car, in the smart infrastructure, in emerging applications-based ecosystems, and in the manufacturing supply chain. When considering automotive security, many factors come into play. Some are noted here:
Automotive security fundamentally depends on the security of the operating system. For example, a microkernel architecture that separates critical OS components into their own protected memory partitions, provides temporal separation, and provides network security, among other things can greatly reduce the attack surface.
Security assets (crypto keys, serial numbers, etc.) must be securely installed into electronic devices such as Electronic Control Units (ECUs), domain/area controllers, and other processors. This process is called "personalization".
Electronic devices will often get personalized and installed into vehicles in globally located factories, which should utilize secure equipment and processes to ensure security of the devices.
Devices must be updateable at dealers and repair shops.
Aftermarket suppliers must be able to sell and update secure devices, and
OEMs must be able to authorize or not authorize specific electronic devices at manufacturing time and after the car is in use (for example to enforce warrantee policies).
And, there are many more. Personalizing a device such as a networked ECU means that it will become one of a kind. However, by definition that device cannot be used anywhere else. It becomes a unique stock keeping unit (SKU), which is averse to the purpose of flexible, just in time manufacturing flows. Security versus manufacturing flexibility is a serious trade off that will play a part of any automotive security design decision. Security robustness versus cost is another critical trade off, and applies to the manufacturing infrastructure and the design of the secure systems inside and outside the vehicle. Because security must be injected in the factory and in the field, a secure manufacturing system must have global reach, be manageable on a distributed basis, be updatable by various entities, and remain secure for years. In addition, security updates will increasingly be made over the air, and the systems that do that must by highly secure while being easy to manage. To maintain the maximum amount of flexibility, personalization and updating should be moved as close as possible to the very last minute, which is becoming a critical objective of the global manufacturing blue print. Blackberry Brings It All Together
In the car, outside the car, and in the manufacturing supply chain, security must be designed with best practices in mind right from the start, and BlackBerry Professional Services can help with that. BlackBerry QNX provides mission-critical automotive software proven in the automotive market. QNX software is well known for safety and new products are setting the new standard for security. BlackBerry's Certicom subsidiary provides certified cryptographic code and design consulting, as well as secure equipment and managed services that harden the automotive supply chain. Completing the picture, BlackBerry's secure OTA managed services make it easy to update software and security assets over the air. When it comes to automotive security, BlackBerry brings it all together.
Bill Boldt Business Development Manager, Security Blackberry
Electronic Control Units (ECUs) started out in the 1970s as discrete modules with each one doing one particular thing, at that time mainly for emissions controls and mileage. Then they became connected via in-car networks with the invention of the CAN bus in 1985. In-car networking represented a big improvement in capability. However, being networked means that ECUs became vulnerable to mischief and thus they, and what the connect to (such as domain and area controllers) need to be secured cryptographically to ensure that the signals being sent have not been tampered with or corrupted, and perhaps most importantly, that they are authentic. There is also the emerging need for confidentiality (i.e. encryption/decryption).
The picture below shows the top attack points. This range or targets indicates just how vulnerable cars have become:
With a car having so many places to attack, how can trusted security be implemented and why is it so important? Well, the main thing is that trust leads to safety, especially as cars become more connected and autonomous. Hacked or corrupted signals can have dire consequences in a car, which is obvious. In a car, safety is related to security and security comes to a large extent from cryptography. (Note that safety and security are not exactly the same thing, but there is tremendous overlap and interplay, and safety is becoming much more dependent on cryptographic security as cars become more connected and autonomous. For more on functional safety look here.)
Trust Trust is paramount in digital systems, and increasingly so in automotive. Trust comes from cryptographic solutions that:
Securely store secret keys
Securely issue, manage, renew and revoke security certificates
Include a mix of software and security hardened hardware devices, and
Are manufactured in highly secure facilities
What Creates Trust? A major tenet of security is that each system and sub-system will have different types of threats and a range of options to provide countermeasures to those. This means that the automotive security equation has many variables and thus is difficult to solve.
However, two things are always common to trustable cryptographic security, and they form the basic foundation of modern security:
A proven algorithm (e.g. Elliptic Curve Cryptography (ECC)), and
A secret cryptographic key (to provide the required level of security for the selected algorithm).
The challenge for the automaker is to choose the right algorithm and key length for the available processing resources and to securely issue, manage/store, renew, and revoke the security certificates. Cryptographic strength comes from the combination and application of these principles, processes, and techniques. Trust Anchor On a CAN bus, which was designed without security in mind, ECUs are exposed. So, connected cars should employ best practices for security, but cost, complexity (especially of the supply chain) and time get in the way. Having said that, best practices will eventually prevail and that will likely include a hardware trust anchor system to establish, maintain, and update cryptographic processes.
From the diagram you can see the four basic things that create a PKI-based hardware trust anchor:
A trusted hardware anchor that stores the key
That key, which becomes the root of trust
The certificate chain anchored by the root of trust, and
A signing mechanism that creates the anchored certificate chain
Multi-level Security Because there are so many systems in the increasingly software-defined car, security has to be multi-layered and fit the specific application. In other words — it must be tailored. You have to figure out what you are securing, what threats that system will face, and what countermeasures should be employed. You have to pick what pillars of security to apply; namely, confidentiality, data integrity, authentication, and non-revocation. Making sure you are doing the right security things on each system is what Blackberry is positioned to help you with, from consulting, to design, testing, certificate management, securing the supply chain, making updates, and applying cryptography to the in-car and around-the-car networks.
To learn more about cryptography for automotive please contact Blackberry's Certicom subsidiary, and for more information and/or help regarding reliable, secure, and trusted software for safety- and mission-critical applications such as automotive please contact QNX.
The bottom line is that BlackBerry, Certicom, and QNX can help your system become not just secure, but BlackBerry secure.
