2018
DOI: 10.1016/j.icte.2017.12.007
|View full text |Cite
|
Sign up to set email alerts
|

Multi-stage crypto ransomware attacks: A new emerging cyber threat to critical infrastructure and industrial control systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
26
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
4
4
1

Relationship

0
9

Authors

Journals

citations
Cited by 65 publications
(26 citation statements)
references
References 4 publications
0
26
0
Order By: Relevance
“…To compensate for this, the DIVDS currently provides vulnerability evaluation for known security vulnerabilities that exist inside Docker images that are not provided in existing Docker environments. However, for the IVD module, there is a disadvantage that the DIVDS are based on Clair that performs static analysis, making it difficult to detect anomalies [12], [13] that may occur during a container execution. To secure the disadvantages of the current DIVDS, the application of dynamic analysis techniques to detect anomalies [4], [14]- [17] that may occur during container execution is necessary.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…To compensate for this, the DIVDS currently provides vulnerability evaluation for known security vulnerabilities that exist inside Docker images that are not provided in existing Docker environments. However, for the IVD module, there is a disadvantage that the DIVDS are based on Clair that performs static analysis, making it difficult to detect anomalies [12], [13] that may occur during a container execution. To secure the disadvantages of the current DIVDS, the application of dynamic analysis techniques to detect anomalies [4], [14]- [17] that may occur during container execution is necessary.…”
Section: Discussionmentioning
confidence: 99%
“…2) Upon receiving requests from the IVD module, the corresponding vulnerability reporting site provides vulnerable software package metadata to the IVD module 3) The client requests the Docker image from Docker image repository through 'docker pull image' command 4) Docker engine, which receives the 'docker pull' command through the Docker cli, requests for the Docker image download from Docker image repository 5) Docker image repository provides the requested Docker image by the client to the Docker engine 6) Client who downloads the Docker image from Docker image repository loads Docker image into the DIVDS to diagnose vulnerability in the Docker image 7) For the Docker image loaded from Step (6), the IVD module of the DIVDS extracts the software package metadata, OS metadata, and the metadata defined in Table 1 (image_metadata) installed in the Docker image 8) The IVD module detects vulnerable software package installed in the Docker image by comparing the vulnerable software package metadata (IVD_metadata) with the metadata of the Docker image extracted in Step (7) 9) The IVD module outputs the vulnerable software package information existing in the Docker image (O) through the comparison process performed in Step (8) 10) The IVD module loads the Docker image vulnerability information output (O) in Step (9) into the IVE module for Docker image vulnerability evaluation 11) The IVE module extracts and counts the number of CVE severities (severity_num), one of the values required for the Docker image vulnerability evaluation, from the Docker image vulnerability result (O) received from the IVD module in Step (10) 12) The IVE module calculates the Docker image vulnerability score (image score ) using the number of CVE severities (severity_num) extracted in Step (11) and the severity weight defined in Table 4 (severity_weight) 13) The IVE module compares the Docker image vulnerability score (image score ) calculated in Step (12) with the Docker image vulnerability threshold score (θ ) defined in the IVE module 14) The IVE module outputs the Docker image vulnerability evaluation result (K ), which is the result of comparison between the Docker image vulnerability score (image score ) and Docker image vulnerability threshold score (θ) performed in Step (13) 15) The IVE module provides the Docker image vulnerability evaluation result (K ) from…”
Section: Overview Of the Divdsmentioning
confidence: 99%
“…Some of the research works were interested in finding the network behavior of ransomware. Zimba et al [21] studied the emerging cyber threat to crucial infrastructure and magnify the network segmentation approach, prioritize the security of production network devices and limiting ransomware propagation. By applying reverse engineering on WannaCry ransomware and perform source code analysis they uncover the employed techniques to discover vulnerable nodes.…”
Section: Network Behaviormentioning
confidence: 99%
“…The attacker tries to characterize sensitive information about a set of individuals and monitors their transactions for a certain period of time. To address this situation, several privacy approaches have been proposed to decouple the users' pseudonymous identities from the specific transactions they make, thereby preventing attempts to link the transacting parties on the based of the data that appears in the blockchain [21,22].…”
Section: Related Workmentioning
confidence: 99%