Distributed Denial of Services Attacks are a nuisance to all software services in the modern era which uses the internet as a platform to do business. I propose a simple solution to stop this kind of attack. The solution does not require any new hardware or revolutionary software. I provide a simple solution with simple software.
The Behavior of DDoS Attackers
First, we will understand what is the behavior of DDoS Attackers. DDoS Attackers all open a particular web page at the same point in time, making the web page unavailable to legitimate users. They continuously refresh a web page at very short intervals. They refresh the Password Page at very short intervals say more than 5 times continuously. We can consider these behaviors as DDoS attackers behaviors. Now we will see how to stop this kind of attack.
Authenticators Connected to Smart Phones
We are going to change the way we use web pages in a very little way. Let's get to the idea. We should use Authenticators in our Smart Phones for important Websites like Amazon Web Services, or an Authenticator for a group of small websites like news websites. If you want to use the internet for important websites like Amazon Web Services, first you should open the Authenticator on your Mobile. Then when you open the AWS website, A plain or very little resource page like a Google Home page will be displayed from the DNS, designed by AWS.
The first thing it will ask is your Mobile number. You should enter your Mobile Number. Upon receiving your mobile number, DNS will first check whether that Mobile Number's Authenticator Service is in open state. Otherwise, it will simply display a minimum resource page like "Open your Authenticator First". This is to make sure that anyone does not simply use some random Mobile Number and bug. If he bugs again and again with a random mobile number, his IP will be blocked for a while. This Service check will be universally done by the DNS for certain websites that avail this kind of service from DNS. DNS itself checks whether the Authenticator is open on your Mobile. After verifying that, DNS will ask you to enter the Authenticator Code. DNS will check the Authenticator code. If it is correct, DNS will direct the user to the website. Then the usual Web page service begins.
Penalize the DDoS Attackers
So, why would a DDoS attacker bother if he is not penalized? He will attack again and again. Isn't it that there is no loss for him? Let's penalize them. The Authenticator Service requires a caution deposit. Say Rs.1000. If you show the behavior of a DDoS attacker, your caution deposit will be gone. Let's say some X number of attackers show the behavior of DDoS on a particular website at a particular time. Is it not that the website is affected? Why don't we give half the penalized amount to them and the remaining to DNS? If they do that attack again, we will increase the caution deposit. Important conspirers who do this can be barred from using a particular service or the whole internet itself for a certain amount of period. We can even arrest them, or bring them before courts. We have their Mobile Numbers. Their Aadhaar Number is connected to their Mobile Number if they are in India. Their identity is with us.
Duration of Attacks
DDoS attack time will be calculated every 5- 10 minutes. If an attack happens in that time duration, all the DDoS attackers who show that behavior, not the ones who don't show that behavior, will be disconnected and penalized. All the resources will be freed and available in a maximum of 5-10 minutes. But the Penalized amount will be huge.

Comments
Post a Comment