© Crown copyright 2017
This publication is licensed under the terms of the Open Government Licence v3.0 except where otherwise stated. To view this licence, visit nationalarchives.gov.uk/doc/open-government-licence/version/3 or write to the Information Policy Team, The National Archives, Kew, London TW9 4DU, or email: email@example.com.
Where we have identified any third party copyright information you will need to obtain permission from the copyright holders concerned.
This publication is available at https://www.gov.uk/government/publications/principles-of-cyber-security-for-connected-and-automated-vehicles/the-key-principles-of-vehicle-cyber-security-for-connected-and-automated-vehicles
As vehicles get smarter, cyber security in the automotive industry is becoming an increasing concern. Whether we’re turning cars into wifi connected hotspots or equipping them with millions of lines of code to create fully autonomous vehicles, cars are more vulnerable than ever to hacking and data theft.
It’s essential that all parties involved in the manufacturing supply chain, from designers and engineers, to retailers and senior level executives, are provided with a consistent set of guidelines that support this global industry. The Department for Transport, in conjunction with Centre for the Protection of National Infrastructure (CPNI), have created the following key principles for use throughout the automotive sector, the CAV and ITS ecosystems and their supply chains.
Principle 1 - organisational security is owned, governed and promoted at board level
There is a security program which is aligned with an organisation’s broader mission and objectives.
Personal accountability is held at the board level for product and system security (physical, personnel and cyber) and delegated appropriately and clearly throughout the organisation.
Awareness and training is implemented to embed a ‘culture of security’ to ensure individuals understand their role and responsibility in ITS/CAV system security.
All new designs embrace security by design. Secure design principles are followed in developing a secure ITS/CAV system, and all aspects of security (physical, personnel and cyber) are integrated into the product and service development process.
Principle 2 - security risks are assessed and managed appropriately and proportionately, including those specific to the supply chain
Organisations must require knowledge and understanding of current and relevant threats and the engineering practices to mitigate them in their engineering roles.
Organisations collaborate and engage with appropriate third parties to enhance threat awareness and appropriate response planning.
Security risk assessment and management procedures are in place within the organisation. Appropriate processes for identification, categorisation, prioritisation, and treatment of security risks, including those from cyber, are developed.
Security risks specific to, and/or encompassing, supply chains, sub-contractors and service providers are identified and managed through design, specification and procurement practices.
Principle 3 - organisations need product aftercare and incident response to ensure systems are secure over their lifetime
Organisations plan for how to maintain security over the lifetime of their systems, including any necessary after-sales support services.
Incident response plans are in place. Organisations plan for how to respond to potential compromise of safety critical assets, non-safety critical assets, and system malfunctions, and how to return affected systems to a safe and secure state.
There is an active programme in place to identify critical vulnerabilities and appropriate systems in place to mitigate them in a proportionate manner.
Organisations ensure their systems are able to support data forensics and the recovery of forensically robust, uniquely identifiable data. This may be used to identify the cause of any cyber, or other, incident.
Principle 4 - all organisations, including sub-contractors, suppliers and potential 3rd parties, work together to enhance the security of the system
Organisations, including suppliers and 3rd parties, must be able to provide assurance, such as independent validation or certification, of their security processes and products (physical, personnel and cyber).
It is possible to ascertain and validate the authenticity and origin of all supplies within the supply chain.
Organisations jointly plan for how systems will safely and securely interact with external devices, connections (including the ecosystem), services (including maintenance), operations or control centres. This may include agreeing standards and data requirements.
Organisations identify and manage external dependencies. Where the accuracy or availability of sensor or external data is critical to automated functions, secondary measures must also be employed.
Principle 5 - systems are designed using a defence-in-depth approach
The security of the system does not rely on single points of failure, security by obscuration or anything which cannot be readily changed, should it be compromised.
The security architecture applies defence-in-depth and segmented techniques, seeking to mitigate risks with complementary controls such as monitoring, alerting, segregation, reducing attack surfaces (such as open internet ports), trust layers / boundaries and other security protocols.
Design controls to mediate transactions across trust boundaries, must be in place throughout the system. These include the least access principle, one-way data controls, full disk encryption and minimising shared data storage.
Remote and back-end systems, including cloud based servers, which might provide access to a system have appropriate levels of protection and monitoring in place to prevent unauthorised access.
Principle 6 - the security of all software is managed throughout its lifetime
Organisations adopt secure coding practices to proportionately manage risks from known and unknown vulnerabilities in software, including existing code libraries. Systems to manage, audit and test code are in place.
It must be possible to ascertain the status of all software, firmware and their configuration, including the version, revision and configuration data of all software components.
It’s possible to safely and securely update software and return it to a known good state if it becomes corrupt.
Software adopts open design practices and peer reviewed code is used where possible. Source code is able to be shared where appropriate.
Principle 7 - the storage and transmission of data is secure and can be controlled
Data must be sufficiently secure (confidentiality and integrity) when stored and transmitted so that only the intended recipient or system functions are able to receive and / or access it. Incoming communications are treated as unsecure until validated.
Personally identifiable data must be managed appropriately.
- what is stored (both on and off the ITS / CAV system)
- what is transmitted
- how it is used
- the control the data owner has over these processes
Where possible, data that is sent to other systems is sanitised.
Users are able to delete sensitive data held on systems and connected systems.
Principle 8 - the system is designed to be resilient to attacks and respond appropriately when its defences or sensors fail
The system must be able to withstand receiving corrupt, invalid or malicious data or commands via its external and internal interfaces while remaining available for primary use. This includes sensor jamming or spoofing.
Systems are resilient and fail-safe if safety-critical functions are compromised or cease to work. The mechanism is proportionate to the risk. The systems are able to respond appropriately if non-safety critical functions fail.
Troubleshooting: applicable standards and guidance
This list is not intended to be exhaustive. Further standards and guidance may be applicable. It’s recommended that for specific technologies or processes corporations should check for any applicable standards or guidance that might be of relevance and for any new standards that have been developed in the field.
- J3061 - Cybersecurity guidebook for cyber-physical vehicle systems
- J3101 - Requirements for hardware protected security for ground vehicle applications
- 9797-1 – Security techniques: message authentication codes – specifies a model for secure message authentication codes using block cyphers and asymmetric keys
- 12207 – Systems and software engineering – software lifecycle processes
- 15408 – Evaluation of IT security – specifies a model for evaluating security aspects within IT
- 17799 – Information technology – security techniques – code of practice for information security management
- 27001 – Information security management system
- 27002 – Code of practice – security – provides recommendations for information management (contains guidance on access control, cryptography and supplier relationship)
- 27010 – Information security management for inter-sector and inter-organizational communications
- 27018 – Code of practice – handling PII / SPI (privacy) – protection of personally identifiable information (PII) in public clouds
- 27034 – Application security techniques – guidance to ensure software delivers necessary level of security in support of an organisations security management system
- 27035 – Information security incident management
- 29101 – Privacy architecture framework
- 29119 – Software testing standard
- 05-138 – Cyber security for defence suppliers
- 800-30 - Guide for conducting risk assessments
- 800-88 - Guidelines for media sanitization
- SP 800-50 - Building an information technology security awareness and training program
- SP 800-61 - Computer security incident handling guide
- Microsoft security development lifecycle (SDL)
- SAFE Code best practices
- OWASP Comprehensive, lightweight application security process (CLASP)
- HMG Security policy framework
- PAS 1192-5 – BSI publication on security-minded building information modelling, digital built environments and smart asset management
- PAS 754 – BSI publication on software trustworthiness, governance and management