In 2014 a refrigerator was implicated in a spam attack involving the distribution of over 750,000 e-mails! The botnet had incoporated about 100,000 devices as part of the attack. This was framed as the first documented attack that involved Internet of Things (IoT) devices. In 2015, researchers exposed security holes in Wi-fi enabled Barbie dolls and Jeep Cherokees. Fast forward to 2016, and an attack that exploited IoT device vulnerabilities and poor network architecture resulted in major brands like Netflix andTwitter and others being severly impacted. This pattern shows that as long as vulnerabilities exist, and bad actors persist such attacks will likely continue to grow in frequency and impact. (You can read my colleague and DNS guru’s perspective on his blog entitled: How to Defend Against the Next DDoS Attack).
The impact of such attacks has grown from a nuisance (spam) to real bottom line impact – for companies that make their money on adverstising or e-commerce – network downtime translates to lost revenue immediately. As the use of such devices grows in segments like healthcare and mining the impact goes beyond money – it could impact human life! While one could argue that eliminating attacks is a myth, it is incumbent upon all of us to make sure that we use every possible avenue to prevent such attacks, detect them quickly when they do happen and are set up to respond rapidly when we do discover them.
On Wednesday, November 2nd, Infoblox’s Chief DNS Architect, Cricket Liu, will share his insights on the recent DDoS attack and discuss best practices during two webinars: one at 3 p.m. GMT (8 a.m. Pacific Time) and the second at 5 p.m. GMT (10 a.m. Pacific Time) entitled “Don’t Be the Next DDos Attack!”
Cricket will discuss:
- Best practices for deploying a DNS architecture
- The role DNS security plays in your network infrastructure
- The pitfalls you should avoid
He will continue the conversation with a Live TweetChat from 11:15-11:45am PDT. You can ask questions or follow the conversation by using the hashtag #DontBeNextDDoS.