Featured Articles

Snapdragon 400 is Qualcomm’s SoC for watches, wearables

Snapdragon 400 is Qualcomm’s SoC for watches, wearables

We wanted to learn a bit more about Qualcomm's plans for wearables and it turns out that the company believes its…

More...
Qualcomm sampling 20nm Snapdragon 810

Qualcomm sampling 20nm Snapdragon 810

We had a chance to talk to Michelle Leyden-Li, Senior Director of Marketing, QCT at Qualcomm and get an update on…

More...
EVGA GTX 970 SC ACX 2.0 reviewed

EVGA GTX 970 SC ACX 2.0 reviewed

Nvidia has released two new graphics cards based on its latest Maxwell GPU architecture. The Geforce GTX 970 and Geforce GTX…

More...
Nvidia GTX 980 reviewed

Nvidia GTX 980 reviewed

Nvidia has released two new graphics cards based on its latest Maxwell GPU architecture. The Geforce GTX 970 and Geforce GTX…

More...
PowerColor TurboDuo R9 285 reviewed

PowerColor TurboDuo R9 285 reviewed

Today we will take a look at the PowerColor TurboDuo Radeon R9 285. The card is based on AMD’s new…

More...
Frontpage Slideshow | Copyright © 2006-2010 orks, a business unit of Nuevvo Webware Ltd.
Friday, 17 May 2013 10:49

Microsoft says invulnerable software impossible

Written by Nick Farrell



We did our best

Microsoft said that despite doing everything possible to make its products secure, it is proving impossible to create risk free software. The company said it has instituted processes intended to make its software secure and even opened up those processes for others to use, but it is still possible to knock its software over.

Speaking at Microsoft's Security Development Conference in San Francisco this week, Scott Charney, corporate vice president for Trustworthy Computing at Microsoft, said that Microsoft created Security Development Lifecycle processes, which made security intrinsic to development. This changed things from the early days when it was all about whack-a-mole. When a problem occurred patches would be issued and it was all done.

That changed in 2004, when Microsoft launched SDL and applied it to products connecting to the Internet, used in the enterprise, or used to store or process personal information. SDL was deployed with the goal of reducing vulnerabilities in products and integrated into the development lifecycle. The SDL process miffed product teams who were ready to move forward ahead with their products but got stalled by Microsoft's new security requirements.

It worked to a point. It reduced customer pain and dramatically reduced vulnerabilities, but it was still not possible to get vulnerabilities down to zero. Software's written by human beings and they make mistakes, he said. At the end of the day there will be a lot of “bad actors” out there who will do their best to turn over software.

Nick Farrell

E-mail: This e-mail address is being protected from spambots. You need JavaScript enabled to view it
blog comments powered by Disqus

 

Facebook activity

Latest Commented Articles

Recent Comments