<?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>Jeff's InfoSec Blog : Information Security</title><link>http://blogs.technet.com/jeffnew/archive/tags/Information+Security/default.aspx</link><description>Tags: Information Security</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Vulnerability analysis using search tools</title><link>http://blogs.technet.com/jeffnew/archive/2005/04/06/403416.aspx</link><pubDate>Thu, 07 Apr 2005 02:52:51 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:403416</guid><dc:creator>jeffnew</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.technet.com/jeffnew/comments/403416.aspx</comments><wfw:commentRss>http://blogs.technet.com/jeffnew/commentrss.aspx?PostID=403416</wfw:commentRss><description>&lt;P&gt;Interesting article:&amp;nbsp; &lt;A href="http://www.windowsnetworking.com/kbase/WindowsTips/WindowsXP/AdminTips/Security/GoogleYourselfToIdentifySecurityHoles.html" target=_blank&gt;&lt;FONT color=#006629&gt;Google Yourself to Identify Security Holes&lt;/FONT&gt;&lt;/A&gt;&amp;nbsp;by Tony Bradley.&amp;nbsp; His point is that security people should be using Google and the discussed tools as one facet of a vulnerability analysis program.&amp;nbsp; &lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=403416" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/jeffnew/archive/tags/Information+Security/default.aspx">Information Security</category></item><item><title>First open O/S, now open BIOS?</title><link>http://blogs.technet.com/jeffnew/archive/2005/04/06/403415.aspx</link><pubDate>Thu, 07 Apr 2005 00:54:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:403415</guid><dc:creator>jeffnew</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/jeffnew/comments/403415.aspx</comments><wfw:commentRss>http://blogs.technet.com/jeffnew/commentrss.aspx?PostID=403415</wfw:commentRss><description>&lt;P&gt;Sorry, I just can't get behind this:&amp;nbsp;&lt;A href="http://news.com.com/Battle+brews+over+unlocking+PC+secrets/2100-1016_3-5654272.html"&gt;Battle brews over unlocking PC secrets&lt;/A&gt;.&amp;nbsp; The PC industry has suffered for not having trusted mechanisms for identifying computers and locking down digital rights.&amp;nbsp; I read the article and I still don't see Stallman's point.&amp;nbsp; Then I read his &lt;A href="http://www.fsf.org/news/freebios.html"&gt;manifesto&lt;/A&gt; and I really don't get it.&amp;nbsp; GNU has come up with some good stuff in the past, and in a previous life I used to use and contribute to that effort.&amp;nbsp; But this seems to be ideology taken to the extreme.&amp;nbsp; Since the typical modern mobo allows users to flash their BIOS rather than remove and replace the chip, suddenly it should be treated differently?&amp;nbsp; Presumably this includes video cards as well, that have extensive (and flash-able) code on the card.&amp;nbsp; &lt;/P&gt;
&lt;P&gt;It's not really a battle, more of a tempest in a teapot.&lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=403415" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/jeffnew/archive/tags/Information+Security/default.aspx">Information Security</category></item><item><title>How do we fight spyware when no one can agree what it is?</title><link>http://blogs.technet.com/jeffnew/archive/2005/04/04/403418.aspx</link><pubDate>Mon, 04 Apr 2005 19:49:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:403418</guid><dc:creator>jeffnew</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/jeffnew/comments/403418.aspx</comments><wfw:commentRss>http://blogs.technet.com/jeffnew/commentrss.aspx?PostID=403418</wfw:commentRss><description>&lt;P&gt;Ahh, the wonderful world of information security in the United States, where the threat of litigation can keep holes open and spyware active.&amp;nbsp; eWeek has had a couple of articles this week on this topic.&amp;nbsp; In&amp;nbsp;&lt;A href="http://www.eweek.com/article2/0,1759,1781753,00.asp"&gt;&lt;FONT color=#006629&gt;The Chaotic World of Defining Spyware&lt;/FONT&gt;&lt;/A&gt;&amp;nbsp;they discuss issues that CA has with companies that are fighting being labeled as spyware.&amp;nbsp; In &lt;A href="http://www.eweek.com/article2/0,1759,1777775,00.asp"&gt;&lt;FONT color=#006629&gt;Big Security Guns Should Aim Carefully at Adware, Spyware&lt;/FONT&gt;&lt;/A&gt;&amp;nbsp;there's a discussion of Symantec's scoring system versus Microsoft's behavior-based approach documented in a recent &lt;A href="http://www.microsoft.com/athome/security/spyware/software/analysis.mspx" target=_blank&gt;&lt;FONT color=#006629&gt;white paper&lt;/FONT&gt;&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;There is money to be made in spyware and the bottom-feeders that are using spyware and "adware" are going to be very aggressive at resisting being labeled as such.&amp;nbsp; You can see this in the Microsoft white paper, where the targets are labeled "potentially unwanted software" rather than spyware.&amp;nbsp; &lt;/P&gt;
&lt;P&gt;It's all just semantics.&amp;nbsp; When you install something on my PC that I don't explicitly want and ask for, you're a bad person and need to be dealt with harshly.&amp;nbsp;&lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=403418" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/jeffnew/archive/tags/Information+Security/default.aspx">Information Security</category></item><item><title>7 computer security tips for students</title><link>http://blogs.technet.com/jeffnew/archive/2005/03/29/403419.aspx</link><pubDate>Wed, 30 Mar 2005 04:02:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:403419</guid><dc:creator>jeffnew</dc:creator><slash:comments>39</slash:comments><comments>http://blogs.technet.com/jeffnew/comments/403419.aspx</comments><wfw:commentRss>http://blogs.technet.com/jeffnew/commentrss.aspx?PostID=403419</wfw:commentRss><description>&lt;P&gt;My group didn't write this... that is, I don't think we did, although this may have come out of our Consumer team.&amp;nbsp; But it is pretty good, basic advice for students that are heading off to school with their new laptops.&amp;nbsp; &lt;/P&gt;
&lt;P&gt;&lt;A href="http://www.microsoft.com/athome/security/children/backtoschool.mspx"&gt;&lt;FONT color=#006629&gt;School is in: 7 computer security tips for students&lt;/FONT&gt;&lt;/A&gt;&lt;BR&gt;&lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=403419" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/jeffnew/archive/tags/Information+Security/default.aspx">Information Security</category></item><item><title>New! IPSec Guidance from Microsoft</title><link>http://blogs.technet.com/jeffnew/archive/2005/03/28/403421.aspx</link><pubDate>Mon, 28 Mar 2005 18:43:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:403421</guid><dc:creator>jeffnew</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/jeffnew/comments/403421.aspx</comments><wfw:commentRss>http://blogs.technet.com/jeffnew/commentrss.aspx?PostID=403421</wfw:commentRss><description>&lt;P&gt;My team just released a new security guide:&amp;nbsp; &lt;A href="http://www.microsoft.com/technet/security/topics/architectureanddesign/ipsec/default.mspx" target=_blank&gt;&lt;FONT color=#006629&gt;Server &amp;amp; Domain Isolation Using IPSec and Group Policy&lt;/FONT&gt;&lt;/A&gt;.&amp;nbsp; This soluton, aimed at enterprise IT Pros, is focused on how you can use IPSec and Group Policy to secure the data connections between systems.&amp;nbsp; One of the key threats that this can mitigate is the rogue computer, infected with a worm, that gets connected to a corporate wired network and, even without authentication,&amp;nbsp;receives an IP address and attempts to find an infect other systems.&amp;nbsp; &lt;/P&gt;
&lt;P&gt;Please let me know what you think!&lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=403421" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/jeffnew/archive/tags/Information+Security/default.aspx">Information Security</category></item><item><title>The Trustworthy Computing Security Development Lifecycle</title><link>http://blogs.technet.com/jeffnew/archive/2005/03/28/403422.aspx</link><pubDate>Mon, 28 Mar 2005 18:31:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:403422</guid><dc:creator>jeffnew</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/jeffnew/comments/403422.aspx</comments><wfw:commentRss>http://blogs.technet.com/jeffnew/commentrss.aspx?PostID=403422</wfw:commentRss><description>&lt;P&gt;If you're wondering how Microsoft bakes security into its software development practices, this paper (by one of the co-authors of "Writing Secure Code") takes you through the process.&amp;nbsp; This is far more than a guide for individual developers; it goes through the organization stucture and processes necessary to make this work for large software development projects.&amp;nbsp; 
&lt;P&gt;Link: &lt;A href="http://msdn.microsoft.com/security/default.aspx?pull=/library/en-us/dnsecure/html/sdl.asp"&gt;&lt;FONT color=#006629&gt;MSDN Security Developer Center: The Trustworthy Computing Security Development Lifecycle&lt;/FONT&gt;&lt;/A&gt;&lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=403422" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/jeffnew/archive/tags/Information+Security/default.aspx">Information Security</category><category domain="http://blogs.technet.com/jeffnew/archive/tags/Privacy/default.aspx">Privacy</category></item><item><title>Automagically isolating Internet worms</title><link>http://blogs.technet.com/jeffnew/archive/2005/03/07/403423.aspx</link><pubDate>Mon, 07 Mar 2005 19:53:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:403423</guid><dc:creator>jeffnew</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.technet.com/jeffnew/comments/403423.aspx</comments><wfw:commentRss>http://blogs.technet.com/jeffnew/commentrss.aspx?PostID=403423</wfw:commentRss><description>&lt;P&gt;A &lt;A href="http://research.microsoft.com/research/pubs/view.aspx?tr_id=788" target=_blank&gt;&lt;FONT color=#006629&gt;paper&lt;/FONT&gt;&lt;/A&gt; from &lt;A href="http://research.microsoft.com/" target=_blank&gt;&lt;FONT color=#006629&gt;Microsoft Research&lt;/FONT&gt;&lt;/A&gt;&amp;nbsp;(MSR), first published last summer, is getting &lt;A href="http://www.eweek.com/article2/0,1759,1772663,00.asp" target=_blank&gt;&lt;FONT color=#006629&gt;new interest &lt;/FONT&gt;&lt;/A&gt;after MSR's internal TechFest last week.&amp;nbsp; The idea is that hosts would analyze traffic hitting them and automatically broadcast alerts.&amp;nbsp; While false negatives can mean that many hosts will not detect the worm, doing this across a large group of machines means that some hosts will detect it and start broadcasting the &lt;EM&gt;self-certifying alerts&lt;/EM&gt;.&amp;nbsp; Of course there are a ton of issues with this approach but the authors have done a good job of going through the threats and countermeasures.&amp;nbsp; It's a really interesting idea and I hope that they continue with the research.&lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=403423" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/jeffnew/archive/tags/Information+Security/default.aspx">Information Security</category></item><item><title>Is finding security holes a good idea?</title><link>http://blogs.technet.com/jeffnew/archive/2005/02/16/403427.aspx</link><pubDate>Wed, 16 Feb 2005 20:04:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:403427</guid><dc:creator>jeffnew</dc:creator><slash:comments>35</slash:comments><comments>http://blogs.technet.com/jeffnew/comments/403427.aspx</comments><wfw:commentRss>http://blogs.technet.com/jeffnew/commentrss.aspx?PostID=403427</wfw:commentRss><description>&lt;P&gt;Some interesting papers came out of the third annual Workshop on Economics and Information Security.&amp;nbsp; If you're an IEE Computer Society member you can read the full text.&amp;nbsp; Eric Rescorla's article, "Is Finding Security Holes a Good Idea?", provides a statistical analysis of a point I have long held:&amp;nbsp; that disclosure of holes is the prime driver for exploits, and that holding off on disclosure (which also means holding off on the fix) can in many cases reduce costs and improve security.&amp;nbsp; That may be counter-intuitive, but read Rescorla's paper and judge it for yourself. 
&lt;P&gt;&lt;A href="http://www.computer.org/security/v3n1/gei.htm"&gt;&lt;FONT color=#006629&gt;S&amp;amp;P: Economics of Information Security&lt;/FONT&gt;&lt;/A&gt;&lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=403427" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/jeffnew/archive/tags/Information+Security/default.aspx">Information Security</category></item><item><title>Hey, Mom finally gets security!</title><link>http://blogs.technet.com/jeffnew/archive/2005/02/07/403431.aspx</link><pubDate>Tue, 08 Feb 2005 06:57:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:403431</guid><dc:creator>jeffnew</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/jeffnew/comments/403431.aspx</comments><wfw:commentRss>http://blogs.technet.com/jeffnew/commentrss.aspx?PostID=403431</wfw:commentRss><description>&lt;P&gt;Interesting -- According to a UK study, demograpghics are skewing for home users, with older people buying a larger percentage of home infosec products (AV, etc.) and younger people being the ones that naively assume they're OK.&amp;nbsp; Without the data it's hard to analyze further.&amp;nbsp; I hope that the shift is due to more existing home PC users taking security seriously, as opposed to merely a shift in who is buying PCs.&amp;nbsp; &lt;/P&gt;&lt;EM&gt;
&lt;BLOCKQUOTE dir=ltr&gt;
&lt;P&gt;"It is thought that 40% of those buying home net security programs are retired.&amp;nbsp; For the last three years, that has gone up by an average of 13.2%.&amp;nbsp; But more retired women (53%) were buying security software than retired men." &lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;/EM&gt;
&lt;BLOCKQUOTE&gt;&lt;A href="http://news.bbc.co.uk/1/hi/technology/4228891.stm"&gt;&lt;FONT color=#006629&gt;BBC NEWS | Technology | More women turn to net security&lt;/FONT&gt;&lt;/A&gt;&lt;/BLOCKQUOTE&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=403431" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/jeffnew/archive/tags/Information+Security/default.aspx">Information Security</category></item><item><title>Former AOL employee pleads guilty in spam case</title><link>http://blogs.technet.com/jeffnew/archive/2005/02/07/403429.aspx</link><pubDate>Mon, 07 Feb 2005 19:00:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:403429</guid><dc:creator>jeffnew</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/jeffnew/comments/403429.aspx</comments><wfw:commentRss>http://blogs.technet.com/jeffnew/commentrss.aspx?PostID=403429</wfw:commentRss><description>&lt;P&gt;Ouch -- 92 million screen names and email addresses stolen from AOL.&amp;nbsp; The guy netted $28k, and will have to pay $200-400k in restitution.&amp;nbsp; Not exactly a lucrative business, was it?&amp;nbsp; 
&lt;P&gt;Once again we see privacy compromised from the inside -- nothing that the individual account holder could have done would have prevented this. 
&lt;P&gt;&lt;A href="http://www.msnbc.msn.com/id/6915632/"&gt;&lt;FONT color=#006629&gt;MSNBC - Former AOL employee pleads guilty in spam case&lt;/FONT&gt;&lt;/A&gt;&lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=403429" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/jeffnew/archive/tags/Information+Security/default.aspx">Information Security</category><category domain="http://blogs.technet.com/jeffnew/archive/tags/Privacy/default.aspx">Privacy</category></item><item><title>Microsoft's Security Cooperation Program</title><link>http://blogs.technet.com/jeffnew/archive/2005/02/02/403432.aspx</link><pubDate>Wed, 02 Feb 2005 19:15:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:403432</guid><dc:creator>jeffnew</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/jeffnew/comments/403432.aspx</comments><wfw:commentRss>http://blogs.technet.com/jeffnew/commentrss.aspx?PostID=403432</wfw:commentRss><description>&lt;P&gt;I love how news reporting can subtly (or not so subtly) slant interpretations while professing to still be reporting facts.&amp;nbsp; CNet's reporting of the Microsoft Security Cooperation Program is a great example.&amp;nbsp; When I heard about this program I thought it was great -- a mechanism for getting governments the security info that they need for national security, but with less stringent retrictions than the existing Government Security Program. 
&lt;P&gt;Of course, I am probably biased as well... 
&lt;BLOCKQUOTE&gt;&lt;A href="http://news.com.com/Microsoft+to+help+governments+with+security/2100-7355_3-5559974.html"&gt;&lt;FONT color=#006629&gt;Microsoft to confide security woes to governments | CNET News.com&lt;/FONT&gt;&lt;/A&gt;&lt;BR&gt;&lt;/BLOCKQUOTE&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=403432" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/jeffnew/archive/tags/Information+Security/default.aspx">Information Security</category><category domain="http://blogs.technet.com/jeffnew/archive/tags/Regulatory+Compliance/default.aspx">Regulatory Compliance</category></item></channel></rss>