architecture purporting to be dynamic, manageable,
cost-effective, adaptable, and seeking to be suitable
for the high-bandwidth, dynamic nature of today's
applications. The SDN architecture decouples
network control and forwarding functions, enabling
network control to be directly programmable and the
underlying infrastructure to be abstracted from
applications and network services. OpenFlow (OF)
(Lei, 2013) protocol is a foundational element for
building SDN solutions. OF separates the control
plane and data plane of network equipment, so as to
realize the flexible control of network traffic and
provide a good platform for the core network and
innovative applications. As a result, SDN offers
more new possibilities to solve network security
problems, including DDoS attacks. Software
Defined Security (SDS) is a branch of SDN
architecture in the network security, and it achieves
the separation and reconstruction of the data surface
and control surface, realizing modularity,
servitization and reusability.
In this paper, based on SDS architecture and
existing approaches, we propose a Dynamic DDoS
Protection Mechanism for WLAN, namely DDPM,
to solve the problem of diverse and complicated
DDoS attacks in WLAN effectively. According to
the types of DDoS attacks, DDPM deploys different
security strategies for the underlying network.
When outer-net data flow streams into the SDN
network, the system can judge the credibility of the
flow by its self-detection function, and then it will
make decision to handle the data flow according to
the credibility before server responds to it.
Compared with traditional DDoS protection
mechanisms, DDPM is a priori detection method,
which is more flexible and efficient.
2 DYNAMIC PROTECTION
MECHANISM BASED ON SDS
2.1 Architecture
DDPM inherits three main features of SDN
framework: centralized control, open interface and
virtualized network (Lei, 2013). The separation of
the data plane and the control plane atomizes the
functions and divides the system into five service
modules, which provide northern interface for the
invocation by higher layer. Meanwhile the
virtualized network shields the realization of devices
and thus reduces the difficulty of deployment.
Figure 1 shows the architecture of DDPM.
In Figure 1, DDPM is divided into five function
modules: Threat Detection module (TD), Credit
Evaluation module (CE), State Table module (ST),
Core Strategy module (CS) and Traffic
Identification module (TI).
Infrastructure
Layer
Thre at
Detection
module
Credit
Evaluation
module
Stat e
Table
module
Core
Strategy
module
Controller:
Floodlight,
Beacon,
Nox,
Traffic
Identificati
on module
Service
Layer
Control
Layer
SDN controller
OFSwitc h OFSwitch
OFRouter
Figure 1: Architecture of DDPM.
On the Infrastructure Layer, OFSwitch and
OFRouter, which are deployed in the SDN network,
maintain flow tables, device status and other
important information. When data flow streams into
the SDN network, these devices will specify
its action to forward or to discard.
On the Control Layer, SDN controller maintains
the underlying network topology, manages network
information, issues forwarding strategy and provides
northern interface to the higher layer. More
specifically, TI, which is deployed in the SDN
controller, processes the data flow that Infrastructure
Layer could not identify and then delivers the
underlying network information to Service Layer.
After receiving the developed strategy from Service
Layer, SDN controller transfers the strategy into
flow tables that specify data flow’s action and status
tables that maintain devices’ status.
Service Layer contains concrete implement of
DDPM. Firstly, TD detects the current status of
network according to the underlying network
information. Secondly, CE evaluates the credit level
of the data flow and preserves the values in the ST.
Actually, these three modules associated with each
other. Finally, CS will develop the newest strategy
according to the information from previous modules
if the system has detected the change of current
network status, and issue this strategy to the Control
Layer. Figure 2 shows the execution flow of DDPM.
2.2 Implement of the Modules
TI, as the function module of Control Layer,
provides intermediate hub for the Service Layer and
ISME 2016 - Information Science and Management Engineering IV
42