Featured Articles

5th Generation Broadwell 14nm family comes in three lines

5th Generation Broadwell 14nm family comes in three lines

Intel's 5th Core processor family, codenamed Broadwell, will launch in three lines for the mobile segment. We are talking about upcoming…

More...
Broadwell Chromebooks coming in late Q1 2015

Broadwell Chromebooks coming in late Q1 2015

Google's Chromebook OS should be updating automatically every six weeks, but Intel doesn't come close with its hardware refresh schedule.

More...
New round of Nexus phone rumour kicks off

New round of Nexus phone rumour kicks off

Rumours involving upcoming Nexus devices are nothing uncommon, but this year there is a fair bit of confusion, especially on the…

More...
Nvidia officially launches the 8-inch Shield Tablet

Nvidia officially launches the 8-inch Shield Tablet

As expected and reported earlier, Nvidia has now officially announced its newest Shield device, the new 8-inch Shield Tablet. While the…

More...
Aerocool Dead Silence reviewed

Aerocool Dead Silence reviewed

Aerocool is well known for its gamer cases with aggressive styling. However, the Dead Silence chassis offers consumers a new choice,…

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