Microsoft Trustworthy Computing Turns 10: What's Next
10 years after Bill Gates famously declared a security emergency within Microsoft, the stakes are much higher. 'TWC Next' will include a focus on cloud services such as Azure.

"Today, information and communications technology (ICT) underpins every aspect of our personal and professional lives," said Microsoft chief research and strategy officer Craig Mundie, in an e-mail to employees Thursday.
More Windows Insights
Webcasts
- Unlock the Value of Your Business Data: IBM's Integration Solution for .NET Environments
- Enhance Business Performance with Process Oriented Data Stewardship
White Papers
More >>Reports
More >>"While it is indisputable that ICT has transformed for the better how we live, society still confronts some long-standing and evolving challenges," Mundie said. "We must protect the security of the electrical power grid, the global financial system, and the telecommunications system, even as determined and persistent adversaries set their sights on these and other critical infrastructures."
[ Malicious attacks accounted for 40% of disclosed breaches last year. Learn more: Hack Attacks Now Leading Cause Of Data Breaches. ]
Gates fired off his Trustworthy Computing memo to employees on Jan. 15, 2002, amid a series of high-profile attacks on Windows computers and browsers in the form of worms and viruses like Code Red and "Anna Kournikova." Code Red, which used buffer overflows to exploit a weakness in Windows Server's Internet Information Services (IIS), infected more than 300,000 PCs.
The onslaught forced Gates to declare a security emergency within Microsoft, and halt all production while the company's 8,500 software engineers sifted through millions of lines of source code to identify and fix vulnerabilities. The hiatus cost Microsoft $100 million. "If we don't do this, people simply won't be willing--or able--to take advantage of all the other great work we do," Gates said in his memo. "We must lead the industry to a whole new level of Trustworthiness in computing."
To accomplish that, Gates identified three principles that Microsoft products were to be designed around--availability, security, and privacy. In practice, that meant placing security on an equal footing with usability and speed-to-market in Microsoft's development cycles.
"Getting your product to market first and killing Netscape was how you got rich at Microsoft. After the Gates memo came out, having your product have fewer top-class bugs and security vulnerabilities and less patches became as important a criterion for measuring the product managers as making an early shipping date," said Gartner research fellow John Pescatore.
As a result, Microsoft products like Visual Studio and Windows Server gained built-in security features for guarding against vulnerabilities caused by errors like stack overflow and were hardened with architectural changes, such as library randomization and formal Secure Development Lifecycle procedures, and the company made many of its own internal safeguards available to third parties.
Related Reading
| To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy. |
Subscribe to RSSResource Links
Related Webcasts
- Reduce Cost and Improve Manageability with IBM Windows Storage Server
- Unlock the Value of Your Business Data: IBM's Integration Solution for .NET Environments
- Data Protection and Microsoft Office 365: How Proofpoint Addresses Concerns of the Distributed Enterprise
- Enhance Business Performance with Process Oriented Data Stewardship
- Best Practices in SMB Desktop Virtualization
This Week's Issue
Free Print Subscription
SubscribeCurrent Healthcare Issue
- InformationWeek Healthcare CIO 25: Our second annual honor roll of the health IT leaders driving healthcare's transformation.
- EHR Unreadiness: Only a small percentage of physicians planning to apply for Meaningful Use funds have e-health record systems capable of achieving most of the requirements. .
- And much more!
- Read the Current Issue
Related Whitepapers
Featured Resource
This technical brief dives deep into migration recommendations and explains how to plan thoroughly, adopt a phased approach and who to ask for help.
Read Now












