4 ms·
being null routed is really the only thing they can do. Then then undid it and they had to do it again. This wasn't a standard DDOS attack, which they normally
by downrightmike 3y ago
being null routed is really the only thing they can do. Then then undid it and they had to do it again. This wasn't a standard DDOS attack, which they normally handle just fine.
Good coverage of the event: Security Now! Podcast https://www.youtube.com/watch?v=ehfV7cRLkFE https://www.youtube.com/watch?v=ehfV7cRLkFE
- aidenn0 3y agoAbout 29minutes in is where it picks up after reading verbatim the status report from Drew.
- MaxBarraclough 3y agoDrew's second mention on Security Now, for what it's worth. Gibson quoted one of his blog posts back in September. https://www.grc.com/sn/sn-941.htm https://www.grc.com/sn/sn-941.htm
- iso8859-1 3y agoSubscribed and the unsubscribed shortly after when they mistook Greenland for Iceland (42m55s), Italy for ??? (43m42s) and then Equatorial Guinea for Chad (44m55s).
- AlexeyBelov 3y agoWhy do you think this DDoS attack is non-standard? What makes it stand out?
- tetha 3y agoI'll give the podcast a listen tomorrow :) But, even if you only have a single action available, isn't communication with the customer key? We've pulled customer systems offline, and parts of the customer were glad because we could provide information and help with handling harsh situations they had. And even if this isn't a 1% revenue customer, if they are receiving a DDOS-whopper you cannot happen, that would probably be a customer you want communication with. Even if the goal was just to figure out if there was glory in hosting them or to just fire them. Just null-routing and being unavailable seems unprofessional, though I know quite well how .. well-structured these acquire-everything hosting providers are internally. Doesn't change that this is bad customer service.