Next Article in Journal
Addressing Challenges of Distance Learning in the Pandemic with Edge Intelligence Enabled Multicast and Caching Solution
Next Article in Special Issue
Systematic Review of Authentication and Authorization Advancements for the Internet of Things
Previous Article in Journal
Data-Driven Techniques for Low-Cost Sensor Selection and Calibration for the Use Case of Air Quality Monitoring
 
 
Font Type:
Arial Georgia Verdana
Font Size:
Aa Aa Aa
Line Spacing:
Column Width:
Background:
Review

Blockchain Based Solutions to Mitigate Distributed Denial of Service (DDoS) Attacks in the Internet of Things (IoT): A Survey

1
Department of Information Technology, Sydney International School of Technology and Commerce, Sydney, NSW 2000, Australia
2
College of Computer Engineering and Sciences, Prince Sattam Bin Abdulaziz University, Al-Kharj 11942, Saudi Arabia
3
School of Information Technology, Whitireia Community Polytechnic, Auckland 1010, New Zealand
4
School of Electrical Engineering and Computer Science (SEECS), National University of Sciences and Technology (NUST), Islamabad 44000, Pakistan
*
Author to whom correspondence should be addressed.
Sensors 2022, 22(3), 1094; https://doi.org/10.3390/s22031094
Submission received: 19 November 2021 / Revised: 26 January 2022 / Accepted: 27 January 2022 / Published: 31 January 2022
(This article belongs to the Special Issue On IoT Security, Privacy and Quality)

Abstract

:
Internet of Things (IoT) devices are widely used in many industries including smart cities, smart agriculture, smart medical, smart logistics, etc. However, Distributed Denial of Service (DDoS) attacks pose a serious threat to the security of IoT. Attackers can easily exploit the vulnerabilities of IoT devices and control them as part of botnets to launch DDoS attacks. This is because IoT devices are resource-constrained with limited memory and computing resources. As an emerging technology, Blockchain has the potential to solve the security issues in IoT. Therefore, it is important to analyse various Blockchain-based solutions to mitigate DDoS attacks in IoT. In this survey, a detailed survey of various Blockchain-based solutions to mitigate DDoS attacks in IoT is carried out. First, we discuss how the IoT networks are vulnerable to DDoS attacks, its impact over IoT networks and associated services, the use of Blockchain as a potential technology to address DDoS attacks, in addition to challenges of Blockchain implementation in IoT. We then discuss various existing Blockchain-based solutions to mitigate the DDoS attacks in the IoT environment. Then, we classify existing Blockchain-based solutions into four categories i.e., Distributed Architecture-based solutions, Access Management-based solutions, Traffic Control-based solutions and the Ethereum Platform-based solutions. All the solutions are critically evaluated in terms of their working principles, the DDoS defense mechanism (i.e., prevention, detection, reaction), strengths and weaknesses. Finally, we discuss future research directions that can be explored to design and develop better Blockchain-based solutions to mitigate DDoS attacks in IoT.

1. Introduction

With the rapid development of IoT technology, more and more fields have been involved in this industry, such as smart homes, smart cities, smart transportation, intelligent logistics management, etc. [1]. It is predicted that in 2030 the number of IoT devices used around the world will be close to 125 billion devices [2]. However, there are still issues present in some areas related to IoT including security, privacy, identity management, etc. [3]. Among security issues, Distributed Denial of Service (DDoS) attacks pose a serious threat [4]. Since most IoT devices are resource-constrained with limited memory and computing resources, security protection is lacking in these devices [5]. Attackers exploit the vulnerabilities present in IoT devices and control them as part of botnets to launch DDoS attacks. For example, in 2016, a well-known DDoS attack on DynDNS, a provider of a dynamic Domain Name System (DNS), forced many web services to stop, including Github and Twitter [6]. In addition, not only were the victims unable to provide services but the owners of IoT devices also spent a lot of money on the used bandwidth and power [7].
To detect and mitigate DDoS attacks in IoT, various solutions [8,9,10] have been proposed. In [8], an algorithm to detect and mitigate DDoS attacks on the Constrained Application Protocol (CoAP) is presented. In [9], an algorithm based on the framework of Software Defined Networking (SDN) in IoT is proposed, which uses the rate of grouped messages at the boundary to determine whether DDoS attacks have occurred. Similarly, a real-time DDoS attack detection based on the service information of the network time synchronisation is presented in [10]. However, all the mitigation and detection solutions presented in [8,9,10,11,12] are based on a centralised architecture, which presents a single point of failure. Blockchain is considered as a possible solution to secure IoT as it provides a distributed structure [5,7,13].
With a distributed structure, Blockchain is considered a possible solution and has an important role in mitigating DDoS attacks in IoT. The concept of the Blockchain originated from Bitcoin. It does not rely on a third party to store or verify data but through distributed nodes. Blockchain is a decentralised data structure that is composed of a sequence of blocks. Blockchain is used in many fields, including smart contracts, e-commerce, IoT, etc. [13]. With characteristics of decentralisation, anonymity, persistency and auditability [13,14,15], Blockchain technology has recently been used to prevent DDoS attacks in IoT.
Hence, it is important to carry out a holistic approach and conduct a comprehensive survey about DDoS mitigation in IoT using Blockchain technology. To the best of our knowledge, this is the first survey that discusses advancements in mitigating the DDoS attacks in IoT environments that use the Blockchain as the base technology. We note that there are few recent surveys e.g., [16,17,18,19] that broadly focus on DDoS mitigation using Blockchain with no specific focus on IoT domain. Therefore, in this work, we carry out a detailed survey of various Blockchain-based solutions proposed in the current literature to mitigate the DDoS attacks in IoT. We classify the various Blockchain-based solutions into four categories i.e., Distributed Architecture-based solutions, Access Management based solutions, Traffic Control based solutions and Ethereum Platform based solutions. We discuss working details of all the four types of solutions and then critically evaluate each of them by discussing their strengths and weaknesses. Future research directions are also discussed that outline promising investigation areas. We note that few surveys [20,21,22] have been carried out which discuss how Blockchain can improve security in IoT. However, to the best of our knowledge, no survey in the existing literature classifies and critically evaluates various Blockchain based solutions to mitigate the DDoS attacks in IoT.
The main contributions of this study are: (1) To classify various Blockchain-based solutions presented in the current literature to mitigate DDoS attacks in IoT. (2) To discuss the working principles of Blockchain-based solutions proposed in the existing literature for mitigating DDoS attacks in IoT. (3) To critically analyse the various categories of Blockchain based solutions that mitigate DDoS attacks in the IoT. (4) To propose future research directions that can be explored further to design and develop new Blockchain-based solutions for mitigating DDoS attacks in the IoT.
The rest of this paper is organised as follows: In Section 2, background information related to DDoS attacks and Blockchain is provided. In Section 3 and Section 4, respectively, the literature review of various related surveys and the literature review methodology are presented. In Section 5, four types of Blockchain-based solutions are discussed and critically evaluated. Future research directions are proposed in Section 6. Finally, the paper is concluded in Section 7.

2. Background

In this section, the background information related to DDoS attacks and Blockchain is discussed.

2.1. Distributed Denial-of-Service (DDoS) Attacks

