Okwuibe, Liyanage, Ahmad, and Ylianttila
392
functions can be placed at the network edge through programmable APIs in the edge.
This will enhance security of systems, such as C‐RAN and MEC in the edge.
16.6.2 SDN‐based Cloud Security Systems
The rise of SDN will change the dynamics around securing the data centers by offering
opportunities to research for enhanced security [43,44]. Cloud computing systems consist of various resources, which are shared among users with the help of hypervisors.
Hence, it provides an opportunity for adversaries to spread malicious traffic to erode
the performance, consume more resources or stealthily access resource of other
users. With the centralized and global view of network behavior and user activities,
SDN provides cost‐effective mechanisms to counter such threats. For example, the
CloudWatcher [45], working as an SDN application, uses the SDN control platform to
provide monitoring services to large and dynamic clouds. CloudWatcher provides
mechanisms to control network flows, in order to guarantee their inspection through
security systems. Similarly, the SnortFlow [46] uses the OpenFlow SDN model to provide intrusion detection and response systems for clouds. SnortFlow uses Snort‐based
Intrusion Prevention System (IPS) to detect intrusions and OpenFlow controller to
generate actions for the detected flows. For data centers, the Automated Malware
Quarantine (AMQ) [44] is an SDN‐based solution that detects potential threats and
isolates insecure network devices to stop them from adversely affecting the network.
Using two modules on top of the SDN controller, such as the Bot Hunter and
threat responder, the AMQ detects threats and isolates those threats using the
SDN controller.
By coupling NFV with SDN, the above solutions can be used for securing any type of
cloud, either in the edge or the data center. As shown in Figure 16.6, modules such as
the Bot Hunter in AMQ, or the CloudWatcher, can be deployed in the network edge
using the programmability offered by SDN and virtual function placement by NFV.
16.7 5GMEC, Cloud Security Research and Standardizations
The standards that will define 5G are yet to be outlined. The standardization of 5G is a
multi‐stakeholder process involving a huge numbers of operators, regulators, vendors,
policy‐makers and representatives of 5G users. However, research and standardization
are currently ongoing in several technology areas related to 5G. A more detailed description of standardization activities in 5G is contained in Chapter 2 of this book. In this
section, we discuss on standardization activities related to MEC and cloud computing:
● European Telecommunications Standards Institute (ETSI
9
): ETSI was created in 1988
to be the main standardization organization in ICT within Europe. It comprises of
several technical committees and Industry Specification Groups (ISGs). Its key
partners are 3GPP
10
and OneM2M
11
. ETSI holds a crucial position in both research
9 ETSI. http://www.etsi.org/
10 3rd Generation Partnership Project (3GPP). http://www.3gpp.org/about-3gpp
11 One M2M. http://www.onem2m.org/
392
functions can be placed at the network edge through programmable APIs in the edge.
This will enhance security of systems, such as C‐RAN and MEC in the edge.
16.6.2 SDN‐based Cloud Security Systems
The rise of SDN will change the dynamics around securing the data centers by offering
opportunities to research for enhanced security [43,44]. Cloud computing systems consist of various resources, which are shared among users with the help of hypervisors.
Hence, it provides an opportunity for adversaries to spread malicious traffic to erode
the performance, consume more resources or stealthily access resource of other
users. With the centralized and global view of network behavior and user activities,
SDN provides cost‐effective mechanisms to counter such threats. For example, the
CloudWatcher [45], working as an SDN application, uses the SDN control platform to
provide monitoring services to large and dynamic clouds. CloudWatcher provides
mechanisms to control network flows, in order to guarantee their inspection through
security systems. Similarly, the SnortFlow [46] uses the OpenFlow SDN model to provide intrusion detection and response systems for clouds. SnortFlow uses Snort‐based
Intrusion Prevention System (IPS) to detect intrusions and OpenFlow controller to
generate actions for the detected flows. For data centers, the Automated Malware
Quarantine (AMQ) [44] is an SDN‐based solution that detects potential threats and
isolates insecure network devices to stop them from adversely affecting the network.
Using two modules on top of the SDN controller, such as the Bot Hunter and
threat responder, the AMQ detects threats and isolates those threats using the
SDN controller.
By coupling NFV with SDN, the above solutions can be used for securing any type of
cloud, either in the edge or the data center. As shown in Figure 16.6, modules such as
the Bot Hunter in AMQ, or the CloudWatcher, can be deployed in the network edge
using the programmability offered by SDN and virtual function placement by NFV.
16.7 5GMEC, Cloud Security Research and Standardizations
The standards that will define 5G are yet to be outlined. The standardization of 5G is a
multi‐stakeholder process involving a huge numbers of operators, regulators, vendors,
policy‐makers and representatives of 5G users. However, research and standardization
are currently ongoing in several technology areas related to 5G. A more detailed description of standardization activities in 5G is contained in Chapter 2 of this book. In this
section, we discuss on standardization activities related to MEC and cloud computing:
● European Telecommunications Standards Institute (ETSI
9
): ETSI was created in 1988
to be the main standardization organization in ICT within Europe. It comprises of
several technical committees and Industry Specification Groups (ISGs). Its key
partners are 3GPP
10
and OneM2M
11
. ETSI holds a crucial position in both research
9 ETSI. http://www.etsi.org/
10 3rd Generation Partnership Project (3GPP). http://www.3gpp.org/about-3gpp
11 One M2M. http://www.onem2m.org/