TBDC_Threshold_based_DDoS_classifier_Distributed_Denial_of_Service__DDoS__threshold_based_mitigation_for_Software_Defined_Networking__SDN__in_healthca (1)
TBDC_Threshold_based_DDoS_classifier_Distributed_Denial_of_Service__DDoS__threshold_based_mitigation_for_Software_Defined_Networking__SDN__in_healthca (1)
Abstract—Although the nature of software defined networks the DDoS attacks restrict the patients data availability as
(SDN) of centralized controller (logically) makes it vulnerable well as the data flow in the network. The major objective
to various threats, they still can handle an escalating number of a DDoS attack is not only to breaching of data, it can
of these threats due to their decoupled control plane and data.
These attacks still affect the performance of the network causing restrict the user to access necessary information from a portal
a degradation of different key performance indicators (KPIs). also. The Cybersecurity and Infrastructure Security Agency
Healthcare systems is one of the major systems that get attacked (CISA) claims that identification of DDoS attacks is very
due to the sensitive nature of the data they contain either tricky as it can be performed virtually. The companies used
medical or financial, making them a popular target of diffident to handle different kinds of sensitive data are the major
types of attacks. With the huge variety of network architectures,
connected devices, possible attacks and threats, it becomes harder targets of this attack. The sensitive data can be modified by
to , identify and handle these threats in a proper time, which malicious intruders and false information may be injected into
leads to either huge delay or performance degradation or even the different data streams by a false node[3].
worse which is a successful attack, a proper way to predict and A medical record can contain a higher significant financial
classify an incoming threat is needed to help dealing with the value associated with credit card data. So, proper DDoS de-
incoming threats in time. Giving healthcare systems as a vital
example, in this paper we conduct a study for the effect of using tection and prevention mechanisms are necessary to tackle the
SDNs for DDoS, and the effect on different network KPIs with issues related to m-healthcare. Access control mechanisms like
different scenarios, and propose a threshold based technique to authentication, authorization, identification and accountability
classify the DDoS attacks in healthcare SDNs, aiming to block are highly needed to protect sensitive data, a typical SDN
the traffic that is considered a hazard as a DDos attack , then enabled architecture for healthcare systems is presented in
analysing the accuracy and the performance of the proposed
approach. Fig.2.
Index Terms—Software Defined Networking; Network Man- Apart from these security and privacy issues the technology
agement; Network Resilience; attack prediction; Distributed also suffers from the low bandwidth of the mobile network,
Denial of Service (DDoS); Healthcare. high cost for cellular network links, inadequate availability
of internet connections, and the heterogeneous platforms sup-
I. I NTRODUCTION ported by different mobile devices. These problems must be
Software-defined networking (SDN) is a promising solution addressed properly to develop a complete security solution of
that aims to simplify network management by separating the this technology with easy accessibility in real-life scenarios[4].
control plane from the packet forwarding plane. Network man- Our contribution in this paper can be summarized as follows.
agement decisions, such as packet forwarding, are decoupled First, we present a novel low complexity system designed
from packet forwarding devices (e.g., switch and router) and for healthcare systems, based on a threshold based DDoS
handled by an external, programmable, and logically central- Classifier (TBDC), that classifies the traffic in SDNs to detect
ized device called the SDN controller [1]. On the other hand, and mitigate possible DDoS attacks. Second, we provide a
devices in traditional networks are configured separately, using preliminary deployment of an emulated healthcare system
a vendor-specific command, which increases the complexity network and analyse the important KPIs. Finally, we apply
of network management and network innovations [2]. The DDoS attacks to the healthcare system network and compare
simplified SDN architecture of a typical data center is shown the results before and after applying our proposed system to
in Fig.1. detect and mitigate the DDoS attacks.
The main challenge of healthcare systems is the security The next parts of this paper is organized as follows. In Section
assurance of clinical and financial sensitive data.The most II, we present the related background and previous work.
sensitive issue here is data availability. Across the network, In section III, we introduce the main aspects of evaluating
Application layer
(Management Plane)
Northbound-API
Control layer
(Control Plane)
SDN Controllers
Southbound-API (OpenFlow)
Infrastructure layer
(Data Plane)
Programmable switches
Fig. 1: A typical three-tier data center architecture illustrating software-defined networking interfaces
our proposed approach, including the network topologies, the In server virtualization in particular, development has been
emulation environment and the performance metrics. Section rapid. Creating a new virtual server can be done via a ready-
IV presents the emulation and the evaluation results. Finally, made template and only takes a few seconds. But if (and this
Section V presents conclusions and suggested future work. is usually the case) this server is to speak out on a network,
this subnet must be created and firewall rules set for how this
II. BACKGROUND AND R ELATED W ORK subnet may communicate with other networks. Traditionally,
this is done by someone in the network team and automation
In this section we present a short review of related works
has not been as fast. The benefit of being able to quickly create
on SDN, Methods related to manage attack and Distributed
a virtual server is to some extent lost.
Denial of Service (DDoS) threats.
Another factor is scalability. Logically separating different
A. SDNs subnets is done today with the help of vlan. There is according
to the standard 4096 vlan and it is probably enough for a
SDN or Software Defined Network is a way to design typical company, but not for a cloud provider of platforms.
the infrastructure to allow system administrators, network The next problem is the layer two protocol ethernet. The
engineers and devoplers to manage and control the network reason why ethernet ”won” the battle for the local network
devices in a data center in a dynamic way using programmable against other technologies a few years ago is largely because
and open interfaces via the REST API. it is a simple technology and the hardware needed is cheap to
The main requirement for software-defined networks comes manufacture. But really, this protocol is poorly equipped for
from today’s need for dynamic, scalable, cost-effective and virtual environments where IP addresses move around between
flexible infrastructure in a data center, which avoids the tradi- different platforms and perhaps different data centers.
tional static, hardware-based and monolithic IT architectures
that are obsolete [5]. B. DDoS attacks
The software-defined architecture executes the control plan , There are different types of DDoS attacks c, from Smurfs
which controls and makes the decisions where the traffic goes, to Teardrops, to Pings of Death. Some of the most common
and the data path , which handles and sends the packages. DDoS attacks are:
The very idea behind sdn is not really new. The concept • ICMP (Ping) Flood.
of server virtualization is about laying a layer between the • SYN Flood.
physical server and the operating systems that execute there. • Ping of Death.
A similar idea exists when it comes to storage virtualization. • Slowloris.
It has now simply become the network’s turn to be virtualized. • NTP Amplification.
Nor is it particularly new. Operators have used technologies • HTTP Flood.
such as Multiprotocol Label Switching (MPLS) to be able • Zero-day DDoS Attacks.
to place customers’ networks on top of the operator’s own • Volume Based Attacks. Imperva counters these attacks
physical network [6]. by absorbing them with a global network of scrubbing
Healthcare Applications
SDN Controller
OpenFlow
Switches
centers that scale, on demand, to counter multi-gigabyte When the pandemic struck and more people started working
DDoS attacks. from home, health care also became a target. The combination
of different online services for booking and responding to tests
In the past, most DDoS attacks have been about harming the
and the widespread use of insufficiently protected IoT devices
affected company or organization by making one or more web
have contributed to a large number of healthcare activities
pages inaccessible. Now it is instead common for the attacker
being affected by DDoS attacks [8].
to demand a ransom to interrupt the attack. Another common
Devices that are not updated become tools for cybercrim-
approach is to use DDoS attacks as a pure distraction where
inals The recently discovered bot network ”Meris”, which
the IT departments are kept busy while the attackers step in
includes about 250,000 infected devices, has also become
with ransomware (hostage programs) or try to steal data.
a tool for DDoS attacks. Most of these devices are not
Considering the reporting from the media, authorities and computers but routers, switches, access points for Wi-Fi and
the security industry itself, it can in some cases be the other devices sold by one and the same Latvian company,
case that companies focus on one type of cyber threat at a MicroTik. Admittedly, MicroTik discovered and remedied the
time. Unfortunately, the reality is more complex than that. current vulnerability as early as 2018, but due to the nature
Companies have to deal with many parallel threats. It is of the devices, users are rarely in contact with MicroTik and
never possible to settle down and old approaches can easily the majority have not made the necessary updates either. This
come back in a partly new suit, comments Peter Gustafsson, in turn has made MicroTik’s devices a tool in the hands of
responsible for Barracuda Networks in the Nordic region [7]. cybercriminals. Although the DDoS attacks remind us of how
New type of attack does not require a large botnet Some complicated everyday life has become for IT security man-
of the companies that have recently been affected by DDoS agers, there are good opportunities to stop this type of attack
attacks are Bandwidth, VoIP.ms, Voip Unlimited and Voipfone. in time. Companies that work with a modern infrastructure in
So-called ”Black Storm attacks” are particularly dangerous for application and network security in combination with active
service providers in communications. These types of attacks do protection against DDoS attacks have very good opportunities
not require the attacker to use a large botnet and are therefore to handle attacks of this kind.
relatively easy to carry out. In a ”Black Storm attack”, the
attacker sends the User Datagram Protocol (UDP) request C. Previous work
to many devices and servers on a network. The request is By conducting a detailed survey for the existing work
”spoofed”, that is, disguised, in this case to look like it comes regarding DDoS attacks in SDNs, most of the focus is on
from other devices in the same network. developing DDoS attacks detecting techniques using different
The approach then triggers a kind of snowball effect that can SDN based architectures. These techniques mainly focus on
quickly knock out a service provider (CSP) with a storm of using SDN technology in different layers (mainly network,
internal data traffic. Although the method has so far only been application and transport layers) to detect and mitigate the
described in tests, companies should be prepared for attackers attacks. Although there is small focus on healthcare systems,
to strike for real as well. a lot of the approaches that uses different techniques can be
Wireless link
OpenFlow
Wired link
SDN Controller
H1
H17
1 Mbps 2 Mbps
H2
2 Mbps
OpenFlow H18
Switch 3 Medical workstation (Doctor)
OpenFlow
Switch 1
OpenFlow
H13 Switch 2 H19
Medical workstation
(Employee)
H14 H20
1
H15 Medical workstation) Laboratory(
H16
used for the suitable scenarios. The techniques varies in a A. Network Topology
wide spectrum, for example using cloud environment as in
[16] which focuses on analyzing the impact of DDoS attack Here we introduce a typical network topology that is used
in hybrid cloud, or Orchestrator–based architecture as in [17]. for healthcare systems as shown in Fig. 3 to study the behavior
The amount of work done is significantly high with the focus in the case of normal performance and the performance under
on using AI, machine learning, with different algorithms, DDoS attacks. In this topology, there are three OpenFlow
either to classify the traffic, detect possible attacks , or mitigate switches numbered as shown, all these switches are connected
them as in [18], [19], [20], [21]. to the SDN controller which is responsible for managing the
traffic flow, which include the forwarding rules. Communi-
cation between the SDN controller in the control plane and
switches in the forwarding plane will be through the OpenFlow
III. E VALUATION
protocol. Beside that, there are eighteen hosts representing
different clients that generate data traffic named either as
In this section we present our evaluation environment. This devices or workstations. The network includes two other hosts,
includes the network topology, the metrics used to measure the one is considered as patients database, and the other as the
performance, and the experimental tools and setup in details. patient portal server, receiving data traffic from the clients.
Wireless link
OpenFlow
Wired link
SDN Controller
Victim
H1
H17
1 Mbps 2 Mbps
H2
2 Mbps
OpenFlow H18
Switch 3 Medical workstation (Doctor)
OpenFlow
Switch 1
OpenFlow
H13 Switch 2 H19
Medical workstation
(Employee)
H14 H20
1
H15 Medical workstation) Laboratory(
H16
Packet Loss(pps)
100
60
75
40 50
20 25
0
0
0 25 50 75 100 125 150 175 200 0 10 20 30 40 50 60
Bytes per packet Time(s)
Fig. 5: Second Scenario: Distribution of samples by size (bytes per packet) Fig. 7: Packet loss analysis for the 2 scenarios vs the proposed approach
Normal Traffic 50
2.5
Normal + DDoS Traffic
TBDC Method 40
2.0
Throughput(kbps)
30
1.5
Delay(s)
20
1.0
10 Normal Traffic
0.5 Normal + DDoS Traffic
0 TBDC Method
0.0 0 10 20 30 40 50 60
0 10 20 30 40 50 60 Time(s)
Time(s)
Fig. 8: Throughput analysis for the 2 scenarios vs the proposed approach
Fig. 6: Delay analysis for the 2 scenarios vs the proposed approach