Featured Articles

AMD SVP John Byrne named turnaround exec of the year

AMD SVP John Byrne named turnaround exec of the year

Director of AMD’s PR Chris Hook has tweeted and confirmed later in a conversation with Fudzilla that John Byrne, Senior Vice…

More...
Shield Tablet 8 launching on Tuesday July 22nd

Shield Tablet 8 launching on Tuesday July 22nd

We knew the date for a while but as of right now we can confirm that Nvidia’s new Shield Tablet 8,…

More...
AMD confirms 20nm in 2015

AMD confirms 20nm in 2015

Lisa Su, Senior Vice President and Chief Operating Officer, AMD, has confirmed what we told you back in May 2014 – …

More...
AMD reports loss, shares tumble

AMD reports loss, shares tumble

AMD’s debt load is causing huge problems for the chipmaker -- this quarter it had another substantial loss. The tame Apple Press…

More...
AMD A8-7600 Kaveri APU reviewed

AMD A8-7600 Kaveri APU reviewed

Today we'll take a closer look at AMD's A8-7600 APU Kaveri APU, more specifically we'll examine the GPU performance you can…

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