Microsoft Admits DDoS Attack Is To Blame For Outages In June Outlook; Details Below
A Distributed Denial-of-Service (DDoS) assault previously caused an outage at Microsoft-owned Outlook, with up to 18,000 users reporting it at its height. This took place after the company posted a blog entry acknowledging the assault and providing technical details as well as advice on how to avoid such attacks in the future.
No indication is given in the blog post as to whether or not things are under control, nor is it stated if the assault ceased on its own. Twitter, on the other hand, asserts that the problem began on June 5 and was fixed the next day.
“Microsoft started to notice traffic surges against certain services at the beginning of June, which momentarily hampered availability. Microsoft said in a blog post that it “immediately launched an investigation and started tracking ongoing DDoS activity by the threat actor known as AStorm-1359.”
“These attacks are most likely based on access to many virtual private servers (VPS), as well as rented cloud infrastructure, open proxies, and DDoS tools,” the statement said. There is no evidence, nevertheless, that the client’s data has been accessed or hacked. Layer 7 was the target of this DDoS assault rather than Layer 3 or Layer 4.
What Safety Procedure Microsoft made a
In order to better shield customers from the consequences of such DDoS assaults, Microsoft enhanced layer 7 defences, including perfecting the Azure Web Application Firewall (WAF). Despite the fact that the majority of disruptions can be successfully controlled with the help of these tools and techniques, the tech giant continuously evaluates the efficacy of its hardening capabilities and integrates learning to enhance and perfect it.
Microsoft found that Storm-1359 has access to many tools and botnets that would enable the threat actor to launch DDoS attacks via a variety of open proxy infrastructures and cloud services. The business said, “Storm-1359 seems to be focused on disruption and notoriety.
