<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>Roger's Security Blog : Incidents</title><link>http://blogs.technet.com/rhalbheer/archive/tags/Incidents/default.aspx</link><description>Tags: Incidents</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Summary of Bitlocker Discussions</title><link>http://blogs.technet.com/rhalbheer/archive/2009/12/11/summary-of-bitlocker-discussions.aspx</link><pubDate>Fri, 11 Dec 2009 09:54:36 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3299828</guid><dc:creator>rhalbh</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.technet.com/rhalbheer/comments/3299828.aspx</comments><wfw:commentRss>http://blogs.technet.com/rhalbheer/commentrss.aspx?PostID=3299828</wfw:commentRss><wfw:comment>http://blogs.technet.com/rhalbheer/rsscomments.aspx?PostID=3299828</wfw:comment><description>&lt;p&gt;Last week there was quite some discussion about “successful attacks” on Bitlocker. Those discussions are often quite interesting for me as they show sometimes that people are looking for one technical solution for all the problems. &lt;/p&gt;  &lt;p&gt;Bitlocker has a clear threat model it wants to protect you from. This is mainly the loss of your computer. If it is running and the attacker is admin – well Bitlocker cannot protect you. To quote a blog post of our Windows Security Team: &lt;em&gt;Our discussions of Windows BitLocker have always been to communicate that it &lt;b&gt;is intended to help protect data at rest&lt;/b&gt; (e.g. when the machine is powered off).&lt;/em&gt;&lt;/p&gt;  &lt;p&gt;So, if you want to read the whole post, it is definitely worth it: &lt;a href="http://windowsteamblog.com/blogs/windowssecurity/archive/2009/12/07/windows-bitlocker-claims.aspx" target="_blank"&gt;Windows BitLocker Claims&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;Roger&lt;/p&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3299828" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Security/default.aspx">Security</category><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Microsoft+Products/default.aspx">Microsoft Products</category><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Incidents/default.aspx">Incidents</category></item><item><title>“Black Screen of Death” Reports</title><link>http://blogs.technet.com/rhalbheer/archive/2009/12/01/black-screen-of-death-reports.aspx</link><pubDate>Tue, 01 Dec 2009 20:16:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3297651</guid><dc:creator>rhalbh</dc:creator><slash:comments>3</slash:comments><comments>http://blogs.technet.com/rhalbheer/comments/3297651.aspx</comments><wfw:commentRss>http://blogs.technet.com/rhalbheer/commentrss.aspx?PostID=3297651</wfw:commentRss><wfw:comment>http://blogs.technet.com/rhalbheer/rsscomments.aspx?PostID=3297651</wfw:comment><description>&lt;P&gt;Oh, wow – sometimes the power of social media, the blogs and the Internet can backfire. I guess in the meantime you have seen the claims by Prevx that approx. 80 Mio of PCs are affected by the &lt;EM&gt;Black Screen of Death&lt;/EM&gt; problems supposedly caused by our November Security Updates. This caused (and still causes) a huge wave of reports about that and one could feel that there is a really big problem out there. On one of the blogs you see a collection of the articles about that: &lt;A href="http://msmvps.com/blogs/donna/archive/2009/12/01/latest-microsoft-patches-cause-black-screen-of-death-microsoft-looking-into-windows-black-screen-of-death-problem.aspx" target=_blank mce_href="http://msmvps.com/blogs/donna/archive/2009/12/01/latest-microsoft-patches-cause-black-screen-of-death-microsoft-looking-into-windows-black-screen-of-death-problem.aspx"&gt;Latest Microsoft patches cause black screen of death, Microsoft looking into Windows 'black screen of death' problem&lt;/A&gt;. &lt;/P&gt;
&lt;P&gt;Now, there are different worries for me: One is that the post by Prevx as well as the title of the above mentioned blog post state it as a fact that our Security Updates caused that. Additionally Prevx makes a statement about the supposed size of the problem – this statement is approximately as good a guess as you could do by taking any random number between 1 and 480’000’000 (the approx. hitrate on Microsoft Update). And finally – and this is the biggest concern to me – customers are now holding back the deployment of our Security Update because of this.&lt;/P&gt;
&lt;P&gt;So, let’s get it straight: We have been looking into this problem (obviously). You can find the official statement quoted in the SeattlePI:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Microsoft is investigating reports that its latest release of security updates is resulting in system issues for some customers. &lt;/LI&gt;
&lt;LI&gt;Based on our investigation so far we can say that we're not seeing this as an issue from our support organization. &lt;/LI&gt;
&lt;LI&gt;The issues as described also do not match any known issues that have been documented in the security bulletins or KB articles. &lt;/LI&gt;
&lt;LI&gt;As always, we encourage customers to review the security bulletin and related KB articles and test and deploy security updates. &lt;/LI&gt;
&lt;LI&gt;If customers do encounter an issue with security updates, we encourage them to contact our Customer Service and Support group for no-charge assistance. Customers can contact CSS using the information at &lt;A href="http://support.microsoft.com/security" mce_href="http://support.microsoft.com/security"&gt;http://support.microsoft.com/security&lt;/A&gt;. &lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;If we add some additional meat to this: Up to now, we have no evidence at all to validate the concerns. Currently we do not have any support volumes to either support the claims or validate the presence of a growing concern. Additionally, our investigation has shown no evidence at all that our security updates nor the Malicious Software Removal Tool nor the non-security updates make the changes as claimed by the Previx reports.&lt;/P&gt;
&lt;P&gt;Looking at that, you should now make your risk assessment and decide which source you want to trust. For me, the ultimate source for information you should build your assessment on is neither Twitter nor your brother’s sister in law’s father's brother (unless he works for Microsoft’s security) but our website.&lt;/P&gt;
&lt;P&gt;UPDATED WITH MSRC BLOG POST: &lt;A href="http://blogs.technet.com/msrc/archive/2009/12/01/reports-of-issues-with-november-security-updates.aspx"&gt;http://blogs.technet.com/msrc/archive/2009/12/01/reports-of-issues-with-november-security-updates.aspx&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Roger&lt;/P&gt;
&lt;DIV style="TEXT-ALIGN: right; PADDING-BOTTOM: 4px; MARGIN: 0px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; PADDING-TOP: 4px" class=wlWriterHeaderFooter&gt;&lt;A href="http://digg.com/submit?url=http%3a%2f%2fblogs.technet.com%2frhalbheer%2farchive%2f2009%2f12%2f01%2fblack-screen-of-death-reports.aspx&amp;amp;title=%e2%80%9cBlack+Screen+of+Death%e2%80%9d+Reports" mce_href="http://digg.com/submit?url=http%3a%2f%2fblogs.technet.com%2frhalbheer%2farchive%2f2009%2f12%2f01%2fblack-screen-of-death-reports.aspx&amp;amp;title=%e2%80%9cBlack+Screen+of+Death%e2%80%9d+Reports"&gt;&lt;IMG style="BORDER-BOTTOM: 0px; BORDER-LEFT: 0px; BORDER-TOP: 0px; BORDER-RIGHT: 0px" title="Digg This" border=0 alt="Digg This" src="http://digg.com/img/badges/100x20-digg-button.png" width=100 height=20 mce_src="http://digg.com/img/badges/100x20-digg-button.png"&gt;&lt;/A&gt;&lt;/DIV&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3297651" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Microsoft+Products/default.aspx">Microsoft Products</category><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Incidents/default.aspx">Incidents</category></item><item><title>H1N1 (Swine) Flu Preparedness - Guide for Critical Infrastructure and Key Resources</title><link>http://blogs.technet.com/rhalbheer/archive/2009/09/16/h1n1-swine-flu-preparedness-guide-for-critical-infrastructure-and-key-resources.aspx</link><pubDate>Wed, 16 Sep 2009 08:33:30 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3281344</guid><dc:creator>rhalbh</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/rhalbheer/comments/3281344.aspx</comments><wfw:commentRss>http://blogs.technet.com/rhalbheer/commentrss.aspx?PostID=3281344</wfw:commentRss><wfw:comment>http://blogs.technet.com/rhalbheer/rsscomments.aspx?PostID=3281344</wfw:comment><description>&lt;p&gt;This morning I stumbled across a guide by the US Health &amp;amp; Human Services with regards to H1N1. Even though it did not catch much news lately I am not sure whether it is really over. Staying prepared it definitely not a bad thing. Even though it is US-centric, you should probably look into it: &lt;a title="http://flu.gov/professional/pdf/cikrpandemicinfluenzaguide.pdf" href="http://flu.gov/professional/pdf/cikrpandemicinfluenzaguide.pdf"&gt;http://flu.gov/professional/pdf/cikrpandemicinfluenzaguide.pdf&lt;/a&gt; it gives a good insightful view of the pandemic planning.&lt;/p&gt;  &lt;p&gt;Roger&lt;/p&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3281344" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Incidents/default.aspx">Incidents</category></item><item><title>Blaster’s Birthday</title><link>http://blogs.technet.com/rhalbheer/archive/2009/08/12/blaster-s-birthday.aspx</link><pubDate>Wed, 12 Aug 2009 12:03:56 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3272658</guid><dc:creator>rhalbh</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/rhalbheer/comments/3272658.aspx</comments><wfw:commentRss>http://blogs.technet.com/rhalbheer/commentrss.aspx?PostID=3272658</wfw:commentRss><wfw:comment>http://blogs.technet.com/rhalbheer/rsscomments.aspx?PostID=3272658</wfw:comment><description>&lt;p&gt;I guess you remember the day back in 2003: I was actually on vacation when I was called in back to the Microsoft offices as we had some strange things going on… It was the day of the Blaster breakout. The first time I personally had to deal with a very severe incident here at Microsoft. So we started to ramp up and tried to deal with what was happening out there. The biggest challenge was at the beginning to bridge the time between the beast hit our customers and everything was popping up in the press and the time we actually knew what was going on – which had to come from the Microsoft Security Response Centre back in Redmond. They did and amazing job but it took them some time as well. At the beginning we were blind and we did not have the same incident response processes back then as we have them today (and as we learned that they are necessary as a post-mortem of Blaster).&lt;/p&gt;  &lt;p&gt;So, the teams ramped up and we tried out best to have an incident response team together locally: Support, PR, Sales, me, and whoever we could draw from any not absolutely critical activity. We did our best to keep the hotlines up but this was a mission impossible. Within hours we were flooded… So, we developed some written guidance what to do (and had to translate that into three languages as I was working in Switzerland back then) but still this only helped partially. People started to call our offices in order to get help and we had an overflow to handle there. And last but not least we had consumers walking into our buildings telling the receptionist that they have this thing they heard in the news and that we have to help them to get rid of it – NOW!&lt;/p&gt;  &lt;p&gt;And then, after the first few days the customer visits started. I never experienced something like that. Customers were literally screaming at me, telling me what they think about Microsoft and that we did all wrong.&lt;/p&gt;  &lt;p&gt;Well, the whole industry came a long way – didn’t it? Trustworthy Computing had a big effect on how software is developed, Security Development Lifecycle has an industry-wide impact, the products themselves grew tremendously looking at how we defend them today… and the industry starts to understand that Patch Management is an important part of the Risk Management processes. Yes, I said deliberately “starts to understand” – there is still an amazing number of customers who still do not even think about patching.&lt;/p&gt;  &lt;p&gt;Looking back to 2003:&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;&lt;a href="http://support.microsoft.com/kb/826955"&gt;Virus alert about the Blaster worm and its variants&lt;/a&gt; on microsoft.com&lt;/li&gt;    &lt;li&gt;&lt;a href="http://news.cnet.com/2009-1002_3-5063226.html"&gt;Worm exploits a widespread Windows vulnerability&lt;/a&gt;&lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;and a lot more&lt;/p&gt;  &lt;p&gt;Roger&lt;/p&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3272658" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Incidents/default.aspx">Incidents</category></item><item><title>A few comments to yesterday’s Out of Band</title><link>http://blogs.technet.com/rhalbheer/archive/2009/07/29/a-few-comments-to-yesterday-s-out-of-band.aspx</link><pubDate>Wed, 29 Jul 2009 14:50:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3269035</guid><dc:creator>rhalbh</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/rhalbheer/comments/3269035.aspx</comments><wfw:commentRss>http://blogs.technet.com/rhalbheer/commentrss.aspx?PostID=3269035</wfw:commentRss><wfw:comment>http://blogs.technet.com/rhalbheer/rsscomments.aspx?PostID=3269035</wfw:comment><description>&lt;P&gt;It is pretty typical – these things often happen, when I have a really bad Internet connection ;-). However, I am back home and the connection is kind of better now…&lt;/P&gt;
&lt;P&gt;I guess you have seen and heard about the two out of band updates we shipped yesterday. They are kind of special and I would like to make sure you are doing everything necessary to protect you and your customers. Therefore – even before you read the bulletins – read the Advisory which goes with the updates from yesterday called &lt;A href="http://www.microsoft.com/technet/security/advisory/973882.mspx" target=_blank mce_href="http://www.microsoft.com/technet/security/advisory/973882.mspx"&gt;Vulnerabilities in Microsoft Active Template Library (ATL) Could Allow Remote Code Execution&lt;/A&gt;. Once you understand the problem space, get familiar with the two bulletins:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;A href="http://www.microsoft.com/technet/security/bulletin/ms09-035.mspx" target=_blank mce_href="http://www.microsoft.com/technet/security/bulletin/ms09-035.mspx"&gt;Vulnerabilities in Visual Studio Active Template Library Could Allow Remote Code Execution (969706)&lt;/A&gt; &lt;/LI&gt;
&lt;LI&gt;&lt;A href="http://www.microsoft.com/technet/security/bulletin/ms09-034.mspx" target=_blank mce_href="http://www.microsoft.com/technet/security/bulletin/ms09-034.mspx"&gt;Cumulative Security Update for Internet Explorer (972260)&lt;/A&gt; &lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;Now, the real problem is with the applications and controls developed by you. If you are a developer, make definitely sure, you read the corresponding article on MSDN: &lt;A href="http://msdn.microsoft.com/en-us/visualc/ee309358.aspx" target=_blank mce_href="http://msdn.microsoft.com/en-us/visualc/ee309358.aspx"&gt;Active Template Library Security Update for Developers&lt;/A&gt;. In there you have a very good flowchart helping you to understand whether your component might be vulnerable.&amp;nbsp; &lt;/P&gt;
&lt;P&gt;Last but definitely not least, ICASI was collaborating with &lt;STRONG&gt;Verizon Business to provide a free of charge scanning service&lt;/STRONG&gt; to help you figuring out, whether your component is vulnerable. you find the information here:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;A href="http://www.icasi.org/alerts.htm" target=_blank mce_href="http://www.icasi.org/alerts.htm"&gt;The ICASI Alert&lt;/A&gt; &lt;/LI&gt;
&lt;LI&gt;&lt;A href="http://codetest.verizonbusiness.com/" target=_blank mce_href="http://codetest.verizonbusiness.com/"&gt;The Verizon Business Scanner&lt;/A&gt; &lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;I hope this helps&lt;/P&gt;
&lt;P&gt;Roger&lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3269035" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Incidents/default.aspx">Incidents</category></item><item><title>SANS: Recent attacks and a false sense of security</title><link>http://blogs.technet.com/rhalbheer/archive/2009/07/16/sans-recent-attacks-and-a-false-sense-of-security.aspx</link><pubDate>Thu, 16 Jul 2009 22:47:35 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3265405</guid><dc:creator>rhalbh</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/rhalbheer/comments/3265405.aspx</comments><wfw:commentRss>http://blogs.technet.com/rhalbheer/commentrss.aspx?PostID=3265405</wfw:commentRss><wfw:comment>http://blogs.technet.com/rhalbheer/rsscomments.aspx?PostID=3265405</wfw:comment><description>&lt;p&gt;Well, as I am not really working, just a quick one: &lt;a title="http://isc.sans.org/diary.html?storyid=6787&amp;amp;rss" href="http://isc.sans.org/diary.html?storyid=6787&amp;amp;rss"&gt;http://isc.sans.org/diary.html?storyid=6787&amp;amp;rss&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;Roger&lt;/p&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3265405" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Incidents/default.aspx">Incidents</category></item><item><title>Distributed Denial of Service – and how it works</title><link>http://blogs.technet.com/rhalbheer/archive/2009/07/08/distributed-denial-of-service-and-how-it-works.aspx</link><pubDate>Wed, 08 Jul 2009 14:30:43 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3262158</guid><dc:creator>rhalbh</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/rhalbheer/comments/3262158.aspx</comments><wfw:commentRss>http://blogs.technet.com/rhalbheer/commentrss.aspx?PostID=3262158</wfw:commentRss><wfw:comment>http://blogs.technet.com/rhalbheer/rsscomments.aspx?PostID=3262158</wfw:comment><description>&lt;p&gt;I often get asked about Distributed Denial of Service (DDoS) attacks, how it works and what role we can play to prevent them.&lt;/p&gt;  &lt;p&gt;So, let me start with the first part of it: Our &lt;a href="http://www.halbheer.info/security/archive/2008/11/03/security-intelligence-report-v5-live.aspx"&gt;Security Intelligence Report version 5&lt;/a&gt; talked about the underground economy and actually explained what is happening before a DDoS takes place. Let’s recap this:&lt;/p&gt;  &lt;p&gt;Often it starts with the plan of a criminal to build a botnet. So, this malicious person goes to an underground marketplace, buys a piece of malware, a bot and a control server software. In addition, he/she might even be able to buy an initial distribution of the bot by letting somebody infect a webpage (which might be unpatched or have a weak password or somehow else being unsecured) or any other distribution channel for malware you might know of (e.g. social engineering):&lt;/p&gt;  &lt;p&gt;&lt;a href="http://blogs.technet.com/blogfiles/rhalbheer/WindowsLiveWriter/DistributedDenialofServiceandhowitworks_B9E6/original%5B1%5D.png" target="_blank"&gt;&lt;img style="border-right-width: 0px; display: block; float: none; border-top-width: 0px; border-bottom-width: 0px; margin-left: auto; border-left-width: 0px; margin-right: auto" title="original[1]" border="0" alt="original[1]" src="http://blogs.technet.com/blogfiles/rhalbheer/WindowsLiveWriter/DistributedDenialofServiceandhowitworks_B9E6/original%5B1%5D_thumb.png" width="500" height="688" /&gt;&lt;/a&gt; &lt;/p&gt;  &lt;p&gt;Now, the criminal is ready to go. He/she might own a certain number of PCs called Zombies. He can now offer his “services” on the same online black market, he initially purchased the malware from and might find “customers” like spammers, phishers, blackmailers or any other criminals:&lt;/p&gt;  &lt;p&gt;&lt;a href="http://blogs.technet.com/blogfiles/rhalbheer/WindowsLiveWriter/DistributedDenialofServiceandhowitworks_B9E6/original%5B2%5D.png" target="_blank"&gt;&lt;img style="border-right-width: 0px; display: block; float: none; border-top-width: 0px; border-bottom-width: 0px; margin-left: auto; border-left-width: 0px; margin-right: auto" title="original[2]" border="0" alt="original[2]" src="http://blogs.technet.com/blogfiles/rhalbheer/WindowsLiveWriter/DistributedDenialofServiceandhowitworks_B9E6/original%5B2%5D_thumb.png" width="500" height="561" /&gt;&lt;/a&gt; &lt;/p&gt;  &lt;p&gt;Here you see the reason why we leverage our &lt;a href="http://www.microsoft.com/security/malwareremove/default.aspx"&gt;Malicious Software Removal Tool&lt;/a&gt; to go after the largest botnets. It is all about protecting the ecosystem.&lt;/p&gt;  &lt;p&gt;So, I could basically rent a botnet to flood a web server with any kind of junk in order to take it offline – this is called a Distributed Denial of Service attack. I often compare this with spam – not for your Inbox but for your web server. The server is still up and running but kept busy sorting junk from legitimate traffic. &lt;/p&gt;  &lt;p&gt;There are often different motivations behind this:&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;Remember the times of Al Capone? Where the criminals attacked shops and then offered them a service to protect them? The same can happen here: A criminal runs a DDoS against your website and takes it down for a few minutes. Then he lets it come up again and tells you that he can protect you from these attacks – I would call this blackmailing. &lt;/li&gt;    &lt;li&gt;We often see such attacks with a political background. You see a conflict happening somewhere and one party (or both) is trying to take down the website of the other. &lt;/li&gt;    &lt;li&gt;Sometimes it is more a “I do not like you” background. Microsoft has been attacked as well from time to time…. &lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;So, if you want to know more about DDoS, I can recommend you two sites:&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;On our Technet site, there is an article called &lt;a href="http://technet.microsoft.com/en-us/library/cc722931.aspx"&gt;Distributed Denial-of-Service Attacks and You&lt;/a&gt;, which is worthwhile reading and shows you some basic protection as well. This article is not too new but it even gives you some advice on how to protect yourself. &lt;/li&gt;    &lt;li&gt;Wikipedia has a site, which can give you some history on it and shows you different types of the attacks: &lt;a href="http://en.wikipedia.org/wiki/DDoS#Distributed_attack"&gt;Denial-of-service attack&lt;/a&gt; &lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;I hope this helps and clarifies some questions. Otherwise, do not hesitate to get in touch with me&lt;/p&gt;  &lt;p&gt;Roger&lt;/p&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3262158" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Cybercrime/default.aspx">Cybercrime</category><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Incidents/default.aspx">Incidents</category></item><item><title>CDC and the Way They Communicate about the Swine Flu</title><link>http://blogs.technet.com/rhalbheer/archive/2009/05/01/cdc-and-the-way-they-communicate-about-the-swine-flu.aspx</link><pubDate>Fri, 01 May 2009 21:41:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3234107</guid><dc:creator>rhalbh</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/rhalbheer/comments/3234107.aspx</comments><wfw:commentRss>http://blogs.technet.com/rhalbheer/commentrss.aspx?PostID=3234107</wfw:commentRss><wfw:comment>http://blogs.technet.com/rhalbheer/rsscomments.aspx?PostID=3234107</wfw:comment><description>&lt;P&gt;This is impressive to me: I was looking at the website of the &lt;A href="http://www.cdc.gov/" target=_blank mce_href="http://www.cdc.gov/"&gt;Centers for Disease Control and Prevention&lt;/A&gt; and the way they use the Internet and social media to communicate about the Swine Flu. They use all the latest media like Widgets, websites for mobile browsers, buttons to add to your website, online videos, podcasts, eCards, RSS Feeds, Twitter etc…&lt;/P&gt;
&lt;P&gt;Read yourself: &lt;A href="http://www.cdc.gov/socialmedia/?s_cid=tw_eh_28" target=_blank mce_href="http://www.cdc.gov/socialmedia/?s_cid=tw_eh_28"&gt;Social Media Tools for Consumers and Partners&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;I think this is really impressive and innovative!&lt;/P&gt;
&lt;P&gt;Roger&lt;/P&gt;
&lt;DIV style="TEXT-ALIGN: left; PADDING-BOTTOM: 4px; MARGIN: 0px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; PADDING-TOP: 4px" class=wlWriterHeaderFooter&gt;&lt;A href="http://digg.com/submit?url=http%3a%2f%2fblogs.technet.com%2frhalbheer%2farchive%2f2009%2f05%2f01%2fcdc-and-the-way-they-communicate-about-the-swine-flu.aspx&amp;amp;title=CDC+and+the+Way+They+Communicate+about+the+Swine+Flu" mce_href="http://digg.com/submit?url=http%3a%2f%2fblogs.technet.com%2frhalbheer%2farchive%2f2009%2f05%2f01%2fcdc-and-the-way-they-communicate-about-the-swine-flu.aspx&amp;amp;title=CDC+and+the+Way+They+Communicate+about+the+Swine+Flu"&gt;&lt;IMG style="BORDER-BOTTOM: 0px; BORDER-LEFT: 0px; BORDER-TOP: 0px; BORDER-RIGHT: 0px" title="Digg This" border=0 alt="Digg This" src="http://digg.com/img/badges/100x20-digg-button.png" width=100 height=20 mce_src="http://digg.com/img/badges/100x20-digg-button.png"&gt;&lt;/A&gt;&lt;/DIV&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3234107" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Incidents/default.aspx">Incidents</category></item><item><title>Why you should not use P2P Windows 7 Builds</title><link>http://blogs.technet.com/rhalbheer/archive/2009/04/30/why-you-should-not-use-p2p-windows-7-builds.aspx</link><pubDate>Thu, 30 Apr 2009 15:36:38 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3233396</guid><dc:creator>rhalbh</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.technet.com/rhalbheer/comments/3233396.aspx</comments><wfw:commentRss>http://blogs.technet.com/rhalbheer/commentrss.aspx?PostID=3233396</wfw:commentRss><wfw:comment>http://blogs.technet.com/rhalbheer/rsscomments.aspx?PostID=3233396</wfw:comment><description>&lt;p&gt;This is not about piracy and not about leaks and not about…&lt;/p&gt;  &lt;p&gt;I am waiting for the new RC build as you are. I am running an intermediate build between Beta and RC and would love to upgrade all my machines (including my MediaCenter) to RC. However, I refrain from downloading it from any of the untrusted sources. The reason for this is pretty simple: You never know (and it is illegal).&lt;/p&gt;  &lt;p&gt;Years back (and I have told this story over and over again) we ran an event where we fixed PCs of consumers for free for a whole week. Pretty often, when we found an infected machine, we found P2P software on it. When we talked to the person owning the PC he/she usually told us the “my son/daughter installed that and uses it”. We know that P2P is one of the most dangerous source of malware.&lt;/p&gt;  &lt;p&gt;Read now, what happens with Windows 7: &lt;a href="http://www.slashgear.com/leaked-windows-7-rc-torrents-infected-with-trojan-2842048/"&gt;Leaked Windows 7 RC torrents infected with trojan&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;So, rather wait until you get access to the RC of Windows 7 – and so do I&lt;/p&gt;  &lt;p&gt;Roger&lt;/p&gt;&lt;div class="wlWriterHeaderFooter" style="text-align:left; margin:0px; padding:4px 0px 4px 0px;"&gt;&lt;a href="http://digg.com/submit?url=http%3a%2f%2fblogs.technet.com%2frhalbheer%2farchive%2f2009%2f04%2f30%2fwhy-you-should-not-use-p2p-windows-7-builds.aspx&amp;amp;title=Why+you+should+not+use+P2P+Windows+7+Builds"&gt;&lt;img src="http://digg.com/img/badges/100x20-digg-button.png" width="100" height="20" alt="Digg This" title="Digg This" border="0" style="border: 0" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3233396" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Microsoft+Products/default.aspx">Microsoft Products</category><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Incidents/default.aspx">Incidents</category></item><item><title>The Potential of Misinformation on the Web</title><link>http://blogs.technet.com/rhalbheer/archive/2009/04/29/the-potential-of-misinformation-on-the-web.aspx</link><pubDate>Wed, 29 Apr 2009 14:55:12 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3232449</guid><dc:creator>rhalbh</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.technet.com/rhalbheer/comments/3232449.aspx</comments><wfw:commentRss>http://blogs.technet.com/rhalbheer/commentrss.aspx?PostID=3232449</wfw:commentRss><wfw:comment>http://blogs.technet.com/rhalbheer/rsscomments.aspx?PostID=3232449</wfw:comment><description>&lt;p&gt;I am blogging, I am on &lt;a href="http://www.twitter.com/rhalbheer" target="_blank"&gt;Twitter&lt;/a&gt;, I have a &lt;a href="http://www.facebook.com/profile.php?id=689773925" target="_blank"&gt;Facebook-Account&lt;/a&gt; and many others. I am not always completely clear what the real business model and value of all the tools are but basically there is a lot of fun in it. Additionally information flows much faster and everybody has the possibility to express himself/herself the way he/she wants. However, there is a huge problem connected as well, which is misinformation and panic on the web.&lt;/p&gt;  &lt;p&gt;It can easily be that a theme becomes an “own-runner” (at least that’s the way we call it in German if something kind of gets a life on its own) and a lot of misinformation is spread via uncontrolled channels and this can lead to irresponsible behavior.&lt;/p&gt;  &lt;p&gt;I just read some articles about this when it comes to the Swine Flu. It does seem to be very serious (even though I am not a doctor) but we have to be very careful what we spread and how. It seems that the US &lt;a href="http://twitter.com/CDCemergency"&gt;Centers for Disease Control and Prevention &lt;/a&gt;has its own Twitter account and they distribute information through this channel. Let’s just for a second put the question aside whether it is really the CDC… they have authoritative information about the flu.&lt;/p&gt;  &lt;p&gt;If you search in Twitter for “swine flu” you find a lot of entries – can you trust them? I think that we need some normal vigilance if we deal with such information and be careful what we trust. These media have a huge potential to cause a panic because everybody trusts and copies from everybody.&lt;/p&gt;  &lt;p&gt;There is actually good articles on the web on this: &lt;a href="http://neteffect.foreignpolicy.com/posts/2009/04/25/swine_flu_twitters_power_to_misinform" target="_blank"&gt;Swine flu: Twitter's power to misinform&lt;/a&gt; and &lt;a href="http://www.infoworld.com/d/adventures-in-it/one-swine-flu-over-cuckoos-nest-078" target="_blank"&gt;One swine flu over the cuckoo's nest&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;Roger&lt;/p&gt;&lt;div class="wlWriterHeaderFooter" style="text-align:left; margin:0px; padding:4px 0px 4px 0px;"&gt;&lt;a href="http://digg.com/submit?url=http%3a%2f%2fblogs.technet.com%2frhalbheer%2farchive%2f2009%2f04%2f29%2fthe-potential-of-misinformation-on-the-web.aspx&amp;amp;title=The+Potential+of+Misinformation+on+the+Web"&gt;&lt;img src="http://digg.com/img/badges/100x20-digg-button.png" width="100" height="20" alt="Digg This" title="Digg This" border="0" style="border: 0" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3232449" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Incidents/default.aspx">Incidents</category></item><item><title>How much does a lost Laptop cost?</title><link>http://blogs.technet.com/rhalbheer/archive/2009/04/27/how-much-does-a-lost-laptop-cost.aspx</link><pubDate>Mon, 27 Apr 2009 15:14:25 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3231058</guid><dc:creator>rhalbh</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.technet.com/rhalbheer/comments/3231058.aspx</comments><wfw:commentRss>http://blogs.technet.com/rhalbheer/commentrss.aspx?PostID=3231058</wfw:commentRss><wfw:comment>http://blogs.technet.com/rhalbheer/rsscomments.aspx?PostID=3231058</wfw:comment><description>&lt;p&gt;I stumbled upon this study today commissioned by Intel and executed by Ponemon. They key findings were:&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;The average value of a lost laptop is $49,246. This value is based on seven cost components: replacement cost, detection, forensics, data breach, lost intellectual property costs, lost productivity and legal, consulting and regulatory expenses. &lt;/li&gt;    &lt;li&gt;What makes a lost laptop costly to a company is the potential for a data breach to occur. In the cases we studied, the occurrence of a data breach represents 80% of the cost. &lt;/li&gt;    &lt;li&gt;The second highest cost component is attributed to intellectual property loss. When the cost of a data breach is removed, intellectual property loss represents 59% of the total cost. &lt;/li&gt;    &lt;li&gt;The faster the company learns that a laptop is lost, the lower the average cost. If a company discovers the loss in the same day, the average cost is $8,950. If it takes more than one week, the average cost rises significantly to approximately $115,849. &lt;/li&gt;    &lt;li&gt;Lost productivity is not a significant cost to companies. When employees have down time due to losing their laptops, it represents only 1% of the total cost. &lt;/li&gt;    &lt;li&gt;While lost laptop costs appear to be correlated to position in an organization, the most senior level respondents do not experience the highest average cost. The average cost of a lost laptop for a senior executive is $28,449 and the highest average costs are for manager and director, $60,781 and $61,040 respectively. &lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;So, protecting the information on your Laptop is fundamental and could significantly reduce the cost of a stolen Laptop – say: Switch on Bitlocker…&lt;/p&gt;  &lt;p&gt;The whole study can be found here: &lt;a href="http://communities.intel.com/docs/DOC-3076" target="_blank"&gt;Cost of a Lost Laptop: A Study Conducted by the Ponemon Institute&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;Roger&lt;/p&gt;&lt;div class="wlWriterHeaderFooter" style="text-align:left; margin:0px; padding:4px 0px 4px 0px;"&gt;&lt;a href="http://digg.com/submit?url=http%3a%2f%2fblogs.technet.com%2frhalbheer%2farchive%2f2009%2f04%2f27%2fhow-much-does-a-lost-laptop-cost.aspx&amp;amp;title=How+much+does+a+lost+Laptop+cost%3f"&gt;&lt;img src="http://digg.com/img/badges/100x20-digg-button.png" width="100" height="20" alt="Digg This" title="Digg This" border="0" style="border: 0" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3231058" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Security/default.aspx">Security</category><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Cybercrime/default.aspx">Cybercrime</category><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Incidents/default.aspx">Incidents</category></item><item><title>Finjan reports world's largest Botnet</title><link>http://blogs.technet.com/rhalbheer/archive/2009/04/24/finjan-reports-world-s-largest-botnet.aspx</link><pubDate>Fri, 24 Apr 2009 12:45:44 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3230067</guid><dc:creator>rhalbh</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/rhalbheer/comments/3230067.aspx</comments><wfw:commentRss>http://blogs.technet.com/rhalbheer/commentrss.aspx?PostID=3230067</wfw:commentRss><wfw:comment>http://blogs.technet.com/rhalbheer/rsscomments.aspx?PostID=3230067</wfw:comment><description>&lt;div class="wlWriterHeaderFooter" style="float:right; margin:0px; padding:0px 0px 4px 8px;"&gt;&lt;script type="text/javascript"&gt;digg_url = "http://blogs.technet.com/rhalbheer/archive/2009/04/24/finjan-reports-world-s-largest-botnet.aspx";digg_title = "Finjan reports world\'s largest Botnet";digg_bgcolor = "#555555";digg_skin = "normal";&lt;/script&gt;&lt;script src="http://digg.com/tools/diggthis.js" type="text/javascript"&gt;&lt;/script&gt;&lt;script type="text/javascript"&gt;digg_url = undefined;digg_title = undefined;digg_bgcolor = undefined;digg_skin = undefined;&lt;/script&gt;&lt;/div&gt;&lt;p&gt;I guess you have read it in the meantime: There are a lot of reports out there, that Finjan found a Botnet affecting 1.9 Million computers. This is really bad – obviously. The press now started to cover this and I think we are already losing a little bit of focus in the discussion. I tried to understand what was going on based on the publically available information.&lt;/p&gt;  &lt;p&gt;To me it seems like the Botnet was leveraging known vulnerabilities in browsers to download malicious Javascript. It then started to spread on the infected machines and downloaded a Trojan called &lt;a href="http://www.microsoft.com/security/portal/Entry.aspx?Name=Trojan%3aWin32%2fProcesemes.A" target="_blank"&gt;Win32/Procesemes.A&lt;/a&gt; (The link leads you to our encyclopedia on this Trojan). We added the detection for this Trojan to our signature version 1.57.181.0 (so, since quite a while) and with that to all our products like Windows Live OneCare, Microsoft Forefront Client Security and &lt;a href="https://safety.live.com" target="_blank"&gt;Windows Live OneCare Safety Scanner&lt;/a&gt;. &lt;/p&gt;  &lt;p&gt;What does this tell us? Well, is it not the same story as always? There are three things that went wrong here:&lt;/p&gt;  &lt;ol&gt;   &lt;li&gt;Machines were unpatched (and not only IE)&lt;/li&gt;    &lt;li&gt;People are running as Admins&lt;/li&gt;    &lt;li&gt;The AV-signature was/is not up-to-date. We even remove the Trojan if you are infected…&lt;/li&gt; &lt;/ol&gt;  &lt;p&gt;So, the Botnet is huge and therefore dangerous and it is definitely a criminal activity to infect people’s machines. But there are ways to protect…&lt;/p&gt;  &lt;p&gt;As always, if you think that you are infected, report it to your local Law Enforcement. You may contact our support (free of charge for security incidents) on&amp;#160; &lt;a href="http://support.microsoft.com/security"&gt;http://support.microsoft.com/security&lt;/a&gt;. And then follow the standard steps of the “&lt;a href="http://www.microsoft.com/protect" target="_blank"&gt;Protect Your PC&lt;/a&gt;” guidance of enabling a firewall, applying all software updates and installing anti-virus and anti-spyware software. &lt;/p&gt;  &lt;p&gt;Roger&lt;/p&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3230067" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Security/default.aspx">Security</category><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Cybercrime/default.aspx">Cybercrime</category><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Incidents/default.aspx">Incidents</category></item><item><title>Security Intelligence Report: “Scareware” on the Raise</title><link>http://blogs.technet.com/rhalbheer/archive/2009/04/08/security-intelligence-report-scareware-on-the-raise.aspx</link><pubDate>Wed, 08 Apr 2009 09:50:58 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3223841</guid><dc:creator>rhalbh</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.technet.com/rhalbheer/comments/3223841.aspx</comments><wfw:commentRss>http://blogs.technet.com/rhalbheer/commentrss.aspx?PostID=3223841</wfw:commentRss><wfw:comment>http://blogs.technet.com/rhalbheer/rsscomments.aspx?PostID=3223841</wfw:comment><description>&lt;p&gt;You know that we release our &lt;a href="http://www.microsoft.com/sir" target="_blank"&gt;Security Intelligence Report&lt;/a&gt; twice an year: Today Version 6 is due. &lt;/p&gt;  &lt;p&gt;Let me try to give you an overview of the “highlights” of the report from my point of view:&lt;/p&gt;  &lt;p&gt;As I wrote in the title and as I blogged about this summer (&lt;a href="http://www.halbheer.info/security/archive/2008/08/29/" target="_blank"&gt;„Scareware“ on the Raise&lt;/a&gt;) one if the biggest growing threats we see is what I call “&lt;b&gt;Scareware&lt;/b&gt;” or what we call in the report “&lt;b&gt;Rogue Security Software&lt;/b&gt;”. I guess you know the feeling of visiting a website which then tells you that you are infected by malware and you should download a piece of software to protect you (or to clean your PC). Here you see a screenshot of how this can look like:&lt;/p&gt;  &lt;p&gt;&lt;a href="http://blogs.technet.com/blogfiles/rhalbheer/WindowsLiveWriter/SecurityIntelligenceReportScarewareonthe_10BFF/Rogue%20Security%20Software%20Screenshot_2.png"&gt;&lt;img style="border-right-width: 0px; display: block; float: none; border-top-width: 0px; border-bottom-width: 0px; margin-left: auto; border-left-width: 0px; margin-right: auto" title="Rogue Security Software Screenshot" border="0" alt="Rogue Security Software Screenshot" src="http://blogs.technet.com/blogfiles/rhalbheer/WindowsLiveWriter/SecurityIntelligenceReportScarewareonthe_10BFF/Rogue%20Security%20Software%20Screenshot_thumb.png" width="604" height="548" /&gt;&lt;/a&gt; &lt;/p&gt;  &lt;p&gt;So, we have seen this growing over the last three periods and therefore we decided to feature a focus section on this growing threat.&lt;/p&gt;  &lt;p&gt;A standard topic in the report is about &lt;strong&gt;vulnerability disclosures&lt;/strong&gt;. Here you find the chart you are used to if you read our Security Intelligence Report, my blog or heard me talking recently:&lt;/p&gt;  &lt;p&gt;&lt;a href="http://blogs.technet.com/blogfiles/rhalbheer/WindowsLiveWriter/SecurityIntelligenceReportScarewareonthe_10BFF/Figure%201%20with%20Title_2.png"&gt;&lt;img style="border-right-width: 0px; display: block; float: none; border-top-width: 0px; border-bottom-width: 0px; margin-left: auto; border-left-width: 0px; margin-right: auto" title="Figure 1 with Title" border="0" alt="Figure 1 with Title" src="http://blogs.technet.com/blogfiles/rhalbheer/WindowsLiveWriter/SecurityIntelligenceReportScarewareonthe_10BFF/Figure%201%20with%20Title_thumb.png" width="604" height="323" /&gt;&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;&lt;/p&gt;  &lt;p&gt;So, looking at the chart there is good and bad news:&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;The good news is that vulnerability disclosures (industry-wide) is decreasing. &lt;/li&gt;    &lt;li&gt;However, there are still more than 2500 vulnerabilities per 6 months (to be clear again: this is the whole industry, not us) &lt;/li&gt;    &lt;li&gt;And, roughly 52% of all the vulnerabilities where high severity ones! &lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;Looking at Microsoft’s vulnerabilities, this is the picture:&lt;/p&gt;  &lt;p&gt;&lt;a href="http://blogs.technet.com/blogfiles/rhalbheer/WindowsLiveWriter/SecurityIntelligenceReportScarewareonthe_10BFF/Figure%203%20with%20Title_2.png"&gt;&lt;img style="border-right-width: 0px; display: block; float: none; border-top-width: 0px; border-bottom-width: 0px; margin-left: auto; border-left-width: 0px; margin-right: auto" title="Figure 3 with Title" border="0" alt="Figure 3 with Title" src="http://blogs.technet.com/blogfiles/rhalbheer/WindowsLiveWriter/SecurityIntelligenceReportScarewareonthe_10BFF/Figure%203%20with%20Title_thumb.png" width="604" height="304" /&gt;&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;One thing I always mention, when I talk about this: If you are planning your Patch Management processes and you look at the figures above, make sure you cover your whole IT and not “just” Microsoft. In H2 2008 we had roughly 100 vulnerabilities out of 2500! So, think about patching the others as well (see &lt;a href="http://blogs.technet.com/rhalbheer/archive/2008/12/05/98-unpatched-and-i-am-one-of-them.aspx" target="_blank"&gt;98% unpatched – and I am one of them :(&lt;/a&gt;)&lt;/p&gt;  &lt;p&gt;There are a few other charts in the report like the percentage of vulnerabilities responsibly disclosed or attacks on applications which I do not want to put in there (there has to be a reason you read the report J). But one thing I want to take up here as it was so important in H2, which is the PDF attacks as this underlines the statement I made above about Patch Management. Look at the exploits by months targeting Adobe Acrobat Reader:&lt;/p&gt;  &lt;p&gt;&lt;img style="border-right-width: 0px; display: block; float: none; border-top-width: 0px; border-bottom-width: 0px; margin-left: auto; border-left-width: 0px; margin-right: auto" title="Figure 10 with Title" border="0" alt="Figure 10 with Title" src="http://blogs.technet.com/blogfiles/rhalbheer/WindowsLiveWriter/SecurityIntelligenceReportScarewareonthe_10BFF/Figure%2010%20with%20Title_thumb.png" width="604" height="267" /&gt;&lt;/p&gt;  &lt;p&gt;To be crystal clear with the graph above: This is not finger-pointing at Adobe. We were working closely together to address this and for both vulnerabilities there are updates available today. What I wanted to show you is that you have to extend your risk management to applications outside Microsoft.&lt;/p&gt;  &lt;p&gt;Another standing set of graphs are world heatmaps. There are three of them in this Security Intelligence Report:&lt;/p&gt;  &lt;p&gt;The “classic” malware infection rate based on the Malicious Software Removal Tool:&lt;/p&gt;  &lt;p&gt;&lt;img style="border-right-width: 0px; display: block; float: none; border-top-width: 0px; border-bottom-width: 0px; margin-left: auto; border-left-width: 0px; margin-right: auto" title="Infection Rate - World (600x344)" border="0" alt="Infection Rate - World (600x344)" src="http://blogs.technet.com/blogfiles/rhalbheer/WindowsLiveWriter/SecurityIntelligenceReportScarewareonthe_10BFF/Infection%20Rate%20-%20World%20(600x344)_thumb.jpg" width="604" height="348" /&gt;&lt;/p&gt;  &lt;p&gt;Even though we changed the way to determine where a computer is based (and therefore last report’s map cannot be compared with this one), EMEA does not look that bad. We have some challenges in the Middle East, Russias and – surprisingly to me – in Spain but the rest looks not great but ok.&lt;/p&gt;  &lt;p&gt;But there is more. This time we look at the source of the malware based on infected websites and where they are hosted:&lt;/p&gt;  &lt;p&gt;&lt;a href="http://blogs.technet.com/blogfiles/rhalbheer/WindowsLiveWriter/SecurityIntelligenceReportScarewareonthe_10BFF/Malware%20World%20(600x342)_2.jpg"&gt;&lt;img style="border-right-width: 0px; display: block; float: none; border-top-width: 0px; border-bottom-width: 0px; margin-left: auto; border-left-width: 0px; margin-right: auto" title="Malware World (600x342)" border="0" alt="Malware World (600x342)" src="http://blogs.technet.com/blogfiles/rhalbheer/WindowsLiveWriter/SecurityIntelligenceReportScarewareonthe_10BFF/Malware%20World%20(600x342)_thumb.jpg" width="604" height="346" /&gt;&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;Here we have quite some green spots – which is good. It is interesting to see that Russia and Spain are red again here…&lt;/p&gt;  &lt;p&gt;And last but not least the heatmap on where phishing sites are hosted:&lt;/p&gt;  &lt;p&gt;&lt;a href="http://blogs.technet.com/blogfiles/rhalbheer/WindowsLiveWriter/SecurityIntelligenceReportScarewareonthe_10BFF/Phishing%20World%20(600x341)_2.jpg"&gt;&lt;img style="border-right-width: 0px; display: block; float: none; border-top-width: 0px; border-bottom-width: 0px; margin-left: auto; border-left-width: 0px; margin-right: auto" title="Phishing World (600x341)" border="0" alt="Phishing World (600x341)" src="http://blogs.technet.com/blogfiles/rhalbheer/WindowsLiveWriter/SecurityIntelligenceReportScarewareonthe_10BFF/Phishing%20World%20(600x341)_thumb.jpg" width="604" height="345" /&gt;&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;If you take a different angle and look at it from a Windows perspective with regards to malware infection, it once more shows the progress we made with the different OSs:&lt;/p&gt;  &lt;p&gt;&lt;a href="http://blogs.technet.com/blogfiles/rhalbheer/WindowsLiveWriter/SecurityIntelligenceReportScarewareonthe_10BFF/Figure%2014%20with%20Title%20(600x317)_2.jpg"&gt;&lt;img style="border-right-width: 0px; display: block; float: none; border-top-width: 0px; border-bottom-width: 0px; margin-left: auto; border-left-width: 0px; margin-right: auto" title="Figure 14 with Title (600x317)" border="0" alt="Figure 14 with Title (600x317)" src="http://blogs.technet.com/blogfiles/rhalbheer/WindowsLiveWriter/SecurityIntelligenceReportScarewareonthe_10BFF/Figure%2014%20with%20Title%20(600x317)_thumb.jpg" width="604" height="321" /&gt;&lt;/a&gt; &lt;/p&gt;  &lt;p&gt;This re-enforces the message I am delivering as often as possible: If I could give you one single advice from security person to security person (I am not measured on quota), this would be “stay on the latest version of your software – everywhere”. This includes Patch Management as well as Lifecycle management. Jus think about every piece of software you have (including embedded systems), think about when it was designed and then think about the threat landscape back then… Do you really have to think twice then?&lt;/p&gt;  &lt;p&gt;If you want to hear Vinny Gullotto (General Manager, Microsoft Malware Protection Center) talk about the Security Intelligence Report, you can look at and interview he did with Tim Rains: &lt;a href="http://go.microsoft.com/fwlink/?LinkId=147941"&gt;Vinny and Tim show - SIR Volume 6 &lt;/a&gt;.&lt;/p&gt;  &lt;p&gt;So, this and much more you can find in our &lt;a href="http://www.microsoft.com/sir" target="_blank"&gt;Security Intelligence Report&lt;/a&gt;. Download it and have fun!&lt;/p&gt;  &lt;p&gt;Roger&lt;/p&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3223841" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Security/default.aspx">Security</category><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Cybercrime/default.aspx">Cybercrime</category><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Microsoft/default.aspx">Microsoft</category><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Incidents/default.aspx">Incidents</category><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Critical+Infrastructure+Protection/default.aspx">Critical Infrastructure Protection</category><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Consumer/default.aspx">Consumer</category></item><item><title>Conficker – Are you infected?</title><link>http://blogs.technet.com/rhalbheer/archive/2009/04/03/conficker-are-you-infected.aspx</link><pubDate>Fri, 03 Apr 2009 16:00:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3222011</guid><dc:creator>rhalbh</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/rhalbheer/comments/3222011.aspx</comments><wfw:commentRss>http://blogs.technet.com/rhalbheer/commentrss.aspx?PostID=3222011</wfw:commentRss><wfw:comment>http://blogs.technet.com/rhalbheer/rsscomments.aspx?PostID=3222011</wfw:comment><description>&lt;P&gt;I just found this pretty clever website which bases its statement with regards to your possible Conficker infection on the information whether you are able to access certain websites:&lt;/P&gt;
&lt;P&gt;&lt;A title=http://www.joestewart.org/cfeyechart.html href="http://www.joestewart.org/cfeyechart.html" mce_href="http://www.joestewart.org/cfeyechart.html"&gt;http://www.joestewart.org/cfeyechart.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Pretty clever&lt;/P&gt;
&lt;P&gt;Roger&lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3222011" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Incidents/default.aspx">Incidents</category></item><item><title>Conficker.D and April 1st</title><link>http://blogs.technet.com/rhalbheer/archive/2009/03/28/conficker-d-and-april-1st.aspx</link><pubDate>Sat, 28 Mar 2009 11:59:39 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3219318</guid><dc:creator>rhalbh</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.technet.com/rhalbheer/comments/3219318.aspx</comments><wfw:commentRss>http://blogs.technet.com/rhalbheer/commentrss.aspx?PostID=3219318</wfw:commentRss><wfw:comment>http://blogs.technet.com/rhalbheer/rsscomments.aspx?PostID=3219318</wfw:comment><description>&lt;p&gt;Will the Internet world end on April 1st? This is at least the impression I got from reading the press in the last couple of days. It seems that some story spun off and started to develop a life of its own.&lt;/p&gt;  &lt;p&gt;What is really going to happen on April 1st? I quote the blog of our colleagues over at the Microsoft Malware Protection Center:&lt;/p&gt;  &lt;p&gt;&lt;em&gt;So what can we expect on April 1, 2009?&amp;#160; Based on the relatively small number of Conficker.D-infected machines, we believe it’s doubtful that we might experience anything out of the ordinary on April 1.&amp;#160; We will however, just as we normally do, take action on anything unusual that might arise from this.&amp;#160; To remain protected, please ensure that your systems are patched with MS08-067, keep your security software signatures updated, and clean any systems you identify that are infected with any variant of Conficker.&lt;/em&gt;&lt;/p&gt;  &lt;p&gt;As I wrote earlier in my blog: Your focus should be deploy MS08-067 (if you have not done so yet) and clean your systems (if they are infected by Conficker) and, please, do not focus on any “end of the world” theories at the moment.&lt;/p&gt;  &lt;p&gt;If you need additional information, please consult our different websites:&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;Microsoft Conficker guidance page for IT Professionals and those focused on security in the enterprise: &lt;a href="http://www.microsoft.com/conficker"&gt;http://www.microsoft.com/conficker&lt;/a&gt;. &lt;/li&gt;    &lt;li&gt;Microsoft Conficker guidance page for consumers and home users: &lt;a href="http://www.microsoft.com/protect/computer/viruses/worms/conficker.mspx"&gt;http://www.microsoft.com/protect/computer/viruses/worms/conficker.mspx&lt;/a&gt;.&lt;/li&gt;    &lt;li&gt;The Microsoft Malware Protection Center (MMPC) encyclopedia page for the Conficker family of malware: &lt;a href="http://www.microsoft.com/security/portal/Entry.aspx?name=Win32/Conficker"&gt;http://www.microsoft.com/security/portal/Entry.aspx?name=Win32/Conficker&lt;/a&gt; (especially focus on the “Analysis” section).&lt;/li&gt;    &lt;li&gt;The Microsoft Malware Protection Center blog: &lt;a href="http://blogs.technet.com/mmpc/"&gt;http://blogs.technet.com/mmpc/&lt;/a&gt;. &lt;/li&gt;    &lt;li&gt;The Microsoft Security Response Center Blog: &lt;a href="http://blogs.technet.com/msrc/"&gt;http://blogs.technet.com/msrc/&lt;/a&gt;. &lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;Enjoy the weekend&lt;/p&gt;  &lt;p&gt;Roger&lt;/p&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3219318" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/rhalbheer/archive/tags/Incidents/default.aspx">Incidents</category></item></channel></rss>