{"id":42506,"date":"2021-10-12T11:08:01","date_gmt":"2021-10-12T11:08:01","guid":{"rendered":"http:\/\/icloud.pe\/blog\/?guid=972aabea032fd0293a218eecfff3cae5"},"modified":"2021-10-12T11:08:01","modified_gmt":"2021-10-12T11:08:01","slug":"microsoft-mitigated-largest-ever-2-4tbps-ddos-attack","status":"publish","type":"post","link":"https:\/\/icloud.pe\/blog\/microsoft-mitigated-largest-ever-2-4tbps-ddos-attack\/","title":{"rendered":"Microsoft mitigated ‘largest ever’ 2.4Tbps DDoS attack"},"content":{"rendered":"


\n Zach Marzouk<\/a><\/span>
\n <\/span><\/p>\n

\n
\n
12 Oct, 2021<\/span><\/div>\n<\/p><\/div>\n<\/div>\n

\n<\/a><\/p>\n

\n

Microsoft<\/a>\u00a0claims to have mitigated a record 2.4Tbps\u00a0DDoS<\/a>\u00a0attack targeting one of its\u00a0Azure<\/a>\u00a0customers in Europe during the last week of August.<\/p>\n

The company said the attack was140% larger\u00a0than than the highest attack bandwidth volume Microsoft recorded in 2020<\/a>\u00a0and higher than any\u00a0network<\/a>\u00a0volumetric event previously detected on Azure. It also surpasses\u00a0the previous largest\u00a0DDoS\u00a0attack,\u00a0which peaked at 2.3Tbps and was\u00a0directed at Amazon Web Services\u00a0(AWS) last year<\/a>.<\/p>\n

<\/p>\n

\nIt said the attack traffic originated from around 70,000 sources and from multiple countries in the\u00a0Asia-Pacific<\/a>\u00a0region, including\u00a0Malaysia, Vietnam,\u00a0Japan<\/a>, and China, as well as the\u00a0US<\/a>. The attack spanned over 10 minutes with very short-lived bursts, each ramping up in seconds to terabit volumes.<\/p>\n

The company monitored three main peaks, the first at 2.4Tbps, the second at 0.55Tbps, and the third at 1.7Tbps.<\/p>\n

Microsoft\u2019s attack mitigation lifecycle is orchestrated by its control plan logic that dynamically allocates mitigation resources to the most optimal locations, closest to the attack sources. This meant that the attack traffic, which originated in the Asia-Pacific region and the US, did not reach the customer region but was instead mitigated at the source countries.<\/p>\n

\u201cAzure\u2019s DDoS mitigation employs fast detection and mitigation of large attacks by continuously monitoring our\u00a0infrastructure<\/a>\u00a0at many points across the network,\u201d said Amir Dahan, senior programme manager at Azure Networking.<\/p>\n

\u201cWhen deviations from baselines are extremely large, our DDoS control plane logic cuts through normal detection steps, needed for lower-volume floods, to immediately kick-in\u00a0mitigation<\/a>. This ensures the fastest time-to-mitigation and prevents collateral damage from such large attacks.\u201d<\/p>\n

Dahan added that the customer did not suffer any impact or downtime, but if they had been running their own\u00a0data centre<\/a>\u00a0instead of using Azure, they would most probably have incurred extensive financial damage as well as other intangible costs.<\/p>\n

In 2020,\u00a0Google revealed its infrastructure absorbed a 2.5Tbps DDoS attack<\/a>\u00a0three years previous. The attack was the culmination of a six-month campaign launched by Chinese-backed hackers that used multiple methods of attack, which ultimately had no material impact. <\/p>\n<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"

Zach Marzouk<\/p>\n

12 Oct, 2021 <\/p>\n

Microsoft\u00a0claims to have mitigated a record 2.4Tbps\u00a0DDoS\u00a0attack targeting one of its\u00a0Azure\u00a0customers in Europe during the last week of August.
\nThe company said the attack was140% larger\u00a0than tha…<\/p>\n","protected":false},"author":654,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-42506","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/posts\/42506","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/users\/654"}],"replies":[{"embeddable":true,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/comments?post=42506"}],"version-history":[{"count":1,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/posts\/42506\/revisions"}],"predecessor-version":[{"id":42507,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/posts\/42506\/revisions\/42507"}],"wp:attachment":[{"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/media?parent=42506"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/categories?post=42506"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/tags?post=42506"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}