Evaluation of a Cyber Risk Assessment Approach for Cyber–Physical Systems: Maritime- and Energy-Use Cases
Abstract
:1. Introduction
- An evaluation of an open-source risk assessment process that is FMECA-ATT&CK supporting its development as a semi-automated cyber risk assessment tool for CPSs.
- Key characteristics for the evaluation of risk assessment methods. These characteristics can be utilized as a basis for comparison among existing and newly proposed methods for risk assessment.
- A standard-aligned methodology for the evaluation of risk assessment methods. The methodology allows for the evaluation according to a group of characteristics while reducing the impact of bias.
2. Background
2.1. Standards, Methods and Approaches
2.1.1. IEC 31010:2019, ISO 15288:2015 and IEC 60812
2.1.2. FMECA-ATT&CK
2.1.3. Bow-Tie
2.2. Use Cases
2.2.1. Autonomous Passenger Ship (APS)
2.2.2. Digital Substation (DS)
3. Related Work
4. Evaluation Methodology
4.1. Preparing for the Evaluation
- Due to the reliance on expert judgment, measures for reducing bias in the assessment must be integrated in order to improve the assessment quality.
- Diversity in the use cases should be pursued to include various application and technology domains in order to measure applicability.
- Another common risk assessment method needs to be chosen that performs a similar function to the method that is subject to evaluation and provides categorically aligned results.
4.2. Executing the Evaluation
4.3. Managing the Evaluation
5. FMECA-ATT&CK Evaluation
5.1. Preparing for the Evaluation
5.1.1. Scope, Objectives and Requirements
5.1.2. Evaluation Procedure
- Group communication is hindered to avoid information bias.
- FMECA-ATT&CK itself implements measures to reduce bias through the utilization of metrics based on graph theory and data from the ATT&CK framework.
- Inputs from previous relevant risk assessment processes are avoided as much as possible. However, the utilization of some previous data was unavoidable. More details will be discussed later on when such a case occurred.
5.1.3. Identifying Stakeholders
5.1.4. Preparing Data, Enabling Systems and Training for the Assessment
5.2. Executing the Evaluation
5.2.1. Delivering Tasks and Receiving Input from Experts
5.2.2. Evaluating the Results
5.3. Managing the Evaluation
- The utilized template for receiving experts’ input for each use case when conducting FMECA-ATT&CK.
- The scoping questions and the prepared answers for the Bow-Tie process.
- The FMECA-ATT&CK scripts, inputs, and outputs.
- The generated Bow-Tie diagrams.
6. Evaluation Results
6.1. Risk Assessment Results
6.1.1. Top Risks
6.1.2. Suggested Risk Controls
6.1.3. Usability Metric
6.2. FMECA-ATT&CK Questionnaire
6.3. Experts Comments
- Scope definition (Step 1): The classification criteria for certain components is not clear. Some components can be classified in different ways, others were outside the knowledge field of some experts. Furthermore, additional technical and non-technical components should be considered, such as the human operator. Moreover, there exist several performance standards for defining safety-related failure modes.
- Relevant failure modes (Step 2): The criteria for defining the relevant failure mode was characterized as difficult. Some emphasized existing failure modes that are safety-related are easier to consider than security-related failure modes. Furthermore, human errors were proposed for consideration.
- Impact estimation of failure modes (Step 4): The current estimation criteria are generic and require additional methods such as a hazard and operability study (HAZOP) or event tree analysis (ETA). Furthermore, some failure modes were unclear to some experts and therefore were unable to estimate their impact. Additionally, quantifying the safety, financial, environmental, and reputation criticality scores for certain components was found to be challenging.
- Training: Additional training was required for better execution.
- Scope: Experts with more operational than technical expertise found the approach difficult to apply due to the lack of knowledge of component-level failures. Furthermore, the human element is under-represented in the current approach. Humans can be an asset in the system as well as a risk.
- Background: the approach requires several experts with diverse backgrounds, including operational and technical experts. Some components require specific knowledge to provide a more sound judgment.
7. Discussion
7.1. Limitations in the Evaluation
- The results received from the fourth group might include bias due to the bandwagon effect. This was an unavoidable effect in order to accommodate the participants’ time limitations. Efforts to reduce the bias were taken in the form of seeking individual confirmation of the results.
- The FMECA-ATT&CK approach for calculating threat likelihood is based on the calculated CVSS metrics for the techniques in the different ATT&CK matrices which are system-independent and pre-estimated and discussed in previous work [12]. The experts were offered a chance to provide their own estimation but due to time limitations, they were unable to do so. Therefore, we resorted to utilizing the pre-estimated data which is subject to bias.
- We are not claiming that FMECA-ATT&CK is straightforwardly applicable in application domains of CPSs other than maritime and energy. This would require extending the evaluation to include additional and diverse use cases.
7.2. Future Work
- The scope of considered failure modes focuses on adversarial threats. Considerations of non-adversarial threats, such as human errors, could be useful as a future direction.
- Additional guidelines and supporting methods are needed to estimate the impact of certain failures. Particularly, the estimation of safety and financial impacts.
- The current asset categorization does limit the scope of relevant use cases. Categorizing some components according to the existing asset categorization criteria was found to be challenging. This suggests the proposition of domain-specific categorization. Consequently, the approach requires additional adaptations to accommodate the change of scope. This can include domain-specific threats, failure modes, and risk controls.
- FMECA-ATT&CK is suitable for tier 3 activities according to NIST risk management tiers which address risk from the perspectives of system components [31]. The conducted risk assessment process using Bow-Tie yielded some risk mitigation measures that are at higher tiers, such as a business continuity plan (BCP). The consideration of such mitigation measures requires additional tasks to be conducted after FMECA-ATT&CK which focus on multi-tier risk management rather than tier 3 risk assessment. In this direction, the expansion of the list of supporting controls will be considered in the future.
- The utilization of additional use cases and different application domains for the application of FMECA-ATT&CK will expand its applicability.
- Investigating the efficiency of integrating FMECA-ATT&CK for cyber risk management in real decision-making units (DMUs) would be an interesting direction. For that, Wang et al. [32] proposed the utilization of data envelopment analysis (DEA) to measure the efficiency of cybersecurity DMUs. This approach would provide quantitative measurements for the reduced cost which FMECA-ATT&CK is hypothesized to achieve as a consequence to reduce the need for expert judgment.
8. Conclusions
Author Contributions
Funding
Institutional Review Board Statement
Informed Consent Statement
Data Availability Statement
Acknowledgments
Conflicts of Interest
Appendix A. Detailed FMECA-ATT&CK Description
Step | Table | Column | Data Description | Data Values | Data Source |
---|---|---|---|---|---|
Step 1: Specify Components | Component Description Table (CDT) | Class | Relevant ATT&CK Matrices | Enterprise, ICS, Mobile, Combination | Experts |
Comp Name | Component Name | Architecture Model | |||
Type | Component ICS Categorization | Control Server, Data Historian, Engineering Workstation, Field Controller/RTU/PLC/IED, HMI, I/O Server, SIS/Protection Relay, Sensor | Experts choice based on ATT&CK categorization | ||
Platform | Component IT Platform | Windows, Linux, Network, macOS, Cloud, Containers | Architecture Model | ||
Technology | Component Technology | App-Based or Other | |||
Additions | Component Additions | Radio, GPS, Cell, Wi-Fi, Video, etc. | |||
Step 2: Identify Failure Modes | - | - | Relevant Failure Modes | All ATT&CK Tactics (16) | Experts choice based on ATT&CK Tactics |
Step 3: Identify Controls | Failure- Mitigation Table (FMT) | Matrix | ATT&CK Matrix | Enterprise, ICS, Mobile | ATT&CK |
Technique | ATT&CK Technique | All ATT&CK Techniques (>700) | |||
Mitigation | ATT&CK Mitigation | All ATT&CK Mitigations (>70) | |||
Efficiency | Mitigation Efficiency | (0.0–1.0) | Experts | ||
Component- Mitigation Table (CMT) | Mitigation | ATT&CK Mitigation | All ATT&CK Mitigations (>70) | ATT&CK | |
Component 1 | Component Name | (0: not covered or 1: covered) | Architecture Model | ||
Component 2 | Architecture Model | ||||
…… | |||||
Component N | |||||
Step 4: Estimate the Impact of the Consequences of Failure Modes | Failure-Mode- Consequences Table (FMCT) | Matrix | ATT&CK Matrix | Enterprise, ICS, Mobile | ATT&CK |
Tactic | ATT&CK Tactics and Impact Techniques | All Tactics and Impact Techniques (>90) | |||
Operational | Wight of Operational Consequence | (0.00–infinity) | Experts | ||
Safety | Wight of Safety Consequence | ||||
Information | Wight of Information Consequence | ||||
Financial | Wight of Financial Consequence | ||||
Staging | Wight of Staging Consequence | ||||
The Failure- Mode-Metric Table (FMMT) | Matrix | ATT&CK Matrix | Enterprise, ICS, Mobile | ATT&CK | |
Tactic | ATT&CK Tactics and Impact Techniques | All Tactics and Impact Techniques (>90) | |||
Operational | Operational Metric to be used | Overall Operational Impact (OOI), Impact to Control Functions (I2CF), Impact to Monitoring Functions (I2MF) | Process Defined | ||
Safety | Safety Metric to be used | Safety Criticality (SC) | |||
Information | Information Metric to be used | Location Information Criticality (LIC), Information Criticality (IC), Intellectual Property Criticality (IPC) | |||
Financial | Financial Metric to be used | Financial Criticality (FC), Occurring Financial Criticality (FC2) | |||
Staging | Staging Metric to be used | Out-Degree Centrality (ODC), Overall Component Criticality (OCC) | |||
Component- Criticality- Scoring Table (CCST) | Comp Name | Component Name | |||
OOI | OOI score of component | (0.0–1.0) | Graph of Architecture Model | ||
I2CF | I2CF score of component | ||||
I2MF | I2MF score of component | ||||
SC | SC score of component | Experts | |||
LIC | LIC score of component | ||||
IC | IC score of component | ||||
IPC | IPC score of component | ||||
FC | FC score of component | ||||
FC2 | FC2 score of component | ||||
ODC | ODC score of component | Graph of Architecture Model | |||
OCC | OCC score of component | Process Defined | |||
Step 5: Identify Failure Mechanisms | Techniques- Description Table (TDT) | Matrix | ATT&CK Matrix | Enterprise, ICS, Mobile | ATT&CK |
Technique | ATT&CK Technique | All ATT&CK Techniques (>700) | |||
Tactic | ATT&CK Tactics | All ATT&CK Tactics (16) | |||
Platform | Technique IT Platform | Windows, Linux, Network, macOS, Cloud, Containers | |||
Type | Technique ICS Assets | Control Server, Data Historian, Engineering Workstation, Field Controller/RTU/PLC/IED, HMI, I/O Server, SIS/Protection Relay, Sensor | |||
Technology | Technique Technology | App-Based or Other | Experts | ||
Additions | Technique Additions | Radio, GPS, Cell, Wi-Fi, Video, etc. | |||
Step 6: Estimate the Likelihood of Failure Mechanisms | Techniques- Description Table (TDT) | CVSS | Technique Expolitability Score based on CVSS | (0.00–3.89) | ATT&CK-based heuristics and Experts |
Step 7: Evaluate the Risks | - | - | Risk Rating Criteria such as thresholds | e.g., Risk <3 = Low | Experts |
Step 8: Propose Risk Reduction Measures | - | - | Suggested mitigation methods for each technique | All ATT&CK Mitigations (>70) | ATT&CK |
Algorithm A1 Risk Priority Number (RPN) Calculation and mitigation identification (RPNMI) (adapted from [12]). Check Table A1 for acronyms |
|
Appendix B. Consolidation Process
Appendix C. Questionnaire Details
Question | Choice | Meaning | |
---|---|---|---|
1 | How applicable is the approach for application in different CPS use cases? | 1 | Very limited applicable use cases |
2 | Only few number of applicable use cases | ||
3 | Several applicable use cases | ||
4 | Many applicable use cases | ||
5 | So many applicable use cases | ||
2 | How feasible was the implementation of the different steps? Note: This is related to the a pproach itself and not the current mode of execution as delivered through the excel sheet | 1 | The entire process is not feasible for implementation |
2 | Some steps are not feasible for implementation | ||
3 | The process is feasible but require some adaptation for implementation | ||
4 | The process is feasible and can be implemented in its current form | ||
3 | How reasonable were the results? | 1 | The results did not make sense at all |
2 | Some of the results did not make sense while others did | ||
3 | The results do make sense | ||
4 | How difficult it is to integrate additional aspects? (asset categories, threats, mitigation measures, impact elements, etc.) | 1 | It would be extremely difficult to integrate additional aspects |
2 | It would require a lot of modifications to integrate additional aspects | ||
3 | Integrating additional aspects is possible with minor modifications | ||
5 | How comprehensive is the approach in its inclusion of elements required for sufficient cyber risk assessment processes? | 1 | The approach scope is very limited |
2 | The approach scope is limited | ||
3 | The approach scope is sufficient, but many elements should be added | ||
4 | The approach scope is comprehensive; but some elements can be added | ||
5 | The approach scope is very comprehensive | ||
6 | How would it perform in large and complex networks or Systems of Systems (SoS)? | 1 | Suitable and efficient only for small SoS |
2 | Suitable and efficient for moderate SoS | ||
3 | Suitable and efficient for large SoS | ||
4 | Suitable and efficient for very large SoS | ||
7 | How easy was it to follow with limited training/Consultation? Note: this is related to the current mode of execution as delivered through the excel sheet | 1 | I could not execute the assessment with the amount of training I received. |
2 | I could only execute some steps of the assessment due to ambiguous tasks. | ||
3 | I executed all the required steps but could not finish some of the tasks due to ambiguity | ||
4 | I executed all the required steps and finished all the tasks | ||
8 | Would you like to elaborate on the applicability, feasibility, accuracy, adaptability, scalability, and required training to apply the approach? | Open Ended | |
9 | How many hours in total did the process took to be completed, approximately. (Filling the Excel sheet) | 1 | an hour or less |
2 | around 2 h | ||
3 | around 3 h | ||
4 | around 4 h | ||
5 | 5 h or more |
References
- Duru, O. The Future Shipping Company: Autonomous Shipping Fleet Operators. Available online: https://www.maritime-executive.com/editorials/the-future-shipping-company-autonomous-shipping-fleet-operators (accessed on 28 February 2023).
- NTNU Autoferry. Autoferry—Autonomous All-Electric Passenger Ferries for Urban Water Transport; Norwegian University of Science and Technology: Trondheim, Norway, 2018. [Google Scholar]
- Amro, A.; Gkioulos, V.; Katsikas, S. Connect and Protect: Requirements for Maritime Autonomous Surface Ship in Urban Passenger Transportation. In Computer Security; Springer: Berlin/Heidelberg, Germany, 2019; pp. 69–85. [Google Scholar]
- Johnson, B. Maritime Cyber Incidents Increased at Least 68 Percent in 2021, Coast Guard Reports. Available online: https://www.hstoday.us/featured/maritime-cyber-incidents-increased-at-least-68-percent-in-2021-coast-guard-reports/ (accessed on 28 February 2023).
- offshore energy.biz. COSCO Shipping Lines Falls Victim to Cyber Attack. 2018. Available online: https://www.offshore-energy.biz/cosco-shipping-lines-falls-victim-to-cyber-attack/ (accessed on 28 February 2023).
- Norman, J. Iranian Hackers Suspected in Cyber Breach and Extortion Attempt on Navy Shipbuilder Austal. 2018. Available online: https://www.abc.net.au/news/2018-11-13/iranian-hackers-suspected-in-austal-cyber-breach/10489310 (accessed on 28 February 2023).
- Greenberg, A. The Untold Story of NotPetya, the Most Devastating Cyberattack in History; Massachusetts Institute of Technology: Cambridge, MA, USA, 2018. [Google Scholar]
- Seals, T. Researcher: Not Hard for a Hacker to Capsize a Ship at Sea. Available online: https://threatpost.com/hacker-capsize-ship-sea/142077/ (accessed on 28 February 2023).
- Hambling, D. Ships Fooled in GPS Spoofing Attack Suggest Russian Cyberweapon. 2017. Available online: https://www.newscientist.com/article/2143499-ships-fooled-in-gps-spoofing-attack-suggest-russian-cyberweapon/ (accessed on 28 February 2023).
- IEC 31010; Risk Management—Risk Assessment Techniques. ISO: Geneva, Switzerland, 2019.
- ISO/IEC 27005:2018; Information Technology. Security Techniques. Information Security Risk Management. ISO: Geneva, Switzerland, 2018.
- Amro, A.; Gkioulos, V.; Katsikas, S. Assessing Cyber Risk in Cyber-Physical Systems Using the ATT&CK Framework. ACM Trans. Priv. Secur. 2022, 26, 1–33. [Google Scholar] [CrossRef]
- IEC/IEEE 15288:2015; Systems and Software Engineering-Content of Systems and Software Life Cycle Process Information Products (Documentation). International Organization for Standardization/International Electrotechnical Commission: Geneva, Switzerland, 2015.
- IEC. Analysis Techniques for System Reliability-Procedure for Failure Mode and Effects Analysis (FMEA); IEC: Geneva, Switzerland, 2018. [Google Scholar]
- Strom, B.E.; Applebaum, A.; Miller, D.P.; Nickels, K.C.; Pennington, A.G.; Thomas, C.B. Mitre ATT&CK: Design and Philosophy; Technical Report; MITRE: Bedford, MA, USA, 2018. [Google Scholar]
- Shostack, A. Threat Modeling: Designing for Security; Wiley Publishing: Hoboken, NJ, USA, 2014. [Google Scholar]
- Mihai, I.C.; Pruna, S.; Barbu, I.D. Cyber kill chain analysis. Int. J. Info. Sec. Cybercrime 2014, 3, 37. [Google Scholar] [CrossRef]
- ENISA. ENISA Threat Landscape 2021. Available online: https://www.enisa.europa.eu/publications/enisa-threat-landscape-2021 (accessed on 28 February 2023).
- Alford, R.; Lawrence, D.; Kouremetis, M. CALDERA: A Red-Blue Cyber Operations Automation Platform; MITRE: Bedford, MA, USA, 2022. [Google Scholar]
- DNV GL. Cyber Security Resilience Management for Ships and Mobile Offshore Units in Operation; Technical Report, DNVGL-RP-0496; DNV GL: Oslo, Norway, 2016. [Google Scholar]
- Amro, A.; Gkioulos, V.; Katsikas, S. Communication architecture for autonomous passenger ship. Proc. Inst. Mech. Eng. Part O J. Risk Reliab. 2021. [Google Scholar] [CrossRef]
- Khodabakhsh, A.; Yayilgan, S.Y.; Abomhara, M.; Istad, M.; Hurzuk, N. Cyber-risk identification for a digital substation. In Proceedings of the 15th International Conference on Availability, Reliability and Security, Virtual, 25–28 August 2020; pp. 1–7. [Google Scholar]
- Tam, K.; Jones, K. Factors affecting cyber risk in maritime. In Proceedings of the 2019 International Conference on Cyber Situational Awareness, Data Analytics Furthermore, Assessment (Cyber SA), Oxford, UK, 3–4 June 2019; pp. 1–8. [Google Scholar]
- Abkowitz, M.; Camp, J. An application of enterprise risk management in the marine transportation industry. WIT Trans. Built Environ. 2011, 119, 221–232. [Google Scholar]
- Grigoriadis, C.; Papastergiou, S.; Kotzanikolaou, P.; Douligeris, C.; Dionysiou, A.; Elias, A.; Bernsmed, K.; Meland, P.H.; Kamm, L. Integrating and Validating Maritime Transport Security Services: Initial results from the CS4EU demonstrator. In Proceedings of the 2021 Thirteenth International Conference on Contemporary Computing (IC3-2021), Noida, India, 5–7 August 2021; pp. 371–377. [Google Scholar]
- Johansen, T.; Utne, I.B. Risk Analysis of Autonomous Ships. In Proceedings of the 30th European Safety and Reliability Conference and 15th Probabilistic Safety Assessment and Management Conference (ESREL2020 PSAM15), Venice, Italy, 1–5 November 2020. [Google Scholar]
- Tam, K.; Jones, K. Cyber-risk assessment for autonomous ships. In Proceedings of the 2018 International Conference on Cyber Security and Protection of Digital Services (Cyber Security), Scotland, UK, 11–12 June 2018; pp. 1–8. [Google Scholar]
- Kavallieratos, G.; Katsikas, S.; Gkioulos, V. Cyber-attacks against the autonomous ship. In Computer Security; Springer: Berlin/Heidelberg, Germany, 2018; pp. 20–36. [Google Scholar]
- Pillitteri, V.Y.; Pierre, J.; Stine, K.; Scholl, M.; Stine, K. Assessing Security and Privacy Controls in Information Systems and Organizations; NIST: Gaithersburg, MD, USA, 2022. [Google Scholar]
- Boddy, C. The nominal group technique: An aid to brainstorming ideas in research. Qual. Mark. Res. Int. J. 2012, 15, 6–18. [Google Scholar] [CrossRef] [Green Version]
- Boyens, J.; Paulsen, C.; Moorthy, R.; Bartol, N.; Shankles, S. NIST Special Publication 800-161: Supply Chain Risk Management Practices for Federal In-Formation Systems and Organizations; NIST: Gaithersburg, MD, USA, 2015. [Google Scholar]
- Wang, C.N.; Yang, F.C.; Vo, N.T.; Nguyen, V.T.T. Wireless communications for data security: Efficiency assessment of cybersecurity industry—A promising application for UAVs. Drones 2022, 6, 363. [Google Scholar] [CrossRef]
Characteristics | Objective | Related Work |
---|---|---|
Applicability | suitability for application in different use cases in different application domains. | [23,24] |
Feasibility | the ability to implement the different steps in the approach. | [25,26] |
Comprehensiveness | the extent to which different aspects of risks have been considered. Aspects of risks include, threats identification, likelihood and impact estimation, mitigation measures, etc. | [12] |
Adaptability | The extent to which the missing aspects can be integrated to improve the method. | |
Scalability | The performance of the process in large and complex networks. | |
Usability | The ability to follow and conduct the process with limited training/consultation. | [23] |
Accuracy | The soundness of the results. | [23,26] |
Group | Assessment Process | Participants | |
---|---|---|---|
Current Roles | Background and Previous Roles | ||
1 | FMECA-ATT&CK on APS | PhD candidate in maritime cybersecurity | Working experience on offshore vessels |
Researcher in cybersecurity | Maritime, energy, and CPS cybersecurity | ||
PhD candidate in maritime cybersecurity | Seafarer (AB apprentice, AB, Deck Cadet, Junior Officer) and FMEA Auditor of DP systems | ||
2 | Bow-Tie on APS | Cybersecurity Consultant | IT/OT cybersecurity |
Cybersecurity Consultant | IT/OT cybersecurity | ||
3 | FMECA-ATT&CK on DS | PhD Candidate in CPS cybersecurity | Cybersecurity in the smart grid |
Postdoctoral researcher | Postdoctoral researcher in smart grid communication and security simulation | ||
Researcher in cybersecurity and privacy | Cybersecurity in the smart grid and IoT privacy | ||
4 | Bow-Tie on DS | Industrial PhD/Cybersecurity Engineer | Cybersecurity in the smart grid |
Industrial PhD/Senior adviser information security | Working with SCADA/OT—systems in the electricity sector for over 30 years |
Bowtie Threats | FMECA-ATT&CK Techniques (ATT&CK ID) | FMECA-ATT&CK Risk |
---|---|---|
APS Use Case | ||
Valid Accounts Stolen from a Student | Valid Accounts (T0859/T1078) | Low risk due to the inclusion of many relevant mitigation methods (e.g., access management) |
Remote Desktop Protocol (RDP) | Remote Desktop Protocol (T1021.001) | Low risk due to the inclusion of many relevant mitigation methods (e.g., network segmentation) |
Compromises Hosts | High-level threat. Relevant techniques: Drive-by Compromise (T1189), Compromise Client Software (T1554) | Both relevant techniques have a low risk either due to the inclusion of several relevant mitigations methods or low estimated impact and likelihood (e.g., update software) |
Internal Spear phishing | Internal Spear phishing (T1534) | Low due to low estimated likelihood |
Malicious Software | Malicious File (T1204.002) | Low risk either due to the inclusion of many relevant mitigation methods, and low estimated likelihood (e.g., execution prevention) |
Compromised Credentials | High-level threat. Relevant techniques: Valid Accounts (T0859/T1078) Default Credentials (T0812) | Low risk due to the inclusion of many relevant mitigation methods (e.g., access management) |
Single 4G/5G link | Outside the scope of FMECA-ATT&CK which only considers adversarial threats. | Although no techniques are identified for this specific threat, FMECA-ATT&CK does consider the existing redundant services to calculate the detectability (risk reduction degree). |
Malicious Remote Access Tools | Exploitation of Remote Services (T1210) | Low risk due to the inclusion of many relevant mitigation methods (e.g., update software) |
Legitimate Credentials with Native Network and Operating System Tools | Remote Services (T1021) | High risk for some components due to high likelihood, impact, and lack of existing relevant mitigation measures |
Remote Services | ||
Commonly used port (RDP, SMB, SSH, etc.) | Commonly Used Port (T0885) | Lw risk due to the inclusion of many relevant mitigation methods (e.g., network segmentation) |
Repetitive Change of the I/O point values at the Control computer | Brute Force I/O (T0806) | Low risk due to the inclusion of many relevant mitigation methods (e.g., network segmentation) |
DS Use Case | ||
Supply Chain Compromise | Supply Chain Compromise (T1195) | High risk for some components due to high likelihood, impact, and lack of existing relevant mitigation measures |
Wrongdoing by Employees | Outside the scope of FMECA-ATT&CK which only considers adversarial threats. | N/A |
External Environmental Threats | ||
Gaining Access to the System | 20 techniques in the “Initial Access” Tactic (TA0001 and TA0108). | High risk for some components due to high likelihood, impact, and lack of existing relevant mitigation measures |
Ransomware | Data Encrypted for Impact (T1486) | Low risk due to low likelihood and existing relevant mitigation measures |
Malware Injection | Malicious File (T1204.002) | Low risk due to low impact and existing relevant mitigation measures |
Rouge Devices | Rogue Master (T0848) | Low risk due to low likelihood and existing relevant mitigation measures |
Bow-Tie Consequences | FMECA-ATT&CK Tactics | C | H | M | L |
---|---|---|---|---|---|
APS Use Case | |||||
Malicious actions with logged in user privileges | Initial Access | 0 | 0 | 7 | 313 |
Attackers with more information about the system | Discovery | 0 | 0 | 0 | 398 |
Loss of view and control of the ferry from RCC | Impact | 0 | 15 | 78 | 301 |
Attackers propagate and move freely within the network | Lateral movement | 0 | 3 | 18 | 239 |
Malicious control over compromised hosts | Command and Control | 0 | 54 | 206 | 208 |
An undesired system state or action is reached | Impair Process Control | 0 | 0 | 0 | 51 |
DS Use Case | |||||
Covert access to the system | Command and Control | 0 | 53 | 69 | 239 |
Gaining physical access to the system | Initial Access | 0 | 4 | 2 | 40 |
Losing trust of the system | Impact * | ||||
Credibility and societal trust | |||||
Human harm | |||||
Reputation damage | Impact | 0 | 6 | 21 | 263 |
Loss of revenue | |||||
Render system non-functional | |||||
Impair Process Control | 0 | 0 | 0 | 35 |
Bow-Tie Mitigations | FMECA-ATT&CK Mitigations | Already Included | Suggested for | |
---|---|---|---|---|
H | M | |||
APS Use Case | ||||
Audit the Remote Desktop Users group membership regularly. | Audit | Yes | 0 | 0 |
Remove unnecessary accounts and groups from Remote Desktop Users groups. | Use Account Management | Limited ** | 3 | 34 |
Secure remote access to internal PC’s and PLC’s | Access Management, Account Use Policies, Authorization Enforcement, Human User Authentication, Password Policies, Software Process and Device Authentication, User Account Management, Multi-factor Authentication | Partially * | 3 | 4 |
Secure portable media | Limit Hardware Installation, Antivirus/ Anti-malware, Behaviour Prevention on Endpoint, Execution Prevention, Exploit Protection | Limited ** | 3 | 90 |
Clean support computers | Antivirus/Anti-malware | Limited ** | 0 | 6 |
Regular patching, minimal applications, AV scan etc. for the jump server | Security Updates, Update Software, Use Recent OS Version, Vulnerability Scanning | Partially * | 0 | 8 |
Email Gateways | Not supported | |||
Redundancy of 4G/5G Service | Redundancy of Service | Yes | 0 | 0 |
Network Segmentation | Network Segmentation, Limit Access to Resource Over Network | Yes | 0 | 3 |
Strict Access Control and Management of Change (MoC) with proper Validation | Not supported | |||
Firewalls | Filter Network Traffic, Limit Access to Resource Over Network, Network Allow lists, SSL/TLS Inspection | Limited ** | 33 | 126 |
Intrusion Detection Systems | Behaviour Prevention on Endpoint, Network Intrusion Prevention | Very Limited | 48 | 195 |
Not Discussed | Data Backup | Very Limited | 3 | 27 |
DS Use Case | ||||
Following Standards and Routines | Not supported | No | ||
Asset Management | Not supported | No | ||
Security Testing | Deploy Compromised Device Detection Method, Vulnerability Scanning | No | 4 | 10 |
Redundancy and Resilience | Redundancy of Service | Partially * | 0 | 0 |
Access Control and Management | Access Management, Account Use Policies, Authorization Enforcement, Human User Authentication, Password Policies, Software Process and Device Authentication, User Account Management, Multi-factor Authentication, User Account Control | Partially * | 0 | 5 |
Segmentation | Network Segmentation, Limit Access to Resource Over Network | Yes | 0 | 14 |
Certification | Not supported | No | ||
Awareness, Competence, and Skills Building | User Guidance, User Training, Application Developer Guidance | Yes | 0 | 0 |
Business Continuity Plan (BCP) | Not supported | No | ||
Recovery Capability | Data Backup, Remote Data Storage | Yes | 0 | 1 |
Isolation Mode | Not supported | No | ||
Incident Response, Detection, and Logging | Audit, Behaviour Prevention on Endpoint, Deploy Compromised Device Detection Method, Exploit Protection, SSL/TLS Inspection, Network Intrusion Prevention | Very Limited | 59 | 75 |
Not Discussed | Filter Network Traffic | Partially * | 12 | 23 |
Update Software | Limited ** | 4 | 14 | |
Execution Prevention | No | 3 | 3 | |
Encrypt Sensitive Information | No | 1 | 4 |
Use Case Expert | APS | DS | Usability | ||||
1 | 2 | 3 | 4 | 5 | 6 | ||
Required decisions | 700 | 700 | 700 | 624 | 624 | 624 | |
Required decisions made | 677 | 608 | 692 | 608 | 538 | 623 | |
% of required decision made | 96.71% | 86.86% | 98.86% | 97.44% | 86.22% | 99.84% | 94.32% |
Disclaimer/Publisher’s Note: The statements, opinions and data contained in all publications are solely those of the individual author(s) and contributor(s) and not of MDPI and/or the editor(s). MDPI and/or the editor(s) disclaim responsibility for any injury to people or property resulting from any ideas, methods, instructions or products referred to in the content. |
© 2023 by the authors. Licensee MDPI, Basel, Switzerland. This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution (CC BY) license (https://creativecommons.org/licenses/by/4.0/).
Share and Cite
Amro, A.; Gkioulos, V. Evaluation of a Cyber Risk Assessment Approach for Cyber–Physical Systems: Maritime- and Energy-Use Cases. J. Mar. Sci. Eng. 2023, 11, 744. https://doi.org/10.3390/jmse11040744
Amro A, Gkioulos V. Evaluation of a Cyber Risk Assessment Approach for Cyber–Physical Systems: Maritime- and Energy-Use Cases. Journal of Marine Science and Engineering. 2023; 11(4):744. https://doi.org/10.3390/jmse11040744
Chicago/Turabian StyleAmro, Ahmed, and Vasileios Gkioulos. 2023. "Evaluation of a Cyber Risk Assessment Approach for Cyber–Physical Systems: Maritime- and Energy-Use Cases" Journal of Marine Science and Engineering 11, no. 4: 744. https://doi.org/10.3390/jmse11040744
APA StyleAmro, A., & Gkioulos, V. (2023). Evaluation of a Cyber Risk Assessment Approach for Cyber–Physical Systems: Maritime- and Energy-Use Cases. Journal of Marine Science and Engineering, 11(4), 744. https://doi.org/10.3390/jmse11040744