<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>How vulnerable are software applications?</title><link>http://blogs.msdn.com/somasegar/archive/2008/06/17/how-vulnerable-are-software-applications.aspx</link><description>In a June 2007 report , the U.S Government Accountability Office (GAO) described cybercrime as “having significant economic impacts and a threat to U.S. national security interests” and referenced a 2005 FBI survey estimating that U.S. businesses lost</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: How vulnerable are software applications?</title><link>http://blogs.msdn.com/somasegar/archive/2008/06/17/how-vulnerable-are-software-applications.aspx#8613333</link><pubDate>Wed, 18 Jun 2008 04:22:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8613333</guid><dc:creator>Mark Gordon</dc:creator><description>&lt;p&gt;Microsoft Security Intelligence... It appears, in my opinion, those words do not even belong in the same sentence. Microsoft is yet to prevent a virus written by some bored 13 year old kid with C compiler from infecting a &amp;nbsp;windows operating system, yet you try to convince us otherwise. &lt;/p&gt;
&lt;p&gt;That sounds real similar to the way you spin that pathetic excuse for a development tool kit codenamed Visual Studio as being better then Visual FoxPro and Visual Basic. &amp;nbsp;I suppose if a programmer enjoys writing 100's if not 1000's of lines of additional code (depending on the project) to get their work done then VS and .BLOAT are way better options then VFP or VB. Currently 80% of my applications are unforunately now developed in C# and .BLOAT and I'm yet to come across a single case where the VS application turned out to contain less code, provided the same level of performance and cheaper for my clients then a VB/SQL or VFP solution. What you are tell customers about VS is all smoke and mirrors. It is unforunate that so many developers are buying into your spin simply because they have NO experience with a &amp;quot;REAL&amp;quot; programming language and development studio which they can compare Visual Studio to. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Keep up the great work !&lt;/p&gt;
&lt;p&gt;Best Regards,&lt;/p&gt;
&lt;p&gt;.Mark&lt;/p&gt;
</description></item><item><title>应用软件有多脆弱？</title><link>http://blogs.msdn.com/somasegar/archive/2008/06/17/how-vulnerable-are-software-applications.aspx#8614894</link><pubDate>Wed, 18 Jun 2008 10:26:49 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8614894</guid><dc:creator>Joycode@Ab110.com</dc:creator><description>&lt;p&gt;[原文发表地址] : How vulnerable are software applications? [原文发表时间]: Tuesday, June 17, 2008 5:56 PM by Somasegar&lt;/p&gt;
</description></item><item><title>re: How vulnerable are software applications?</title><link>http://blogs.msdn.com/somasegar/archive/2008/06/17/how-vulnerable-are-software-applications.aspx#8615919</link><pubDate>Wed, 18 Jun 2008 14:28:49 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8615919</guid><dc:creator>O Dahle</dc:creator><description>&lt;p&gt;I know you at MS warns about &amp;quot;security by obscurity&amp;quot;, but I would like to address an aspect of this that often causes security problems when (web) applications are being installed and does not work. &lt;/p&gt;
&lt;p&gt;Often the error messages are on a generic form like &amp;quot;access denied&amp;quot;, &amp;quot;missing privilege&amp;quot; or similar. And what is done by the installation guy? - oh yes, a lot: Access to everyone. Run application as administrator. Allow all kind of scripts, etc, and finally: IT WORKS! And delivery is overdue so the removing of privileges is left to &amp;quot;another day&amp;quot;. So even if both OS, IIS and the application is secure by themselves, the result is not secure. &lt;/p&gt;
&lt;p&gt;I would like error messages like &amp;quot;Read access denied to &amp;lt;folder&amp;gt; for &amp;lt;user&amp;gt;&amp;quot;. You need privilege &amp;lt;privilege&amp;gt; to do operation &amp;lt;operation&amp;gt;. &lt;/p&gt;
&lt;p&gt;Bad error messages are in my opinion a sort of &amp;quot;security by obscurity&amp;quot;.&lt;/p&gt;
</description></item><item><title>re: How vulnerable are software applications?</title><link>http://blogs.msdn.com/somasegar/archive/2008/06/17/how-vulnerable-are-software-applications.aspx#8616262</link><pubDate>Wed, 18 Jun 2008 15:38:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8616262</guid><dc:creator>Eli Cohen</dc:creator><description>&lt;p&gt;Firstly may I quickly thank you and your team for such an amazing product. VS2008 with dot net and WPF is truly amazing!&lt;/p&gt;
&lt;p&gt;We understand that MS wants ISV's to develop apps that work in Partial Trust in order to improve the overall security of users. However, there are many features of WPF and dot net that make it extremely difficult to do so. Things like limited isolated storage space (0.5MB is really very small), XAML Serialization, drag and drop, even bitmaps effect do not work in Partial Trust. Our applications started out strictly only using Isolated Storage, not using the registry etc. in order that it would run in Partial Trust. Very early on in the development cycle it clearly did not make business sense for us to restrict ourselves in order that our desktop apps will run in Partial Trust.&lt;/p&gt;
&lt;p&gt;As ISV's using MS development tools, we look to MS for providing us with a framework that will make it easy for us to develop in Partial Trust. Looking forward ...&lt;/p&gt;
</description></item><item><title>re: How vulnerable are software applications?</title><link>http://blogs.msdn.com/somasegar/archive/2008/06/17/how-vulnerable-are-software-applications.aspx#8616444</link><pubDate>Wed, 18 Jun 2008 16:22:30 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8616444</guid><dc:creator>Muralikrishna Nalajala</dc:creator><description>&lt;p&gt;Hi Somasegar,&lt;/p&gt;
&lt;p&gt;Its a value information you have given on security terms.&lt;/p&gt;
&lt;p&gt;I read it but didnt understand much ,but it may help people who are already have knowledge about security models&lt;/p&gt;
</description></item><item><title>re: How vulnerable are software applications?</title><link>http://blogs.msdn.com/somasegar/archive/2008/06/17/how-vulnerable-are-software-applications.aspx#8616910</link><pubDate>Wed, 18 Jun 2008 17:59:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8616910</guid><dc:creator>Jeremy Gray</dc:creator><description>&lt;p&gt;I make a living day to day using MSFT technology, and do really appreciate the efforts the company is making in security and other areas, but I do take one issue with your post:&lt;/p&gt;
&lt;p&gt;Showing _disclosure_ trends of _operating systems_ on the left and _fixed_ trends of _database servers_ on the right is misleading at best.&lt;/p&gt;
&lt;p&gt;It is great that the operating systems have had progressively less disclosures, but says nothing about how vulnerable they are because you didn't show their fixed trends or outstanding counts.&lt;/p&gt;
&lt;p&gt;It is also great that SQL Server 2005 has had zero fixes, but again that says nothing about how vulnerable it is because you didn't show its disclosure trends or outstanding counts. It only says you've fixed nothing.&lt;/p&gt;
</description></item><item><title>re: How vulnerable are software applications?</title><link>http://blogs.msdn.com/somasegar/archive/2008/06/17/how-vulnerable-are-software-applications.aspx#8618304</link><pubDate>Thu, 19 Jun 2008 00:02:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8618304</guid><dc:creator>Somasegar</dc:creator><description>&lt;p&gt;Hi Jeremey, &lt;/p&gt;
&lt;p&gt;You make a good point. &amp;nbsp;I should have clarified that. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;The goal of the Microsoft SDL is to reduce the number and severity of vulnerabilities in software that is released to customers. Therefore, the relevant metric for measuring the success of the SDL are disclosed vulnerabilities. For more on security metrics see the following blog post on the SDL blog: &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/sdl/archive/2008/04/18/oh-no-security-metrics.aspx"&gt;http://blogs.msdn.com/sdl/archive/2008/04/18/oh-no-security-metrics.aspx&lt;/a&gt;. &lt;/p&gt;
&lt;p&gt;For Vista, the disclosed vulnerabilities graph shows that the SDL has been effective in reducing the number of vulnerabilities in Windows Vista compared Windows XP. This is the goal of the SDL and why this is a relevant metric here. For the complete analysis of Windows Vista one-year vulnerability report including patch events and fixes, Jeff Jones’ full report can be found here: &lt;a rel="nofollow" target="_new" href="http://blogs.technet.com/security/archive/2008/01/23/download-windows-vista-one-year-vulnerability-report.aspx"&gt;http://blogs.technet.com/security/archive/2008/01/23/download-windows-vista-one-year-vulnerability-report.aspx&lt;/a&gt;. &lt;/p&gt;
&lt;p&gt;For SQL Server, the title of the graph is a bit misleading. The information in the graph actually represents the number of vulnerabilities that were “disclosed and fixed” for SQL server. The complete analysis, along with a comparison to database software from other vendors, was performed by David Litchfield of NGS Software and can be found here: &lt;a rel="nofollow" target="_new" href="http://www.databasesecurity.com/dbsec/comparison.pdf"&gt;http://www.databasesecurity.com/dbsec/comparison.pdf&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;-somasegar&lt;/p&gt;
</description></item><item><title>re: How vulnerable are software applications?</title><link>http://blogs.msdn.com/somasegar/archive/2008/06/17/how-vulnerable-are-software-applications.aspx#8618308</link><pubDate>Thu, 19 Jun 2008 00:04:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8618308</guid><dc:creator>Somasegar</dc:creator><description>&lt;p&gt;Hi O Dahle,&lt;/p&gt;
&lt;p&gt;I agree with your comments on error messages. &amp;nbsp;The product teams look constantly at how we can have our error messages be more relevant and meaningful and as much as we have made progress, I know we can do more here.&lt;/p&gt;
&lt;p&gt;-somasegar&lt;/p&gt;
</description></item><item><title>Security Development Lifecycle Resources Help ISVs</title><link>http://blogs.msdn.com/somasegar/archive/2008/06/17/how-vulnerable-are-software-applications.aspx#8619164</link><pubDate>Thu, 19 Jun 2008 02:25:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8619164</guid><dc:creator>US ISV Developer Evangelism Team</dc:creator><description>&lt;p&gt;It turns out that less than 10% of vulnerabilities disclosed through June 2007 were targeted at Operating&lt;/p&gt;
</description></item><item><title>¿Cuán vulnerables son las aplicaciones de software?</title><link>http://blogs.msdn.com/somasegar/archive/2008/06/17/how-vulnerable-are-software-applications.aspx#8623205</link><pubDate>Fri, 20 Jun 2008 00:41:54 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8623205</guid><dc:creator>Blog de Soma en español</dc:creator><description>&lt;p&gt;Publicaci&amp;#243;n del ingl&amp;#233;s original Martes, 17 de junio de 2008 5:56 PM PST por Somasegar En un informe de&lt;/p&gt;
</description></item><item><title>re: How vulnerable are software applications?</title><link>http://blogs.msdn.com/somasegar/archive/2008/06/17/how-vulnerable-are-software-applications.aspx#8628028</link><pubDate>Sat, 21 Jun 2008 02:48:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8628028</guid><dc:creator>caywen</dc:creator><description>&lt;p&gt;Wow, thanks! Say, when is Windows 7 going to ship?&lt;/p&gt;
</description></item><item><title>re: How vulnerable are software applications?</title><link>http://blogs.msdn.com/somasegar/archive/2008/06/17/how-vulnerable-are-software-applications.aspx#8628843</link><pubDate>Sat, 21 Jun 2008 06:19:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8628843</guid><dc:creator>Ian Ellison-Taylor</dc:creator><description>&lt;p&gt;# re: How vulnerable are software applications? &lt;/p&gt;
&lt;p&gt;Eli, you make a good point about the current limitations in WPF when running in partial trust. We'll definitely look at how we can take enable more scenarios in future versions based on your suggestions.&lt;/p&gt;
&lt;p&gt;Thanks for feedback,&lt;/p&gt;
&lt;p&gt;Ian.&lt;/p&gt;
&lt;p&gt;(GM For WPF)&lt;/p&gt;
</description></item><item><title>Software Applications, the targets of vulnerabilities</title><link>http://blogs.msdn.com/somasegar/archive/2008/06/17/how-vulnerable-are-software-applications.aspx#8744108</link><pubDate>Thu, 17 Jul 2008 18:07:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8744108</guid><dc:creator>ASP.NET Debugging</dc:creator><description>&lt;p&gt;I was just reading Soma’s blog post How vulnerable are software applications? and it really makes you&lt;/p&gt;
</description></item></channel></rss>