<?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: vam]]></title>
    <link>http://securityratty.com/tag/vam</link>
    <description></description>
    <pubDate>Tue, 18 Mar 2008 21:48:50 +0000</pubDate>
    <generator>iRatty Engine</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA[Are current vulnerability and compliance testing tools like answering the phone at 3am?]]></title>
      <link>http://securityratty.com/article/6654f6456677a336f8a4941afb4009d8</link>
      <guid>http://securityratty.com/article/6654f6456677a336f8a4941afb4009d8</guid>
      <description><![CDATA[I was at a meeting for a potentially large customer engagement for vulnerability assessment and compliance testing last week. The requirements for this customer was not unusual. They wanted to test...]]></description>
      <content:encoded><![CDATA[
<div xmlns="http://www.w3.org/1999/xhtml"><p></p> <p>I was at a meeting for a potentially large customer engagement for vulnerability assessment and compliance testing last week.&nbsp; The requirements for this customer was not unusual. They wanted to test for conventional CVE type vulnerabilities. Additionally, they also wanted to test for configuration compliance. Hotfixes, patch level, AV, etc.&nbsp; This direction is where a lot of the traditional vulnerability management solutions have been heading.&nbsp; Whether adding a separate compliance module or audit and local check capability, most of the traditional vulnerability scanning solutions offer some coverage in this area.&nbsp; However, in speaking to this potential customer and in thinking about their needs, an inherent problem with this solution is that it is only as good as the devices that are available on the network when the scan takes place.</p> <p>In traditional vulnerability scanning, <u>when</u> the scan takes place was not as much of an issue, usually you are scanning servers and other devices that are on the network 24/7. In fact doing the scans during off hours was usually preferred. Too many of the network based vulnerability scanners took up too much bandwidth and other resources to accomplish during the prime time hours of the day. In compliance scanning though, you need the status of laptops, desktops and other devices that may not be connected to the network 24/7.&nbsp; Therefore it is important to reach and test these devices when they are on the network.&nbsp; That is the rub.&nbsp; How do you really make sure the devices connecting to your network are compliant if you are only testing them at a point in time and that usually at an off hour?</p> <p>This problem reminded me of the Clinton-Obama flap over who answers the phone at the White House at 3am.&nbsp; That is an important question for who is president, but for compliance answering the phone when someone is there to talk to is more important.&nbsp; I think this is where NAC provides an advantage.&nbsp; By utilizing NAC to detect devices coming on the network and than using a low impact compliance test as well as traditional vulnerability scanning, you get a picture of vulnerability posture and compliance status as of the last time they accessed the network. You can still do follow on tests at any time you desire, but at least when a device is logging on you are sure of a test.</p> <p>Will NAC supplement vulnerability testing in this manner? I think so.&nbsp; Many customers we have spoken to about this like the idea of "scan on connect" and we have already enabled our own NAC product Safe Access and vulnerability management platform VAM to do this.&nbsp; What do you think?</p></div>

<p><a href="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?a=atl0PH"><img src="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?i=atl0PH" border="0"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=JgJVaH"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=JgJVaH" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=kjoSqH"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=kjoSqH" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=OqhPXH"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=OqhPXH" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=pS6W5H"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=pS6W5H" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=YCq7Eh"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=YCq7Eh" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=qHBwth"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=qHBwth" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~4/293979749" height="1" width="1"/>]]></content:encoded>
      <pubDate>Mon, 19 May 2008 19:16:18 +0000</pubDate>
      <category domain="http://securityratty.com/tag/compliance">compliance</category>
      <category domain="http://securityratty.com/tag/configuration compliance">configuration compliance</category>
      <category domain="http://securityratty.com/tag/compliance status">compliance status</category>
      <category domain="http://securityratty.com/tag/status">status</category>
      <category domain="http://securityratty.com/tag/prime time hours">prime time hours</category>
      <category domain="http://securityratty.com/tag/time">time</category>
      <category domain="http://securityratty.com/tag/network">network</category>
      <category domain="http://securityratty.com/tag/detect devices">detect devices</category>
      <category domain="http://securityratty.com/tag/devices">devices</category>
      <source url="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~3/293979749/are-current-vul.html">Are current vulnerability and compliance testing tools like answering the phone at 3am?</source>
    </item>
    <item>
      <title><![CDATA[Matt Asay again shows that he doesn't know much about open source security]]></title>
      <link>http://securityratty.com/article/182375cfc9883805e5743d468a40bff0</link>
      <guid>http://securityratty.com/article/182375cfc9883805e5743d468a40bff0</guid>
      <description><![CDATA[I often comment or blog disagreeing with Matt Asay and his views on open source and security. Frankly from the comments Matt leaves back, I think he views me as a pain in his butt and why if I don't...]]></description>
      <content:encoded><![CDATA[<p>I often comment or blog disagreeing with Matt Asay and his views on open source and security. Frankly from the comments Matt leaves back, I think he views me as a pain in his butt and why if I don't agree with him do I read his blog. I read Matt's blog because I often do agree with him, but I also read it because I think it important that just because you don't agree with someones views, doesn't mean they have nothing to say. However, I also feel that I have the right to call BS when I see it. Matt's <a href="http://www.cnet.com/8301-13505_1-9944793-16.html?part=rss&amp;tag=feed&amp;subj=TheOpenRoad">article yesterday on Tenable's new licensing</a> is one of those times. Matt you don't know what you are talking about on this one. If you are not going to take the time to dig in than just stay out. <br><br>First a little background. Tenable announced the other day <a href="http://www.nessus.org/news/data/pr95.pdf">a change in their licensing</a> of their NASL feed. For those who don't know, Tenable is the owner of the formerly open sourced Nessus vulnerability scanner. They also develop and publish a feed of NASL scripts which run in Nessus, which are likewise no longer and some say never were open sourced. I know Ron Gula pretty well and understand perfectly why Nessus is no longer under a GPL license for a few years now. I also understand the economics and reasons why they would charge for their NASL feed. I think it is good business and more power to Ron, Jack, Renaud and the rest of the Tenable gang. The change in their license is that now commercial customers will have to pay for the NASL feed, whereas before only people who resold the feed or otherwise profited from it would have to pay for the "registered feed". Now schools and charities can still get the feed for free, but others have to pay. Again, I don't have the slightest problem with this and wish them well.<br><br>Matt sticks his two cents here and at the same time sticks his foot in his mouth. For some reason Matt has not realized that Nessus has not been open sourced since the release of the 3.x version some time ago. It is not like this is a secret, Tenable is very "open" about it and there has been much written about it. Because they are still open in Matt's eyes, they can do little wrong. Matt this is just plain negligence on your part, go beyond the press release before writing! Matt talks about and links to <a href="http://blog.milkingthegnu.org/2008/03/from-close-to-o.html">Pierre Teilhard de Chardin's blog article</a> about Tenable closing the source to Nessus and still doesn't take notice that it is no longer open source. Matt did you read the article you linked to?<br><br>Matt than goes on to try and claim that it is OK for Tenable to charge for the NASL scripts because "the code is free, but the information that flows through it (Up-to-date vulnerability information, for example) is not". Matt, NASL scripts are scripts. I would think the word scripts in the name would be a dead give away. Don't you think that implies some code? <br><br>Yes, you can "drill your own wells" as Matt says and write your own NASL scripts. We do it at StillSecure for our own VAM vulnerability product. But we also use our own customized version of Nessus based off of the old 2.x open source code. <br><br>The fact is there is nothing open sourced about the current version of Nessus and NASL scripts and Ron and company don't make any bones about it. Matt your readers expect more from you. Do a little homework before you spout off!</p>
<p><a href="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?a=w16801"><img src="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?i=w16801" border="0"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=nGdXcH"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=nGdXcH" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=5EK8RH"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=5EK8RH" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=0F9r0H"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=0F9r0H" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=as5VHH"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=as5VHH" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=UHAX7h"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=UHAX7h" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=QKequh"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=QKequh" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~4/291382440" height="1" width="1"/>]]></content:encoded>
      <pubDate>Thu, 15 May 2008 18:43:17 +0000</pubDate>
      <category domain="http://securityratty.com/tag/matt">matt</category>
      <category domain="http://securityratty.com/tag/matt asay">matt asay</category>
      <category domain="http://securityratty.com/tag/matt sticks">matt sticks</category>
      <category domain="http://securityratty.com/tag/matt talks">matt talks</category>
      <category domain="http://securityratty.com/tag/comments matt leaves">comments matt leaves</category>
      <category domain="http://securityratty.com/tag/source">source</category>
      <category domain="http://securityratty.com/tag/reason matt">reason matt</category>
      <category domain="http://securityratty.com/tag/scripts">scripts</category>
      <category domain="http://securityratty.com/tag/word scripts">word scripts</category>
      <source url="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~3/291382440/matt-asay-again.html">Matt Asay again shows that he doesn't know much about open source security</source>
    </item>
    <item>
      <title><![CDATA[What's new in vulnerability management?]]></title>
      <link>http://securityratty.com/article/c6608547b09e0cfbcec61b74ceefeff7</link>
      <guid>http://securityratty.com/article/c6608547b09e0cfbcec61b74ceefeff7</guid>
      <description><![CDATA[For too long the vulnerability management vendors have been quiet. In fact the whole sector has taken on the &quot;mature&quot; label which seems to indicate there is no new innovation happening. Recently...]]></description>
      <content:encoded><![CDATA[
<div xmlns="http://www.w3.org/1999/xhtml"><p>For too long the vulnerability management vendors have been quiet. In fact the whole sector has taken on the &quot;mature&quot; label which seems to indicate there is no new innovation happening.&nbsp; Recently though we have seen some new announcements in this area.&nbsp; Also, Gartner should have a new marketscope due out soon.&nbsp; Here is a recap of some recent developments:</p>

<p>1. <strong>Qualys</strong> - I had a chance to speak with Philippe and his son at RSA. After riding high on the PCI wave and pioneering the SaaS in security movement, Qualys is now clearly moving into the compliance arena. This <a href="http://www.qualys.com/company/newsroom/newsreleases/usa/?view=20080407" target="_blank">release</a> details what Qualys is doing but clearly they see compliance and risk management as a new driver for the business.</p>

<p>2. <strong>McAfee</strong>- Say goodbye to Foundstone. Years after buying the company McAfee is finally getting rid of the Foundstone name for the vulnerability product and renaming it Vulnerability Manager 6.5 (I think I like the Foundstone name better), as part of the <a href="http://www.eweek.com/c/a/Security/McAfee-Governance-Risk-and-Compliance-Business-Unit/" target="_blank">new business unit</a> they have started around GRC. Foundstone founder George Kurtz is heading that unit up. They indicate they will supplement the old Foundstone scanner with abilities to scan applications, web sites and data and databases.</p>

<p>3,. <strong>nCircle</strong> - I spoke with Andrew Storms and Elizabeth Ireland at RSA. nCircle has been touting their compliance and risk management capabilities for a while now.&nbsp; They also are showing off web application scanning as well. Though they don't get the press that Qualys does, they appear to be holding their own.&nbsp; The question in my mind is how do they break out to the next level (see my post on <a href="http://www.stillsecureafteralltheseyears.com/ashimmy/2008/04/shimmys-theory.html" target="_blank">shimmy's theory of relativity</a>).5. </p>

<p>4. eEye - After many of us including me raised doubts about their viability, eEye has announced the addition of web application scanning to their Retina product. I understand this is an OEM of another companies product and does not represent a lot of investment on eEye's point.&nbsp; I think at the end of the day they are trying to be an endpoint company but can't afford to jettison the scanner business.&nbsp; Their long term viability according to my relativity theory is still in doubt if you ask me.</p>

<p>5. <strong>ISS/IBM</strong> - I hear nothing on this one, do you?&nbsp; You have to question what is the game plan from Big Blue on this.&nbsp; Do they buy an update or put the money into actually taking this dinosaur out of the Jurassic?&nbsp; I guess we will have to see.</p>

<p>So I am sure some of you ask, OK Shimmy enough about the competition what is StillSecure doing with its VAM product?&nbsp; Well the purpose of this blog post was to set the stage for that. I will post an update on some of the cool stuff we have planned with VAM shortly. </p></div>
]]></content:encoded>
      <pubDate>Sun, 13 Apr 2008 18:58:13 +0000</pubDate>
      <category domain="http://securityratty.com/tag/unit">unit</category>
      <category domain="http://securityratty.com/tag/business unit">business unit</category>
      <category domain="http://securityratty.com/tag/business">business</category>
      <category domain="http://securityratty.com/tag/risk management capabilities">risk management capabilities</category>
      <category domain="http://securityratty.com/tag/foundstone">foundstone</category>
      <category domain="http://securityratty.com/tag/risk management">risk management</category>
      <category domain="http://securityratty.com/tag/foundstone scanner">foundstone scanner</category>
      <category domain="http://securityratty.com/tag/blog post">blog post</category>
      <category domain="http://securityratty.com/tag/compliance">compliance</category>
      <source url="http://www.stillsecureafteralltheseyears.com/ashimmy/2008/04/whats-new-in-vu.html">What's new in vulnerability management?</source>
    </item>
    <item>
      <title><![CDATA[What's new in vulnerability management?]]></title>
      <link>http://securityratty.com/article/8a2f19eefde655e44f34cc0710699d5d</link>
      <guid>http://securityratty.com/article/8a2f19eefde655e44f34cc0710699d5d</guid>
      <description><![CDATA[For too long the vulnerability management vendors have been quiet. In fact the whole sector has taken on the &quot;mature&quot; label which seems to indicate there is no new innovation happening. Recently...]]></description>
      <content:encoded><![CDATA[
<div xmlns="http://www.w3.org/1999/xhtml"><p>For too long the vulnerability management vendors have been quiet. In fact the whole sector has taken on the &quot;mature&quot; label which seems to indicate there is no new innovation happening.&nbsp; Recently though we have seen some new announcements in this area.&nbsp; Also, Gartner should have a new marketscope due out soon.&nbsp; Here is a recap of some recent developments:</p>

<p>1. <strong>Qualys</strong> - I had a chance to speak with Philippe and his son at RSA. After riding high on the PCI wave and pioneering the SaaS in security movement, Qualys is now clearly moving into the compliance arena. This <a href="http://www.qualys.com/company/newsroom/newsreleases/usa/?view=20080407" target="_blank">release</a> details what Qualys is doing but clearly they see compliance and risk management as a new driver for the business.</p>

<p>2. <strong>McAfee</strong>- Say goodbye to Foundstone. Years after buying the company McAfee is finally getting rid of the Foundstone name for the vulnerability product and renaming it Vulnerability Manager 6.5 (I think I like the Foundstone name better), as part of the <a href="http://www.eweek.com/c/a/Security/McAfee-Governance-Risk-and-Compliance-Business-Unit/" target="_blank">new business unit</a> they have started around GRC. Foundstone founder George Kurtz is heading that unit up. They indicate they will supplement the old Foundstone scanner with abilities to scan applications, web sites and data and databases.</p>

<p>3,. <strong>nCircle</strong> - I spoke with Andrew Storms and Elizabeth Ireland at RSA. nCircle has been touting their compliance and risk management capabilities for a while now.&nbsp; They also are showing off web application scanning as well. Though they don't get the press that Qualys does, they appear to be holding their own.&nbsp; The question in my mind is how do they break out to the next level (see my post on <a href="http://www.stillsecureafteralltheseyears.com/ashimmy/2008/04/shimmys-theory.html" target="_blank">shimmy's theory of relativity</a>).5. </p>

<p>4. eEye - After many of us including me raised doubts about their viability, eEye has announced the addition of web application scanning to their Retina product. I understand this is an OEM of another companies product and does not represent a lot of investment on eEye's point.&nbsp; I think at the end of the day they are trying to be an endpoint company but can't afford to jettison the scanner business.&nbsp; Their long term viability according to my relativity theory is still in doubt if you ask me.</p>

<p>5. <strong>ISS/IBM</strong> - I hear nothing on this one, do you?&nbsp; You have to question what is the game plan from Big Blue on this.&nbsp; Do they buy an update or put the money into actually taking this dinosaur out of the Jurassic?&nbsp; I guess we will have to see.</p>

<p>So I am sure some of you ask, OK Shimmy enough about the competition what is StillSecure doing with its VAM product?&nbsp; Well the purpose of this blog post was to set the stage for that. I will post an update on some of the cool stuff we have planned with VAM shortly. </p></div>

<p><a href="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?a=TII961"><img src="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?i=TII961" border="0"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=BXE9w2G"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=BXE9w2G" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=buMzw2G"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=buMzw2G" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=EoPB2tG"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=EoPB2tG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=JennaCG"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=JennaCG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=MfVIVZg"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=MfVIVZg" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=Vy2M06g"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=Vy2M06g" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~4/269748929" height="1" width="1"/>]]></content:encoded>
      <pubDate>Sun, 13 Apr 2008 17:58:13 +0000</pubDate>
      <category domain="http://securityratty.com/tag/unit">unit</category>
      <category domain="http://securityratty.com/tag/business unit">business unit</category>
      <category domain="http://securityratty.com/tag/business">business</category>
      <category domain="http://securityratty.com/tag/risk management capabilities">risk management capabilities</category>
      <category domain="http://securityratty.com/tag/foundstone">foundstone</category>
      <category domain="http://securityratty.com/tag/risk management">risk management</category>
      <category domain="http://securityratty.com/tag/foundstone scanner">foundstone scanner</category>
      <category domain="http://securityratty.com/tag/blog post">blog post</category>
      <category domain="http://securityratty.com/tag/compliance">compliance</category>
      <source url="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~3/269748929/whats-new-in-vu.html">What's new in vulnerability management?</source>
    </item>
    <item>
      <title><![CDATA[NAC is a battlefield - Only the strong survive]]></title>
      <link>http://securityratty.com/article/c960dc03b52138212a94130ce5290bca</link>
      <guid>http://securityratty.com/article/c960dc03b52138212a94130ce5290bca</guid>
      <description><![CDATA[First it was Caymas Systems, then it was Vernier Networks, now Lockdown Networks appears to be exiting the NAC market . Of course the obvious reaction as a competitor is to say good riddance, one less...]]></description>
      <content:encoded><![CDATA[
<div xmlns="http://www.w3.org/1999/xhtml"><p>First it was Caymas Systems, then it was Vernier Networks, now Lockdown Networks <a href="http://lockdownnetworks.com/lockdown_networks.php" target="_blank">appears to be exiting the NAC market</a>.&nbsp; Of course the obvious reaction as a competitor is to say good riddance, one less competitor to deal with.&nbsp; But to turn a quote on its ear, I write today not to bury Lockdown Networks, but to praise them. More than the other two NAC companies that have exited the market, I was personally in the loop on Lockdown Networks. I first heard about them when a VC friend of ours asked us about them years ago.&nbsp; This was when we were still planning Safe Access and Lockdown's business plan was vulnerability management. They had not raised money yet and were still in stealth mode. We thought of them as competition for our VAM product, but wanted to see what they would come up with. I stayed abreast watching their progress from afar. Some time later, when I was looking to put together a group of companies to form a coalition to develop an independent NASL script library, knowing that they used Nessus, I reached out to them.</p>

<p>This is when I first met Rob Gilde.&nbsp; Subsequently I also met Brett and most of the rest of the team there. I like Rob, he ran their product team, was knowledgeable and a nice guy in a west coast laid back kind of way.&nbsp; In short time it became apparent&nbsp; to me that Lockdown was looking to move out of the VM business.&nbsp; Rob realized that just scanning and reporting was not going to make it.&nbsp; He had the notion of adding enforcement to his vulnerability scanning. If you failed a vulnerability scan, you should be denied access to the network.&nbsp; My initial reaction was vulnerability scans are done mostly on servers, but Rob wanted to do vulnerability scans on endpoints.&nbsp; That is when I told him about our own product which we were about to release. Rob and the team re-tooled and released their Enforcer product some time later.&nbsp; </p>

<p>I personally always thought that doing SANS TOP 20 scans on endpoints was not where it was at in NAC, but Lockdown raised money from Intel and a bunch of other folks and was making a big splash in the heady, gold rush days of NAC.&nbsp; We ran into them on deals from time to time, especially in many of our major partner/OEM deals.&nbsp; The good news for us, is that just about all of the time, our product was picked over theirs.</p>

<p>Soon rumors were everywhere that Lockdown was on the block.&nbsp; Brett and team were looking to grab 20 or so major customers and quickly flip the company for a big win.&nbsp; Than we began hearing that they were looking for less and less money.&nbsp; Also, their PR began becoming more and more desperate.&nbsp; That is when I began calling them on it in my blogging.&nbsp; Evidently that got their attention.&nbsp; A few Interop shows ago, Rob called me over and said he and especially Brett were really upset I called them out.&nbsp; I apologized and said hey I call them as I see them.&nbsp; At RSA or another show after that Brett walked right by me and tried his best to diss me.&nbsp; People from NY don't get dissed that easy though.&nbsp; I just laughed it off, but it was the last time I spoke to anyone at Lockdown.&nbsp; </p>

<p>Recently we have begun to see a few customers that were choosing our Safe Access product to replace Lockdown's.&nbsp; I thought this was ominous for them, but hey good for us! I truly expected to hear any day of someone picking them up at a decent price. I didn't think it would just implode.&nbsp; In many ways a company shutting down is a death of a thousand dreams.&nbsp; The soaring aspirations of the founders, the individual sugar plum fantasies of the early hires, the VC's thinking this could be the big hit.&nbsp; Perhaps most sad of all, the customers who looked at the market and for whatever reasons decided that Lockdown offered them the best product for providing NAC and solving their problems.&nbsp; Those people made a bet that Lockdown would be there to solve the issues and provide a great solution.&nbsp; They as much as anyone lost that bet.&nbsp; </p>

<p>As they do on Ebay, here is a second chance for Lockdown customers.&nbsp; We will have on our web site a special offer to upgrade you to Safe Access and leverage your investment in Lockdown.&nbsp; Lockdown's misfortune does not have to be yours.&nbsp; We are here to help and are here to stay.&nbsp; So to all of Lockdown's customers, I am sorry you are left in a hard place here, but there is help.</p>

<p>To Brett, Dan Clark and the rest of the Lockdown crew, most especially to Rob Gilde, I offer my sympathies that this did not turn out better for you.&nbsp; You all made a great effort and you made us try harder which resulted in our product being developed faster than it would have otherwise.&nbsp; For that I thank you and wish you all the best of luck in your future endeavors. This song is for you:</p>

<div class="wlWriterSmartContent" id="scid:5737277B-5D6D-4f48-ABFC-DD9C333F4C5D:ac1ba53c-4651-4700-8523-c45cc557ec53" style="PADDING-RIGHT: 0px; DISPLAY: inline; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px"><div id="d5269806-6ca5-47f2-afdd-a496ae1b682a" style="PADDING-RIGHT: 0px; DISPLAY: inline; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px"><div><embed src="http://www.youtube.com/v/j9J9rTZJBmw&amp;hl=en" width="425" height="350" type="application/x-shockwave-flash" wmode="transparent"></embed></div></div></div></div>
]]></content:encoded>
      <pubDate>Tue, 18 Mar 2008 22:48:33 +0000</pubDate>
      <category domain="http://securityratty.com/tag/lockdown networks appears">lockdown networks appears</category>
      <category domain="http://securityratty.com/tag/lockdown networks">lockdown networks</category>
      <category domain="http://securityratty.com/tag/bury lockdown networks">bury lockdown networks</category>
      <category domain="http://securityratty.com/tag/lockdown">lockdown</category>
      <category domain="http://securityratty.com/tag/team">team</category>
      <category domain="http://securityratty.com/tag/product team">product team</category>
      <category domain="http://securityratty.com/tag/product">product</category>
      <category domain="http://securityratty.com/tag/vam product">vam product</category>
      <category domain="http://securityratty.com/tag/customers">customers</category>
      <source url="http://www.stillsecureafteralltheseyears.com/ashimmy/2008/03/nac-is-a-battle.html">NAC is a battlefield - Only the strong survive</source>
    </item>
    <item>
      <title><![CDATA[NAC is a battlefield - Only the strong survive]]></title>
      <link>http://securityratty.com/article/893663b3663f65421ed045d52b851cc5</link>
      <guid>http://securityratty.com/article/893663b3663f65421ed045d52b851cc5</guid>
      <description><![CDATA[First it was Caymas Systems, then it was Vernier Networks, now Lockdown Networks appears to be exiting the NAC market . Of course the obvious reaction as a competitor is to say good riddance, one less...]]></description>
      <content:encoded><![CDATA[
<div xmlns="http://www.w3.org/1999/xhtml"><p>First it was Caymas Systems, then it was Vernier Networks, now Lockdown Networks <a href="http://lockdownnetworks.com/lockdown_networks.php" target="_blank">appears to be exiting the NAC market</a>.&nbsp; Of course the obvious reaction as a competitor is to say good riddance, one less competitor to deal with.&nbsp; But to turn a quote on its ear, I write today not to bury Lockdown Networks, but to praise them. More than the other two NAC companies that have exited the market, I was personally in the loop on Lockdown Networks. I first heard about them when a VC friend of ours asked us about them years ago.&nbsp; This was when we were still planning Safe Access and Lockdown's business plan was vulnerability management. They had not raised money yet and were still in stealth mode. We thought of them as competition for our VAM product, but wanted to see what they would come up with. I stayed abreast watching their progress from afar. Some time later, when I was looking to put together a group of companies to form a coalition to develop an independent NASL script library, knowing that they used Nessus, I reached out to them.</p>

<p>This is when I first met Rob Gilde.&nbsp; Subsequently I also met Brett and most of the rest of the team there. I like Rob, he ran their product team, was knowledgeable and a nice guy in a west coast laid back kind of way.&nbsp; In short time it became apparent&nbsp; to me that Lockdown was looking to move out of the VM business.&nbsp; Rob realized that just scanning and reporting was not going to make it.&nbsp; He had the notion of adding enforcement to his vulnerability scanning. If you failed a vulnerability scan, you should be denied access to the network.&nbsp; My initial reaction was vulnerability scans are done mostly on servers, but Rob wanted to do vulnerability scans on endpoints.&nbsp; That is when I told him about our own product which we were about to release. Rob and the team re-tooled and released their Enforcer product some time later.&nbsp; </p>

<p>I personally always thought that doing SANS TOP 20 scans on endpoints was not where it was at in NAC, but Lockdown raised money from Intel and a bunch of other folks and was making a big splash in the heady, gold rush days of NAC.&nbsp; We ran into them on deals from time to time, especially in many of our major partner/OEM deals.&nbsp; The good news for us, is that just about all of the time, our product was picked over theirs.</p>

<p>Soon rumors were everywhere that Lockdown was on the block.&nbsp; Brett and team were looking to grab 20 or so major customers and quickly flip the company for a big win.&nbsp; Than we began hearing that they were looking for less and less money.&nbsp; Also, their PR began becoming more and more desperate.&nbsp; That is when I began calling them on it in my blogging.&nbsp; Evidently that got their attention.&nbsp; A few Interop shows ago, Rob called me over and said he and especially Brett were really upset I called them out.&nbsp; I apologized and said hey I call them as I see them.&nbsp; At RSA or another show after that Brett walked right by me and tried his best to diss me.&nbsp; People from NY don't get dissed that easy though.&nbsp; I just laughed it off, but it was the last time I spoke to anyone at Lockdown.&nbsp; </p>

<p>Recently we have begun to see a few customers that were choosing our Safe Access product to replace Lockdown's.&nbsp; I thought this was ominous for them, but hey good for us! I truly expected to hear any day of someone picking them up at a decent price. I didn't think it would just implode.&nbsp; In many ways a company shutting down is a death of a thousand dreams.&nbsp; The soaring aspirations of the founders, the individual sugar plum fantasies of the early hires, the VC's thinking this could be the big hit.&nbsp; Perhaps most sad of all, the customers who looked at the market and for whatever reasons decided that Lockdown offered them the best product for providing NAC and solving their problems.&nbsp; Those people made a bet that Lockdown would be there to solve the issues and provide a great solution.&nbsp; They as much as anyone lost that bet.&nbsp; </p>

<p>As they do on Ebay, here is a second chance for Lockdown customers.&nbsp; We will have on our web site a special offer to upgrade you to Safe Access and leverage your investment in Lockdown.&nbsp; Lockdown's misfortune does not have to be yours.&nbsp; We are here to help and are here to stay.&nbsp; So to all of Lockdown's customers, I am sorry you are left in a hard place here, but there is help.</p>

<p>To Brett, Dan Clark and the rest of the Lockdown crew, most especially to Rob Gilde, I offer my sympathies that this did not turn out better for you.&nbsp; You all made a great effort and you made us try harder which resulted in our product being developing faster than it would have otherwise.&nbsp; For that I thank you and wish you all the best of luck in your future endeavors. This song is for you:</p>

<div class="wlWriterSmartContent" id="scid:5737277B-5D6D-4f48-ABFC-DD9C333F4C5D:ac1ba53c-4651-4700-8523-c45cc557ec53" style="PADDING-RIGHT: 0px; DISPLAY: inline; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px"><div id="d5269806-6ca5-47f2-afdd-a496ae1b682a" style="PADDING-RIGHT: 0px; DISPLAY: inline; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px"><div><embed src="http://www.youtube.com/v/j9J9rTZJBmw&amp;hl=en" width="425" height="350" type="application/x-shockwave-flash" wmode="transparent"></embed></div></div></div></div>

<p><a href="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?a=TILm20"><img src="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?i=TILm20" border="0"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=HKAJDSF"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=HKAJDSF" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=TTKjSCF"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=TTKjSCF" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=VGlkLDF"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=VGlkLDF" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=R7tpBuF"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=R7tpBuF" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=NNemlbf"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=NNemlbf" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=BAmoWbf"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=BAmoWbf" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~4/254086539" height="1" width="1"/>]]></content:encoded>
      <pubDate>Tue, 18 Mar 2008 21:48:50 +0000</pubDate>
      <category domain="http://securityratty.com/tag/lockdown networks appears">lockdown networks appears</category>
      <category domain="http://securityratty.com/tag/lockdown networks">lockdown networks</category>
      <category domain="http://securityratty.com/tag/bury lockdown networks">bury lockdown networks</category>
      <category domain="http://securityratty.com/tag/lockdown">lockdown</category>
      <category domain="http://securityratty.com/tag/team">team</category>
      <category domain="http://securityratty.com/tag/product team">product team</category>
      <category domain="http://securityratty.com/tag/product">product</category>
      <category domain="http://securityratty.com/tag/vam product">vam product</category>
      <category domain="http://securityratty.com/tag/customers">customers</category>
      <source url="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~3/254086539/nac-is-a-battle.html">NAC is a battlefield - Only the strong survive</source>
    </item>
  </channel>
</rss>
