2020
DOI: 10.1007/978-3-030-64330-0_7
|View full text |Cite
|
Sign up to set email alerts
|

Learning from Vulnerabilities - Categorising, Understanding and Detecting Weaknesses in Industrial Control Systems

Abstract: Where a licence is displayed above, please note the terms and conditions of the licence govern your use of this document.When citing, please reference the published version. Take down policyWhile the University of Birmingham exercises care and attention in making items available there are rare occasions when an item has been uploaded in error or has been deemed to be commercially or otherwise sensitive.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
7
0

Year Published

2021
2021
2024
2024

Publication Types

Select...
6
2
1

Relationship

0
9

Authors

Journals

citations
Cited by 12 publications
(7 citation statements)
references
References 7 publications
(8 reference statements)
0
7
0
Order By: Relevance
“…Throughout the paper, we assume the attacker can compromise one actuator and change its control action. The attacker can achieve this partial compromise by exploiting memory vulnerabilities or resource access control vulnerabilities (based on the ICS vulnerabilities categorization [61]). In this paper we focus on post-exploitation rather than on the specific method the attacker used to get access into the system.…”
Section: Adversary Modelmentioning
confidence: 99%
“…Throughout the paper, we assume the attacker can compromise one actuator and change its control action. The attacker can achieve this partial compromise by exploiting memory vulnerabilities or resource access control vulnerabilities (based on the ICS vulnerabilities categorization [61]). In this paper we focus on post-exploitation rather than on the specific method the attacker used to get access into the system.…”
Section: Adversary Modelmentioning
confidence: 99%
“…Input: pddl file template domain_temp and problem_temp connection object to a graph database hg; planning goals Output: constructed pddl domain and problem files (1) function GENERATE PDDL FILE (domain_temp, problem_temp, hg) (2) query device nodes, device reachability, vulnerability and component via hg (3) generate domain file: (4) generate predicates of vulnerability, reachability, pre and postconditions (5) generate actions of vulnerability from pre-and postconditions of vulnerability ( 6) end (7) generate problem file: (8) generate objects from device nodes (9) generate initially satisfied conditions (10) generate goals based on your input (11) end (12) return generated domain and problem files (13) end function ALGORITHM 2: Automatic construction of PDDL domain and problem files. experimental setup is introduced by a hypothetical network topology from IT to OT networks in Section 6.1. en, attack paths are illustrated, and the corresponding data is stored in the form of graph data in Section 6.2.…”
Section: Case Studymentioning
confidence: 99%
“…Apart from the cyberattacks migrated from IT networks, some inherent issues exist in the OTnetworks, such as design defects in industrial control network protocols [3] and vulnerabilities of proprietary devices [4]. On account of frequent interactions between IT devices and OT components, there are no clear boundaries between IT and OT partitions in the current industrial environment.…”
Section: Introductionmentioning
confidence: 99%
“…Others narrow their scope too far; for instance, [10] focuses on IoT devices, but specifically on communication protocols and hardware (no software). Similarly, [4] looks exclusively at industrial control system devices, and [3] examines IoT malware (i.e., malicious software that targets IoT devices). Existing surveys also frequently deal with privacy in addition to security, like [5] and [7].…”
Section: Introductionmentioning
confidence: 99%