<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title><![CDATA[[SecurityRatty] tag: nac]]></title>
    <link>http://securityratty.com/tag/nac</link>
    <description></description>
    <pubDate>Wed, 23 Jul 2008 00:09:44 +0000</pubDate>
    <generator>iRatty Engine</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA[Network Access Control: Deploy now or wait?]]></title>
      <link>http://securityratty.com/article/47d2af4f4aab186a7caeac1845e07be0</link>
      <guid>http://securityratty.com/article/47d2af4f4aab186a7caeac1845e07be0</guid>
      <description><![CDATA[It's far from a perfect technology. Not only is NAC still maturing, but there are also several competing factions and little in the way of industry standards, leading some to wonder if it might make...]]></description>
      <content:encoded><![CDATA[It's far from a perfect technology. Not only is NAC still maturing, but there are also several competing factions and little in the way of industry standards, leading some to wonder if it might make sense to wait.
<p><a href="http://feeds.computerworld.com/~a/Computerworld/Security/News?a=JNcgrX"><img src="http://feeds.computerworld.com/~a/Computerworld/Security/News?i=JNcgrX" border="0"></img></a></p><img src="http://feeds.computerworld.com/~r/Computerworld/Security/News/~4/364999392" height="1" width="1"/>]]></content:encoded>
      <pubDate>Thu, 14 Aug 2008 09:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/perfect technology">perfect technology</category>
      <category domain="http://securityratty.com/tag/wait">wait</category>
      <category domain="http://securityratty.com/tag/industry standards">industry standards</category>
      <category domain="http://securityratty.com/tag/sense">sense</category>
      <category domain="http://securityratty.com/tag/factions">factions</category>
      <category domain="http://securityratty.com/tag/nac">nac</category>
      <source url="http://feeds.computerworld.com/~r/Computerworld/Security/News/~3/364999392/article.do">Network Access Control: Deploy now or wait?</source>
    </item>
    <item>
      <title><![CDATA[ConSentry's LANShield gear has NAC]]></title>
      <link>http://securityratty.com/article/59688d32a631298ce150a6741f824f9a</link>
      <guid>http://securityratty.com/article/59688d32a631298ce150a6741f824f9a</guid>
      <description><![CDATA[ConSentry makes switches that support NAC, and that is how the company hyped itself when it started out, but the gear does a lot...]]></description>
      <content:encoded><![CDATA[ConSentry makes switches that support NAC, and that is how the company hyped itself when it started out, but the gear does a lot more.<p><A href="http://ad.doubleclick.net/jump/idg.us.nwf.rss/security;sz=468x60;ord=51376?">
<IMG src="http://ad.doubleclick.net/ad/idg.us.nwf.rss/security;sz=468x60;ord=51376?" border="0" width="468" height="60"></A>
</p>]]></content:encoded>
      <pubDate>Wed, 13 Aug 2008 20:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/support nac">support nac</category>
      <category domain="http://securityratty.com/tag/gear">gear</category>
      <category domain="http://securityratty.com/tag/company hyped">company hyped</category>
      <category domain="http://securityratty.com/tag/consentry">consentry</category>
      <category domain="http://securityratty.com/tag/lot">lot</category>
      <category domain="http://securityratty.com/tag/switches">switches</category>
      <source url="http://www.networkworld.com/newsletters/vpn/2008/081108nac2.html?fsrc=rss-security">ConSentry's LANShield gear has NAC</source>
    </item>
    <item>
      <title><![CDATA[Verizon helps customers get a knack for NAC ]]></title>
      <link>http://securityratty.com/article/f67c66bcd1a16b32af795c3df75b0496</link>
      <guid>http://securityratty.com/article/f67c66bcd1a16b32af795c3df75b0496</guid>
      <description><![CDATA[Verizon Business is offering to help its customers deploy and manage network access control (NAC) technologies that grant users access to networks based not on their IP addresses, but on a combination...]]></description>
      <content:encoded><![CDATA[Verizon Business is offering to help its customers deploy and manage network access control (NAC) technologies that grant users access to networks based not on their IP addresses, but on a combination of their identities, end points and behaviors.]]></content:encoded>
      <pubDate>Tue, 12 Aug 2008 03:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/grant users access">grant users access</category>
      <category domain="http://securityratty.com/tag/networks based">networks based</category>
      <category domain="http://securityratty.com/tag/verizon business">verizon business</category>
      <category domain="http://securityratty.com/tag/customers deploy">customers deploy</category>
      <category domain="http://securityratty.com/tag/nac">nac</category>
      <category domain="http://securityratty.com/tag/combination">combination</category>
      <category domain="http://securityratty.com/tag/technologies">technologies</category>
      <category domain="http://securityratty.com/tag/behaviors">behaviors</category>
      <category domain="http://securityratty.com/tag/identities">identities</category>
      <source url="http://www.networkworld.com/news/2008/081208-verizon-nac.html?fsrc=rss-security">Verizon helps customers get a knack for NAC </source>
    </item>
    <item>
      <title><![CDATA[Pedal to the metal NAC]]></title>
      <link>http://securityratty.com/article/7521a3b0531ce4d781c478df46961baf</link>
      <guid>http://securityratty.com/article/7521a3b0531ce4d781c478df46961baf</guid>
      <description><![CDATA[OK, I am not really a big car racing fan. I dont know, Long Island was not a NASCAR hot bed. Of course the Indy 500 was always big news. In any event I have become much more of a race fan since Chip...]]></description>
      <content:encoded><![CDATA[
<div xmlns="http://www.w3.org/1999/xhtml"><p>OK, I am not really a big car racing fan.&nbsp; I don’t know, Long Island was not a NASCAR hot bed. Of course the Indy 500 was always big news.&nbsp; In any event I have become much more of a race fan since Chip Ganassi racing became a StillSecure customer.&nbsp; They are using a complete NAC solution that performs both pre and post connect testing. Racing today is not about some gearheads putting in spark plugs and changing tires.&nbsp; It is high, hi-tech and their information security needs to protect their IP are high priority.&nbsp; </p>

<p>Rather than the usual case study, our VP of marketing Jayson Ayers actually tried something new.&nbsp; A video case study is what we have done.&nbsp; I think it is pretty cool and in the spirit of the YouTube generation, am embedding it here.&nbsp; You can read more about this <a href="http://www.stillsecure.com/library/case_studies/ganassi.php">on our site here</a>.</p>

<table cellspacing="0" cellpadding="2" width="400" border="0"><tbody><tr><td valign="top" width="200"><a href="http://www.stillsecureafteralltheseyears.com/ashimmy/WindowsLiveWriter/image.png"><img title="image" height="346" alt="image" src="http://www.stillsecureafteralltheseyears.com/ashimmy/WindowsLiveWriter/image_thumb.png" width="274" border="0" style="BORDER-RIGHT: 0px; BORDER-TOP: 0px; BORDER-LEFT: 0px; BORDER-BOTTOM: 0px" /></a> </td>

<td valign="top" width="200"><embed src="http://www.youtube.com/v/cTNNDnXPkUo&amp;hl=en&amp;fs=1" width="425" height="344" type="application/x-shockwave-flash" allowfullscreen="true"></embed></td></tr></tbody></table></div>

<p><a href="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?a=tRam5k"><img src="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?i=tRam5k" border="0"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=7ARydK"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=7ARydK" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=LIqnKK"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=LIqnKK" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=VIW8dK"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=VIW8dK" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=jLzWYK"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=jLzWYK" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=JRWh9k"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=JRWh9k" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=gDfMWk"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=gDfMWk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~4/359748366" height="1" width="1"/>]]></content:encoded>
      <pubDate>Fri, 08 Aug 2008 12:01:03 +0000</pubDate>
      <category domain="http://securityratty.com/tag/fan">fan</category>
      <category domain="http://securityratty.com/tag/race fan">race fan</category>
      <category domain="http://securityratty.com/tag/nascar hot bed">nascar hot bed</category>
      <category domain="http://securityratty.com/tag/complete nac solution">complete nac solution</category>
      <category domain="http://securityratty.com/tag/stillsecure customer">stillsecure customer</category>
      <category domain="http://securityratty.com/tag/youtube generation">youtube generation</category>
      <category domain="http://securityratty.com/tag/jayson ayers">jayson ayers</category>
      <category domain="http://securityratty.com/tag/study">study</category>
      <category domain="http://securityratty.com/tag/chip ganassi">chip ganassi</category>
      <source url="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~3/359748366/pedal-to-the-me.html">Pedal to the metal NAC</source>
    </item>
    <item>
      <title><![CDATA[Symantec takes a fling it on the wall approach to NAC]]></title>
      <link>http://securityratty.com/article/5fdd01f2a0625307de1c754d60d3d1b2</link>
      <guid>http://securityratty.com/article/5fdd01f2a0625307de1c754d60d3d1b2</guid>
      <description><![CDATA[I was reading Tim Greene's column this morning about Symantec 's new on demand web log in for guests as part of their SNAC appliance offering. I have to admit that even I who follows the NAC market...]]></description>
      <content:encoded><![CDATA[
<div xmlns="http://www.w3.org/1999/xhtml"><p>I was reading <a href="http://www.networkworld.com/newsletters/vpn/2008/072808nac1.html">Tim Greene's column</a> this morning about <a class="zem_slink" title="Symantec" href="http://www.symantec.com/" rel="homepage">Symantec</a>'s new on demand web log in for guests as part of their SNAC appliance offering. I have to admit that even I who follows the NAC market and competition pretty closely, get pretty confused with all of the different offerings Symantec has come out with around NAC. Symantec seems to be following a fling stuff on the wall and see what sticks strategy when it comes to NAC.&nbsp; The problem is separating the keepers from the rest of it when evaluating their offering.</p>

<p>This latest offering appears to sure up a hole that was called out in the recent <a href="http://www.crn.com/security/209101095;jsessionid=4CV2CAHUGZHEMQSNDLRSKHSCJUNN2JVN?pgno=1">CRN review</a> of their product in a bake off against Sophos and StillSecure's Safe Access. In that review Symantec's drop off in functionality between agent and agentless was called out.&nbsp; So within just a few days comes this announcement addressing the issue.&nbsp; Very timely indeed.&nbsp; This comes on the heels of Symantec's peer-to-peer approach to NAC, which came on the heels of their Endpoint Security product version 11 which had NAC included (and which I understand has already been patched/upgraded several times since its release).&nbsp; </p>

<p>At this point you have Symantec NAC with their endpoint suite which is a throw in but has no guest access option on its own. Than you have the Symantec NAC appliance which can do enforcement of managed devices beyond what just endpoint suite gives you.&nbsp; Now you also have on demand/dissolvable agents available with the Symantec NAC server (but I guess not with the endpoint suite). You also have the Symantec peer-to-peer stuff, which I think also requires the SNAC server.&nbsp; Starting to get confusing? I guess this is what happens when your NAC offering is made up of an amalgamation of several different products lumped together.</p>

<p>Not to worry though, I am sure Big Yellow will still sell plenty of all flavors of their NAC offering. At the end of the day some of this stuff is bound to stick.</p>

<div class="zemanta-pixie" style="MARGIN-TOP: 10px; HEIGHT: 15px"><a class="zemanta-pixie-a" title="Zemified by Zemanta" href="http://reblog.zemanta.com/zemified/a9b9cd5b-92ba-48a1-b363-de44351587fe/"><img class="zemanta-pixie-img" alt="Zemanta Pixie" src="http://img.zemanta.com/reblog_e.png?x-id=a9b9cd5b-92ba-48a1-b363-de44351587fe" style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; FLOAT: right; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none" /></a></div></div>
]]></content:encoded>
      <pubDate>Tue, 29 Jul 2008 03:41:20 +0000</pubDate>
      <category domain="http://securityratty.com/tag/nac">nac</category>
      <category domain="http://securityratty.com/tag/symantec nac appliance">symantec nac appliance</category>
      <category domain="http://securityratty.com/tag/symantec nac">symantec nac</category>
      <category domain="http://securityratty.com/tag/symantec nac server">symantec nac server</category>
      <category domain="http://securityratty.com/tag/symantec">symantec</category>
      <category domain="http://securityratty.com/tag/offerings symantec">offerings symantec</category>
      <category domain="http://securityratty.com/tag/symantec peer-to-peer stuff">symantec peer-to-peer stuff</category>
      <category domain="http://securityratty.com/tag/nac market">nac market</category>
      <category domain="http://securityratty.com/tag/endpoint suite">endpoint suite</category>
      <source url="http://www.stillsecureafteralltheseyears.com/ashimmy/2008/07/symantec-takes.html">Symantec takes a fling it on the wall approach to NAC</source>
    </item>
    <item>
      <title><![CDATA[Symantec takes a fling it on the wall approach to NAC]]></title>
      <link>http://securityratty.com/article/0df0f414409f58415c15cbc4f2fea03c</link>
      <guid>http://securityratty.com/article/0df0f414409f58415c15cbc4f2fea03c</guid>
      <description><![CDATA[I was reading Tim Greene's column this morning about Symantec 's new on demand web log in for guests as part of their SNAC appliance offering. I have to admit that even I who follows the NAC market...]]></description>
      <content:encoded><![CDATA[
<div xmlns="http://www.w3.org/1999/xhtml"><p>I was reading <a href="http://www.networkworld.com/newsletters/vpn/2008/072808nac1.html">Tim Greene's column</a> this morning about <a class="zem_slink" title="Symantec" href="http://www.symantec.com/" rel="homepage">Symantec</a>'s new on demand web log in for guests as part of their SNAC appliance offering. I have to admit that even I who follows the NAC market and competition pretty closely, get pretty confused with all of the different offerings Symantec has come out with around NAC. Symantec seems to be following a fling stuff on the wall and see what sticks strategy when it comes to NAC.&nbsp; The problem is separating the keepers from the rest of it when evaluating their offering.</p>

<p>This latest offering appears to sure up a hole that was called out in the recent <a href="http://www.crn.com/security/209101095;jsessionid=4CV2CAHUGZHEMQSNDLRSKHSCJUNN2JVN?pgno=1">CRN review</a> of their product in a bake off against Sophos and StillSecure's Safe Access. In that review Symantec's drop off in functionality between agent and agentless was called out.&nbsp; So within just a few days comes this announcement addressing the issue.&nbsp; Very timely indeed.&nbsp; This comes on the heels of Symantec's peer-to-peer approach to NAC, which came on the heels of their Endpoint Security product version 11 which had NAC included (and which I understand has already been patched/upgraded several times since its release).&nbsp; </p>

<p>At this point you have Symantec NAC with their endpoint suite which is a throw in but has no guest access option on its own. Than you have the Symantec NAC appliance which can do enforcement of managed devices beyond what just endpoint suite gives you.&nbsp; Now you also have on demand/dissolvable agents available with the Symantec NAC server (but I guess not with the endpoint suite). You also have the Symantec peer-to-peer stuff, which I think also requires the SNAC server.&nbsp; Starting to get confusing? I guess this is what happens when your NAC offering is made up of an amalgamation of several different products lumped together.</p>

<p>Not to worry though, I am sure Big Yellow will still sell plenty of all flavors of their NAC offering. At the end of the day some of this stuff is bound to stick.</p>

<div class="zemanta-pixie" style="MARGIN-TOP: 10px; HEIGHT: 15px"><a class="zemanta-pixie-a" title="Zemified by Zemanta" href="http://reblog.zemanta.com/zemified/a9b9cd5b-92ba-48a1-b363-de44351587fe/"><img class="zemanta-pixie-img" alt="Zemanta Pixie" src="http://img.zemanta.com/reblog_e.png?x-id=a9b9cd5b-92ba-48a1-b363-de44351587fe" style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; FLOAT: right; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none" /></a></div></div>

<p><a href="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?a=2Val4x"><img src="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?i=2Val4x" border="0"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=QOQfsJ"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=QOQfsJ" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=1VUC0J"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=1VUC0J" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=jtR7aJ"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=jtR7aJ" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=OoZFwJ"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=OoZFwJ" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=BrlZNj"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=BrlZNj" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=1KoExj"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=1KoExj" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~4/349362002" height="1" width="1"/>]]></content:encoded>
      <pubDate>Tue, 29 Jul 2008 02:49:15 +0000</pubDate>
      <category domain="http://securityratty.com/tag/nac">nac</category>
      <category domain="http://securityratty.com/tag/symantec nac appliance">symantec nac appliance</category>
      <category domain="http://securityratty.com/tag/symantec nac">symantec nac</category>
      <category domain="http://securityratty.com/tag/symantec nac server">symantec nac server</category>
      <category domain="http://securityratty.com/tag/symantec">symantec</category>
      <category domain="http://securityratty.com/tag/offerings symantec">offerings symantec</category>
      <category domain="http://securityratty.com/tag/symantec peer-to-peer stuff">symantec peer-to-peer stuff</category>
      <category domain="http://securityratty.com/tag/nac market">nac market</category>
      <category domain="http://securityratty.com/tag/endpoint suite">endpoint suite</category>
      <source url="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~3/349362002/symantec-takes.html">Symantec takes a fling it on the wall approach to NAC</source>
    </item>
    <item>
      <title><![CDATA[In the great NAC debate, Snyder KOs Stiennon in the first round!]]></title>
      <link>http://securityratty.com/article/257e5281878e732cc8ef2afaee430827</link>
      <guid>http://securityratty.com/article/257e5281878e732cc8ef2afaee430827</guid>
      <description><![CDATA[Just got done reading the transcript of yesterdays great NAC debate between Joel Snyder and Richard Stiennon. As I predicted Snyder scored a knockout early on and it was mostly over from that point...]]></description>
      <content:encoded><![CDATA[<p><a href="http://www.stillsecureafteralltheseyears.com/ashimmy/WindowsLiveWriter/boxer.jpg"><img title="boxer" style="border-right: 0px; border-top: 0px; margin: 0px 0px 5px 5px; border-left: 0px; border-bottom: 0px" height="124" alt="boxer" src="http://www.stillsecureafteralltheseyears.com/ashimmy/WindowsLiveWriter/boxer_thumb.jpg" width="142" align="right" border="0"></img></a> Just got done <a href="http://www.networkworld.com/chat/archive/2008/072308-snyder-stiennon-nac-debate.html">reading the transcript</a> of yesterdays great NAC debate between Joel Snyder and Richard Stiennon.  As I predicted Snyder scored a knockout early on and it was mostly over from that point on.  The knockout came earlier than I expected though, right off the first question.  Each combatant was asked to define NAC and that was when it happened.  Richard brought an EPAC (end point access control) to a NAC fight.  That was akin to him bringing a rubber knife to a gun fight.  A quick bullet between the eyes by Snyder and it was almost painlessly over for Richard.</p>  <p>I have been preaching for some time about what I call complete NAC. That is a complete network access control solution, not just network admission control and certainly not end point access control.  It is not an evil plot to extend Cisco/Microsoft dominance and most importantly Richard, no one and let me say this again, no one has ever said that NAC negates the need for a layered security model.  NAC is just another layer in that model.  Richard’s comments deriding the .edu and .mil markets were also laughable.  Richard, have you ever heard the term military grade?  Are you seriously trying to say that enterprises take security more seriously than the military does?  Come on now Richard.</p>  <p>The bottom line is Joel Snyder is not only a sharp dude technically, but is street savvy enough to run circles around my friend Richard.  He made Richard stay focused on the question at hand, did not let him wander and so Richard had to face reality a bit. I am sure Richard will still say NAC is useless and <a href="http://securityuncorked.squarespace.com/security-uncorked/2008/7/22/hps-nac-what-ive-been-wanting-to-tell-you-but-couldnt.html">will admonish people about hanging out with the likes of the StillSecure</a> crowd, but I guess some things will just never change.  Except, I don’t think Richard will be in anymore of these bouts.  Maybe he can start selling a grill that takes the fat out of meat or perhaps a reality TV show like the other washed up palookas ?</p>
<p><a href="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?a=ZeWwIp"><img src="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?i=ZeWwIp" border="0"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=9TwouJ"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=9TwouJ" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=JHaO4J"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=JHaO4J" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=vbaihJ"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=vbaihJ" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=QDT1DJ"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=QDT1DJ" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=jnZSlj"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=jnZSlj" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=6zfMHj"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=6zfMHj" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~4/344260979" height="1" width="1"/>]]></content:encoded>
      <pubDate>Wed, 23 Jul 2008 20:13:54 +0000</pubDate>
      <category domain="http://securityratty.com/tag/nac">nac</category>
      <category domain="http://securityratty.com/tag/richard">richard</category>
      <category domain="http://securityratty.com/tag/importantly richard">importantly richard</category>
      <category domain="http://securityratty.com/tag/richard stiennon">richard stiennon</category>
      <category domain="http://securityratty.com/tag/snyder">snyder</category>
      <category domain="http://securityratty.com/tag/friend richard">friend richard</category>
      <category domain="http://securityratty.com/tag/define nac">define nac</category>
      <category domain="http://securityratty.com/tag/nac fight">nac fight</category>
      <category domain="http://securityratty.com/tag/richard stay">richard stay</category>
      <source url="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~3/344260979/in-the-great-na.html">In the great NAC debate, Snyder KOs Stiennon in the first round!</source>
    </item>
    <item>
      <title><![CDATA[Is there any reason to go to Black Hat still?]]></title>
      <link>http://securityratty.com/article/48dccc0384334ebae07a6e1e34cb280b</link>
      <guid>http://securityratty.com/article/48dccc0384334ebae07a6e1e34cb280b</guid>
      <description><![CDATA[I was reading the Security Bloggers Network feed this morning. I had missed a day or so and had a lot of articles to go through. I was also thinking of what could be the next topic suggested for...]]></description>
      <content:encoded><![CDATA[
<div xmlns="http://www.w3.org/1999/xhtml"><p><a onclick="window.open(this.href, '_blank', 'width=200,height=177,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false" href="http://www.stillsecureafteralltheseyears.com/.shared/image.html?/photos/uncategorized/2008/07/23/blackhatbloggers.gif"><img title="Blackhatbloggers" height="132" alt="Blackhatbloggers" src="http://www.stillsecureafteralltheseyears.com/ashimmy/images/2008/07/23/blackhatbloggers.gif" width="150" border="0" style="FLOAT: left; MARGIN: 0px 5px 5px 0px" /></a> I was reading the <a href="http://networks.feedburner.com/Security-Bloggers-Network">Security Bloggers Network</a> feed this morning. I had missed a day or so and had a lot of articles to go through. I was also thinking of what could be the next topic suggested for members to blog about as part of our cross-promotion with Black Hat.&nbsp; Than I realized there really was not any need.&nbsp; The topic was obvious, DNS. I didn't do an actual count of how many times it was mentioned (as <a href="http://www.bumpinthewire.com/?p=234">Mr Bump did with NAC vendors mentioned in the Information Week NAC survey</a>), but there had to be at least a dozen and half, if not more articles on the great DNS leak of 2008.&nbsp; </p>

<p>Dan Kaminsky's research was exemplary, but his naivete about people keeping the exploit under thier hat was not.&nbsp; While <a href="http://www.matasano.com/log/1105/regarding-the-post-on-chargen-earlier-today/#comments">Thomas Matasano apologized for his mistake</a>, frankly from the moment Havlar Flake begain speculating on it, it was just a matter of time.&nbsp; </p>

<p>Anyway, the cat is out of that bag, but something tells me that Dan K's presentation will still be a standing room only crowd in just a few weeks in Vegas.&nbsp; But beyond that there are still a bunch of good topics to be discovered at Black Hat.&nbsp; Not to mention lots of social activities brewing for both BH and DefCon.&nbsp; I amreally looking forward to it. I would hope that no one is feeling the air out of the ballon on this one!</p><br /><br /><fieldset class="zemanta-related"><legend class="zemanta-related-title">Related articles by Zemanta</legend><ul class="zemanta-article-ul"><li class="zemanta-article-ul-li"><a href="http://blog.wired.com/27bstroke6/2008/07/details-of-dns.html">Details of DNS Flaw Leaked; Exploit Expected by End of Today</a></li>

<li class="zemanta-article-ul-li"><a href="http://www.infoworld.com/article/08/07/22/Details_of_major_Internet_flaw_posted_by_accident_1.html?source=rss&amp;url=http://www.infoworld.com/article/08/07/22/Details_of_major_Internet_flaw_posted_by_accident_1.html">Details of major Internet flaw posted by accident</a></li>

<li class="zemanta-article-ul-li"><a href="http://gigaom.com/2008/07/22/the-kaminsky-hack-dns-exploits-in-the-wild/">The Kaminsky Hack: DNS Exploits in the Wild</a></li>

<li class="zemanta-article-ul-li"><a href="http://news.cnet.com/8301-1009_3-9996316-83.html?hhTest=1&amp;part=rss&amp;subj=news">Is Kaminsky's DNS flaw public?</a></li>

<li class="zemanta-article-ul-li"><a href="http://www.boingboing.net/2008/07/22/kaminsky-on-the-nets.html">Kaminsky on the net-shaking DNS bug</a></li>

<li class="zemanta-article-ul-li"><a href="http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;articleId=9110418&amp;source=rss_topic82">Details of major Internet flaw posted by accident</a></li></ul></fieldset> <div class="zemanta-pixie" style="MARGIN-TOP: 10px; HEIGHT: 15px"><a class="zemanta-pixie-a" title="Zemified by Zemanta" href="http://reblog.zemanta.com/zemified/a94ce1a9-f719-4533-9603-beb582d33313/"><img class="zemanta-pixie-img" alt="Zemanta Pixie" src="http://img.zemanta.com/reblog_e.png?x-id=a94ce1a9-f719-4533-9603-beb582d33313" style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; FLOAT: right; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none" /></a></div></div>

<p><a href="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?a=mPLh0z"><img src="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?i=mPLh0z" border="0"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=iDfnaJ"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=iDfnaJ" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=sAYmLJ"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=sAYmLJ" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=CaWUSJ"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=CaWUSJ" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=Gh4sLJ"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=Gh4sLJ" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=Z6tX2j"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=Z6tX2j" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=7rsO8j"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=7rsO8j" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~4/343474506" height="1" width="1"/>]]></content:encoded>
      <pubDate>Wed, 23 Jul 2008 03:58:05 +0000</pubDate>
      <category domain="http://securityratty.com/tag/dns flaw">dns flaw</category>
      <category domain="http://securityratty.com/tag/dns flaw public">dns flaw public</category>
      <category domain="http://securityratty.com/tag/dns">dns</category>
      <category domain="http://securityratty.com/tag/dns bug">dns bug</category>
      <category domain="http://securityratty.com/tag/black hat">black hat</category>
      <category domain="http://securityratty.com/tag/dns leak">dns leak</category>
      <category domain="http://securityratty.com/tag/kaminsky">kaminsky</category>
      <category domain="http://securityratty.com/tag/kaminsky hack">kaminsky hack</category>
      <category domain="http://securityratty.com/tag/major internet flaw">major internet flaw</category>
      <source url="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~3/343474506/is-there-any-re.html">Is there any reason to go to Black Hat still?</source>
    </item>
    <item>
      <title><![CDATA[Is there any reason to go to Black Hat still?]]></title>
      <link>http://securityratty.com/article/dde51fc8529a127d8c2ff85832932ba6</link>
      <guid>http://securityratty.com/article/dde51fc8529a127d8c2ff85832932ba6</guid>
      <description><![CDATA[I was reading the Security Bloggers Network feed this morning. I had missed a day or so and had a lot of articles to go through. I was also thinking of what could be the next topic suggested for...]]></description>
      <content:encoded><![CDATA[
<div xmlns="http://www.w3.org/1999/xhtml"><p><a onclick="window.open(this.href, '_blank', 'width=200,height=177,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false" href="http://www.stillsecureafteralltheseyears.com/.shared/image.html?/photos/uncategorized/2008/07/23/blackhatbloggers.gif"><img title="Blackhatbloggers" height="132" alt="Blackhatbloggers" src="http://www.stillsecureafteralltheseyears.com/ashimmy/images/2008/07/23/blackhatbloggers.gif" width="150" border="0" style="FLOAT: left; MARGIN: 0px 5px 5px 0px" /></a> I was reading the <a href="http://networks.feedburner.com/Security-Bloggers-Network">Security Bloggers Network</a> feed this morning. I had missed a day or so and had a lot of articles to go through. I was also thinking of what could be the next topic suggested for members to blog about as part of our cross-promotion with Black Hat.&nbsp; Than I realized there really was not any need.&nbsp; The topic was obvious, DNS. I didn't do an actual count of how many times it was mentioned (as <a href="http://www.bumpinthewire.com/?p=234">Mr Bump did with NAC vendors mentioned in the Information Week NAC survey</a>), but there had to be at least a dozen and half, if not more articles on the great DNS leak of 2008.&nbsp; </p>

<p>Dan Kaminsky's research was exemplary, but his naivete about people keeping the exploit under thier hat was not.&nbsp; While <a href="http://www.matasano.com/log/1105/regarding-the-post-on-chargen-earlier-today/#comments">Thomas Matasano apologized for his mistake</a>, frankly from the moment Havlar Flake begain speculating on it, it was just a matter of time.&nbsp; </p>

<p>Anyway, the cat is out of that bag, but something tells me that Dan K's presentation will still be a standing room only crowd in just a few weeks in Vegas.&nbsp; But beyond that there are still a bunch of good topics to be discovered at Black Hat.&nbsp; Not to mention lots of social activities brewing for both BH and DefCon.&nbsp; I amreally looking forward to it. I would hope that no one is feeling the air out of the ballon on this one!</p><br /><br /><fieldset class="zemanta-related"><legend class="zemanta-related-title">Related articles by Zemanta</legend><ul class="zemanta-article-ul"><li class="zemanta-article-ul-li"><a href="http://blog.wired.com/27bstroke6/2008/07/details-of-dns.html">Details of DNS Flaw Leaked; Exploit Expected by End of Today</a></li>

<li class="zemanta-article-ul-li"><a href="http://www.infoworld.com/article/08/07/22/Details_of_major_Internet_flaw_posted_by_accident_1.html?source=rss&amp;url=http://www.infoworld.com/article/08/07/22/Details_of_major_Internet_flaw_posted_by_accident_1.html">Details of major Internet flaw posted by accident</a></li>

<li class="zemanta-article-ul-li"><a href="http://gigaom.com/2008/07/22/the-kaminsky-hack-dns-exploits-in-the-wild/">The Kaminsky Hack: DNS Exploits in the Wild</a></li>

<li class="zemanta-article-ul-li"><a href="http://news.cnet.com/8301-1009_3-9996316-83.html?hhTest=1&amp;part=rss&amp;subj=news">Is Kaminsky's DNS flaw public?</a></li>

<li class="zemanta-article-ul-li"><a href="http://www.boingboing.net/2008/07/22/kaminsky-on-the-nets.html">Kaminsky on the net-shaking DNS bug</a></li>

<li class="zemanta-article-ul-li"><a href="http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;articleId=9110418&amp;source=rss_topic82">Details of major Internet flaw posted by accident</a></li></ul></fieldset> <div class="zemanta-pixie" style="MARGIN-TOP: 10px; HEIGHT: 15px"><a class="zemanta-pixie-a" title="Zemified by Zemanta" href="http://reblog.zemanta.com/zemified/a94ce1a9-f719-4533-9603-beb582d33313/"><img class="zemanta-pixie-img" alt="Zemanta Pixie" src="http://img.zemanta.com/reblog_e.png?x-id=a94ce1a9-f719-4533-9603-beb582d33313" style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; FLOAT: right; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none" /></a></div></div>
]]></content:encoded>
      <pubDate>Wed, 23 Jul 2008 03:41:47 +0000</pubDate>
      <category domain="http://securityratty.com/tag/dns flaw">dns flaw</category>
      <category domain="http://securityratty.com/tag/dns flaw public">dns flaw public</category>
      <category domain="http://securityratty.com/tag/dns">dns</category>
      <category domain="http://securityratty.com/tag/dns bug">dns bug</category>
      <category domain="http://securityratty.com/tag/black hat">black hat</category>
      <category domain="http://securityratty.com/tag/dns leak">dns leak</category>
      <category domain="http://securityratty.com/tag/kaminsky">kaminsky</category>
      <category domain="http://securityratty.com/tag/kaminsky hack">kaminsky hack</category>
      <category domain="http://securityratty.com/tag/major internet flaw">major internet flaw</category>
      <source url="http://www.stillsecureafteralltheseyears.com/ashimmy/2008/07/is-there-any-re.html">Is there any reason to go to Black Hat still?</source>
    </item>
    <item>
      <title><![CDATA[Coming Up: NAC Sauces & 1X Vulnerabilities]]></title>
      <link>http://securityratty.com/article/e0b7495fadd39033d01edf84bb0b88a3</link>
      <guid>http://securityratty.com/article/e0b7495fadd39033d01edf84bb0b88a3</guid>
      <description><![CDATA[Per requests, and as part of the ask JJ responses, Ive been working on a couple of blog post series for you
Im juggling blog-moving with blog-posting and trying to find the happy medium. Coming soon...]]></description>
      <content:encoded><![CDATA[<P>Per requests, and as part of the <A href="http://securityuncorked.squarespace.com/security-uncorked/2008/6/6/jjs-security-qa-month.html">&#8216;ask JJ&#8217;</A> responses, I&#8217;ve been working on a couple of blog post series for you.</P>
<P>I&#8217;m juggling blog-moving with blog-posting and trying to find the happy medium. Coming soon though, are two NAC/1X series I hope you&#8217;ll enjoy&#8230;</P>
<P><STRONG>NAC Vendor Sauce Series: Fishing out Features<br></STRONG> Each NAC solution on the market has it&#8217;s own special NAC <EM>&#8216;sauce&#8217;</EM> , a feature that sets it apart, or makes it better for certain situations, than others. This series highlights the advantages of each solution and includes <A class=offsite-link-inline title="Juniper Networks" href="http://www.juniper.net" target=_blank>Juniper</A>, <A class=offsite-link-inline title=Cisco href="http://www.cisco.com" target=_blank>Cisco</A>, <A class=offsite-link-inline title=Symantec href="http://www.symantec.com" target=_blank>Symantec</A>, <A class=offsite-link-inline title=Enterasys href="http://www.enterasys.com" target=_blank>Enterasys</A>, <A class=offsite-link-inline title="ProCurve Networking by HP" href="http://www.procurve.com" target=_blank>ProCurve</A>, <A class=offsite-link-inline title=StillSecure href="http://www.stillsecure.com" target=_blank>StillSecure</A>, <A class=offsite-link-inline title=Napera href="http://www.napera.com" target=_blank>Napera</A> along with a few&nbsp;others. </P>
<P><STRONG>802.1X Vulnerabilities: Designing for Security</STRONG><br>Often, users put too much stake in 802.1X, relying on it too heavily&nbsp;in many circumstances. There are vulnerabilities with 1X, but most can be mitigated or avoided with smart planning. This series describes various vulnerabilities with 802.1X, gives you details on each and provides information on how to protect yourself from them. To get started, check out my <A title="802.1X Primer" href="http://securityuncorked.squarespace.com/security-uncorked/2008/4/2/what-is-8021x-heres-a-technology-primer-for-you.html">802.1X Technology Primer</A>. </P>
<P># # #</P>
]]></content:encoded>
      <pubDate>Wed, 23 Jul 2008 00:09:44 +0000</pubDate>
      <category domain="http://securityratty.com/tag/vulnerabilities">vulnerabilities</category>
      <category domain="http://securityratty.com/tag/special nac sauce">special nac sauce</category>
      <category domain="http://securityratty.com/tag/solution">solution</category>
      <category domain="http://securityratty.com/tag/nac solution">nac solution</category>
      <category domain="http://securityratty.com/tag/blog post series">blog post series</category>
      <category domain="http://securityratty.com/tag/technology primer">technology primer</category>
      <category domain="http://securityratty.com/tag/series describes">series describes</category>
      <category domain="http://securityratty.com/tag/happy medium">happy medium</category>
      <category domain="http://securityratty.com/tag/includes juniper">includes juniper</category>
      <source url="http://www.securityuncorked.com/security-uncorked/2008/7/23/coming-up-nac-sauces-1x-vulnerabilities.html">Coming Up: NAC Sauces &amp; 1X Vulnerabilities</source>
    </item>
  </channel>
</rss>
