GitHub, collaborative platform, has just been the target of an attack from hackers rather spectacular. Indeed for several days the infrastructure of the platform suffer record assaults a few days ago we spoke of 1.35 terabyte and yesterday there were peaks at 1.7 terabyte. Despite its record-breaking attacks, the collaborative site did rather well, having withstood the onslaught or failing for only a few minutes.
---DDoS attacks: forms of assault favored by hackers---
DDoS attacks are one of the hackers' favorite weapons, which they used at the beginning of the year against Dutch banks, for example. This is a form of intrusion that aims to overload the server, in order to make it unfit to operate. Indeed, the support servers of a website end up being out of service following an attack of this type. And the process is quite aggressive, since a multitude of requests are sent to them, that the servers can no longer satisfy. It is then that they go out and the site is no longer accessible before restarting. Surprisingly, this kind of attack does not really succeed when the sites are regularly updated like GitHub, especially since its servers benefit from security devices deemed efficient.
---GitHub: already targeted by an attack in 2015---
Indeed, the servers play the role of filters, generally effective. But something special, hackers have achieved their goal with GitHub, probably by attacking one of the loading devices of the site. By appropriating an IP address, the hackers were able to overcome the pitfalls related to the security system proposed by the server. But the hackers have struggled with this attack and have worked hard: with 1.35 terabyte of data received by the servers, it is an assault of a rare density. In the end, the site GitHub was not operational for about ten minutes last weekend and the peaks rose to 1.7 terabyte Monday. Several attack experts believe that this assault is the result of a smart device in place, as it was necessary to have a detailed knowledge of the web structure of GitHub to complete the attack. The previous intrusion took place in 2015. It was spread over five days.
