Great article on Threatpost that summarizes how far we’ve come as a company dealing with Security Challenges 10 years ago. Tim Rains, from Microsoft Trustworthy Computing, does great job summarizing our challenges 10 years ago with dealing with Security. This article brings back some memories of the turmoil Slammer and Blaster created for our customers. The US Business Marketing Organization (USBMO) went through a lot of turmoil, trying to get the message out quickly. Since then thanks to folks like Steve Lipner and Eric Bidstrup, the Microsoft Security Development Lifecycle (SDL) was implemented and quickly adopted by our engineering culture here at Microsoft.
This February, I will have been at Microsoft 13 years. Working with our customers and partners to quickly handle incident response took some time to build up the capabilities. Today, this is something Microsoft Trustworthy Computing has gotten really good at. When both Slammer and Blaster hit in 2003, I remember how much effort it took to quickly respond and get help to our customers that needed it. I recall at the time, running 7X24 MSDN webcasts with information on dealing with Slammer and Blaster. We had Product Support Services engineers on the call answering and trough application sharing showing customers what to look for and steps to take.