It only happens to the best of them. If you supersized your order at any restaurant, you are certain to gain more calories for your dollars. If you survived a supersized distributed denial of service (DDoS) attack, you are sure to be celebrated for your cyber security incident response plan. On Wednesday, February 28, 2018, GitHub.com endured a supersized DDoS cyberattack that lasted only ten minutes. The size of the tremor (wrong monstrosity) or the size of the cyberattack surpassed 1.2 terabit per second (Tb/s). This is rather newsworthy as the City of Atlanta’s network has been paralyzed by a ransomware attack that has lasted more than 10 days. City of Atlanta’s ransomware was detected at 5:40AM on Thursday, March 22, 2018. Newman reports that after intermittent outages, GitHub called Akamai Prolexic, which used an intermediary (DDoS appliance?) to route incoming and outgoing traffic. Perhaps the intermediaries were scattered throughout GitHub’s network? The traffic was sent to its scrubbing centers. After eight minutes, the threat actors grew weary and desisted. What are scrubbing centers? Scrubbing centers are alternative methods against DDoS with competing objectives, whereby an organization has to choose between “just in time protection,” “on demand protection,” or “always-on protection.” The unknown intermediary would have filtered- according to the White Paper-all traffic from the Internet which explains fatigued threat actors. Although this method is advantageous for immediate mitigation devices, there are bandwidth, latency and resource utilization limitations. The sources of the DDoS attack were memcached servers that consisted of several thousand autonomous endpoints according to Skottler. When multiple memcached servers are integrated with User Datagram Protocol (UDP) enabled, this type of cyberattack also is referred to an amplification attack. An advantage of using a memcached server is less overhead in establishing a Transmission Control Protocol (TCP) connection. Although GitHub.com thwarted the largest DDoS attack, there have been other notable DDoS attacks. Two of the five memorable DDoS attacks in 2017 were Electroneum- the mobile-based cryptocurrency- and Melbourne IT according to Bisson. Also, in 2016, DDoS attacks were common against Domain Name System (DNS) infrastructures.
Resources:
Bisson, D.”5 Notable DDoS Attacks of 2017.” 21 December 2017, Tripwire.com, https//www.tripwire.com/state-of-security/featured/5-notable-ddos-attacks-2017/. Accessed 07 April 2018.
City of Atlanta. “Ransomware Cyberattack Information.” 22 March 2018, City of Atlanta, https//www.atlantaga.gov/government/ransomware-cyberattack-information. Accessed 04 April 2018.
GitHub Inc., https//github.com/vz-risk/VCDB/issues/11182. Accessed 04 April 2018.
Levine, Alan. Giddyup! Gotta ride before that sun chases us off the wall. 25 July 2010. Flickr. https//www.flickr.com/photos/cogdog/. Accessed 04 April 2018.
Mallon, C. “Why Dwell Time Continues to Plague Organizations.” 10 May 2017, Crowdstrike.com, https//www.crowdstrike.com/blog/why-dwell-time-continues-to-plague-organizations/. Accessed 04 April 2018.
Newman, L. H. “GITHUB SURVIVED THE BIGGEST DDOS ATTACK EVER RECORDED.” 01 March 2018, Wired.com. https//www.wired.com/story/github-ddos-memcached/. Accessed 31 March 2018.
Skottler.”February 28th DDoS Incident Report.”01 March 2018. GitHub Engineering, https//githubengineering.com/ddos-incident-report/. Accessed 07 March 2018.
Siluk, S. “Largest DDoS Attack Ever Reported: Here’s What We Know.” 02 March 2018. CIO-Today.com, https//www.cio-today.com/article/index.php?story_id=1230048S72S3. Accessed 31 March 2018.
Tannam,E. “GitHub falls victim to the world’s largest DDoS attack: What you should know.” 02 March 2018, Siliconrepublic.com, https//www.siliconrepublic.com/enterprise/github-ddos-memcache-cyberattack. Accessed 31 March 2018.
“White Paper – Private Scrubbing Centers: Establishing Efficient, Effective and Flexible DDoS Defense.” 2015. RioRey, Inc., https//static1.squarespace.com/static/5548bab5e4b08ecb6652391c/t/56d7b2b859827e4e235710c1/1456976569091/Scrubbing+Center+WP_v1.2.pdf. Accessed 04 April 2018.