Day 59: What next!

The features built into the architecture so far:
  • high sustainability of controllers when DoS attack occurs - due to switchover mechanism (high availability)
  • avoiding single point of failures in load balancer and master controller
  • dynamic learning of new flows
  • scalability 
  • synchronized controllers
Thus in case any DoS attack happens from switch to controller, the distributed controller architecture can sustain this attack for a very long time. This was the purpose of the architecture from when we conceived the idea of building it. What other features should we be implement?

  • an ML server - detection and decision regarding malicious packets (  watch out for Swati's blogs regarding this)
  • this ML server must receive packets from load balancer using any pub-sub model like kafka and zookeeper architecture
What other features can make our already existing architecture better?

As a further enhancement to the architectural design, I have intended to add a component to detect and mitigate DDoS attacks on the SDN network side. As we know, only when DDoS attack occurs from a malicious host to a victim host is when the FX switch also floods the controller with large amounts of packets. This is what causes DoS attack on the controller side.

Given the fact that the controller always knows about the hosts and switches connected to it, it has all information required to detect and mitigate any DDoS attack on SDN network. Thus we can build an Ryu program that identifies if any DoS attack is likely to occur on the controller. To mitigate the same, we can come up with strategies.

I am referring to this github repo to know more about detection and mitigation of DDoS attacks from controllers.

Refer to previous and next posts here.

Author: Shravanya
Co-author: Swati

Comments

Post a Comment

Popular posts from this blog

Day 12: Master Slave SDN Controller Architecture

In the previous post, I was struggling to figure out why all controllers can install flows in all switches irrespective of the code. Well, today the mystery is getting resolved. I found this book that explains beautifully the various roles that a controller can play. The three roles are: Equal : this happens by default all the equal controllers in a network that are connected to the switch can add and delete flows from it Slave: it has a read-only limitation to the switch openflow tables Master: very similar to the switch, but only 1 master can be connected to the switch at that point of time, and no other flows can intercept the communication between switch and master. I highly recommend you go through the above link to get a better picture. Since the default role of any controller is "Equal", we couldn't really differentiate between the three controller flows yesterday. But one good news from this is that we don't really need extensive coding to assi...
Read more

Day 50: Tcpreplay and tcpliveplay approach

Today we shall be exploring how to copy and redirect the OpenFlow packets to more than one controller from the load balancer. The load balancer is anyway sending the OpenFlow packets to one of the slave controllers - c1 or c2. The packets sent to these two controllers needs to be sent to master controller so the master controller can update the new flows added by c1 or c2 on the switches. This ensures synchronization between controllers. There are two implementation methods to achieve the same: Copy all packets generated from the load balancer to the controller side. Only the packets having destination IP address of c1 and c2 can be redirected to the master controller. Thus we can prevent the packets which already are reaching the master controller to be sent as duplicates Copy and redirect packets from the slave controllers - c1 and c2. We need not take care of duplicate packets reaching master controller. This will reduce the time taken to redirect packets. Since the second a...
Read more

Day 1: Understanding Ransomware and how to detect them?

Image
To start this journey, let’s begin at the basics and learn about what ransomwares are, what is the meaning of a ransomware attack, how have other people detected it so far? By learning the above, we will be in a position to analyze any ransomware attack and devise methods to detect, mitigate and prevent them. Definition: Ransomware is a type of malicious software from cryptovirology that threatens to publish the victim's data or perpetually block access to it unless a ransom is paid. To continue understanding and addressing the threats posed by ransomware, let us dig a little deeper. As the definition specifies, ransomware is a type of malicious software. Now, what is a malicious software? Definition: Malware (= Malicious + Software) is a software which is specifically designed to disrupt, damage, or gain authorized access to a computer system. These malwares (or simply dangerous content that can corrupt your system), can enter your system from various s...
Read more