Vtt R 01087 19

Vtt R 01087 19

This document is downloaded from the VTT’s Research Information Portal https://cris.vtt.fi VTT Technical Research Centre of Finland Cybersecurity in Autonomous Machine Systems Development Pentikäinen, Heimo; Malm, Timo; Heikkilä, Eetu Published: 14/11/2019 Document Version Publisher's final version Link to publication Please cite the original version: Pentikäinen, H., Malm, T., & Heikkilä, E. (Ed.) (2019). Cybersecurity in Autonomous Machine Systems Development. VTT Technical Research Centre of Finland. VTT Research Report No. VTT-R-01087-19 VTT By using VTT’s Research Information Portal you are bound by the http://www.vtt.fi following Terms & Conditions. P.O. box 1000FI-02044 VTT I have read and I understand the following statement: Finland This document is protected by copyright and other intellectual property rights, and duplication or sale of all or part of any of this document is not permitted, except duplication for research use or educational purposes in electronic or print form. You must obtain permission for any other use. Electronic or print copies may not be offered for sale. Download date: 27. Sep. 2021 RESEARCH REPORT VTT-R-01087-19 Cybersecurity in Autonomous Machine Systems Development Authors: Heimo Pentikäinen, Timo Malm, Eetu Heikkilä (editor) Confidentiality: Public RESEARCH REPORT VTT-R-01087-19 2 (15) Contents Contents ................................................................................................................................. 2 1. Introduction ....................................................................................................................... 3 2. Relations of cybersecurity risks and machinery risks ........................................................ 3 3. Standards, guidelines and certification for cybersecurity ................................................... 4 3.1 Secure by design – standards and guidelines ........................................................... 4 3.1.1 ISO 2700x standard series ............................................................................ 4 3.1.2 IEC 62443 standard series ............................................................................ 4 3.1.3 ISO/TR 22100-4 ............................................................................................ 5 3.1.4 IoT standardization ....................................................................................... 5 3.1.5 Secure Development: Towards Approval ...................................................... 6 3.1.6 Further guidelines and best practices............................................................ 6 3.2 Certification of cybersecurity aspects ........................................................................ 7 4. Cybersecurity for autonomous machine systems .............................................................. 8 4.1 Differences of office networks and automation networks ........................................... 8 4.2 Case example: one system ....................................................................................... 8 4.3 Case example: two connected systems .................................................................... 9 4.4 Cybersecurity requirements for autonomous machine systems .............................. 10 4.4.1 Data flow actors .......................................................................................... 10 4.4.2 White and black channels ........................................................................... 10 4.5 Trusted Platform Module ......................................................................................... 11 4.6 IPR and secret data ................................................................................................ 12 5. Secure development environments ................................................................................. 12 6. Conclusions .................................................................................................................... 12 Appendix 1. Abbreviations .................................................................................................... 14 Appendix 2. Selected examples of cyberattacks ................................................................... 15 RESEARCH REPORT VTT-R-01087-19 3 (15) 1. Introduction Autonomous machine systems (AMS) are typically software-intensive and highly connected systems. While there is no one and agreed definition available for cybersecurity, it is widely considered as one of the key aspects to be addressed in development of AMS. First, and perhaps the most important issue for cybersecurity in this context is that cybersecurity must be an essential part of entire system design from the starting point. This approach is called Secure by design. A way to reach secure by design approach is to emphasize requirements of cybersecurity. In addition to the actual machine system being developed, system developers need to consider the entire software development environment, e.g. secure software compiling and proper version management. This issue is also relevant with hardware development. In this report, focus will be on software development. This report provides an overview of the cybersecurity related issues, some proposed solutions, as well as future development needs. It combines views from a technical cybersecurity perspective with a machinery safety perspective. The report is structured so that we first discuss the relations of cybersecurity and machinery related risks. This is followed by an overview of standards and guidelines applicable in AMS design, after which the cybersecurity for AMS is further elaborated. Appendix 1 contains selected abbreviations and definitions, and Appendix 2 provides examples of cybersecurity related incidents reported recently. While this report focuses on technical issues of cybersecurity in machine systems, cybersecurity is always also a human issue. Even the most autonomous systems interact with humans over their life cycle. 2. Relations of cybersecurity risks and machinery risks In safety engineering, risk is typically defined as a function of probability and consequence, e.g. risk = probability * consequence. However, with cybersecurity issues it is problematic to estimate both probability and consequence. This is because usually we do not have enough data for these estimations. Additionally, safety risk is usually related to random events, whereas security risk is based on actions done on purpose. This means that probability of vulnerability associated to random events can be low, but if the vulnerability is searched on purpose, the probability becomes meaningless. Another characteristic of cybersecurity is that the cyber world is dynamic, that trends of cybersecurity attacks vary temporally or occasionally and consequences can vary case by case. Security risk may change as technologies or circumstances change, but it does not wear out and a long use history does not necessarily guarantee a secure system (see ISO/TR 22100-4). Standard family IEC/ISA 62443 suggest that there should be target security levels (SL 1 – SL 4), which specify the general risk level and the target to quantify countermeasures against cyber-security risks. There is some similarity to Safety Integrity Levels (SIL according to IEC 61508 and IEC 62061) and to Performance Levels (PL according to ISO 13849-11), which are applied to measure safety risk and related protective measures of machinery safety functions. 1 ISO 13849-1:2015. Safety of machinery. Safety-related parts of control systems. Part 1: General principles for design. 86 p. RESEARCH REPORT VTT-R-01087-19 4 (15) According to Machinery Directive2, the machine builder (or authorized representative) must consider in risk assessment “intended use and any reasonably foreseeable misuse thereof”. Some cyber-security risks could be associated to “reasonably foreseeable misuse”, but usually it is not the case. Machinery Directive is related to safety, but if cyber-security issue can affect safety, it should be considered. The different approaches for machinery and cyber risk assessment are comprehensively discussed in VTT report “Risk assessment of machinery system with respect to safety and cyber-security” available online3. 3. Standards, guidelines and certification for cybersecurity 3.1 Secure by design – standards and guidelines Secure by design approach can be implemented following various standards and guidelines. This chapter provides an overview of selected key standards, which can be applied in the development of AMS. 3.1.1 ISO 2700x standard series A basic standard for information security ISO 27000 (SFS-EN ISO/IEC 27001:2017) defines information security as follow: information security preservation of confidentiality (2.12), integrity (2.40) and availability (2.9) of information Note 1 to entry: In addition, other properties, such as authenticity (2.8), accountability, non-repudiation (2.54), and reliability (2.62) can also be involved. ISO 27001 standard (SFS-EN ISO/IEC 27000:2017) states management and risk issues for information security as follow: The information security management system preserves the confidentiality, integrity and availability of information by applying a risk management process and gives confidence to interested parties that risks are adequately managed. ‘Confidentiality, Integrity, Availability’ is also called as CIA-triad. 3.1.2 IEC 62443 standard series One of the main standard of industrial control system is IEC 62443 series. The IEC 62443-1-1 standard defines

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    17 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us