<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Security Anecdotes</title>
	<atom:link href="http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/</link>
	<description>Bringing Fire To The Village: Your Source For Computer, Network &#38; Information Security News from Dave Lewis, Security Blogger</description>
	<lastBuildDate>Mon, 15 Mar 2010 13:04:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dave Lewis</title>
		<link>http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/comment-page-1/#comment-67795</link>
		<dc:creator>Dave Lewis</dc:creator>
		<pubDate>Fri, 21 Dec 2007 15:52:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/#comment-67795</guid>
		<description>@CJ

Love it! Too funny, thanks for that.</description>
		<content:encoded><![CDATA[<p>@CJ</p>
<p>Love it! Too funny, thanks for that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CJ</title>
		<link>http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/comment-page-1/#comment-67792</link>
		<dc:creator>CJ</dc:creator>
		<pubDate>Fri, 21 Dec 2007 15:19:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/#comment-67792</guid>
		<description>My all-time favorite archive of lame excuses to not secure something:

http://www.crypto.com/bingo/pr</description>
		<content:encoded><![CDATA[<p>My all-time favorite archive of lame excuses to not secure something:</p>
<p><a href="http://www.crypto.com/bingo/pr" rel="nofollow">http://www.crypto.com/bingo/pr</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Lewis</title>
		<link>http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/comment-page-1/#comment-60938</link>
		<dc:creator>Dave Lewis</dc:creator>
		<pubDate>Sat, 03 Nov 2007 01:00:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/#comment-60938</guid>
		<description>@Abuse Desk

OMFG That was hysterical! 

Thanks!</description>
		<content:encoded><![CDATA[<p>@Abuse Desk</p>
<p>OMFG That was hysterical! </p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abuse Desk</title>
		<link>http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/comment-page-1/#comment-60929</link>
		<dc:creator>Abuse Desk</dc:creator>
		<pubDate>Fri, 02 Nov 2007 22:52:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/#comment-60929</guid>
		<description>Here&#039;s a few you might find amusing.  From actual conversations with IT site admins on business class service.

&quot;If thats so vulnerable, why hasn&#039;t it been attacked yet?&quot;  -- customer questioning advice to firewall a server better

&quot;But I thought Firefox was a firewall!!&quot; -- customer being advised on need to firewall their LAN.

&quot;I&#039;m not sure why you are calling this abuse, it&#039;s not like he&#039;s doing it on purpose.&quot;  -- customer objecting to being held accountable for their malware infestation

&quot;You guys call here, you little pissant trying to tell me about my computers&quot; -- some self described network administrator complaining of being notified his LAN was overrun by spambots and malware.

&quot;I have a Law Degree from Harvard.... I don&#039;t need you to tell me how to troubleshoot.&quot; -- customer complaining when given troubleshooting advice

&quot;I checked the machine and it was not connecting anywhere on port 25. It was only connecting on port 80 to find hosts to compromise so I have no indication that it sent any spam.&quot; -- customer baffled as to how his LAN could be outbounding malware spams.

&quot;Loyalty tests have been given to all computers on the network, and all failing members have been purged. The streets run red with blood.&quot; -- amusing customer who audited his LAN successfully.

&quot;We have a pix box so am I correct in assuming that acts as a firewall?&quot; -- alert customer</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a few you might find amusing.  From actual conversations with IT site admins on business class service.</p>
<p>&#8220;If thats so vulnerable, why hasn&#8217;t it been attacked yet?&#8221;  &#8212; customer questioning advice to firewall a server better</p>
<p>&#8220;But I thought Firefox was a firewall!!&#8221; &#8212; customer being advised on need to firewall their LAN.</p>
<p>&#8220;I&#8217;m not sure why you are calling this abuse, it&#8217;s not like he&#8217;s doing it on purpose.&#8221;  &#8212; customer objecting to being held accountable for their malware infestation</p>
<p>&#8220;You guys call here, you little pissant trying to tell me about my computers&#8221; &#8212; some self described network administrator complaining of being notified his LAN was overrun by spambots and malware.</p>
<p>&#8220;I have a Law Degree from Harvard&#8230;. I don&#8217;t need you to tell me how to troubleshoot.&#8221; &#8212; customer complaining when given troubleshooting advice</p>
<p>&#8220;I checked the machine and it was not connecting anywhere on port 25. It was only connecting on port 80 to find hosts to compromise so I have no indication that it sent any spam.&#8221; &#8212; customer baffled as to how his LAN could be outbounding malware spams.</p>
<p>&#8220;Loyalty tests have been given to all computers on the network, and all failing members have been purged. The streets run red with blood.&#8221; &#8212; amusing customer who audited his LAN successfully.</p>
<p>&#8220;We have a pix box so am I correct in assuming that acts as a firewall?&#8221; &#8212; alert customer</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Lewis</title>
		<link>http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/comment-page-1/#comment-52207</link>
		<dc:creator>Dave Lewis</dc:creator>
		<pubDate>Wed, 29 Aug 2007 02:27:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/#comment-52207</guid>
		<description>@Steve, Benny, Portswigger, Taylor and Myrcurial

Thanks everyone for your comments! I loved the snmpwalk and %n lines. Brilliant!</description>
		<content:encoded><![CDATA[<p>@Steve, Benny, Portswigger, Taylor and Myrcurial</p>
<p>Thanks everyone for your comments! I loved the snmpwalk and %n lines. Brilliant!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Security Anecdotes &#171; From The Watch Tower</title>
		<link>http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/comment-page-1/#comment-51568</link>
		<dc:creator>Security Anecdotes &#171; From The Watch Tower</dc:creator>
		<pubDate>Fri, 24 Aug 2007 15:09:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/#comment-51568</guid>
		<description>[...] Site [...]</description>
		<content:encoded><![CDATA[<p>[...] Site [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: taylor</title>
		<link>http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/comment-page-1/#comment-51549</link>
		<dc:creator>taylor</dc:creator>
		<pubDate>Fri, 24 Aug 2007 13:48:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/#comment-51549</guid>
		<description>upon notifying a security hardware vendor that their device reboots when running an snmpwalk against it, i was told &quot;you shouldn&#039;t do that - we don&#039;t support snmpwalk&quot;.</description>
		<content:encoded><![CDATA[<p>upon notifying a security hardware vendor that their device reboots when running an snmpwalk against it, i was told &#8220;you shouldn&#8217;t do that &#8211; we don&#8217;t support snmpwalk&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PortSwigger</title>
		<link>http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/comment-page-1/#comment-51437</link>
		<dc:creator>PortSwigger</dc:creator>
		<pubDate>Thu, 23 Aug 2007 15:16:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/#comment-51437</guid>
		<description>A vendor&#039;s response to notification of a format string bug:

&quot;I don&#039;t understand. You should be typing your password. Where are all those %n&#039;s coming from?&quot;</description>
		<content:encoded><![CDATA[<p>A vendor&#8217;s response to notification of a format string bug:</p>
<p>&#8220;I don&#8217;t understand. You should be typing your password. Where are all those %n&#8217;s coming from?&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benny K</title>
		<link>http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/comment-page-1/#comment-51378</link>
		<dc:creator>Benny K</dc:creator>
		<pubDate>Thu, 23 Aug 2007 06:45:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/#comment-51378</guid>
		<description>Some of my own:

    * Why do we need to secure this? We are not a bank. (from the CTO of a manufacturing company)
    * We need to get this fixed. We&#039;ll worry about security tomorrow (yeah right)
    * We have no security policy
    * Why can&#039;t we allow ipsec from the vendor into this blackbox in the corporate LAN? (aka preventing the huge hole in the firewall)

And if you need more IT humor, just hit the BOFH archives.</description>
		<content:encoded><![CDATA[<p>Some of my own:</p>
<p>    * Why do we need to secure this? We are not a bank. (from the CTO of a manufacturing company)<br />
    * We need to get this fixed. We&#8217;ll worry about security tomorrow (yeah right)<br />
    * We have no security policy<br />
    * Why can&#8217;t we allow ipsec from the vendor into this blackbox in the corporate LAN? (aka preventing the huge hole in the firewall)</p>
<p>And if you need more IT humor, just hit the BOFH archives.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Dispensa</title>
		<link>http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/comment-page-1/#comment-51372</link>
		<dc:creator>Steve Dispensa</dc:creator>
		<pubDate>Thu, 23 Aug 2007 03:36:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.liquidmatrix.org/blog/2007/08/22/security-anecdotes/#comment-51372</guid>
		<description>“We have two factor authentication, a) username b) password”

Amazingly enough, I recently had lunch with a senior security official at a bank, who told me that the term &quot;two-factor authentication&quot; is defined very broadly from the perspective of FFIEC compliance - it can simply be two different passwords, or a password plus the fact that you&#039;ve connected from that IP address before, or other similarly vague things.

The accepted security-industry definition of two-factor is much stricter than this federal standard.</description>
		<content:encoded><![CDATA[<p>“We have two factor authentication, a) username b) password”</p>
<p>Amazingly enough, I recently had lunch with a senior security official at a bank, who told me that the term &#8220;two-factor authentication&#8221; is defined very broadly from the perspective of FFIEC compliance &#8211; it can simply be two different passwords, or a password plus the fact that you&#8217;ve connected from that IP address before, or other similarly vague things.</p>
<p>The accepted security-industry definition of two-factor is much stricter than this federal standard.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