DDoS attacks aim to consume bandwidth or resources and prevent legitimate users from reaching the services [21,23,24]. Various researchers [21,24] discussed DDoS attacks on the three layers of the IoT architecture. For the perception layer, there are jamming, kill command attacks and de-synchronising attacks to avoid reading data from RFID [21]. In the network layer, the Layer-3 attacks aim to exhaust the victim’s resources with different methods, such as flooding attacks, reflection-based flooding attacks, protocol exploitation flooding attacks and amplification-based flooding attacks [24]. The application-level DDoS attacks (Layer-7 attack) are considered more complicated than layer-3 attacks and are harder to be detected by filters. Applications with the potential to be attacked include DNS, HyperText Transfer Protocol (HTTP), Voice over Internet Protocol (VoIP), etc. [21].
The increasing popularity and the ubiquity of IoT, since they are constantly connected to the Internet with negligible security configurations, have made these networks a platform which is strongly exposed to cyberattacks. As a result, these networks have become the new weakest link in the security chain of modern computer networks. Hence, due to their distributed nature, pervasiveness and immense vulnerability, the IoT devices have attracted many bad actors, in particular, those organising for massive DDoS attacks. A DDoS attack scenario within the IoT networks is shown in Figure 1. Such a monstrous attack was done against the KrebsOnSecurity (In-depth security news and investigation: https://krebsonsecurity.com/ accessed on 18 November 2021) in 2016 [25] that knocked out the site for four days and was executed through a network of hacked IoT devices, such as security cameras, video recorders, etc., hit with 620 Gbps of traffic (KrebsOnSecurity Hit With Record DDoS: https://krebsonsecurity.com/2016/09/krebsonsecurity-hit-with-record-ddos/ accessed on 18 November 2021). An even bigger DDoS attack at about the same time was executed using Mirai malware that reached 1.1 Tbps through a collection of hacked Internet-connected cameras and digital video recorders [26].
Although there are slight differences for various strategies that mitigate DDoS attacks, the general defense mechanism contains three parts—prevention, detection and reaction (which is a response to mitigate the attack) [4]. In prevention technologies, filters are commonly used to stop malicious packets. Detection technologies are used to identify attacks and response technologies are used to stop DDoS attacks when they are detected [24].

2.2. Blockchain

Blockchain is based on a distributed ledger of transactions (i.e., the communication that takes place between two nodes), composed of a sequence of blocks [27], shared across the participating entities, and provides auditable transactions [28], where the transactions are verified using cryptographic proof [20] by participating entities within the operating network. Blockchain was first proposed by Satoshi Nakamoto, which is also the underlying technology behind Bitcoin [29]. Blockchain has been shown to possess a number of salient features i.e., security, immutability, and hence, could be a useful technology to address various challenges posed by the conventional security systems [30], such as centralised systems with bottleneck and a single point of failure, lack of privacy [31], etc. Contrary to the central trust broker, e.g., Certificate Authority (CA), a node verifies the transactions by validating the signature of the transaction generator against their Public Key (PK), which achieves a trustless consensus [32]. In addition, the Smart Contracts provide a secure and reliable capability to record and manage interactions for the participating devices [13]. We note that enormous smart-contract-based platforms are emerging that could achieve enhanced functionalities and be used in many application areas, such as IoT [33] and banking services [34]. The Blockchain structure is shown in Figure 2a.
The architecture of a Blockchain is shown in Figure 2b. Each block contains a block header, which includes the timestamp when the current block gets created, nonce, and Merkle root, the Hash value of the previous block (parent block); the first block is called the Genesis block as it has no parent block. Merkle tree, presented on the right side of Figure 2b, is the Hash values of all transactions in a specific block and provides efficient and secure verification of transactions. To form a block, a node periodically collects multiple transactions from the pool of pending transactions, appends it to the local copy of the Blockchain after validating using its PK, and broadcasts to the network [35]; this process is called Mining (Bitcoin mining the hard way: the algorithms, protocols and bytes: https://www.righto.com/2014/02/bitcoin-mining-hard-way-algorithms.html accessed on 18 November 2021). Each node in the participating network uses a Consensus algorithm [36], such as Proof of Work (PoW) [37] and Proof of Stake (PoS) [38] that involves solving a hard-to-solve and easy-to-verify puzzle, to control the participation of nodes within the Blockchain.
There are few comprehensive systematic analysis that examine, compare and contrast on the consensus algorithms [39,40,41,42,43]. The existing Blockchain consensus algorithms can be divided into Byzantine Agreement algorithms (e.g., PBFT [44] ePBFT [45] HoneyBadgerBFT [46]) and Proof-of-X (PoX) (e.g., PoW [37] PoS [38] and Delegated-proof-of-stake (DPoS) [47]). The PoW is computationally expensive [48]; however, there are other algorithms that do not incentivise extreme amounts of energy consumption, e.g., the PoS [38], Proof of Elapsed Time (PoET) [49], Proof of Luck (PoL) [50] and Proof of Space (PoSp) [51], Delegated Proof of Stake (DPoS) [52]. The Byzantine Fault Tolerance (BFT) is used to reach consensus in order to respond with correct information when some of the nodes fail to respond or malicious users trying to propagate false information to their peers. The BFT is implemented in various Blockchains, including Ripple (https://ripple.com/ accessed on 18 November 2021), Hyperledger Fabric (https://www.hyperledger.org/use/fabric accessed on 18 November 2021) and Zilliqa (https://www.zilliqa.com/ accessed on 18 November 2021).
An important feature of Blockchain is the signing and verification process of the transactions that are carried out using Digital Signature, which is used to identify users with (owning) a pair of Public and Private Keys. When a user A wants to sign a transaction (e.g., transaction data in the form of sending crypto BTC), she first generates a Hash value derived from a transaction; then, she signs (i.e., encrypts) this Hash value using her Private Key and sends it to user B along with original transaction data. User B verifies this transaction by comparing the decrypted Hash (while using A’s Public Key) and the Hash value derived from the received data using the same Hash function as A’s; an example scenario is shown in Figure 3. The Elliptic Curve Digital Signature Algorithm (ECDSA) is a representative algorithm that is used in the Blockchain [53].

2.3. Internet of Things (IoT)

The IoT has become an important part of our daily lives, and it has received immense attention from the research, academia and industry due to its growing need for IoT devices in everyday life [54,55,56,57,58,59]. The IoT combines hardware and software components together [60] as defined by the International Telecommunication Union (ITU) that can concurrently operate various services implemented over TCP/IP and non-TCP/IP protocols [61] according to the definition provided by the Internet Engineering Task Force (IETF). IoT has many applications and deployment scenarios, such as Industrial Internet of Things (IIoT), Internet of Anything (IoA), Internet of Everything (IoE), Social Internet of Things (SIoT), Web of Things (WoT), and Internet of Medical Things (IoMT).
The increased number of connected devices poses several challenges e.g., to effectively handle the enormous amounts of data [62,63], interoperability among various hardware and software platforms [64,65], challenges related to Big data management, privacy and provenance [66], mobility management and handover [67,68,69], and privacy and security challenges [70,71]. We note that there are various efforts from the research community in order to improve the performance and scalability of the IoT netwroks e.g., the use of edge computing to perform resource-intensive tasks [72,73,74], the use of SDN for flexible management and programmability [75,76] including flexible network programmability [77,78] that introduced a new combination of Software-Defined Internet of Things (SDIoT) architecture for an effective management [78,79,80,81,82]; similarly, the Software-Defined Internet of Things and Edge (SDIoT-Edge) frameworks [83,84] were suggested for increased scalability and interoperability [82].

2.4. Integration of Blockchain and IoT

The Internet of Things (IoT) refers to the interconnection of smart devices that collect and disseminate data and can be used for making intelligent decisions, which is bringing the capabilities of converting the physical world into a huge information system. The Statista (https://www.statista.com/statistics/802690/worldwide-connected-devices-by-access-technology/ accessed on 18 November 2021) forecast suggests that, by 2030, around 50 billion devices will be in use around the globe. This technology is essentially causing the growth of the ICTs that incorporates various technologies e.g., cloud computing, information modeling, including the Blockchain. An important aspect of IoT in enabling the development of new services in ICT is the data enhancement; however, the lack of security measures makes the IoT vulnerable to security threats [85], such as Distributed Denial-of-Service (DDoS) to exploit the distributed nature of IoT devices [86]. The centralised configuration of IoT networks is a single point of failure, which must be dealt with [87], causing threats to confidentiality and authentication [88]. We note that the Blockchain has various “by-design” potentials that can help with solving major security and privacy issues in IoT by its various capabilities i.e., transparency, immutability, auditability, etc.
In addition, the data aggregated from several sensor nodes are used to make timely decisions e.g., healthcare or other emergency services, which raises the ‘problem of data integrity’. Hence, it is important to protect the data during data collection and dissemination from possible false data injection attacks [87]. Similarly, the correct data availability is another major issue [85] for real-time applications e.g., smart grid, where smart devices’ downtime can result in the loss of real-time system monitoring. Another problem with IoT is ‘non-repudiation’ i.e., the trust among the participating entities in IoT [89] including the central authority; hence, it needs a publicly verifiable audit without the presence of any trusted third party.

2.5. Benefits and Challenges of Using Blockchain in IoT

The characteristics of Blockchain include decentralisation, anonymity, persistency and auditability [90]. Recall that these unique features of Blockchain provide a promising solution to the security problems of IoT. It improves the IoT systems in terms of decentralisation, resilience, security and identity management. The current implementation of IoT is composed of a decentralised architecture [91] that poses several challenges such as interoperability, scalability and adaptability surrounding IoT. The Blockchain, hence, can provide a secure platform for IoT networks, thus eliminating decentralised traffic flows and single point of failure. The majority of the participants within the Blockchain must verify the transactions in order to approve them and further add them to the distributed public ledger, which provides publicity and transparency. In addition, there is no single authority for transactions approval or to set specific rules communication or services access for the participants. Hence, there is an improved and huge trust since the majority of the participating IoT network devices must reach an agreement in order to validate transactions.
Despite the benefits of the combination of IoT and Blockchain, there are many challenges, such as scalability, security, algorithms specific for IoT environments, etc. [92]. Since security is the primary concern of this article, the challenges of security are addressed here. Although Blockchain can improve the security of the IoT environment, such as data storage, transaction processing and communication [93], data reliability is still one of the challenges when Blockchain is combined with IoT. Data storage in a Blockchain is permanent. When data of IoT devices are corrupted before they reach the Blockchain, storing such data can cause serious problems in the Blockchain [5]. In addition, IoT devices are likely to be hacked, bugged and controlled by attackers, in addition to the increasing number of attacks against the IoT, Blockchain is itself vulnerable to attacks, such as DDoS attacks, 51% attacks, the Sybil attacks, etc. [14].

3. Literature Review

The combination of Blockchain and IoT has attracted a lot of attention and recently many surveys and review articles are published in this area. Some of the surveys [14,92,94] discussed these two technologies in terms of the importance of usage of Blockchain for the security of IoT, challenges and future directions of applying Blockchain in IoT. However, these surveys [14,92,94] did not discuss how Blockchain can be used to detect and mitigate DDoS attacks in IoT. In the surveys conducted by [95,96], the authors reviewed and compared several case studies that utilise Blockchain in IoT to provide security and privacy in different scenarios, such as access control, economic scenarios, smart homes, etc. However, authors in [95,96] did not provide any discussion on mitigating DDoS attacks in IoT. Some researchers analysed the requirements of deploying Blockchain in IoT [5,90,97] and explained how Blockchain is used in IoT but without consideration of DDoS attacks.
The history of DDoS attacks can be traced back to 1998 [4] and, therefore, there is a lot of literature [4,98,99,100] that reviews types of DDoS attacks and various defense mechanisms. However, these surveys are only for traditional networks and do not discuss IoT-based networks. For surveys in the IoT environment, Refs. [15,101] discussed DDoS attacks in three layers of the IoT architecture. However, they did not explain and critically analyse different solutions for mitigating DDoS attacks in IoT. Some researchers [102,103] reviewed the effects of DDoS attacks on IoT, prevention mechanisms and solutions to mitigate DDoS attacks in IoT. In [102], the focus of authors is on the DDoS attacks at the network layer; however, Ref. [103] discussed technologies on an IoT protocol stack to mitigate DDoS attacks, such as IPv6, IEEE 802.15.4, 6LoWPAN, etc. However, Refs. [102,103] did not mention Blockchain-based solutions that mitigate DDoS attacks. Table 1 summarises the results of our literature review.
Our literature review shows that there is no study available in the existing literature that has carried out a survey to analyse the Blockchain-based solutions to mitigate DDoS attacks in IoT. This paper aims to fill in this research gap by categorising and critically evaluating various Blockchain-based solutions to mitigate DDoS attacks in IoT. Another novelty of our work is to propose future work directions that can be explored by other researchers to propose better Blockchain solutions to mitigate DDoS attacks in IoT.

4. Research Methodology

The strategy of selecting articles for this study includes search keywords, mentioned databases and the paper selection criteria, which resulted in this survey. Specifically, the keywords such as Internet of Things, IoT, DDoS and Blockchain were utilized to search for the articles from journals and conferences. To summarise, in order to qualify based on our search criteria, a selected article must satisfy the following conditions: (1). the published work must be within the IoT domain, (2). the IoT domain may be generic or application specific (e.g., IIoT), (3). the considered scenario must be of DDoS, IoT and Blockchain, thus excluding all papers that do not either address DDoS attack scenarios or do not use Blockchain as the underlying technology, (4). it must have been published (inclusive) between 2016 and 2021, (5). exclude the review papers written in languages other than English, and (6). the resultant paper should be a Conference or Journal, hence, Books, Newspapers, Dissertations, etc., were excluded.
The research questions that helped provide a systematic and comprehensive survey to analyse the Blockchain-based solutions to mitigate DDoS attacks in the IoT domain are as follows:
  • How the attackers exploit IoT networks as a botnet to launch DDoS attacks to target legitimate users, in addition to the severity of the DDoS attacks in IoT domains;
  • How the Blockchain may be a candidate technology to mitigate the DDoS attacks;
  • What are the current proposals of Blockchain-based solutions used to mitigate the DDoS attacks in the IoT domain, specifically, their working principles, and the DDoS defense mechanism (i.e., prevention, detection, reaction)?
  • What are the strengths and weaknesses of the current solutions and the major challenges for designing and implementing comprehensive architectures for implementing Blockchain-based solutions to mitigate DDoS attacks in IoT networks?
  • What are the open research areas and challenges for proposing secure Blockchain-based IoT networks (and to suggest the use of other supporting technologies) to mitigate DDoS attacks?
Note that the majority of the search facility of the publishers and databases looks for the combination of keywords e.g., “IoT DDoS Blockchain” in either paper’s title or abstract or the contents, etc. The ACM, instead, provides an advanced search where the keywords can be specifically found in metadata or other parts of a research article including the paper’s title, publication title, paper’s contents, etc., either with ‘AND’ or ‘OR’ operations, to limit or widen the search result. We used various keyword combinations to find the most relevant papers, e.g., “IoT DDoS Blockchain”, “IoT DDoS Mitigation Blockchain” and “IoT DDoS Mitigate Blockchain” that resulted in different number of papers, i.e., with IEEE Xplore, respectively 65, 5, 2. We note that the last two keyword combinations would reduce the number of our search results; hence, we continued our search with the “IoT DDoS Blockchain” keyword combinations to find relevant research articles.
We mainly look for the relevant papers published with various databases i.e., IEEE Xplore, Elsevier, Springer, ScienceDirect and ProQuest based on our criteria. Furthermore, we search for relevant research articles in Google Scholar so as to find articles published with publishers, e.g., MDPI, other than our focused database (we interchangeably use the terms ‘publisher’ and ‘database’). Our search results found 3983 resources that include Conference papers, Journals, Books, Early Access Articles, Magazines, Webpages, Connect, Survey Articles, Discussions, Editorials, Dissertations & Thesis, Newsletter and Reports. Among the search results, we note that there were 1117 Journals and Conference papers and 2866 were other resources e.g., Newsletter, Reports, etc. that were excluded from our repository in the first phase. As an example, based on our search criteria, the IEEE Xplore (https://ieeexplore.ieee.org/Xplore/home.jsp accessed on 18 November 2021) resulted in 65 resources; among them, 32 were Conference papers and seven were Journal articles. The search results from various databases are given in Table 2.
In the second phase, we downloaded the metadata of the searched articles and stored them in our repository in BibTex format that includes, author list, title, abstract, keywords, etc. We thoroughly read the relevant metadata i.e., title, abstract and keywords list and stored the (expected list of) relevant papers to be considered in our survey. Finally, to the best of our knowledge and efforts, we found 34 papers that were classified into various Blockchain-based solutions for mitigating DDoS attacks in the IoT domain, 12 survey papers for a comparison with our work, and the remaining 103 were supporting articles that provide generic Blockchain-based solutions for securing IoT networks or contain other supporting materials. Finally, out of 1117 papers, the 1117 − 149 (Total references in this survey are 153, which includes four web-references) = 968 research articles were excluded from our repository that were not classified as Blockchain-based solutions based on our classification. We note that the search facility of the publishers and databases looks for the combination of keywords “IoT DDoS Blockchain” in either paper’s title or abstract or the contents e.g., in ‘Introduction’ section that may discuss about DDoS security attacks in general or the DDoS discussed in the ‘Future Works’ within the paper. Furthermore, we note that there was no duplication of the research articles among individual publishers, since a particular article is published with only one publisher. However, the duplication occurred when we searched for papers in ProQuest or Google Scholar, which we compared with our repository for duplication, deleted them, and then merged them within the repository.

5. Blockchain Based Solutions to Mitigate DDoS Attacks in IoT

In this section, the working principles of various Blockchain-based solutions to mitigate DDoS attacks in IoT are discussed. An important feature of our work is to critically evaluate these solutions and highlight the issues in them. We divide the various Blockchain-based solutions discussed in the current literature into four broad categories, which are: Distributed Architecture-based solutions, Access Management based solutions, Traffic Control based solutions and Ethereum Platform based solutions. This classification is shown in Figure 4.

5.1. Distributed Architecture Based Solutions

The distributed architecture-based solutions are proposed in [104,105,106], and they use Blockchain as redundancy data storage, where all the nodes share the ledger with the transactions. These methods take advantage of the distributed structure of Blockchain to mitigate DDoS attacks. This is because it is difficult for an attacker to flood all nodes at once to prevent the system from providing services. Even if some nodes are corrupted, the entire system can continuously provide services [104,105,106].

Strengths and Weaknesses of Distributed Architecture Based Solutions

This type of solution utilises the natural feature of Blockchain to prevent DDoS attacks. It uses asymmetric cryptography for identity authentication of IoT devices. However, these solutions [104,105,106] rely solely on the distributed structure of the Blockchain to prevent DDoS attacks. When a DDoS attack occurs, although the whole system can continue to run, the attacked node would be affected. This may further degrade the performance of the whole system. This is because the average latency of processing each transaction increases as the number of transactions processed by each node increases. If the system runs normally under a DDoS attack, the non-working nodes will cause the working nodes to deal with more tasks, which will further reduce the performance of the whole system. This type of solution only prevents DDoS attacks; however, once a hacker takes advantage of the vulnerability of IoT devices to send malicious requests, these systems cannot detect and react to mitigate the attack. The working principle, weaknesses and strengths of these solutions are summarised in Table 3.

5.2. Access Management Based Solutions

Solutions in this category take advantage of the fact that DDoS attacks can be mitigated by preventing malicious access. These solutions prevent malicious attackers from accessing the system and allow legitimate users to use the system. Therefore, attackers cannot access the IoT devices to launch DDoS attacks. We divide these solutions into two categories i.e., Public Key based Access Management (PKAM) and Physically Unclonable Function based Access Management (PUF). These two categories are discussed below:

5.2.1. Public Key Based Access Management (PKAM)

PKAM is proposed in [107,108] to prevent DoS attacks in IoT. When a management node receives a transaction request, it determines whether to process or forward the transaction by validating the requester’s public key. If the requester’s public key is not registered or unavailable, the request is forwarded to another management node. Once the request is not accepted by many management nodes after several attempts, the request will be blocked. The public key will be blocked if it sends multiple unsuccessful access requests. Therefore, PKAM mitigates DDoS attacks by verifying access rights and preventing network traffic caused by fraudulent transactions. In addition, to avoid DDoS attacks, the authors in [109] design a Blocikchain-based access control system for IoT devices based on identity-based signature to enable servers to filter and forward access requests.
The strength of this approach is that it is considered IoT access management. In addition, it is a relatively lightweight solution that is suitable for resource-limited IoT devices. Moreover, this method can be used in any IoT industry to control access and protect data security. However, the weaknesses of this approach are (1) if adversaries exploit multiple public keys, they can generate a significant burden on the system, as requests are constantly forwarded and confirmed. This means that the scheme cannot mitigate DDoS attacks in such a scenario. (2) If an attacker can control a device that has been authenticated and make it send malicious requests repeatedly, there is no working mechanism to detect or stop this unwanted traffic.

5.2.2. PUF Based Access Management (PUFAM)

PUFAM provides a unique identity for every IoT device [7,110]. Once a device is registered in the system, the device owner can verify its authenticity anywhere and at anytime. All tampered, fake and cloned devices will be detected, which can prevent devices from becoming part of a botnet [7,110]. In addition, because all the IoT devices are authenticated by Blockchain, the edge network is considered trustworthy and verified. Therefore, the system limits unauthorised access and thus prevents DDoS attacks. Experiments are conducted in [110] to test the system performance under different transaction rates. The results showed that using Blockchain leads to a decrease in performance, such as throughput, latency and CPU usage. The cost increased as the transaction rate is increased. The strength of this PUFAM is that it provides a lightweight access management solution to prevent potential botnet threats. It uses PUF technology to verify the authenticity of the IoT devices. The Blockchain is used to protect data and verify the identity of devices, so as to protect the security and privacy of user data. The weaknesses in this type of solutions is that, once an attacker gets access to the system, there is no mechanism to detect or react to mitigate DDoS attacks.

5.2.3. Strengths and Weaknesses of Access Management Based Solutions

Access management based solutions focus solely on authentication of IoT devices. Their strength is that these solutions considered IoT access management with a relatively lightweight solution. Although to some extent, these solutions can prevent DDoS attacks, there is no comprehensive mechanism to provide defense against DDoS attacks e.g., monitoring transactions or traffic to detect DDoS attacks and then preventing them. Once an attacker finds a way to bypass authentication and launch a DDoS attack, the system has no working mechanism to respond and stop the attack. The working principles, weaknesses and strengths of these solutions are summarised in Table 4.

5.3. Traffic Control Based Solutions

The basic working principle of this type of solution is that they utilise traffic control to mitigate DDoS attacks. These solutions monitor transactions to analyse and detect malicious traffic. According to the detection results, the system responds to DDoS attacks with corresponding measures. We divide these solutions into four subtypes i.e., Software Defined Networing based Traffic Control via Blockchain (SDNTCB), Traffic Control based on the Maximum Rate of Transactions (TCMRT), Traffic Control based on Verification of Transactions (TCVT) and Traffic Control based on Whitelisting Mechanism (TCWM). The working principles, strengths and weaknesses of these solutions are explained below:

5.3.1. Software Defined Networking (SDN) Based Traffic Control via Blockchain (SDNTCB)

Recall that the SDN, composed of different layers e.g., the infrastructure layer, control layer and application layer, hence, it may be targeted with DDoS attacks aiming at three different kinds of DDoS attacks i.e., DDoS attacks against the infrastructure, control and application layers [111]. The authors in [112] proposed a blockchain-based decentralised security architecture for IoT networks that consider different SDN controllers as fog nodes. The fog nodes act as processing nodes that detect attacks and where the attack detection model is dynamically updated at the fog nodes. Furthermore, a central cloud server is introduced that manages the attack model from a set of fog nodes. The performance measures, evaluated as of accuracy, detection rate and F-score, show good accuracy with effective DDoS detection.
The key idea of solutions in this category is to utilise SDN based traffic control via Blockchain to mitigate DDoS attacks [113,114,115,116,117,118]. In order to resist DDoS attacks, these solutions combine the SDN and Blockchain to take advantages of both technologies. All SDN controllers in the IoT network are interconnected by the distributed Blockchain network, which enables each IoT device to communicate conveniently and efficiently [113]. With Blockchain technology, security policies and flow rules can be enforced and updated [115]. SDN enabled switches provide dynamic flow management of traffic, which assists in the detection of DDoS attacks [115]. Therefore, solutions under this classification are able to track suspicious traffic and detect DDoS attacks, and thus respond to DDoS attacks [112,113,114,115,116,117,118].
The [113,115] have experimented with preventing DDoS attacks. [113] launched several types of DDoS attacks including TCP/SYN flood, UDP flood and ICMP flood with Stacheldraht tool (which is used to generate traffic). However, Ref. [113] did not give specific experimental results but stated that their solution could accurately detect whether devices are in a botnet through the flow rules on the switches.
Authors in [115] conducted a large-scale experiment with 6000 nodes, which includes three aspects i.e., bandwidth usage, accuracy and CPU utilisation. UDP flooding attack was launched on the SDN switches with different attack rates. The bandwidth of users was analysed, and results show that the bandwidth remained basically unchanged with and without DDoS attacks. As a result, the solution reduced the impact of DDoS attacks without too much resource consumption. In addition, the accuracy of DDoS attacks detection was tested. The results showed that the system can quickly identify DDoS attacks [115]. In addition, the mitigation performance of DDoS attacks is evaluated. The results showed that the proposed solution prevents DDoS attacks in 5 to 7 s and the bandwidth is restored. [114] uses SDN controllers to monitor traffic to add IP addresses into blacklists and whitelists. Similarly, Ref. [116] integrates Blockchain with SDN to manage IoT services.
The strength of these solutions [112,113,114,115,116,117,118] is that they use comprehensive architecture to prevent, detect and mitigate DDoS attacks. The weakness of these solutions [112,113,114,115,116] is that the use of SDN will require additional processing and calculation on controllers, which will lead to a certain delay. However, all these solutions did not calculate that delay. In addition, traffic monitoring follows certain flow rules, and it is possible that unwanted traffic can comply with the established rules but carry out malicious behavior [119]. Moreover, SDN infrastructure is itself vulnerable to many attacks [119] which are not considered by authors in [112,113,114,115,116].

5.3.2. Traffic Control Based on the Maximum Rate of Transactions (TCMRT)

The solutions in this category are characterised by setting a maximum transaction rate to control traffic to mitigate DDoS attacks [120,121]. Nodes in these solutions [120,121] have a threshold for the maximum transaction rate. If the threshold is exceeded, the node manager updates to prevent the node from continuously sending transactions to the target nodes, which can stop DDoS attacks. The strength is that limiting the number of transactions by a threshold can mitigate the impact of a DDoS attack. The weaknesses are that legitimate traffic from users may not get a response in time under an attack. In addition, the dynamic threshold adjustment needs to be realised through network communication. When nodes are active frequently, the whole communication medium will be flooded rapidly. Moreover, the local Blockchain in the system presented by [120] is not distributed, but centralised, which is contrary to Blockchain’s decentralised principle. It will limit its ability and availability [122].

5.3.3. Traffic Control Based on the Verification of Transactions (TCVT)

The solution [123] in this category prevents the nodes from becoming part of a botnet to launch DDoS attacks by validating outgoing transactions. Firstly, the Blockchain will determine whether the device is normal or malicious. Secondly, all outgoing transactions need to be verified through smart contracts. Transactions or traffic that do not conform to the security policy in the smart contract will be rejected. When an adversary gains access and wants to infect the victims, the illegal transactions cannot be sent out and thus the victim will not be attacked [123].
The advantage of this category is that it uses Blockchain without many additional resources. The weakness is that there is no mechanism to protect smart contracts since the solution relies on smart contracts to verify transactions.

5.3.4. Traffic Control Based on the Whitelisting Mechanism (TCWM)

A whitelisting mechanism is used in [124,125,126,127] to prevent DDoS attacks by filtering and eliminating malicious traffic. The whitelisting mechanism controls traffic from data sources, including Internet Protocol (IP) addresses, nodes and users. The whitelisting mechanism usually combines the whitelist and blacklist together to classify users as trusted and untrusted users. There are two types of methods to identify the whitelist—using a tracking manager [124,125] and Machine Learning technology [126,127]. While Refs. [124,125] used tracking managers to identify and record IP addresses in the whitelist, Refs. [126,127] utilised data mining methods to analyse and filter malicious traffic, such as community detection analysis on the mutual contacts graph, neural and mesh networks.
By using this mechanism, it is very quick to verify the access traffic and filter the unwanted traffic. However, these solutions did not consider authentication of IoT devices or how to manage resource limited devices. In addition, similar to flow rules, it is possible that illegal traffic can comply with whitelist validation rules but is actually harmful to the system.

5.3.5. Strengths and Weaknesses of Traffic Control Based Solutions

The strengths of traffic control-based solutions are that they can monitor traffic before or during the processing of each transaction. In addition, experiments are carried out in three solutions in the SDNTCB [113,115] to gauge the feasibility of these solutions to detect and mitigate DDoS attacks. However, all traffic control based solutions did not conduct experiments. Another weakness of the solutions in this category is that monitoring traffic needs additional calculation and processing. For example, solutions in SDNTCB need to calculate delay caused by SDN controllers; Refs. [126,127] in TCWM are required to calculate the likelihood of malicious users based on traffic by using data mining techniques. These additional calculations and processing might lead to a decrease in system performance, such as high latency, increased CPU utilisation, etc. Table 5 summarises the weaknesses and strengths of the solutions in this category.

5.4. The Ethereum Platform Based Solutions

The Ethereum platform based solutions take advantage of the mechanism of Ethereum platform to prevent DDoS attacks. This is because each transaction must be paid, which effectively prevents attackers from making too many service requests [128]. The Ethereum Blockchain is a public Blockchain platform that provides an opportunity for developers to write code flexibly on the Blockchain to execute. It uses the concept of “gas” which refers to the fee of conducting transactions or executing smart contracts. Gas is used to allocate resources of the Ethereum virtual machine. If the user does not pay enough gas, the contract will not be fully implemented, and all changes will be rolled back [129]. These types of solutions are further divided into three categories i.e., Solutions Simply based on the Ethereum Platform (SSEP), Solutions based on the Ethereum Platform with Traffic Control (SEPTC) and Solutions based on the Ethereum Platform with Authorization (SEPA). The working principles, strengths and weaknesses of these solutions are explained below:

5.4.1. Solutions Simply Based on the Ethereum Platform (SSEP)

This type of solutions [128,129,130,131,132] uses inherent features of Ethereum platform to prevent DDoS attacks. These solutions [128,129,130,131,132] mentioned that the system is robust to DDoS attacks with the Ethereum platform. This is because the distributed architecture is used and the payment for transactions effectively prevents DDoS attacks by avoiding too many service requests in the Ethereum Blockchain.
The weaknesses of this type of solutions are that these solutions are in the initial stage, and the Ethereum platform is used to quickly implement the proposed solutions. The authors in [128,129,130,131,132] did not evaluate performance and the capability of the solutions against DDoS attacks. In addition, these solutions just simply rely on the Ethereum platform without any extra working mechanism for detecting and mitigating DDoS attacks. Even without an attack, the performance of the systems under the Ethereum platform is worrying. This is because only by submitting normal transactions is it possible to cause a service disruption on the Ethereum platform. Furthermore, these solutions only prevent attacks in Ethereum based Blockchains. They cannot be readily used in other Blockchain-based platforms like Bitcoin, Ripple, etc.

5.4.2. Solutions Based on the Ethereum Platform with Traffic Control (SEPTC)

In addition to the Ethereum platform, the solutions presented in [133,134,135] also pay attention to traffic control to mitigate DDoS attacks. Similar to the category of traffic control-based solutions (i.e., Section 5.3), in this classification, two types of strategies are used, which are the maximum rate of transactions [133] and whitelisting mechanism [134,135].
The solution proposed by [133] uses the maximum rate of transactions to prevent DDoS attacks. They take advantage of the gas limit attribute of the Ethereum to ensure that no more resources will be consumed if the gas consumption reaches the value of the threshold [133]. This mechanism has two benefits for preventing DDoS attacks. Firstly, because of the gas limitation, the server’s bandwidth can be protected from exhaustion even if all devices send data at the same time. Secondly, the malicious device itself needs to consume gas first to launch a DDoS attack. Once the limit is reached, the malicious traffic will be automatically terminated [133].
Solutions presented by [134,135] are based on the Ethereum platform and the whitelisting mechanism to mitigate DDoS attacks. Interestingly, Ref. [134] runs this system for more than 500 days with a large number of IoT devices and tested the effectiveness of mitigating DDoS attacks. The result of the experiment revealed that the latency under a DDoS attack is the same as that of normal traffic. In addition, CPU utilisation is only slightly more than normal circumstances. However, users used more bandwidth under the DDoS attack. It is noticed that Ref. [134] not only prevents DDoS attacks by applying whitelisting mechanism but also checks TLS handshakes to prevent layer 3 DDoS attacks.
Solutions in this category take advantage of the Ethereum platform and traffic control to mitigate DDoS attacks. However, combining both technologies also inherits their issues. For example, these solutions need to consider the limitation of the Ethereum platform’s performance on these solutions e.g., the performance can be affected because of the extra processing of traffic, high CPU utilisation, etc.

5.4.3. Solutions Based on the Ethereum Platform with Authorization (SEPA)

These solutions combine the Ethereum platform with authorisation to prevent DDoS attacks [136,137,138,139]. The Ethereum platform itself does not filter incoming devices, leaving malicious devices free to use the platform. Refs. [136,137,139] authorise users by checking access tokens generated by a smart contract. Ref. [138] uses PUF technology to control IoT devices. This type of solution manages devices’ authorisation in addition to only relying on the platform. To some extent, this can help to prevent DDoS attacks. Interestingly, Ref. [136] presented that it is necessary to prevent DDoS attacks from triggering smart contracts. They proposed a mechanism in which each user must solve a cryptographic puzzle before a transaction.
Besides the prevention of DDoS attacks by payment of gas, these solutions can also prevent malicious users from accessing the systems. However, the issues of this type of solutions are that most of the solutions are in the initial stage, and no consideration is given to detecting and mitigating DDoS attacks. Once an attacker finds a way to bypass authentication and launch a DDoS attack, the system has no working mechanism to detect and mitigate the attack.

5.4.4. Strengths and Weaknesses of the Ethereum Platform Based Solutions

Although it is convenient to use the Ethereum platform to deploy IoT devices, there are several weaknesses with the Ethereum platform-based solutions. To begin with, most of the solutions are in the initial stage, and they just simulate the implementation by using few nodes. The widespread use of the IoT requires the ability of scalability. However, with only a few nodes, it is hard to judge the availability and performance of these solutions. Furthermore, there are negative effects on the processing delays and costs on the Ethereum Blockchain when an attack occurs [139]. Even without an attack, submitting normal transactions might cause a service disruption on the Ethereum platform [140]. In addition, smart contracts need to be protected because they are susceptible to security failures. Attackers can make a particular smart contract operate incorrectly and thus cost money [140]. However, the only solution proposed in [135] considered DDoS attacks that trigger smart contracts. Finally, coupling with a third-party platform might lead to unpredictable issues [123], such as unpredictable transaction latencies, the time cost to update the Blockchain, the requirement of large storage size, etc. [140]. The summary of these three categories is shown in Table 6.
A complete list of the acronyms used in this research is presented in Table 7.

6. Future Research Directions

In this section, we present future research directions that can be explored further by other researchers. These future research directions are given below:

6.1. Protection of Smart Contracts

On the Ethereum platform, smart contracts are used to enforce specific rules to audit access policies to manage and control IoT devices. When defending against DDoS attacks, the systems rely on the security of Blockchain and smart contracts to reduce the impact. However, little attention is paid to the fact that smart contracts are themselves vulnerable to security issues and need to be protected. Once the smart contract is attacked, there will be economic losses and the specific smart contract will not work. Many popular Blockchain platforms use smart contracts, such as Ethereum, Fabric, etc. However, our survey results show that only Ref. [135] considered the protection of smart contracts. Therefore, one of the future research directions is to protect smart contracts.

6.2. Portability of Mitigation Solutions

Mitigation solutions for DDoS attacks should be portable and not simply dependent on one platform. The mechanisms should still protect the system when migration to other platforms is carried out. However, many solutions [128,129,130,131,133,134,135,136,137,138,139] are based on the Ethereum Platform and cannot be readily used on other blockchain based platforms. Therefore, another future research direction is to design and develop portable solutions to mitigate DDoS attacks.

6.3. Combination of Prevention, Detection and Reaction Mechanisms for DDoS Attacks

The three defence mechanisms against DDoS attacks are prevention, detection and reaction [4]. The defense mechanisms used by different solutions are mentioned in Table 3, Table 4, Table 5 and Table 6. Prevention is considered as the best strategy to mitigate DDoS attacks and most of the solutions [104,105,107,108,110,112,113,114,115,116] used this strategy. Prevention increases security but cannot completely stop DDoS attacks. By using detection methods, systems can detect DDoS attacks, and few solutions considered this mechanism [124,125,126,127,133,134,135]. Similarly, upon detection of DDoS attack, a reaction mechanism is used to stop the attack, to find the attacker, to recover from attack, etc. However, many solutions do not consider the reaction mechanism. Only Refs. [112,113,114,115,116,126,133,134,135] have considered the reaction mechanism. Therefore, future solutions should be proposed that take into account all three defense mechanisms against DDoS attacks.

6.4. Different Types of DDoS Attacks

Our survey results show that most solutions just mentioned that they are mitigating DDoS attacks in IoT-based networks without specifically mentioning the type of DDoS attack. Only few solutions [112,113,115,134,135] specifically mentioned the type of DDoS attack that they are mitigating. TCP SYN flood, UDP flood and ICMP flood are a few of the DDoS attacks that are considered by [112,113,115,134,135]. However, other DDoS attacks that can occur in IoT networks e.g., Hello flood, HTTP flood, DNS amplification, etc. are not considered by the existing solutions. Therefore, future researchers should propose Blockchain-based solutions to mitigate these DDoS attacks in IoT.

6.5. DDoS Attacks on IoT Based on Recently Known Botnets

In recent years, many sophisticated malware have been discovered by researchers that can make millions of IoT devices part of a botnet to carry out DDoS attacks. These malware include the famous Mirai Botnet which infected 15 million IoT devices with a flooding speed of 1 Tbps [141]. Other similar malware includes Reaper, Torii [142,143,144], etc. Hence, new schemes are essential to evaluate within the environment capable of replicating real-time conditions, both in terms of traffic scenarios and IoT infrastructure. This will also ensure the scalability of preventing DDoS attacks within the increased traffic demands and the heterogeneity of network structure.
Recall that the IoT ecosystems operate over a number of applications with different communication and security requirements (e.g., real-time delays intolerant applications such as health and disaster recovery applications or traffic control and smart home scenarios), which resulted in growing demands of intensive resource sharing and generic IoT infrastructures. Hence, new security solutions must be able to identify and prioritise malicious activities intended in different application scenarios. This will also enable the IoT infrastructure to be reconfigured at runtime. Furthermore, the routing protocols (including routing protocols for Mobile IoT [59]) for IoT need to be explored for their routing mechanisms and to search for opportunities in their routing mechanism to detect and mitigate DDoS attacks.

6.6. Large-Scale IoT Network and Scalability

The wide application of IoT determines its high scalability requirement. However, only two solutions [115,134] used relatively large-scale devices to verify the feasibility of their solution. For example, Ref. [115] conducted an experiment with 6000 IoT forwarding devices, and Ref. [134] used hundreds of devices. Simulations of using only a few nodes are far away from the actual scenario in IoT to evaluate the ability of any solution to mitigate DDoS attacks. Therefore, future research directions should include large-scale IoT networks.
As discussed earlier that the detection accuracy is high on the victim side, it is not robust enough to prevent the system because of massive DDoS attacks. Furthermore, it is highly possible that the intermediate network nodes are highly impacted because of the high-volume attacks generated at source IoT devices. Hence, first, it would be best to stop attacks at the sources; however, it is difficult to differentiate the traffic at sources because of minor traffic over the IoT devices. In addition, there should be centralised mechanisms deployed with various defense components i.e., prevention, detection and response, in order to deal with the DDoS flooding attacks.
In addition, there should be an authentication mechanism of IoT devices (specifically for Mobile IoT [59]) within the participating network so that the IoT devices could be made accountable for malicious activities generated at them. This also directs for introducing trusted infrastructures in order to enable trusted cooperation and collaboration among distributed components.

6.7. Compatibility of Solutions with Different IoT Application Domains

Considering the heterogeneity and usage of IoT devices in different industries, compatible and portable Blockchain-based solutions that mitigate DDoS attacks should be proposed in the future. However, our survey shows that all the solutions are used in specific situations with no proof that the mitigation mechanism is suitable for various industries in IoT. For example, solutions in [128] can only be used in firmware upgrade area; Refs. [108,120] are applied in smart homes; Refs. [107,136] are used in healthcare. Therefore, future research should be directed towards proposing solutions that can be used in multiple IoT application domains.

6.8. Comprehensive Experiments

Our survey results show that only four solutions [112,113,115,134] carried out experiments to determine the performance of their proposed solution. However, the experiments carried out by [112,113,115,134] are not comprehensive. This is because all of them do not consider multiple types of DDoS attacks on a large number of IoT devices. Moreover, experiments carried out in [112,113,115,134] fail to consider the prevention, detection and reaction ability of the solution; time is taken by solutions to detect and mitigate DDoS attacks, etc. Therefore, comprehensive experiments should be carried out in the future to properly gauge the effectiveness of the proposed solution.

6.9. Hybrid Platforms for Securing IoT Using Blockchain

The Blockchain is a powerful technology to secure the internet; however, the adoption of the Blockchain in IoT is still under development and is facing major challenges due to the limited capabilities of IoT devices in terms of resources, scalability and securing the overall network. A recent work [145] proposes a solution for protecting IoT devices from Mirai botnet attacks using Blockchain, suggesting dividing the network into different Autonomous Systems (AS) that monitor the communication activity within the network and determine whether a host is infected with malware. Hence, researchers are proposing the use of Blockchain in IoT using various technologies; we discuss a few challenges and possible research directions as follows:

6.9.1. Edge Computing and Blockchain IoT

Recall that the IoT devices pose several challenges while integrating with the blockchain technology due to their limited computation and networking capabilities (as IoT devices use traditional ways for connecting to the internet). Then, the IoT devices cannot process Proof-of-Work consensus algorithms due to limited computational power and constrained battery lifetime. The edge devices also lack the authorisation and authentication capabilities and limited interoperability [146], which can be enabled by implementing blockchain technology. Although there are several research works e.g., reputation and trust integration model between IoT and fog/edge computing [147], a blockchain-based reputation model for each participating agents [148], the consortium blockchain proposal for efficient and secure knowledge trading in edge AI-enabled IoT [149], and lightweight blockchain framework using a dynamic trust algorithm in IIoT edge applications [150]. These proposals suggest the integration of IoT devices with edge computing while extending the capabilities of blockchain technology. However, a major challenge is to propose a hybrid infrastructure in order to integrate IoT and edge computing with the blockchain without publishing blockchain transactions in a centralised pool as is done in traditional blockchain networks.

6.9.2. Software-Defined Internet of Things, Blockchain and Edge

As mentioned earlier, there are very few works that present a combined architecture including SDIoT [78,79,80,81,82] and SDIoT-Edge frameworks [83,84] suggested for effective management, increased scalability and interoperability. However, we note that (to the best of our knowledge) there are no works that study the heterogeneous service architecture that combines SDIoT-Edge with blockchain. This will enable a diverse combination of platforms, network topologies, protocols and various technologies, which will equip the IoT networks with increased security. This will pose several challenges in order to propose, operate, manage and secure applications that would operate on heterogeneous platforms. In addition, the security challenges can be addressed by providing network-based solutions and over the interface between the IoT networks combined with other technologies.

6.9.3. High-Speed Cellular 5G/6G Networks

The high-speed 5G/6G networks have enabled seamless communication among different platforms, e.g., SDIoT, SDIoT-Edge, blockchain, etc., and have increasingly been deployed as a communication resource. Although this will create immense opportunities for the researchers to develop the standards and protocols in order to coexist the wireless SDN with the IoT networks [58]. It is noted that the security features of blockchain can be implemented in IoT edge devices by separating the control layer from the application layer that will help in implementing various features within the cellular network such as data authentication and protection. However, an energy-efficient resources provision e.g., in SDIoT-Edge and privacy are still challenging [151]. In addition, the network scalability will still be an issue because of a high volume of data exchange over IoT devices, in addition to managing synchronising protocols for data exchange [152,153].

7. Conclusions

In this survey, we reviewed how the IoT networks are vulnerable to the DDoS attacks by exploiting IoT devices to target legitimate services. We discuss the DDoS attack scenario, its effect on IoT network and connected services, the layer of impact, the integration of Blockchain in IoT and its potential use to address DDoS attacks; in addition, we further briefly discuss challenges of Blockchain implementation in IoT. We discuss various existing Blockchain-based solutions to mitigate the DDoS attacks in the IoT environment and further categorise them into four categories—Distributed Architecture-based solutions, Access Management-based solutions, Traffic Control-based solutions and the Ethereum Platform-based solutions. We analyse existing solutions under each category for their working principles, the DDoS attack mitigation (i.e., prevention, detection, reaction), along with their weaknesses and strengths. Various research directions are also proposed in this survey that will enable future researchers to propose better Blockchain-based solutions to mitigate DDoS attacks in IoT. This work limits its investigation to security issues related to the Network layer of IoT and does not classify existing solutions that address security issues related to IoT’s Application and Sensor layers. In addition, we did not discuss the solutions that address the privacy issues. Furthermore, this article limits its study to Blockchain-based solutions, and we plan to see how the DDoS security (along with privacy) issues were addressed using Machine Learning or other technologies.

Author Contributions

Conceptualization: Z.S., I.U. and H.L.; Methodology: A.L. and K.K.; Investigation: Z.S., A.L. and K.K.; Resources: I.U. and H.L.; Writing—original draft preparation: Z.S., I.U. and H.L.; Writing—review and editing: K.K.; Supervision: Z.S. All authors have read and agreed to the published version of the manuscript.

Funding

There are no internal or external funds available for this research work. We further declare that the corresponding author will fully pay the APC charges.

Informed Consent Statement

This submission does not include human or animal research.

Data Availability Statement

There is no data associated with this article.

Conflicts of Interest

The authors do not declare any conflict of interests.

References

  1. Rghioui, A.; Oumnad, A. Internet of things: Surveys for measuring human activities from everywhere. Int. J. Electr. Comput. Eng. 2017, 7, 2474–2482. [Google Scholar] [CrossRef]
  2. IHS Market. The Internet of Things: A Moment, Not a Market. Available online: https://cdn.ihs.com/www/pdf/IoT_ebook.pdf (accessed on 18 November 2021).
  3. Li, S.; Tryfonas, T.; Li, H. The Internet of things: A security point of view. Internet Res. 2016, 26, 337–359. [Google Scholar] [CrossRef] [Green Version]
  4. Rashmi, D.; Devadkar, K. Understanding DDoS attack & its effect in cloud environment. Procedia Comput. Sci. 2015, 49, 202–210. [Google Scholar]
  5. Mohammad, M.; Abdolee, R.; Tazekand, B.M. On the convergence of blockchain and Internet of Things (IoT) technologies. arXiv 2019, arXiv:1904.01936. [Google Scholar]
  6. Castagna, L.R.; Michelin, R.A.; Neu, C.V.; Zorzo, A.F. Distributed access control on IoT ledger-based architecture. In Proceedings of the IEEE/IFIP Network Operations and Management Symposium, Taipei, Taiwan, 23–27 April 2018. [Google Scholar]
  7. Ujjwal, G.; Cui, P.; Skjellum, A. Ensuring proof-of-authenticity of IoT edge devices using blockchain technology. In Proceedings of the 2018 IEEE International Conference on Internet of Things (iThings), Halifax, NS, Canada, 30 July–3 August 2018. [Google Scholar]
  8. Kajwadkar, S.; Jain, V.K. A novel algorithm for DoS and DDoS attack detection in Internet of things. In Proceedings of the Conference on Information and Communication Technology (CICT), Jabalpur, India, 26–28 October 2018. [Google Scholar]
  9. Da, Y.; Zhang, L.; Yang, K. A DDoS attack detection and mitigation with software-defined Internet of things framework. IEEE Access 2018, 6, 24694–24705. [Google Scholar]
  10. Tamotsu, K.; Fukushi, M.; Hirano, Y.; Fujita, Y.; Hamamoto, Y. An NTP-based detection module for DDoS attacks on IoT. In Proceedings of the IEEE International Conference on Consumer Electronics-Taiwan (ICCE-TW), Taipei, Taiwan, 12–14 June 2017. [Google Scholar]
  11. Modi, K.; Quadir, A. Detection and prevention of DDoS attacks on the cloud using double-TCP mechanism and HMM-based architecture. Int. J. Cloud Comput. Serv. Sci. 2014, 3, 113. [Google Scholar]
  12. Sriman, I.; Banerjee, A.; Ganapathy, G. A fuzzy logic based defense mechanism against distributed denial of service attack in cloud computing environment. Int. J. Commun. Netw. Inf. Secur. (IJCNIS) 2014, 6, 233–245. [Google Scholar]
  13. Dargahi, T.P.J.T.; Dehghantanha, A.; Parizi, R.M.; Choo, K.K.R. A systematic literature review of blockchain cyber security. Digit. Commun. Netw. 2020, 6, 147–156. [Google Scholar]
  14. Hany, A.; Alenezi, A.; Alassafi, M.O.; Wills, G. Blockchain with Internet of things: Benefits, challenges, and future directions. Int. J. Intell. Syst. Appl. 2018, 10, 40–48. [Google Scholar]
  15. Horn, N.J.; Koohang, A.; Paliszkiewicz, J. The Internet of things: Review and theoretical framework. Expert Syst. Appl. 2019, 133, 97–108. [Google Scholar]
  16. Wani, S.; Imthiyas, M.; Almohamedh, H.; Alhamed, K.M.; AlMotairi, S.; Gulzar, Y. Distributed Denial of Service (DDoS) Mitigation Using Blockchain—A Comprehensive Insight. Symmetry 2021, 13, 227. [Google Scholar] [CrossRef]
  17. Shammar, E.A.; Zahary, A.T.; Al-Shargabi, A.A. A Survey of IoT and Blockchain Integration: Security Perspective. IEEE Access 2021, 9, 156114–156150. [Google Scholar] [CrossRef]
  18. Li, D.X.; Yang, L.; Ling, L. Embedding blockchain technology into IoT for security: A survey. IEEE Internet Things J. 2021, 8, 10452–10473. [Google Scholar]
  19. Banerjee, M.; Lee, J.; Chen, Q.; Choo, K.K.R. Blockchain-based security layer for identification and isolation of malicious things in IoT: A conceptual design. In Proceedings of the IEEE 2018 27th International Conference on Computer Communication and Networks (ICCCN), Hangzhou, China, 30 July–2 August 2018; pp. 1–6. [Google Scholar]
  20. Ahmad, K.M.; Salah, K. IoT security: Review, blockchain solutions, and open challenges. Future Gener. Comput. Syst. 2018, 82, 395–411. [Google Scholar]
  21. Krushang, S.; Upadhyay, H. A survey: DDOS attack on Internet of things. Int. J. Eng. Res. Dev. 2014, 10, 56–63. [Google Scholar]
  22. Zibin, Z.; Xie, S.; Dai, Ho.; Chen, X. Blockchain challenges and opportunities: A survey. Int. J. Web Grid Serv. 2018, 14, 352–357. [Google Scholar]
  23. Michael, C.; Pattanayak, P.; Verma, S.; Kalyanaraman, V. Blockchain technology: Beyond bitcoin. Appl. Innov. 2016, 2, 71. [Google Scholar]
  24. Andrew, C.; Hammoudeh, M.; Aldabbas, O. Defence for distributed denial of service attacks in cloud computing. Procedia Comput. Sci. 2015, 73, 490–497. [Google Scholar]
  25. KrebsonSecurity “Study: Attack on KrebsOnSecurity Cost IoT Device Owners $323 K”. Available online: https://krebsonsecurity.com/2018/05/study-attack-on-krebsonsecurity-cost-iot-device-owners-323k/ (accessed on 18 November 2021).
  26. Record-Breaking DDoS Reportedly Delivered by >145 k Hacked Cameras. Available online: https://arstechnica.com/information-technology/2016/09/botnet-of-145k-cameras-reportedly-deliver-internets-biggest-ddos-ever/ (accessed on 18 November 2021).
  27. Zhang, C.; Green, R. Communication security in internet of thing: Preventive measure and avoid DDoS attack over IoT network. In Proceedings of the 18th Symposium on Communications & Networking, Alexandria, VA, USA, 12–15 April 2015. [Google Scholar]
  28. Ahmed, K.; Andrew, M.; Elaine, S.; Zikai, W.; Charalampos, P. Hawk: The blockchain model of cryptography and privacy-preserving smart contracts. In Proceedings of the IEEE 2016 IEEE Symposium on Security and Privacy (SP), San Jose, CA, USA, 22–26 May 2016; pp. 839–858. [Google Scholar]
  29. Satoshi, N. Bitcoin: A Peer-to-Peer Electronic Cash System. Available online: https://bitcoin.org/bitcoin.pdf (accessed on 31 October 2008).
  30. Ullah, I.; Boreli, R.; Kanhere, S.S. Privacy in targeted advertising: A survey. arXiv 2020, arXiv:2009.06861. [Google Scholar]
  31. Ullah, I.; Kanhere, S.S.; Boreli, R. Privacy-preserving targeted mobile advertising: A Blockchain-based framework for mobile ads. arXiv 2020, arXiv:2008.10479. [Google Scholar]
  32. Dorri, A.; Steger, M.; Kanhere, S.S.; Jurdak, R. Blockchain: A distributed solution to automotive security and privacy. IEEE Commun. Mag. 2017, 55, 119–125. [Google Scholar] [CrossRef] [Green Version]
  33. Christidis, K.; Michael, D. Blockchains and smart contracts for the internet of things. IEEE Access 2016, 4, 2292–2303. [Google Scholar] [CrossRef]
  34. Peters, G.W.; Panayi, E. Understanding modern banking ledgers through blockchain technologies: Future of transaction processing and smart contracts on the internet of money. In Banking Beyond Banks and Money; Springer: Cham, Switzerland, 2016; pp. 239–278. [Google Scholar]
  35. Rossi, A.H.; Kurniawan, N.B.; Suhardi. Blockchain technology and implementation: A systematic literature review. In Proceedings of the International Conference on Information Technology Systems and Innovation (ICITSI), Bandung, Indonesia, 22–26 October 2018.
  36. Gramoli, V. From blockchain consensus back to Byzantine consensus. Future Gener. Comput. Syst. 2020, 107, 760–769. [Google Scholar] [CrossRef]
  37. Vukolić, M. The quest for scalable blockchain fabric: Proof-of-work vs. BFT replication. In Springer International Workshop on Open Problems in Network Security; iNetSec: Zurich, Switzerland, 29 October 2015; pp. 112–125. [Google Scholar]
  38. Wood, G. Ethereum: A secure decentralised generalised transaction ledger. Ethereum Proj. Yellow Pap. 2014, 151, 1–32. [Google Scholar]
  39. Ferdous, M.S.; Chowdhury, M.J.M.; Hoque, M.A. “A survey of consensus algorithms in public blockchain systems for crypto-currencies. J. Netw. Comput. Appl. 2021, 182, 103035. [Google Scholar] [CrossRef]
  40. Xiao, Y.; Zhang, N.; Lou, W.; Hou, Y.T. A survey of distributed consensus protocols for blockchain networks. IEEE Commun. Surv. Tutor. 2020, 22, 1432–1465. [Google Scholar] [CrossRef] [Green Version]
  41. Nguyen, G.-T.; Kim, K. A survey about consensus algorithms used in blockchain. J. Inf. Process. Syst. Korea Inf. Process. Soc. 2018, 14, 101–128. [Google Scholar]
  42. Bamakan, S.M.H.; Motavali, A.; Bondarti, A.B. A survey of blockchain consensus algorithms performance evaluation criteria. Expert Syst. Appl. 2020, 154, 113385. [Google Scholar] [CrossRef]
  43. Garay, J.; Kiayias, A. Sok: A consensus taxonomy in the blockchain era. In Proceedings of the Cryptographers’ Track at the RSA Conference, San Francisco, CA, USA, 24–28 February 2020; Springer: Cham, Switzerland, 2020; pp. 284–318. [Google Scholar]
  44. Castro, M.; Liskov, B. Practical Byzantine fault tolerance and proactive recovery. ACM Trans. Comput. Syst. (TOCS) 2002, 20, 398–461. [Google Scholar] [CrossRef]
  45. He, L.; Hou, Z. An improvement of consensus fault tolerant algorithm applied to alliance chain. In Proceedings of the IEEE 9th International Conference on Electronics Information and Emergency Communication (ICEIEC), Beijing, China, 12–14 July 2019; pp. 1–4. [Google Scholar]
  46. Miller, A.; Xia, Y.; Croman, K.; Shi, E.; Song, D. The honey badger of BFT protocols. In Proceedings of the ACM SIGSAC Conference on Computer and Communications Security, Vienna, Austria, 24–28 October 2016; pp. 31–42. [Google Scholar]
  47. Delegated Proof-of-Stake Consensus. 2018. Available online: https://how.bitshares.works/en/master/technology/dpos.html (accessed on 18 November 2021).
  48. Qu, X.; Wang, S.; Hu, Q.; Cheng, X. Proof of Federated Learning: A Novel Energy-Recycling Consensus Algorithm. IEEE Trans. Parallel Distrib. Syst. 2021, 32, 2074–2085. [Google Scholar] [CrossRef]
  49. Intel. Sawtooth. 2021. Available online: https://www.hyperledger.org/use/sawtooth (accessed on 18 November 2021).
  50. Milutinovic, M.; He, W.; Wu, H.; Kanwa, M. Proof of luck: An efficient Blockchain consensus protocol. In Proceedings of the 1st Workshop on System Software for Trusted Execution, New York, NY, USA, 12–16 December 2016. [Google Scholar]
  51. Park, S.; Kwon, A.; Fuchsbauer, G.; Gai, P.; Alwen, J.; Pietrzak, K. SpaceMint: A Cryptocurrency Based on Proofs of Space. Cryptology ePrint Archive, Report 2015/528. 2015. Available online: https://eprint.iacr.org/2015/528 (accessed on 18 November 2021).
  52. Daniel, L. Delegated proof-of-stake (DPoS). Bitshare Whitepaper 2014, 81, 85. [Google Scholar]
  53. Johnson, D.; Menezes, A.; Vanstone, S. The elliptic curve digital signature algorithm (ECDSA). Springer Int. J. Inf. Secur. 2001, 1, 36–63. [Google Scholar] [CrossRef]
  54. Wu, Y.-C.; Tseng, H.-R.; Yang, W.; Jan, R.-H. DDoS detection and traceback with decision tree and grey relational analysis. Int. J. Hoc Ubiquitous Comput. 2011, 7, 121–136. [Google Scholar] [CrossRef] [Green Version]
  55. Cabrera, J.B.D.; Lewis, L.; Qin, X.; Lee, W.; Prasanth, R.K.; Ravichandran, B.; Mehra, R.K. Proactive detection of distributed denial of service attacks using mib traffic variables-a feasibility study. In Proceedings of the 2001 IEEE/IFIP International Symposium on Integrated Network Management Proceedings, Seattle, WA, USA, 14–18 May 2001; pp. 609–622. [Google Scholar]
  56. Jalili, R.; Imani-Mehr, F.; Amini, M.; Shahriari, H.R. Detection of Distributed Denial of Service Attacks Using Statistical Pre-Processor and Unsupervised Neural Networks; Springer International Conference on Information Security Practice and Experience: Berlin/Heidelberg, Germany, 2005. [Google Scholar]
  57. Ahanger, T.A.; Tariq, U.; Ibrahim, A.; Ullah, I.; Bouteraa, Y. Iot-inspired framework of intruder detection for smart home security systems. Electronics 2020, 9, 1361. [Google Scholar] [CrossRef]
  58. Rafique, W.; Qi, L.; Yaqoob, I.; Imran, M.; Rasool, R.U.; Dou, W. Complementing IoT services through software defined networking and edge computing: A comprehensive survey. IEEE Commun. Surv. Tutor. 2020, 22, 1761–1804. [Google Scholar] [CrossRef]
  59. Shah, Z.; Levula, A.; Khurshid, K.; Ahmed, J.; Ullah, I.; Singh, S. Routing Protocols for Mobile Internet of Things (IoT): A Survey on Challenges and Solutions. Electronics 2021, 10, 2320. [Google Scholar] [CrossRef]
  60. Li, M.; Liu, J.; Long, D. Probability principle of a reliable approach to detect signs of DDOS flood attacks. In Proceedings of the International Conference on Parallel and Distributed Computing: Applications and Technologies, Singapore, 8–10 December 2004; Springer: Berlin/Heidelberg, Germany, 2004; pp. 596–599. [Google Scholar]
  61. Peng, T.; Leckie, C.; Ramamohanarao, K. Protection from distributed denial of service attacks using history-based IP filtering. In Proceedings of the IEEE International Conference on Communications, ICC’2003, Anchorage, AK, USA, 11–15 May 2003; Volume 3, pp. 482–486. [Google Scholar]
  62. Xu, X.; Liu, Q.; Luo, Y.; Peng, K.; Zhang, X.; Meng, S.; Qi, L. A computation offloading method over big data for IoT-enabled cloud-edge computing. Future Gener. Comput. Syst. 2019, 95, 522–533. [Google Scholar] [CrossRef]
  63. Tu, L.; Liu, S.; Wang, Y.; Zhang, C.; Li, P. An optimized cluster storage method for real-time big data in Internet of Things. J. Supercomput. 2020, 76, 5175–5191. [Google Scholar] [CrossRef]
  64. Habib, S.; Qadir, J.; Ali, A.; Habib, D.; Li, M.; Sathiaseelan, A. The past, present, and future of transport-layer multipath. J. Netw. Comput. Appl. 2016, 75, 236–258. [Google Scholar] [CrossRef] [Green Version]
  65. Vasseur, J.P.; Dunkels, A. Chapter 3-Why IP for Smart Objects? In Interconnecting Smart Objects with IP; Morgan Kaufmann: Boston, MA, USA, 2010. [Google Scholar]
  66. Sollins, K.R. IoT big data security and privacy versus innovation. IEEE Internet Things J. 2019, 6, 1628–1635. [Google Scholar] [CrossRef]
  67. Olaniyan, R.; Fadahunsi, O.; Maheswaran, M.; Zhani, M.F. Opportunistic edge computing: Concepts, opportunities and research challenges. Future Gener. Comput. Syst. 2018, 89, 633–645. [Google Scholar] [CrossRef] [Green Version]
  68. Ahmed, E.; Ahmed, A.; Yaqoob, I.; Shuja, J.; Gani, A.; Imran, M.; Shoaib, M. Bringing computation closer toward the user network: Is edge computing the solution? IEEE Commun. Mag. 2017, 55, 138–144. [Google Scholar] [CrossRef]
  69. Latif, K.; Javaid, N.; Ullah, I.; Kaleem, Z.; Abbas Malik, Z.; Nguyen, L.D. DIEER: Delay-intolerant energy-efficient routing with sink mobility in underwater wireless sensor networks. Sensors 2020, 20, 3467. [Google Scholar] [CrossRef]
  70. Dizdarević, J.; Carpio, F.; Jukan, A.; Masip-Bruin, X. A survey of communication protocols for internet of things and related challenges of fog and cloud computing integration. ACM Comput. Surv. (CSUR) 2019, 51, 1–29. [Google Scholar] [CrossRef]
  71. Yaqoob, I.; Hashem, I.A.T.; Ahmed, A.; Kazmi, S.M.A.; Hong, C.S. Internet of things forensics: Recent advances, taxonomy, requirements, and open challenges. Future Gener. Comput. Syst. 2019, 92, 265–275. [Google Scholar] [CrossRef]
  72. Ferrer, A.J.; Marquès, J.M.; Jorba, J. Towards the decentralised cloud: Survey on approaches and challenges for mobile, ad hoc, and edge computing. ACM Comput. Surv. (CSUR) 2019, 51, 1–36. [Google Scholar] [CrossRef]
  73. Baresi, L.; Mendonça, D.F.; Garriga, M.; Guinea, S.; Quattrocchi, G. A unified model for the mobile-edge-cloud continuum. ACM Trans. Internet Technol. (TOIT) 2019, 19, 1–21. [Google Scholar] [CrossRef]
  74. Wang, S.; Zhao, Y.; Huang, L.; Xu, J.; Hsu, C.-H. QoS prediction for service recommendations in mobile edge computing. J. Parallel Distrib. Comput. 2019, 127, 134–144. [Google Scholar] [CrossRef]
  75. Farris, I.; Taleb, T.; Khettab, Y.; Song, J. A survey on emerging SDN and NFV security mechanisms for IoT systems. IEEE Commun. Surv. Tutor. 2018, 21, 812–837. [Google Scholar] [CrossRef]
  76. Khan, S.; Gani, A.; Wahab, A.W.A.; Guizani, M.; Khan, M.K. Topology discovery in software defined networks: Threats, taxonomy, and state-of-the-art. IEEE Commun. Surv. Tutor. 2016, 19, 303–324. [Google Scholar] [CrossRef]
  77. Zarca, A.M.; Bernabe, J.B.; Trapero, R.; Rivera, D.; Villalobos, J.; Skarmeta, A.; Bianchi, S.; Zafeiropoulos, A.; Gouvas, P. Security management architecture for NFV/SDN-aware IoT systems. IEEE Internet Things J. 2019, 6, 8005–8020. [Google Scholar] [CrossRef]
  78. Akhunzada, A.; Khan, M.K. Toward secure software defined vehicular networks: Taxonomy, requirements, and open issues. IEEE Commun. Mag. 2017, 55, 110–118. [Google Scholar] [CrossRef]
  79. Darabseh, A.; Freris, N.M. A software-defined architecture for control of IoT cyberphysical systems. Clust. Comput. 2019, 22, 1107–1122. [Google Scholar] [CrossRef] [Green Version]
  80. Jararweh, Y.; Al-Ayyoub, M.; Benkhelifa, E. An experimental framework for future smart cities using data fusion and software defined systems: The case of environmental monitoring for smart healthcare. Future Gener. Comput. Syst. 2020, 107, 883–897. [Google Scholar] [CrossRef]
  81. Haque, I.; Nurujjaman, M.; Harms, J.; Abu-Ghazaleh, N. SDSense: An agile and flexible SDN-based framework for wireless sensor networks. IEEE Trans. Veh. Technol. 2018, 68, 1866–1876. [Google Scholar] [CrossRef]
  82. Alam, I.; Sharif, K.; Li, F.; Latif, Z.; Karim, M.M.; Nour, B.; Biswas, S.; Wang, Y. IoT virtualization: A survey of software definition & function virtualization techniques for internet of things. arXiv 2019, arXiv:1902.10910. [Google Scholar]
  83. Uddin, M.; Nadeem, T.; Nukavarapu, S. Extreme SDN framework for IoT and mobile applications flexible privacy at the edge. In Proceedings of the 2019 IEEE International Conference on Pervasive Computing and Communications (PerCom), Kyoto, Japan, 11–15 March 2019; pp. 1–11. [Google Scholar]
  84. Sairam, R.; Bhunia, S.S.; Thangavelu, V.; Gurusamy, M. NETRA: Enhancing IoT security using NFV-based edge traffic analysis. IEEE Sens. J. 2019, 19, 4660–4671. [Google Scholar] [CrossRef] [Green Version]
  85. Panarello, A.; Tapas, N.; Merlino, G.; Longo, F.; Puliafito, A. Blockchain and iot integration: A systematic survey. Sensors 2018, 18, 2575. [Google Scholar] [CrossRef] [Green Version]
  86. Kolias, C.; Kambourakis, G.; Stavrou, A.; Voas, J. DDoS in the IoT: Mirai and other botnets. IEEE Comput. 2017, 50, 80–84. [Google Scholar] [CrossRef]
  87. Gubbi, J.; Buyya, R.; Marusic, S.; Palaniswami, M. Internet of Things (IoT): A vision, architectural elements, and future directions. Future Gener. Comput. Syst. 2013, 29, 1645–1660. [Google Scholar] [CrossRef] [Green Version]
  88. Sicari, S.; Rizzardi, A.; Cappiello, C.; Miorandi, D.; Coen-Porisini, A. Toward data governance in the internet of things. In New Advances in the Internet of Things; Springer: Cham, Switzerland, 2018; pp. 59–74. [Google Scholar]
  89. Hawlitschek, F.; Notheisen, B.; Teubner, T. The limits of trust-free systems: A literature review on blockchain technology and trust in the sharing economy. Electron. Commer. Res. Appl. 2018, 29, 50–63. [Google Scholar] [CrossRef]
  90. Imran, M.; Abolhasan, M.; Abbas, H.; Ni, W. Blockchain’s adoption in IoT: The challenges, and a way forward. J. Netw. Comput. Appl. 2018, 125, 251–279. [Google Scholar]
  91. Mocnej, J.; Seah, W.K.G.; Pekar, A.; Zolotova, I. Decentralised IoT architecture for efficient resources utilisation. IFAC-PapersOnLine 2018, 51, 168–173. [Google Scholar] [CrossRef]
  92. Xu, W.; Zha, X.; Ni, W.; Liu, R.P.; Guo, Y.J.; Niu, X.; Zheng, K. Survey on blockchain for Internet of Things. Comput. Commun. 2019, 136, 10–29. [Google Scholar]
  93. Ana, R.; Martín, C.; Chen, J.; Soler, E.; Díaz, M. On blockchain and its integration with IoT. Challenges and opportunities. Future Gener. Comput. Syst. 2018, 88, 173–190. [Google Scholar]
  94. Amine, F.M.; Derdour, M.; Mukherjee, M.; Derhab, A.; Maglaras, L.; Janicke, H. Blockchain technologies for the Internet of things: Research issues and challenges. IEEE Internet Things J. 2018, 6, 2188–2204. [Google Scholar]
  95. Ferreira, J.E.; Chicarino, V.R.L.; de Albuquerque, C.V.N.; Rocha, A.A.D.A. A survey of how to use blockchain to secure Internet of things and the stalker attack. Secur. Commun. Netw. 2018, 7, 1–27. [Google Scholar]
  96. Mandrita, B.; Lee, J.; Choo, Ki.R. A blockchain future for Internet of things security: A position paper. Digit. Commun. Netw. 2018, 4, 149–160. [Google Scholar]
  97. Sana, M.; Karim, A.; Safdar, Z.; Safdar, K.; Ahmed, E.; Imran, M. Securing IoTs in distributed blockchain: Analysis, requirements and open issues. Future Gener. Comput. Syst. 2019, 100, 325–343. [Google Scholar]
  98. Riza’ain, Y.A.; Udzir, N.I.; Selamat, A. Systematic literature review and taxonomy for DDoS attack detection and prediction. Int. J. Digit. Enterp. Technol. 2019, 1, 292–315. [Google Scholar]
  99. Jaafar Ghafar, A.; Shahidan, M. Abdullah and Saifuladli Ismail. Review of Recent Detection Methods for HTTP DDoS Attack. J. Comput. Netw. Commun. 2019, 2019, 1–10. [Google Scholar] [CrossRef] [Green Version]
  100. Taghizadeh, M.M. Defense mechanisms against Distributed Denial of Service attacks: A survey. Comput. Electr. Eng. 2018, 72, 26–38. [Google Scholar]
  101. Jeet, K.; Gandhi, A.B. Security and DDOS mechanisms in Internet of things. Int. J. Adv. Res. Comput. Sci. 2017, 8, 261–265. [Google Scholar]
  102. Hanan, M.; Alghamdi, A.M. DDoS attacks on the Internet of things and their prevention methods. In Proceedings of the 2nd International Conference on Future Networks and Distributed Systems, New York, NY, USA, 26–27 June 2018. [Google Scholar]
  103. Malik Manisha and Maitreyee Dutta. Defending DDoS in the Insecure Internet of things: A Survey. In Artificial Intelligence and Evolutionary Computations in Engineering Systems; Springer: Singapore, 2018. [Google Scholar]
  104. Ziyan, W.; Dong, X.; Li, Y.; Fang, L.; Chen, P. IoT security model and performance evaluation: A blockchain approach. In Proceedings of the International Conference on Network Infrastructure and Digital Content (IC-NIDC), Guiyang, China, 22–24 August 2018. [Google Scholar]
  105. Li, D.; Peng, W.; Deng, W.; Gai, F. A blockchain-based authentication and security mechanism for IoT. In Proceedings of the 27th International Conference on Computer Communication and Networks (ICCCN), Hangzhou, China, 30 July–2 August 2018. [Google Scholar]
  106. Spathoulas, G.; Giachoudis, N.; Damiris, G.-P.; Theodoridis, G. Collaborative blockchain-based detection of distributed denial of service attacks based on internet of things botnets. Future Internet 2019, 11, 226. [Google Scholar] [CrossRef] [Green Version]
  107. Dhar, D.A.; Srivastava, G.; Dhar, S.; Singh, R. A decentralized privacy-preserving healthcare blockchain for IoT. Sensors 2019, 19, 326. [Google Scholar] [CrossRef] [Green Version]
  108. Ali, D.; Kanhere, S.S.; Jurdak, R. Blockchain in internet of things: Challenges and solutions. arXiv 2016, arXiv:1608.05187. [Google Scholar]
  109. Sun, S.; Du, R.; Chen, S.; Li, W. Blockchain-Based IoT Access Control System: Towards Security, Lightweight, and Cross-Domain. IEEE Access 2021, 9, 36868–36878. [Google Scholar] [CrossRef]
  110. Pinchen, C.; Guin, U. Countering botnet of things using blockchain-based authenticity framework. In Proceedings of the IEEE Computer Society Annual Symposium on VLSI (ISVLSI), Miami, FL, USA, 15–17 July 2019. [Google Scholar]
  111. Cui, Y.; Qian, Q.; Guo, C.; Shen, G.; Tian, Y.; Xing, H.; Yan, L. Towards DDoS detection mechanisms in Software-Defined Networking. J. Netw. Comput. Appl. 2021, 190, 103156. [Google Scholar] [CrossRef]
  112. Shailendra, R.; Kwon, B.W.; Park, J.H. BlockSecIoTNet: Blockchain-based decentralized security architecture for IoT network. J. Netw. Comput. Appl. 2019, 143, 167–177. [Google Scholar]
  113. Qaisar, S.; Basit, A. DDoS botnet prevention using blockchain in software defined Internet of things. In Proceedings of the 16th International Bhurban Conference on Applied Sciences and Technology (IBCAST), Islamabad, Pakistan, 8–12 January 2019. [Google Scholar]
  114. Bruno, R.; Bocek, T.; Lareida, A.; Hausheer, D.; Rafati, S.; Stiller, B. A blockchain-based architecture for collaborative DDoS mitigation with smart contracts. In Proceedings of the IFIP International Conference on Autonomous Infrastructure, Management and Security, Zurich, Switzerland, 10–13 July 2017. [Google Scholar]
  115. Kumar, S.P.; Singh, S.; Jeong, Yo.; Park, J.H. Distblocknet: A distributed blockchains-based secure SDN architecture for IoT networks. IEEE Commun. Mag. 2017, 55, 78–85. [Google Scholar]
  116. Kotaro, K.; Gangwar, S.; Podili, P. Trust list: Internet-wide and distributed IoT traffic management using blockchain and SDN. In Proceedings of the IEEE 4th World Forum on Internet of Things (WF-IoT), Singapore, 5–8 February 2018. [Google Scholar]
  117. Abou El Houda, Z.; Hafid, A.; Khoukhi, L. Co-IoT: A collaborative DDoS mitigation scheme in IoT environment based on blockchain using SDN. In Proceedings of the 2019 IEEE Global Communications Conference (GLOBECOM), Waikoloa, HI, USA, 9–13 December 2019; pp. 1–6. [Google Scholar]
  118. Islam, M.J.; Rahman, A.; Kabir, S.; Karim, M.R.; Acharjee, U.K.; Nasir, M.K.; Band, S.S.; Sookhak, M.; Wu, S. Blockchain-sdn based energy-aware and distributed secure architecture for IoTs in smart cities. IEEE Internet Things J. 2021. [Google Scholar] [CrossRef]
  119. Shah, Z.; Cosgrove, S. Mitigating ARP Cache Poisoning Attack in Software-Defined Networking (SDN): A Survey. Electronics 2019, 8, 1095. [Google Scholar] [CrossRef] [Green Version]
  120. Ali, D.; Kanhere, S.S.; Jurdak, R.; Gauravaram, P. LSB: A lightweight scalable blockchain for IoT security and privacy. arXiv 2017, arXiv:1712.02969. [Google Scholar]
  121. Haiping, S.; Sun, C.; Li, Y.; Qiao, H.; Shi, L. IoT information sharing security mechanism based on blockchain technology. Future Gener. Comput. Syst. 2019, 101, 1028–1040. [Google Scholar]
  122. Tahar, H.M.; Hammi, B.; Bellot, P.; Serhrouchni, A. Bubbles of trust: A decentralized blockchain-based authentication system for IoT. Comput. Secur. 2018, 78, 126–142. [Google Scholar]
  123. Jawad, A.; Ali, T.; Musa, S.; Zahrani, A. Towards secure IoT communication with smart contracts in a blockchain infrastructure. Trans. Hash. 2018, 9, 584–591. [Google Scholar]
  124. Jiafu, W.; Li, J.; Imran, M.; Li, D. A blockchain-based solution for enhancing security and privacy in smart factory. IEEE Trans. Ind. Inform. 2019, 15, 3652–3660. [Google Scholar]
  125. Lun, L.; Liu, J.; Cheng, L.; Qiu, S.; Wang, W.; Zhang, X.; Zhang, Z. Creditcoin: A privacy-preserving blockchain-based incentive announcement network for communications of smart vehicles. IEEE Trans. Intell. Transp. Syst. 2018, 19, 2204–2220. [Google Scholar]
  126. Gokhan, S.; Carminati, B.; Ferrari, E. AutoBotCatcher: Blockchain-based P2P botnet detection for the Internet of things. In Proceedings of the IEEE 4th International Conference on Collaboration and Internet Computing (CIC), Philadelphia, PA, USA, 18–20 October 2018. [Google Scholar]
  127. Gregory, F.; Li, C.; Fedorov, P.; Caldera, C.; Arora, R.; Jackson, K. Neuromesh: IoT security enabled by a blockchain powered botnet vaccine. In Proceedings of the The International Conference on Omni-Layer Intelligent Systems, Crete Greece, 5–7 May 2019. [Google Scholar]
  128. Akshay, P.; Sindhu, M.; Lakshmy, K.V. Securing firmware in Internet of things using blockchain. In Proceedings of the 5th International Conference on Advanced Computing & Communication Systems (ICACCS), Coimbatore, India, 15–16 March 2019. [Google Scholar]
  129. Seyoung, H.; Cho, S.; Kim, S. Managing IoT devices using blockchain platform. In Proceedings of the 2017 19th International Conference on Advanced Communication Technology (ICACT), Pyeongchang, Korea, 19–22 February 2017. [Google Scholar]
  130. Quanqing, X.; Aung, K.M.M.; Zhu, Y.; Yong, K.L. A blockchain-based storage system for data analytics in the Internet of things. In New Advances in the Internet of Things; Springer: Cham, Switzerland, 2018. [Google Scholar]
  131. Lee, J. Patch transporter: Incentivized, decentralized software patch system for WSN and IoT environments. Sensors 2018, 18, 574. [Google Scholar] [CrossRef] [Green Version]
  132. Kruthik, J.T.; Ramakrishnan, K.; Sunitha, R.; Honnavalli, B.P. Security Model for Internet of Things Based on Blockchain. In Innovative Data Communication Technologies and Application; Springer: Singapore, 2021; pp. 543–557. [Google Scholar]
  133. Lee, J. Mitigating loT device based DDoS attacks using blockchain. In Proceedings of the 1st Workshop on Cryptocurrencies and Blockchains for Distributed Systems, Munich, Germany, 15 June 2018. [Google Scholar]
  134. Michael, A.; Kolb, J.; Chen, K.; Fierro, G.; Culler, D.E.; Popa, R.A. Wave: A Decentralized Authorization System for IoT via Blockchain Smart Contracts; EECS Department, University of California: Berkeley, CA, USA, 2017. [Google Scholar]
  135. Mena, M.; Diego, M.; Yang, B. Blockchain-based whitelisting for consumer IoT devices and home networks. In Proceedings of the 19th Annual SIG Conference on Information Technology Education, Fort Lauderdale, FL, USA, 3–6 October 2018. [Google Scholar]
  136. Olivier, A.; Amoretti, M.; Claeys, T.; Dall’Asta, S.; Duda, A.; Ferrari, G.; Rousseau, F.; Tourancheau, B.; Veltri, L.; Zanichelli, F. IoTChain: A blockchain security architecture for the Internet of things. In Proceedings of the IEEE Wireless Communications and Networking Conference (WCNC), Barcelona, Spain, 15–18 April 2018. [Google Scholar]
  137. Mansoor, A.; Salah, K.; Alhammadi, Y. Blockchain-based ownership management for medical IoT (MIoT) devices. In Proceedings of the International Conference on Innovations in Information Technology (IIT), Al Ain, United Arab Emirates, 18–19 November 2018. [Google Scholar]
  138. Uzair, J.; Aman, M.N.; Sikdar, B. BlockPro: Blockchain based data provenance and integrity for secure IoT environments. In Proceedings of the 1st Workshop on Blockchain-Enabled Networked Sensor Systems, Shenzhen, China, 4 November 2018. [Google Scholar]
  139. Tahar, H.M.; Bellot, P.; Serhrouchni, A. BCTrust: A decentralized authentication blockchain-based mechanism. In Proceedings of the IEEE Wireless Communications and Networking Conference (WCNC), Barcelona, Spain, 15–18 April 2018. [Google Scholar]
  140. Ingo, W.; Gramoli, V.; Ponomarev, A.; Staples, M.; Holz, R.; Tran, A.B.; Rimba, P. On availability for blockchain-based systems. In Proceedings of the IEEE 36th Symposium on Reliable Distributed Systems (SRDS), Hong Kong, China, 26–29 September 2017. [Google Scholar]
  141. Santeri, P.; Elo, T.; Nikander, P. Risks from spam attacks on blockchains for Intemet-of-Things devices. In Proceedings of the IEEE 9th Annual Information Technology, Electronics and Mobile Communication Conference (IEMCON), Vancouver, BC, Canada, 1–3 November 2018. [Google Scholar]
  142. Vishwakarma, R.; Kumar, A. A survey of DDoS attacking techniques and defence mechanisms in the IoT network. Telecommun. Syst. 2019, 73, 1–23. [Google Scholar] [CrossRef]
  143. Prokofiev, A.; Smirnova, Y.S. Counteraction against Internet of Things Botnets in Private Networks. In Proceedings of the IEEE Conference of Russian Young Researchers in Electrical and Electronic Engineering (EIConRus), Saint Petersburg, Russia, 28–31 January 2019. [Google Scholar]
  144. Madiha, S.; Fernandez, E.; Moreno, J. A misuse pattern for DDoS in the IoT. In Proceedings of the ACM European Conference on Pattern Languages of Programs, Irsee, Germany, 4–8 July 2018. [Google Scholar]
  145. Ahmed, Z.; Danish, S.M.; Qureshi, H.K.; Lestas, M. Protecting iots from mirai botnet attacks using blockchains. In Proceedings of the IEEE 24th International Workshop on Computer Aided Modeling and Design of Communication Links and Networks (CAMAD), Limassol, Cyprus, 11–13 September 2019; pp. 1–6. [Google Scholar]
  146. Saxena, S.; Bhushan, B.; Ahad, M.A. Blockchain based solutions to secure IoT: Background, integration trends and a way forward. J. Netw. Comput. Appl. 2021, 181, 103050. [Google Scholar] [CrossRef]
  147. Fortino, G.; Fotia, L.; Messina, F.; Rosaci, D.; Sarné, G.M.L. Trust and reputation in the internet of things: State-of-the-art and research challenges. IEEE Access 2020, 8, 60117–60125. [Google Scholar] [CrossRef]
  148. Fortino, G.; Messina, F.; Rosaci, D.; Sarné, G.M.L. Using blockchain in a reputation-based model for grouping agents in the Internet of Things. IEEE Trans. Eng. Manag. 2019, 67, 1231–1243. [Google Scholar] [CrossRef]
  149. Lin, X.; Li, J.; Wu, J.; Liang, H.; Yang, W. Making knowledge tradable in edge-AI enabled IoT: A consortium blockchain-based efficient and incentive approach. IEEE Trans. Ind. Inform. 2019, 15, 6367–6378. [Google Scholar] [CrossRef]
  150. Xu, X.; Zeng, Z.; Yang, S.; Shao, H. A novel blockchain framework for industrial IoT edge computing. Sensors 2020, 20, 2061. [Google Scholar] [CrossRef] [PubMed] [Green Version]
  151. Yeh, L.-Y.; Lu, P.J.; Huang, S.-H.; Huang, J.-L. SOChain: A privacy-preserving DDoS data exchange service over soc consortium blockchain. IEEE Trans. Eng. Manag. 2020, 67, 1487–1500. [Google Scholar] [CrossRef]
  152. Muñoz, R.; Vilalta, R.; Yoshikane, N.; Casellas, R.; Martínez, R.; Tsuritani, T.; Morita, I. Integration of IoT, transport SDN, and edge/cloud computing for dynamic distribution of IoT analytics and efficient use of network resources. IEEE J. Light. Technol. 2018, 36, 1420–1428. [Google Scholar] [CrossRef]
  153. P1916.1; Standard for Software Defined Networking and Network Function Virtualization Performance. Available online: https://sagroups.ieee.org/1916-1/ (accessed on 18 November 2021).
Figure 1. A DDoS attack scenario in IoT networks as a Botnet to target legitimate servers.
Figure 1. A DDoS attack scenario in IoT networks as a Botnet to target legitimate servers.
Sensors 22 01094 g001
Figure 2. The Chain of Transactions within Blockchain [29], (a). the architecture of Blockchain (b), and a sample Merkle Tree is also shown.
Figure 2. The Chain of Transactions within Blockchain [29], (a). the architecture of Blockchain (b), and a sample Merkle Tree is also shown.
Sensors 22 01094 g002
Figure 3. The signing and verification of messages (i.e., transaction data) in a Blockchain network.
Figure 3. The signing and verification of messages (i.e., transaction data) in a Blockchain network.
Sensors 22 01094 g003
Figure 4. Classification of the blockchain-based solutions to mitigate DDoS attacks in IoT.
Figure 4. Classification of the blockchain-based solutions to mitigate DDoS attacks in IoT.
Sensors 22 01094 g004
Table 1. Summary of literature works.
Table 1. Summary of literature works.
Referenced WorksExplanation of BlockchainSecurity Issues in IoTDDoS AttacksBenefits and Challenges of Combining IoT and BlockchainGeneral Defense Mechanisms against DDoS AttacksUsage of Blockchain in SecuritySolutions for DDoS Attacks in IoT
[20]YesYesNoYesNoNoNo
[94]Yes
[92]NoNo
[12]Yes
[95]Yes
[96]
[90]No
[97]Yes
[5]No
[98]NoNoYesNoYes
[4]
[15]
[99]
[100]
[102]YesNoYes
[103]No
[101]YesNo
Table 2. Distribution of research articles with various publishers.
Table 2. Distribution of research articles with various publishers.
ResourcesIEEE XploreElsevierScienceDirectSpringerProQuestACM
Conference32023815942952
Journals719 156 25
Books242002234521320
Early Access Articles100000
Magazines1000200
Webpages0000160
Connect010000
Survey Articiles0076000
Discussion001000
Editorials001000
Dissertations & Thesis0000200
Newsletter000006
Reports000000
Total
Total652203386602617833983
Excluded (Books, etc.)26201100345218862866
Included (Conf. Jour.)3919238315429771117
The excluded 2866 articles were Books, Reports, etc. Following is the breakdown of resultant 1117 research articles:
Blockchain-based Solutions = 34; Survey Articles = 12; Supporting Articles = 103; Remaining = 1117 − 149 = 968
Finally, 968 research articles were excluded from our repository that were not classified as Blockchain-based Solutions.
Table 3. Summary of distributed architecture based solutions.
Table 3. Summary of distributed architecture based solutions.
SolutionsWorking PrincipleDDoS Attack MitigationWeaknessesStrengths
PreventionDetectionReaction
[104]The systems are decentralised, and all the nodes share the ledger with redundancy data storage.YesNoNoNodes not under attack will be under heavy load.Utilise natural feature of Blockchain to mitigate DDoS attacks.
[105]Use the distributed structure of Blockchain to mitigate DDoS attacks.YesNoNoSpecific node under attack can not work.When DDoS attacks occur, the whole system continues to work.
[106]Uses the collaborative DDoS detection scheme utilising Blockchain and lightweight agents in IoT.YesYesYesDetails over the consensus algorithm on agents are missing, since these algorithms are supposed to be installed over limited resources hardware.The use of lightweight agents exchange outbound traffic information to identify possible victims of DDoS attacks and is governed by a Blockchain smart contract, which ensures the integrity of both the procedure and exchanged information.
Table 4. Summary of access management based solutions.
Table 4. Summary of access management based solutions.
SolutionsWorking PrincipleDDoS Attack MitigationWeaknessesStrengths
PreventionDetectionReaction
PKAM [107,108,109]Based on public key to manage access. Reject requests if the requester’s public key is not registered or unavailable.YesNoNoCannot prevent DDoS attacks if attackers use multiple public keys.Prevent DDoS attacks by limiting unauthorised access.
PUFAM [7,110]Use PUF to verify the authenticity of the IoT devices. All tampered, fake and cloned devices will be detected, which can prevent devices from becoming part of a botnet.YesNoNoNo experiments to prove the robustness against DDoS attacks.It is a lightweight access management solution which is suitable for an IoT environment.
Table 5. Summary of traffic control based solutions.
Table 5. Summary of traffic control based solutions.
SolutionsWorking PrincipleDDoS Attack MitigationWeaknessesStrengths
PreventionDetectionReaction
SDNTCB [112,113,114,115,116,117,118]Combine SDN and Blockchain to monitor traffic to detect DDoS attacks.YesYesYesDelay caused by processing of traffic is not calculated.Sound mechanism to mitigate DDoS attacks.
TCMRT [120,121]If the threshold of maximum transaction rate is exceeded, the node manager updates to prevent the node from continuously sending transactions to the target nodes.YesYesYesCan create too much traffic in the network.A lightweight mechanism to mitigate DDoS attacks.
TCVT [123]Verify outgoing transactions to prevent nodes from becoming part of botnets.YesNoNoLack of protection of smart contract.Does not utilise additional resources.
TCWM [124,125,126,127]A whitelisting mechanism is used to prevent DDoS attacks by filtering and eliminating malicious traffic.YesYesOnly [126]It is possible that illegal traffic complies with validation rules but perform harmful actions.It is very quick to verify the access traffic and filter the unwanted traffic.
Table 6. Summary of the Ethereum Platform based solutions.
Table 6. Summary of the Ethereum Platform based solutions.
SolutionsWorking PrincipleDDoS Attack MitigationWeaknessesStrengths
PreventionDetectionReaction
SSEP [128,129,130,131,132]Prevent attackers from sending too many service requests because of payment of transactions.YesNoNoNo mechanism for detecting and mitigating DDoS attacks.Use existing Ethereum platform to prevent DDoS attacks.
SEPTC [133,134,135]Combines the Ethereum platform and traffic control to mitigate DDoS attacks.YesYesYesDecrease in performance because of extra processing of data.Use maximum rate of transactions and white listing mechanisms.
SEPA [136,137,138,139]Combines the Ethereum platform with authorisation to prevent DDoS attacks.YesNoNoDo not consider detection and mitigation of DDoS attacks.Can also prevent malicious users from accessing the systems.
Table 7. List of acronyms and their explanation.
Table 7. List of acronyms and their explanation.
AcronymsExplanation
DDoSDistributed Denial of Service
IoTInternet of Things
IIoTIndustrial Internet of Things
IoAInternet of Anything
IoEInternet of Everything
SIoTSocial Internet of Things
WoTWeb of Things
IoMTInternet of Medical Things
SDIoTSoftware-Defined Internet of Things
SDIoT-EdgeSoftware-Defined Internet of Things and Edge
SDNSoftware Defined Networking
PoSProof of Stake
BFTByzantine Fault Tolerance
PoETProof of Elapsed Time
ECDSAElliptic Curve Digital Signature Algorithm
HTTPHyper Text Transfer Protocol
VoIPVoice over Internet Protocol
SHASecure Hash Algorithm
6LoWPANIPv6 over Low-Power Wireless Personal Area Networks
PKAMPublic Key based Access Management
PUFPhysically Unclonable Function based Access Management
PUFAMPUF based Access Management
SDNTCBSDN based Traffic Control via Blockchain
TCMRTTraffic Control based on the Maximum Rate of Transactions
TCVTTraffic Control based on Verification of Transactions
TCWMTraffic Control based on Whitelisting Mechanism
TCPTransmission Control Protocol
SYNSynchronise
DNSDomain Name System
CoAPConstrained Application Protocol
PoWProof of Work
DPoSDelegated-Proof-of-Stake
PoETProof of Elapsed Time
PoLProof of Luck
PoSpProof of Space
PBFTPractical Byzantine Fault Tolerance
ePBFTExcellent Practical Byzantine Fault Tolerance
PoLProof of Luck
CACertificate Authority
PKPublic Key
SCSmart Contracts
BTCBitcoin
ICMPInternet Control Message Protocol
SSEPSolutions Simply based on Ethereum Platform
SEPTCEthereum Platform with Traffic Control
SEPASolutions based on the Ethereum Platform with Authorization
TLSTransport Layer Security
CPUCentral Processing Unit
SSLSecure Sockets Layer
IPInternet Protocol
UDPUser Datagram Protocol
ICTInformation and Communication Technologies
ITUInternational Telecommunication Union
RFIDRadio Frequency Identification
Publisher’s Note: MDPI stays neutral with regard to jurisdictional claims in published maps and institutional affiliations.

Share and Cite

MDPI and ACS Style

Shah, Z.; Ullah, I.; Li, H.; Levula, A.; Khurshid, K. Blockchain Based Solutions to Mitigate Distributed Denial of Service (DDoS) Attacks in the Internet of Things (IoT): A Survey. Sensors 2022, 22, 1094. https://doi.org/10.3390/s22031094

AMA Style

Shah Z, Ullah I, Li H, Levula A, Khurshid K. Blockchain Based Solutions to Mitigate Distributed Denial of Service (DDoS) Attacks in the Internet of Things (IoT): A Survey. Sensors. 2022; 22(3):1094. https://doi.org/10.3390/s22031094

Chicago/Turabian Style

Shah, Zawar, Imdad Ullah, Huiling Li, Andrew Levula, and Khawar Khurshid. 2022. "Blockchain Based Solutions to Mitigate Distributed Denial of Service (DDoS) Attacks in the Internet of Things (IoT): A Survey" Sensors 22, no. 3: 1094. https://doi.org/10.3390/s22031094

APA Style

Shah, Z., Ullah, I., Li, H., Levula, A., & Khurshid, K. (2022). Blockchain Based Solutions to Mitigate Distributed Denial of Service (DDoS) Attacks in the Internet of Things (IoT): A Survey. Sensors, 22(3), 1094. https://doi.org/10.3390/s22031094

Note that from the first issue of 2016, this journal uses article numbers instead of page numbers. See further details here.

Article Metrics

Back to TopTop