Featured Articles

Hands on: Nvidia Shield Tablet with Android 5.0

Hands on: Nvidia Shield Tablet with Android 5.0

We broke the news of Nvidia's ambitious gaming tablet plans back in May and now the Shield tablet got a bit…

More...
Nokia N1 Android tablet ships in Q1 2015

Nokia N1 Android tablet ships in Q1 2015

Nokia has announced its first Android tablet and when we say Nokia, we don’t mean Microsoft. The Nokia N1 was designed…

More...
Marvell launches octa-core 64-bit PXA1936

Marvell launches octa-core 64-bit PXA1936

Marvell is better known for its storage controllers, but the company doesn’t want to give up on the smartphone and…

More...
TSMC 16nm FinFET Plus in risk production

TSMC 16nm FinFET Plus in risk production

TSMC’s next generation 16nm process has reached an important milestone – 16nm FinFET Plus (16FF+) is now in risk production.

More...
Nvidia GTX 970 SLI tested

Nvidia GTX 970 SLI tested

Nvidia recently released two new graphics cards based on its latest Maxwell GPU architecture, with exceptional performance-per-watt. The Geforce GTX 970…

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