<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:georss="http://www.georss.org/georss" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-968722795408899035</atom:id><lastBuildDate>Sat, 31 Oct 2009 06:14:46 +0000</lastBuildDate><title>Grok Computer Security</title><description>One hacker's odyssey to understand computer security</description><link>http://grok-security.blogspot.com/</link><managingEditor>noreply@blogger.com (Michael)</managingEditor><generator>Blogger</generator><openSearch:totalResults>56</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/Grok-Security" type="application/rss+xml" /><feedburner:emailServiceId>Grok-Security</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-1986021862969113637</guid><pubDate>Thu, 13 Aug 2009 13:59:00 +0000</pubDate><atom:updated>2009-08-13T07:16:04.554-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">defense in depth</category><category domain="http://www.blogger.com/atom/ns#">9/11</category><title>Missing Russian Ship</title><description>Right out of a Tom Clancy &lt;a href="http://en.wikipedia.org/wiki/Sum_of_all_fears"&gt;novel&lt;/a&gt;, a 4,000 tonne cargo ship is missing.  Reportedly, this ship had nothing worth hijacking.  There are not a lot of facts about this available but there are some interesting bits:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;10 armed men boarded the ship about a week before it disappeared.  They left 12 hours later.&lt;/li&gt;&lt;li&gt;The ship spent two weeks in &lt;a href="http://en.wikipedia.org/wiki/Kaliningrad"&gt;Kaliningrad&lt;/a&gt; before beginning its voyage.&lt;/li&gt;&lt;li&gt;The Russians are searching for  the ship with all available resources.&lt;/li&gt;&lt;/ol&gt;As reported &lt;a href="http://www.encyclopedia.com/doc/1P2-8639619.html"&gt;here&lt;/a&gt;, the Russians have battlefield nuclear weapons in Kaliningrad.&lt;br /&gt;&lt;br /&gt;I wish the Russians good luck in their search and I hope the NATO forces provide all available resources to assist.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-1986021862969113637?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=Gs8PocccTQw:S8tTlm6BCWA:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=Gs8PocccTQw:S8tTlm6BCWA:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=Gs8PocccTQw:S8tTlm6BCWA:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=Gs8PocccTQw:S8tTlm6BCWA:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=Gs8PocccTQw:S8tTlm6BCWA:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=Gs8PocccTQw:S8tTlm6BCWA:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/Gs8PocccTQw/missing-russian-ship.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2009/08/missing-russian-ship.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-6032618850053678368</guid><pubDate>Fri, 24 Apr 2009 03:45:00 +0000</pubDate><atom:updated>2009-04-23T20:48:59.755-07:00</atom:updated><title>Data Protection for Virtualized Servers</title><description>I am recording a webcast live next Wednesday.  It's free and only requires a short pre-registration.&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.brighttalk.com/webcasts/3762/attend"&gt;Data Protection for Virtualized Servers&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;object height="330" width="353"&gt;  &lt;param name="movie" value="http://www.brighttalk.com/dc/swf/dotcom_base.swf?212"&gt; &lt;/param&gt; &lt;param name="flashvars" value="channelid=286&amp;commid=2744&amp;autoStart=FALSE"&gt; &lt;/param&gt; &lt;embed src="http://www.brighttalk.com/dc/swf/dotcom_base.swf?234" type="application/x-shockwave-flash" width="353" height="330" wmode="transparent" flashvars="channelid=286&amp;commid=2744&amp;autoStart=FALSE"&gt; &lt;/embed&gt; &lt;/object&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-6032618850053678368?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=S2NHlwqwFSk:-6cIMQ2cfvs:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=S2NHlwqwFSk:-6cIMQ2cfvs:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=S2NHlwqwFSk:-6cIMQ2cfvs:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=S2NHlwqwFSk:-6cIMQ2cfvs:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=S2NHlwqwFSk:-6cIMQ2cfvs:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=S2NHlwqwFSk:-6cIMQ2cfvs:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/S2NHlwqwFSk/data-protection-for-virtualized-servers.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2009/04/data-protection-for-virtualized-servers.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-8703151861581861943</guid><pubDate>Fri, 10 Apr 2009 14:05:00 +0000</pubDate><atom:updated>2009-04-10T07:26:39.123-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Network Security</category><title>How many manhole covers are in San Jose, CA?</title><description>&lt;a href="http://www.mercurynews.com/ci_12106300?source=most_viewed"&gt;From the Mercury News&lt;/a&gt;:&lt;br /&gt;&lt;blockquote&gt;John Britton, a spokesman for AT&amp;amp;T, said it appears somebody opened a manhole in South San Jose, climbed down eight to 10 feet and cut four or five fiber-optic cables.  Britton also said there was a report of underground cables being cut in San Carlos.&lt;br /&gt;AT&amp;amp;T's contract with the Communication Workers of America expired at 11:59 p.m. Saturday, but Britton said "we have a really good relationship with the union" and that negotiations continue between the two sides.&lt;/blockquote&gt;It's my understanding that a single cut in one location would not cause the outage we recently experienced.  There would need to be two or more cuts at strategic locations to cause an outage to cell phone, land line, and emergency services.&lt;br /&gt;&lt;br /&gt;Knowing which manhole covers to open would require very specific knowledge of the Bay Area fiber infrastructure.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-8703151861581861943?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=8ipR7QtIIo4:0fDe3zCoj6Q:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=8ipR7QtIIo4:0fDe3zCoj6Q:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=8ipR7QtIIo4:0fDe3zCoj6Q:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=8ipR7QtIIo4:0fDe3zCoj6Q:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=8ipR7QtIIo4:0fDe3zCoj6Q:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=8ipR7QtIIo4:0fDe3zCoj6Q:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/8ipR7QtIIo4/how-many-manhole-covers-are-in-san-jose.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2009/04/how-many-manhole-covers-are-in-san-jose.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-2143446808421673859</guid><pubDate>Tue, 31 Mar 2009 19:56:00 +0000</pubDate><atom:updated>2009-03-31T16:11:22.673-07:00</atom:updated><title>Securing the Dynamic Data Center</title><description>I am recording a webcast live today.  It's free and only requires a short pre-registration.&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.brighttalk.com/webcasts/3430/attend"&gt;Securing the Dynamic Data Center&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;object width="353" height="330"&gt; &lt;param name="movie" value="http://www.brighttalk.com/dc/swf/dotcom_base.swf?212"&gt; &lt;/param&gt; &lt;param name="flashvars" value="channelid=679&amp;commid=2504&amp;autoStart=FALSE"&gt; &lt;/param&gt; &lt;embed src="http://www.brighttalk.com/dc/swf/dotcom_base.swf?234" type="application/x-shockwave-flash" width="353" height="330" wmode="transparent" flashvars="channelid=679&amp;commid=2504&amp;autoStart=FALSE"&gt; &lt;/embed&gt; &lt;/object&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-2143446808421673859?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=0tg2XIu_AJU:iBo6q9LUwKE:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=0tg2XIu_AJU:iBo6q9LUwKE:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=0tg2XIu_AJU:iBo6q9LUwKE:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=0tg2XIu_AJU:iBo6q9LUwKE:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=0tg2XIu_AJU:iBo6q9LUwKE:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=0tg2XIu_AJU:iBo6q9LUwKE:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/0tg2XIu_AJU/securing-dynamic-data-center.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2009/03/securing-dynamic-data-center.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-2912540240012786060</guid><pubDate>Tue, 31 Mar 2009 04:13:00 +0000</pubDate><atom:updated>2009-03-30T21:16:35.915-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Internet Security</category><title>Conficker and April 1</title><description>Well, here’s the Wikipedia entries that got me thinking:&lt;br /&gt;&lt;blockquote&gt; As a countermeasure, ICANN and several TLD registrars began in February 2009 a coordinated barring of transfers and registrations for these domains”&lt;br /&gt;&lt;br /&gt;Variant C contains code to sidestep these countermeasures by generating an expanded daily list of 50000 domains across 110 TLDs. This new pull mechanism, however, is disabled until April 1&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;I’ve also been following the work at SRI regarding this threat.&lt;br /&gt;&lt;br /&gt;Even 1 million Variant C infections results in potentially 50 billion whois queries.&lt;br /&gt;&lt;br /&gt;I think Wednesday is going to be a slow day on the Internet.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-2912540240012786060?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=lfnwtgtf5EQ:rAjbDTceswQ:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=lfnwtgtf5EQ:rAjbDTceswQ:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=lfnwtgtf5EQ:rAjbDTceswQ:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=lfnwtgtf5EQ:rAjbDTceswQ:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=lfnwtgtf5EQ:rAjbDTceswQ:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=lfnwtgtf5EQ:rAjbDTceswQ:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/lfnwtgtf5EQ/conficker-and-april-1.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2009/03/conficker-and-april-1.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-2727489858495950725</guid><pubDate>Wed, 04 Feb 2009 04:37:00 +0000</pubDate><atom:updated>2009-02-03T20:45:58.787-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">virtualization security</category><category domain="http://www.blogger.com/atom/ns#">trust zones</category><category domain="http://www.blogger.com/atom/ns#">Network Security</category><title>Heartland Breach</title><description>&lt;span style="font-size:130%;"&gt;Summary:&lt;/span&gt;&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Level 1 credit card processor fails to prevent data loss effecting hundreds of millions of transactions. &lt;/li&gt;&lt;li&gt;Attacker installed tools on Heartland server, inside the PCI trust path network &lt;/li&gt;&lt;li&gt;Tools “sniffed” transactions and sent data to system(s) outside North America&lt;/li&gt;&lt;/ul&gt;&lt;blockquote&gt;&lt;a href="http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;amp;articleId=333222&amp;amp;intsrc=news_ts_head"&gt;“Heartland has said intruders broke into its systems sometime last year and planted malware that they used to steal the card data. The number of compromised cards still isn't known. But Heartland processes more than 100 million transactions per month.”&lt;br /&gt;- Banks, customers feel the fallout of the Heartland breach. 2/2/2009. Jalkumar Vijayan, Computer World, Security. &lt;/a&gt;&lt;/blockquote&gt;&lt;span style="font-size:130%;"&gt;&lt;br /&gt;Breach analysis:&lt;/span&gt;&lt;br /&gt;Root cause includes but is not limited to the following:&lt;ul&gt;&lt;li&gt;Failure of host based intrusion prevention system (HIPS) &lt;/li&gt;&lt;li&gt;Failure of network based intrusion prevention systems (IDP) &lt;/li&gt;&lt;li&gt;Failure of configuration management, to detect changes to host and network configuration &lt;/li&gt;&lt;li&gt;Failure of separation of duties and detection of abuse or escalation of privilege &lt;/li&gt;&lt;li&gt;Failure to segment the processor network and enforce a zone of trust&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;In summary, Heartland failed to properly implement and enforce defense-in-depth, network segmentation and separation of duties. Remember, Heartland is a level 1 PCI processor and was required by regulation to get this right.  This means Heartland's auditors failed.&lt;br /&gt;&lt;span style="font-size:130%;"&gt;&lt;br /&gt;Solution:&lt;/span&gt;&lt;br /&gt;Catbird directly addresses all of the above, except for HIPS.  HIPS requires an agent on every end-point, this is not a component of our architecture, which is agent-less by design.  Our customers are able to implement and enforce defense-in-depth using Catbird TrustZones™ security policies, virtual infrastructure configuration management and virtual machine tracking technologies.  These technologies include but are not limited to:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Policy and detection templates for IDP, to monitor and control network flows between zones and intra-machine flows inside a trust zone &lt;/li&gt;&lt;li&gt;Policy based configuration monitoring and enforcement using session blocking and quarantine, including quarantine of virtual machines &lt;/li&gt;&lt;li&gt;Monitoring of virtual administrator activities and enforcement of dual controls for virtual machine connection to network zones&lt;/li&gt;&lt;li&gt;Catbird TrustZones monitor and enforce network segmentation within and between machines on any network, VLAN or port group&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;In summary, proper deployment of Catbird TrustZones technology would have detected and prevented a data breach like the one that occurred at Heartland.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-2727489858495950725?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=MtyhQi6m5Wk:kP-VK-yAo70:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=MtyhQi6m5Wk:kP-VK-yAo70:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=MtyhQi6m5Wk:kP-VK-yAo70:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=MtyhQi6m5Wk:kP-VK-yAo70:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=MtyhQi6m5Wk:kP-VK-yAo70:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=MtyhQi6m5Wk:kP-VK-yAo70:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/MtyhQi6m5Wk/heartland-breach.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2009/02/heartland-breach.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-7074738675879953080</guid><pubDate>Fri, 12 Dec 2008 19:09:00 +0000</pubDate><atom:updated>2008-12-12T11:52:29.931-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">virtualization security</category><title>Guardians?  What Guardians?</title><description>Yesterday, the &lt;a href="http://www.nytimes.com/"&gt;New York Times&lt;/a&gt; covered the recent arrest of &lt;a href="http://www.nytimes.com/2008/12/12/business/12scheme.html?em=&amp;amp;pagewanted=all"&gt;Bernard L. Madoff.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Madoff, a prominent Wall Street Hedge fund manager, has admitted to running a $50 Billion Ponzi scheme.&lt;br /&gt;&lt;br /&gt;While law enforcement has been quick to react, the revelation came when Mr. Madoff confessed to an associate.  While rival Hedge fund managers had been suspicious that Madoff's results were too good to be true, &lt;span style="font-weight: bold;"&gt;THE REGULATORS HAD NO CLUE&lt;/span&gt;.&lt;br /&gt;&lt;br /&gt;Years ago, there were many warnings on and off the Hill.  Regulators, economists and many others sounded the alarm that allowing an entire financial industry to exist without regulations was a bad idea.  However, the standard responses were: regulations are bad, the market will police itself, we can trust our Hedge fund managers.  Well, look at what has happened.  AIG failed to accurately assess and hedge their risks.  Dozens of financial institutions have gone under and hundreds more are at risk.  Hedge fund managers have admitted to running a crooked game.&lt;br /&gt;&lt;br /&gt;The lesson is clear, &lt;span style="font-weight: bold;"&gt;systems and the people who work within them are not self-policing&lt;/span&gt;.  Shocker.  I am sure &lt;a href="http://en.wikipedia.org/wiki/Niccol%C3%83%C2%B2_Machiavelli"&gt;Machiavelli&lt;/a&gt; and &lt;a href="http://en.wikipedia.org/wiki/Juvenal"&gt;Juvenalis&lt;/a&gt; are laughing at the continuing naivete of the human race.&lt;br /&gt;&lt;br /&gt;Now, right now, we have a very similar pattern emerging in information technology.  Institutions around the world are virtualizing like crazy.   IT is deploying the vast majority of these virtual infrastructures without any of the protections I recommend &lt;a href="http://grok-security.blogspot.com/2008/11/risk-mitigation-for-virtual.html"&gt;here&lt;/a&gt;.  PCI, HIPAA, SOX, you name it, these IT Groups are putting sensitive data about you and me, valuable data worth billions of dollars is at risk.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Where are the Guardians?&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;The Guardians are out to lunch, they missed the memo, they drank the Kool-aid from the platform vendors.&lt;br /&gt;&lt;br /&gt;People like myself, &lt;a href="http://rationalsecurity.typepad.com/"&gt;Chris Hoff&lt;/a&gt;, &lt;a href="http://gregness.wordpress.com/"&gt;Greg Ness&lt;/a&gt;, &lt;a href="http://www.usenix.org/events/nsdi08/tech/pratt.pdf"&gt;Ian Pratt&lt;/a&gt;, &lt;a href="http://www.blackhat.com/presentations/bh-usa-07/Baker/Presentation/BH07_Baker_WSV_Hypervisor_Security.pdf"&gt;Brandon Baker&lt;/a&gt; and many others are sounding the alarm.&lt;br /&gt;&lt;br /&gt;It's time for the Guardians to get to work.  It's time for the IT security team to get off their butts and start addressing this issue.&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.catbird.com/"&gt;Michael&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-7074738675879953080?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=Y-cvFKvTYvY:jVKH8jA9iZ0:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=Y-cvFKvTYvY:jVKH8jA9iZ0:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=Y-cvFKvTYvY:jVKH8jA9iZ0:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=Y-cvFKvTYvY:jVKH8jA9iZ0:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=Y-cvFKvTYvY:jVKH8jA9iZ0:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=Y-cvFKvTYvY:jVKH8jA9iZ0:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/Y-cvFKvTYvY/guardians-what-guardians.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2008/12/guardians-what-guardians.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-7543061502259078334</guid><pubDate>Tue, 09 Dec 2008 18:16:00 +0000</pubDate><atom:updated>2008-12-09T10:37:35.140-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Web Security</category><category domain="http://www.blogger.com/atom/ns#">pharming</category><category domain="http://www.blogger.com/atom/ns#">Internet Security</category><title>Registrar's are still a weak link</title><description>Very nice article on the hack against &lt;a href="http://www.checkfree.com"&gt;Check Free&lt;/a&gt; &lt;a href="http://voices.washingtonpost.com/securityfix/2008/12/digging_deeper_into_the_checkf.html"&gt;here&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Current theories center on the likelihood that a Check Free employee got suckered by a phishing or straight-up social engineering attack.&lt;br /&gt;&lt;br /&gt;I'm going to hazard a guess that this was a spear-phish or more targeted form of attack.  A quick search of Linkedin, Facebook and other social networking applications finds a treasure trove of CheckFree/Fiserv employees.&lt;br /&gt;&lt;br /&gt;It's a small step to go from these links to a targeted attack against Fiserv IT staff.&lt;br /&gt;&lt;br /&gt;However, as the article notes Fiserv was not the only target in this attack and Financial Institutions (FI) are dangerously reliant on a single registrar.&lt;br /&gt;&lt;br /&gt;My recommendations:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;FI's and others must monitor and protect themselves from domain hijack -- I recommend &lt;a href="http://www.catbird.com/our_services/pharming_shield_s.shtml"&gt;Pharming Shield&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;Get social networking applications out of the data center, IT personnel must not use corporate resources (including email) to access these sites&lt;/li&gt;&lt;li&gt;The Financial Industry is at risk from a single-point of failure at Network Solutions.  This must be addressed through community efforts and directly by the platform providers.&lt;/li&gt;&lt;/ol&gt;Happy Holidays!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-7543061502259078334?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=i39_Z1KBseU:1J5VuOWKduA:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=i39_Z1KBseU:1J5VuOWKduA:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=i39_Z1KBseU:1J5VuOWKduA:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=i39_Z1KBseU:1J5VuOWKduA:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=i39_Z1KBseU:1J5VuOWKduA:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=i39_Z1KBseU:1J5VuOWKduA:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/i39_Z1KBseU/registrars-are-still-weak-link.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2008/12/registrars-are-still-weak-link.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-8672896588530295625</guid><pubDate>Wed, 12 Nov 2008 19:41:00 +0000</pubDate><atom:updated>2008-11-25T09:48:25.752-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">virtualization security</category><title>Virtual Security and Compliance Webcast</title><description>Recorded last week, go &lt;a href="http://www.brighttalk.com/webcasts/1318/play"&gt;here &lt;/a&gt;to register and listen (sorry, the sound is ahead of the slides, I am trying to get that fixed).&lt;br /&gt;&lt;br /&gt;Shout out to &lt;a href="http://www.blogger.com/tarrysingh.blogspot.com"&gt;Tarry &lt;/a&gt;and everyone else who participated.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-8672896588530295625?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=IxnCqJV_Bf4:jX1J7L7C1_I:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=IxnCqJV_Bf4:jX1J7L7C1_I:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=IxnCqJV_Bf4:jX1J7L7C1_I:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=IxnCqJV_Bf4:jX1J7L7C1_I:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=IxnCqJV_Bf4:jX1J7L7C1_I:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=IxnCqJV_Bf4:jX1J7L7C1_I:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/IxnCqJV_Bf4/virtual-security-and-compliance-webcast.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2008/11/virtual-security-and-compliance-webcast.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-1026216434192037323</guid><pubDate>Tue, 11 Nov 2008 05:06:00 +0000</pubDate><atom:updated>2008-12-10T21:17:32.804-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">virtualization security</category><title>Risk mitigation for virtual infrastructures</title><description>&lt;p&gt;Virtualization in the Data Center introduces the following: (skip down below)&lt;br /&gt;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;br /&gt;&lt;td style="background: rgb(153, 51, 102) none repeat scroll 0% 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" width="36"&gt;&lt;br /&gt;&lt;/td&gt;&lt;br /&gt;&lt;td style="background: rgb(153, 51, 102) none repeat scroll 0% 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; text-align: center; color: white;" width="200"&gt;&lt;b&gt;EFFECT&lt;/b&gt;&lt;br /&gt;&lt;/td&gt;&lt;br /&gt;&lt;td style="background: rgb(153, 51, 102) none repeat scroll 0% 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; text-align: center; color: white;" width="200"&gt;&lt;b&gt;RISK&lt;/b&gt;&lt;br /&gt;&lt;/td&gt;&lt;br /&gt;&lt;/tr&gt;&lt;tr&gt;&lt;br /&gt;&lt;td width="36"&gt;1.&lt;/td&gt;&lt;br /&gt;&lt;td width="200"&gt;Flattens infrastructure and networks&lt;/td&gt;&lt;br /&gt;&lt;td width="200"&gt;Unauthorized network access or communication&lt;/td&gt;&lt;br /&gt;&lt;/tr&gt;&lt;tr&gt;&lt;br /&gt;&lt;td style="background: rgb(217, 217, 217) none repeat scroll 0% 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" width="36"&gt;2.&lt;/td&gt;&lt;br /&gt;&lt;td style="background: rgb(217, 217, 217) none repeat scroll 0% 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" width="200"&gt;Adds new operating system and infrastructure layers&lt;/td&gt;&lt;br /&gt;&lt;td style="background: rgb(217, 217, 217) none repeat scroll 0% 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" width="200"&gt;Denial of service and data security breach due to software defects&lt;/td&gt;&lt;br /&gt;&lt;/tr&gt;&lt;tr&gt;&lt;br /&gt;&lt;td width="36"&gt;&lt;p class=""&gt;3.&lt;/p&gt;&lt;/td&gt;&lt;br /&gt;&lt;td width="200"&gt;Collapses roles and increases privilege of administrators&lt;br /&gt;&lt;/td&gt;&lt;br /&gt;&lt;td width="200"&gt;Escalation of privilege, abuse of privilege&lt;br /&gt;&lt;/td&gt;&lt;br /&gt;&lt;/tr&gt;&lt;tr&gt;&lt;br /&gt;&lt;td style="background: rgb(217, 217, 217) none repeat scroll 0% 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" width="36"&gt;4.&lt;br /&gt;&lt;/td&gt;&lt;br /&gt;&lt;td style="background: rgb(217, 217, 217) none repeat scroll 0% 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" width="200"&gt;Increases transience, mobility and frequency of change within the data center&lt;br /&gt;&lt;/td&gt;&lt;br /&gt;&lt;td style="background: rgb(217, 217, 217) none repeat scroll 0% 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" width="200"&gt;Misconfiguration, server sprawl and data security breach&lt;br /&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;br /&gt;&lt;ol&gt;&lt;li&gt;Virtual machine (VM) hosts, clusters and data centers reduce the logical and physical segmentation of systems and networks.  This flattening exacerbates the risk of unauthorized access due to reduced visibility of events on the virtualized network.  &lt;/li&gt;&lt;br /&gt;&lt;p&gt;&lt;b&gt;Mitigation:&lt;/b&gt; implement increased monitoring and access controls for each virtualized access layer and network.  Monitoring must correlate virtual infrastructure management, network traffic, security events and validation of intra-VM access control policies.&lt;/p&gt;&lt;li&gt;The Hypervisor is a new operating system, which along with hypervisor and virtual infrastructure management tools increases the defect, vulnerability and attack threat surface of the data center.&lt;/li&gt;&lt;br /&gt;&lt;p&gt;&lt;b&gt;Mitigation:&lt;/b&gt; incorporate all new software and management layers into your vulnerability management system (VMS).  The VMS must be mandatory and integrated with automated discovery and validation of virtualized infrastructures.&lt;/p&gt;&lt;li&gt;Like the introduction of DBAs for SQL databases and Domain Administrators for Window’s systems, Virtual Administrators have privileges that allow them to bypass existing controls and effectively access underlying systems and data at the hardware layer.&lt;/li&gt;&lt;br /&gt;&lt;p&gt;&lt;b&gt;Mitigation: &lt;/b&gt;implement compensating controls to log and audit all Virtual Administrator activities.  Introduce dual controls and separation of duties for critical functions.  You must deploy tools to perform continuous validation of these secondary controls to detect and prevent abuse of privilege.  This will also reduce the risk from virtual machine breakout and hyperjacking.&lt;br /&gt;&lt;/p&gt;&lt;li&gt;Servers are now files.  Virtual machine mobility, snapshots, roll-backs and other features of virtualization have magnified the rate of change within the data center.  This increase in operational velocity leads to increased risk of configuration error, capacity failures and for a security breach due to incorrect configuration or a lapse of controls.&lt;/li&gt;&lt;br /&gt;&lt;p&gt;&lt;b&gt;Mitigation:&lt;/b&gt; extend configuration and life-cycle management processes to track virtual machines.  These processes must be effective regardless of the mobility and non-linear attributes of virtual machines.  Configuration management tools must enforce mandatory controls and support correlation of virtual and physical infrastructure configuration attributes – extending from virtual machine internals to external network access layers.  Monitor and audit direct access to virtual machines files at the operating system and storage access layers.&lt;br /&gt;&lt;/p&gt;&lt;/ol&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-1026216434192037323?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=pP5SonNsaIo:aTnm2cOXLVs:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=pP5SonNsaIo:aTnm2cOXLVs:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=pP5SonNsaIo:aTnm2cOXLVs:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=pP5SonNsaIo:aTnm2cOXLVs:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=pP5SonNsaIo:aTnm2cOXLVs:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=pP5SonNsaIo:aTnm2cOXLVs:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/pP5SonNsaIo/risk-mitigation-for-virtual.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2008/11/risk-mitigation-for-virtual.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-2509070895826725197</guid><pubDate>Fri, 31 Oct 2008 17:22:00 +0000</pubDate><atom:updated>2008-11-11T13:36:13.944-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Internet Security</category><title>A few Podcasts with Dane Deutch</title><description>&lt;a href="http://www.dcsnetlink.com/podcasts-CB.asp"&gt;These&lt;/a&gt; were done with a &lt;a href="http://www.catbird.com/"&gt;Catbird &lt;/a&gt;partner &lt;a href="http://www.dcsnetlink.com/"&gt;DCS NetLink&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-2509070895826725197?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=aJHtXi9Vmao:qj889Hf7C3g:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=aJHtXi9Vmao:qj889Hf7C3g:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=aJHtXi9Vmao:qj889Hf7C3g:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=aJHtXi9Vmao:qj889Hf7C3g:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=aJHtXi9Vmao:qj889Hf7C3g:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=aJHtXi9Vmao:qj889Hf7C3g:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/aJHtXi9Vmao/few-podcasts-with-dane-deutch.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2008/10/few-podcasts-with-dane-deutch.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-2984727122201000310</guid><pubDate>Thu, 11 Sep 2008 20:11:00 +0000</pubDate><atom:updated>2008-09-11T16:52:33.941-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Security</category><category domain="http://www.blogger.com/atom/ns#">9/11</category><title>7 Years Later</title><description>&lt;p&gt;&lt;span style="color: rgb(0, 0, 153);font-family:Verdana,Geneva,Arial,Helvetica,sans-serif;font-size:85%;"  &gt;&lt;span style="font-size:180%;"&gt;&lt;strong&gt;&lt;/strong&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;blockquote&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 153);font-family:Verdana,Geneva,Arial,Helvetica,sans-serif;font-size:100%;"  &gt;&lt;strong&gt;Public release of PSA's&lt;/strong&gt;&lt;/span&gt;&lt;span style="color: rgb(0, 0, 153);font-family:Verdana,Geneva,Arial,Helvetica,sans-serif;font-size:100%;"  &gt;&lt;strong&gt; WMD REPORT CARD&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;&lt;span style="color: rgb(0, 0, 153);font-family:Verdana,Geneva,Arial,Helvetica,sans-serif;font-size:85%;"  &gt;&lt;strong&gt;Focusing on efforts since 2005, our Report Card gives the government a "C".  &lt;/strong&gt;    &lt;br /&gt; &lt;br /&gt;&lt;strong&gt;"Moving from a D to a C in three years is progress, but not really acceptable progress," Hamilton said.&lt;br /&gt;&lt;/strong&gt;&lt;span style="font-weight: bold;"&gt;      &lt;br /&gt;"What we need now is for the next Administration to commit itself to unwavering dedication to ensure that we capitalize on the progress we've made and push forward to improve and solidify our efforts on all fronts," Gorton said. "Now is the time to turn our resolve into action." &lt;/span&gt;&lt;/span&gt;&lt;/blockquote&gt;PDF for full report card &lt;a href="http://psaonline.org/downloads/ReportCard%208-25-08.pdf"&gt;here&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;I've spent the last couple of weeks re-reading the &lt;a href="http://www.gpoaccess.gov/911/pdf/fullreport.pdf"&gt;full commission report&lt;/a&gt;, and I am struck by how few of their direct recommendations have been implemented. It's possible that the current administration has done more than I know, but here is the focus of the recommendations:&lt;br /&gt;&lt;br /&gt;&lt;a href="http://govinfo.library.unt.edu/911/report/911Report_Ch13.htm"&gt;Chapter 13: &lt;span style="font-style: italic;"&gt;HOW TO DO IT?  A DIFFERENT WAY OF ORGANIZING THE GOVERNMENT&lt;/span&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;This chapter emphasizes 13 (see below) of the 41 recommendations made by the commission.&lt;br /&gt;Of these 13, two may have been implemented, two others partially implemented, the remaining 9 are incomplete.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-size:130%;"&gt;&lt;span style="font-weight: bold;"&gt;Failing on 9 out of 13, I give them an F!&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;---------------------------&lt;br /&gt;&lt;blockquote&gt;&lt;strong&gt;1. Recommendation: We recommend the establishment of a National Counterterrorism Center (NCTC), built on the foundation of the existing Terrorist Threat Integration Center (TTIC). Breaking the older mold of national government organization, this NCTC should be a center for joint operational planning &lt;em&gt;and&lt;/em&gt; joint intelligence, staffed by personnel from the various agencies. The head of the NCTC should have authority to evaluate the performance of the people assigned to the Center.&lt;br /&gt;&lt;/strong&gt;&lt;br /&gt;&lt;/blockquote&gt;&lt;a href="http://www.nctc.gov/about_us/about_nctc.html"&gt;NCTC was established in 2004.&lt;/a&gt;  Does the head of the NCTC have the authority to evaluate the performance of their personnel?&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;&lt;/strong&gt;&lt;blockquote&gt;&lt;strong&gt;2. Recommendation: The current position of Director of Central Intelligence should be replaced by a National Intelligence Director with two main areas of responsibility: (1) to oversee national intelligence centers on specific subjects of interest across the U.S. government and (2) to manage the national intelligence program and oversee the agencies that contribute to it.&lt;/strong&gt;&lt;/blockquote&gt;&lt;br /&gt;&lt;a href="http://www.dni.gov/faq_about.htm"&gt;ODNI established in 2005.&lt;/a&gt;  Current report card indicates incomplete, why?&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;&lt;blockquote&gt;3. Recommendation: The CIA Director should emphasize (a) rebuilding the CIA's analytic capabilities; (b) transforming the clandestine service by building its human intelligence capabilities; (c) developing a stronger language program, with high standards and sufficient financial incentives; (d) renewing emphasis on recruiting diversity among operations officers so they can blend more easily in foreign cities; (e) ensuring a seamless relationship between human source collection and signals collection at the operational level; and (f) stressing a better balance between unilateral and liaison operations.&lt;/blockquote&gt;&lt;br /&gt;&lt;/strong&gt;The President issued a &lt;a href="http://www.fas.org/irp/news/2004/11/wh112304dci.html"&gt;memorandum &lt;/a&gt;on November 23, 2004.  This &lt;a href="http://www.9-11pdp.org/press/2005-10-20_report.pdf"&gt;report&lt;/a&gt; from October 2005, reported "some progress."  Is there anything more current?&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;&lt;/strong&gt;&lt;blockquote&gt;&lt;strong&gt;4. Recommendation: Lead responsibility for directing and executing paramilitary operations, whether clandestine or covert, should shift to the Defense Department. There it should be consolidated with the capabilities for training, direction, and execution of such operations already being developed in the Special Operations Command.&lt;/strong&gt;&lt;/blockquote&gt;&lt;br /&gt;Incomplete, this consolidation has not occurred.&lt;br /&gt;&lt;strong&gt;&lt;blockquote&gt;5. Recommendation: Finally, to combat the secrecy and complexity we have described, the overall amounts of money being appropriated for national intelligence and to its component agencies should no longer be kept secret. Congress should pass a separate appropriations act for intelligence, defending the broad allocation of how these tens of billions of dollars have been assigned among the varieties of intelligence work.&lt;/blockquote&gt;&lt;/strong&gt;House Appropriations Select Intelligence Oversight Panel &lt;a href="http://en.wikipedia.org/wiki/United_States_House_Appropriations_Select_Intelligence_Oversight_Panel"&gt;established January 9, 2007&lt;/a&gt;.&lt;br /&gt;&lt;strong&gt;&lt;/strong&gt;&lt;blockquote&gt;&lt;strong&gt;6. Recommendation: Information procedures should provide incentives for sharing, to restore a better balance between security and shared knowledge.&lt;/strong&gt;&lt;/blockquote&gt;This is addressed by H.R. 6575, &lt;a href="http://www.fas.org/sgp/congress/2008/overclass.html"&gt;Over-Classification Reduction Act&lt;/a&gt;, adopted on September 9, 2008.  Currently incomplete pending passage by the Senate and signature of the President.&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;&lt;blockquote&gt;7. Recommendation: The president should lead the government-wide effort to bring the major national security institutions into the information revolution. He should coordinate the resolution of the legal, policy, and technical issues across agencies to create a "trusted information network."&lt;/blockquote&gt;&lt;br /&gt;&lt;/strong&gt;Incomplete, no indication of implementation beyond &lt;a href="http://www.markletaskforce.org/reports/TFNS_Report2_Master.pdf"&gt;studies&lt;/a&gt;.  Ironically, the Center for Strategic and International Studies &lt;a href="http://www.fcw.com/print/12_32/news/95853-1.html"&gt;may have done this for themselves&lt;/a&gt; without the participation of classified networks.&lt;br /&gt;&lt;strong&gt;&lt;blockquote&gt;8. Recommendation: Congressional oversight for intelligence-and counterterrorism-is now dysfunctional. Congress should address this problem. We have considered various alternatives: A joint committee on the old model of the Joint Committee on Atomic Energy is one. A single committee in each house of Congress, combining authorizing and appropriating authorities, is another.&lt;/blockquote&gt;&lt;br /&gt;&lt;/strong&gt;Incomplete, no &lt;span style="font-weight: bold;"&gt;Joint &lt;/span&gt;committee comprising members of both House and Senate.&lt;strong&gt;&lt;/strong&gt;&lt;blockquote&gt;&lt;strong&gt;9. Recommendation: Congress should create a single, principal point of oversight and review for homeland security. Congressional leaders are best able to judge what committee should have jurisdiction over this department and its duties. But we believe that Congress does have the obligation to choose one in the House and one in the Senate, and that this committee should be a permanent standing committee with a nonpartisan staff.&lt;/strong&gt;&lt;/blockquote&gt;&lt;br /&gt;&lt;a href="http://www.govexec.com/story_page.cfm?articleid=40599&amp;amp;dcn=todaysnews"&gt;Incomplete, DHS still overburdened with too much oversight.&lt;/a&gt;   This lack of focus wastes resources and probably still leaves oversight gaps.&lt;br /&gt;&lt;strong&gt;&lt;/strong&gt;&lt;blockquote&gt;&lt;strong&gt;10. Recommendation: Since a catastrophic attack could occur with little or no notice, we should minimize as much as possible the disruption of national security policymaking during the change of administrations by accelerating the process for national security appointments. We think the process could be improved significantly so transitions can work more effectively and allow new officials to assume their new responsibilities as quickly as possible.&lt;/strong&gt;&lt;/blockquote&gt;&lt;br /&gt;Incomplete, no sign that these procedural recommendations have been implemented.&lt;br /&gt;&lt;strong&gt;&lt;/strong&gt;&lt;blockquote&gt;&lt;strong&gt;11. Recommendation: A specialized and integrated national security workforce should be established at the FBI consisting of agents, analysts, linguists, and surveillance specialists who are recruited, trained, rewarded, and retained to ensure the development of an institutional culture imbued with a deep expertise in intelligence and national security.&lt;/strong&gt;&lt;/blockquote&gt;&lt;br /&gt;The President issued a &lt;a href="http://www.fas.org/irp/news/2004/11/wh112304ag.html"&gt;memorandum on November 23, 2004&lt;/a&gt;.  Has it been implemented?&lt;br /&gt;&lt;strong&gt;&lt;/strong&gt;&lt;blockquote&gt;&lt;strong&gt;12. Recommendation: The Department of Defense and its oversight committees should regularly assess the adequacy of Northern Command's strategies and planning to defend the United States against military threats to the homeland.&lt;/strong&gt;&lt;/blockquote&gt;&lt;br /&gt;Incomplete, as of April, 2008 the &lt;a href="http://www.stormingmedia.us/78/7820/A782084.html"&gt;"GAO making several recommendations to DOD to direct NORTHCOM to take actions to  address the challenges it faces in its planning and interagency coordination  efforts." &lt;/a&gt;&lt;br /&gt;&lt;strong&gt;&lt;/strong&gt;&lt;blockquote&gt;&lt;strong&gt;13. Recommendation: The Department of Homeland Security and its oversight committees should regularly assess the types of threats the country faces to determine (a) the adequacy of the government's plans-and the progress against those plans-to protect America's critical infrastructure and (b) the readiness of the government to respond to the threats that the United States might face.&lt;/strong&gt;&lt;/blockquote&gt;&lt;br /&gt;Incomplete, as stated above too many committees is more likely to lead to a failure of oversight and assessment rather than to a successful assessment and response.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-2984727122201000310?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=R3qwwvT2ELQ:2sGM3FZTymU:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=R3qwwvT2ELQ:2sGM3FZTymU:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=R3qwwvT2ELQ:2sGM3FZTymU:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=R3qwwvT2ELQ:2sGM3FZTymU:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=R3qwwvT2ELQ:2sGM3FZTymU:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=R3qwwvT2ELQ:2sGM3FZTymU:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/R3qwwvT2ELQ/7-years-later.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2008/09/7-years-later.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-819915368729934809</guid><pubDate>Tue, 09 Sep 2008 20:44:00 +0000</pubDate><atom:updated>2008-09-11T15:37:56.225-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Fraud</category><title>Flash parties, flash crowds, now we have "flash dump"</title><description>&lt;div&gt;&lt;p&gt;&lt;/p&gt;&lt;blockquote&gt;Panic ensued, as they say, and &lt;a href="http://www.sun-sentinel.com/business/sfl-090808-sentinel-united-airlines,0,5067344.story"&gt;United  Airlines stock price plummeted&lt;/a&gt; 75 percent (down from $12.30 to $3 a share)  before someone realized it was an old news story and things righted themselves.  The stock rebounded to $10.92 a share by Monday's closing. But not before United  Airlines contacted the&lt;em&gt; Sun Sentinel&lt;/em&gt; and demanded the newspaper retract  its (6-year-old) story.&lt;/blockquote&gt;&lt;p&gt;&lt;/p&gt;&lt;br /&gt;&lt;span class="984093420-09092008"&gt;&lt;span style=";font-family:Arial;font-size:85%;"  &gt;I wonder how long  before we see the Google spider being intentionally  manipulated?&lt;/span&gt;&lt;/span&gt;&lt;/div&gt; &lt;div&gt;&lt;span class="984093420-09092008"&gt;&lt;/span&gt; &lt;/div&gt; &lt;div&gt;&lt;span class="984093420-09092008"&gt;&lt;span style=";font-family:Arial;font-size:85%;"  &gt;With web 2.0 there  wouldn't even be a human brain in the publishing loop.&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-819915368729934809?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=6eWjFxuYA0A:cZTrcofOw-I:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=6eWjFxuYA0A:cZTrcofOw-I:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=6eWjFxuYA0A:cZTrcofOw-I:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=6eWjFxuYA0A:cZTrcofOw-I:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=6eWjFxuYA0A:cZTrcofOw-I:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=6eWjFxuYA0A:cZTrcofOw-I:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/6eWjFxuYA0A/flash-parties-flash-crowds-now-we-have.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2008/09/flash-parties-flash-crowds-now-we-have.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-8677718636540000880</guid><pubDate>Fri, 13 Jun 2008 22:46:00 +0000</pubDate><atom:updated>2008-06-13T15:53:34.138-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">pci</category><category domain="http://www.blogger.com/atom/ns#">defense in depth</category><category domain="http://www.blogger.com/atom/ns#">trust zones</category><category domain="http://www.blogger.com/atom/ns#">Network Security</category><title>PCI compliant but still hacked</title><description>&lt;blockquote&gt;The malware on the store servers stored up records of these purchases in batches, then transmitted them to an unnamed offshore Internet service provider, the letter states. Foreign crime rings have been blamed in a number of other payment card fraud cases.&lt;/blockquote&gt;&lt;blockquote&gt;Hannaford said in its letter that it was certified a year ago as meeting card security standards and was recertified on Feb. 27. Eleazer said that was the day Visa first notified Hannaford of unusual card activity and began its investigation. That the standards did not stop the thieves, she said, "speaks to the increasing sophistication of the criminal element that propagates these attacks," she said.&lt;/blockquote&gt;It looks to me like Hannaford made the mistake of allowing "multi-level access" in a "single level" network.   Servers that handle payment card data must be prevented from access to an unauthorized network or end-point.&lt;br /&gt;&lt;br /&gt;These servers and the processors they communicate with should have been in a "PCI trust zone."  All other systems would have been in an "untrusted zone."  Then it would be a simple matter for IDP/NAC appliance to detect and prevent this type of breach.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-8677718636540000880?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=8-7rfyFNe24:mO3nD9jPEP8:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=8-7rfyFNe24:mO3nD9jPEP8:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=8-7rfyFNe24:mO3nD9jPEP8:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=8-7rfyFNe24:mO3nD9jPEP8:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=8-7rfyFNe24:mO3nD9jPEP8:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=8-7rfyFNe24:mO3nD9jPEP8:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/8-7rfyFNe24/pci-compliant-but-still-hacked.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2008/06/pci-compliant-but-still-hacked.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-2436897203702815351</guid><pubDate>Tue, 27 May 2008 16:32:00 +0000</pubDate><atom:updated>2008-05-27T09:39:55.402-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">virtualization security</category><title>Virtualization Security Getting Some Attention</title><description>My response to "&lt;a href="http://virtualization.com/guest-posts-guestposts/2008/05/21/who-owns-virtualization-security-the-hoffcrosby-debate/"&gt;Who Owns Virtualization Security&lt;/a&gt;" blog:&lt;br /&gt; &lt;p class="MsoNormal"&gt;&lt;/p&gt;&lt;blockquote&gt;&lt;p class="MsoNormal"&gt;Virtualization absolutely presents us with the possibility of avoiding past mistakes and making virtual infrastructure (VI) more secure than the physical infrastructure it replaces.&lt;/p&gt;    &lt;p class="MsoNormal"&gt;Why?&lt;/p&gt;  &lt;ol style="margin-top: 0in;" start="1" type="1"&gt;&lt;li class="MsoNormal" style=""&gt;Virtual      security appliances and hypervisor APIs have made it possible for us to      build security into the VI fabric at all layers.&lt;/li&gt;&lt;li class="MsoNormal" style=""&gt;The      virtualization platforms give us the tools to automate deployment of      primary controls, secondary controls and separation of duties throughout      the virtual data center.&lt;/li&gt;&lt;li class="MsoNormal" style=""&gt;Virtualization      means we can simplify security management and make true defense-in-depth      affordable for everyone.&lt;/li&gt;&lt;li class="MsoNormal" style=""&gt;Secure      hypervisors, their APIs and the right application of security smarts means      we can build agent-less security that protects against rootkits, spyware      and almost all forms of malware.&lt;/li&gt;&lt;li class="MsoNormal" style=""&gt;Virtual      security appliances allow us not only to write good security policy but      also to automatically enforce policy and provide continuous compliance      auditing for the VI.&lt;/li&gt;&lt;li class="MsoNormal" style=""&gt;All of      the above means, we can create tools for secure life-cycle, trust zones,      trusted data paths and secure management in ways never possible with      physical infrastructure.&lt;/li&gt;&lt;/ol&gt;    &lt;p class="MsoNormal"&gt;&lt;o:p&gt; &lt;/o:p&gt;&lt;br /&gt;We (as vendors) have a responsibility to educate the IT community to the myths and realities of VI security.&lt;span style=""&gt;  &lt;/span&gt;The platform OEMs must recognize that simply saying virtual is more secure than physical – is a disservice to all of their customers.&lt;span style=""&gt;  &lt;/span&gt;Then, when the manufacturers provide the security community the tools and support we need _and_ intelligently inform the market about real risks, then, and only then can we make virtual more secure than physical.&lt;/p&gt;&lt;/blockquote&gt;&lt;p class="MsoNormal"&gt; &lt;/p&gt;  (more to come)&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-2436897203702815351?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=17WBV7MKMNg:BSTnnCp1UXs:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=17WBV7MKMNg:BSTnnCp1UXs:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=17WBV7MKMNg:BSTnnCp1UXs:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=17WBV7MKMNg:BSTnnCp1UXs:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=17WBV7MKMNg:BSTnnCp1UXs:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=17WBV7MKMNg:BSTnnCp1UXs:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/17WBV7MKMNg/virtualization-security-getting-some.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2008/05/virtualization-security-getting-some.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-2329593013987052368</guid><pubDate>Mon, 28 Jan 2008 02:52:00 +0000</pubDate><atom:updated>2008-01-27T18:54:47.566-08:00</atom:updated><title>French bank details $7.2 billion loss</title><description>This sort of thing makes me think that in some cases it is more than greed.  It must also be the "thrill" of beating the system.&lt;br /&gt;&lt;br /&gt;Being smarter -- thinking you can out-smart everyone else?&lt;br /&gt;&lt;br /&gt;Michael&lt;br /&gt;---------------------------&lt;br /&gt;&lt;blockquote&gt;French bank Societe Generale described Sunday how one of its traders allegedly carried out a $7.2 billion (€4.9 billion) fraud, how the loss came to light and what it is doing to ensure such a case does not recur.&lt;br /&gt;The 31-year-old trader, Jerome Kerviel, started working at the bank in 2000 and spent his first five years there overseeing traders, the bank said in a five-page summary of events.&lt;br /&gt;&lt;br /&gt;"Consequently, he had a very good understanding of all of Societe Generale's processing and control procedures," it said.&lt;br /&gt;&lt;br /&gt;Kerviel apparently put that knowledge to use after he became a trader for the bank involved in arbitrage -- the practice of buying a portfolio of financial instruments in one market and selling a similar offsetting portfolio at the same time that had a slightly different value. The idea is that, in such trades, the risk of major loss would be minimized.&lt;br /&gt;&lt;br /&gt;In fact, Kerviel's first portfolio of financial instruments -- in his case futures -- included genuine operations -- but the offsetting portfolio proved to be "fictitious," the bank said.&lt;br /&gt;&lt;br /&gt;"As a result, the trader was able to hide a very sizable speculative position, which was neither consistent with nor related to his normal business activity for the bank," Societe Generale said.&lt;br /&gt;&lt;br /&gt;French police questioned Kerviel on Friday and searched his apartment in a Paris suburb Friday night. Efforts to reach his attorneys for comment have been unsuccessful.&lt;br /&gt;&lt;br /&gt;Finance Minister Christine Lagarde said Friday that she would meet with banking regulators Monday to establish a timeline of events that led to the massive trading loss.&lt;br /&gt;&lt;br /&gt;According to Societe Generale, Kerviel used his early banking experience "to successfully circumvent all the controls which allow the bank to check the characteristics of the operations carried out by its traders, and consequently their real existence," it said.&lt;br /&gt;&lt;br /&gt;For example, it said, Kerviel chose operations that had no cash movements or margin call and that did not require immediate confirmation and he canceled certain operations by using access codes assigned to other bank employees.&lt;br /&gt;&lt;br /&gt;In addition, it said, he falsified documents and made sure that his fictitious operations involved different instruments from the ones he had just canceled, thereby reducing his chances of being controlled.&lt;br /&gt;&lt;br /&gt;But about mid-January, bank officials detected "abnormal counterparty risk," and Kerviel's explanations led to additional controls being placed on his activities, the bank said.&lt;br /&gt;&lt;br /&gt;Then, on Friday, January 18, Kerviel's bosses were informed and an investigation had begun.&lt;br /&gt;&lt;br /&gt;The next day, after a large bank told Societe Generale that it did not recognize an operation, the trader "acknowledges committing unauthorized acts and, in particular, creating fictitious operations," his employer said.&lt;br /&gt;&lt;br /&gt;By early afternoon on Sunday, January 20, the bank's fraudulent position had been calculated at approximately 50 billion euros ($73.6 billion), and "the unwinding of the fraudulent position begins in particularly unfavorable market conditions."&lt;br /&gt;&lt;br /&gt;In fact, the timing was terrible. On Jan. 18, European markets had swooned and two days later, the Asian markets tumbled, too. By January 23, "the unwinding" was completed and the total loss calculated at 4.9 billion euros ($7.2 billion).&lt;br /&gt;Since then, the bank said, it has tightened its controls to ensure such an operation cannot recur.&lt;br /&gt;&lt;/blockquote&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-2329593013987052368?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=iuUcDZ1PijU:ARStgTIx6eE:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=iuUcDZ1PijU:ARStgTIx6eE:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=iuUcDZ1PijU:ARStgTIx6eE:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=iuUcDZ1PijU:ARStgTIx6eE:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=iuUcDZ1PijU:ARStgTIx6eE:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=iuUcDZ1PijU:ARStgTIx6eE:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/iuUcDZ1PijU/french-bank-details-72-billion-loss.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2008/01/french-bank-details-72-billion-loss.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-8903649676795470181</guid><pubDate>Wed, 03 Oct 2007 18:30:00 +0000</pubDate><atom:updated>2007-10-03T11:35:16.655-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Network Security</category><title>Virtualised desktops will end laptop management</title><description>With virtual desktop infrastructure (VDI) there are at least three modes of operation:&lt;br /&gt;&lt;br /&gt;&lt;ol&gt;&lt;li&gt;IT controls VDI completely, desktop is "thin" only IT approved virtual machines are allowed&lt;/li&gt;&lt;li&gt;IT does not completely control the desktop, options get complicated fast:&lt;br /&gt;a) user virtual machines are allowed&lt;br /&gt;b) user controls the host&lt;br /&gt;&lt;/li&gt;&lt;/ol&gt;Looking at option 2a, we could have rogue guests, infected guests, any kind of guest ... telling them apart and acting accordingly will be fun!&lt;br /&gt;&lt;br /&gt;Looking at option 2b, I can buy a Macintosh or linux or windoze and as long as I can run the IT approved virtual machine, then IT is happy.  But what if my Macintosh is owned by the Uzebek barbarian horde?  Have I just given the Horde access to my corporate network?&lt;br /&gt;&lt;br /&gt;Lot's of interesting questions arise.  We have our own use case right here at Catbird.  The "approved" IT image is Windows XP with Microsoft Office.&lt;br /&gt;We allow a VDI where an employee can use a Macintosh to run Windows in a vm.  We're happy until there is a mac worm!&lt;br /&gt;&lt;br /&gt;For example, an organization using Active Directory to lock down their desktops ... Active Directory does nothing to lock down a Macintosh.&lt;br /&gt;&lt;br /&gt;How is a windows savvy IT team going to cope with users running Ubuntu, Fedora, Macintosh ...  VDI is going to lead to an explosion of host operating system diversity.  This will be very exciting for those of us running Windows under duress.&lt;br /&gt;&lt;br /&gt;Their will be a huge value in giving IT the tools to manage and secure a highly diverse and constantly changing environment.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-8903649676795470181?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=Xiq0tQcKqw8:t5GavVDbcgo:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=Xiq0tQcKqw8:t5GavVDbcgo:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=Xiq0tQcKqw8:t5GavVDbcgo:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=Xiq0tQcKqw8:t5GavVDbcgo:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=Xiq0tQcKqw8:t5GavVDbcgo:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=Xiq0tQcKqw8:t5GavVDbcgo:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/Xiq0tQcKqw8/virtualised-desktops-will-end-laptop.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2007/10/virtualised-desktops-will-end-laptop.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-3531199867490296805</guid><pubDate>Sat, 22 Sep 2007 16:07:00 +0000</pubDate><atom:updated>2007-09-22T09:11:38.214-07:00</atom:updated><title>Another one from SANS newsbites</title><description>&lt;span style="font-family:courier;"&gt;&lt;span style="font-family: arial;"&gt;A vulnerability scan would have warned them that their Cerberus implementation was open to attack.  Either they were not validating their security compliance, or they were not following an effective process for curing their vulnerabilities.&lt;/span&gt;&lt;br /&gt;&lt;blockquote&gt; &lt;span style="font-family: times new roman;"&gt;--Layered Technologies Customer Data Stolen (September 19 &amp;amp; 20, 2007) An attack on a helpdesk application in Layered Technologies' support database has compromised the security of personally identifiable data of as many as 6,000 of the server hosting company's customers.  The data include names, addresses, phone numbers and server login details.&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family: times new roman;"&gt;Layered Technologies is asking all its customers to change their login credentials.  The attack occurred on the evening of September 17, 2007.&lt;/span&gt;&lt;br /&gt;&lt;a href="http://www.theregister.co.uk/2007/09/19/layered_technologies_breach_disclosure/print.html"&gt;&lt;span style="font-family: times new roman;"&gt;http://www.theregister.co.uk/2007/09/19/layered_technologies_breach_disclosure/print.html&lt;/span&gt;&lt;/a&gt;&lt;br /&gt;&lt;a href="http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;amp;articleId=9038040&amp;amp;source=rss_topic17"&gt;&lt;span style="font-family: times new roman;"&gt;http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;amp;articleId=9038040&amp;amp;source=rss_topic17&lt;/span&gt;&lt;/a&gt;&lt;/blockquote&gt;&lt;br /&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-3531199867490296805?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=IaugEz7MRN0:5n5B99J1e1g:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=IaugEz7MRN0:5n5B99J1e1g:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=IaugEz7MRN0:5n5B99J1e1g:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=IaugEz7MRN0:5n5B99J1e1g:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=IaugEz7MRN0:5n5B99J1e1g:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=IaugEz7MRN0:5n5B99J1e1g:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/IaugEz7MRN0/another-one-from-sans-newsbites.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2007/09/another-one-from-sans-newsbites.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-108785811443755756</guid><pubDate>Wed, 19 Sep 2007 14:14:00 +0000</pubDate><atom:updated>2007-09-19T07:16:48.617-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Network Security</category><title>Highlights from a recent SANS News bites</title><description>&lt;span style="font-family:Arial;font-size:85%;"&gt;&lt;span class="843530914-19092007"&gt;From SANS ... note that  bank account details are now worth $400/per account.&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;a href="http://www.sans.org"&gt;TOP OF THE NEWS&lt;/a&gt;&lt;br /&gt;&lt;br /&gt; --Ameritrade May Have Been Aware of Breach for a Year (September 14, 15 &amp;amp; 17, 2007) Online brokerage TD Ameritrade Holding has acknowledged that a data security breach has compromised more than 6.3 million accounts.  The database contains customer names, addresses, account numbers, Social Security numbers (SSNs) and birth dates.  The attackers gained access to the database through a backdoor program they had installed on the TD Ameritrade network. TD Ameritrade says it has removed the rogue code from its systems.  The intrusion was discovered in the course of an investigation into stock-related spam that had been reported by the company's customers.  An attorney representing plaintiffs in a planned class action lawsuit against the online broker alleges that the company knew of the data security problem for a year before customers were notified.  Furthermore, the suit alleges that the company kept entering customer data into the vulnerable database during an internal investigation.&lt;br /&gt;http://www.theregister.co.uk/2007/09/15/ameritrade_database_burgled/print.html&lt;br /&gt;http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;amp;articleId=9036639&amp;amp;source=rss_topic17&lt;br /&gt;http://www.amtd.com/newsroom/releasedetail.cfm?ReleaseID=264044&lt;br /&gt;http://www.informationweek.com/shared/printableArticle.jhtml?articleID=201807006&lt;br /&gt;&lt;br /&gt; --Symantec Report: Malware Moves Toward Commercialism (September 17 &amp;amp; 18, 2007) Cyber attackers aiming to damage computers or inconvenience users are giving way to more financially motivated criminals.  According to Symantec's most recent Internet Security Threat Report, cyber criminals are turning to good business practices to ply their trade. Some malware purveyors are offering guarantees about the performance of their products as well as updates to keep the products current.  The report also notes that phishers are scouring social networking sites to gather personal information, which they then use to create targeted emails that lure recipients to phony sites where they can harvest valuable data.&lt;br /&gt;Stolen bank account details are being sold online for as much as US $400 apiece.  In addition, levels of pump-and-dump schemes and image-based spam have decreased.&lt;br /&gt;http://www.technewsworld.com/story/59374.html&lt;br /&gt;http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;amp;articleId=9036819&amp;amp;source=NLT_SEC&amp;amp;nlid=38&lt;br /&gt;http://www.itnews.com.au/News/61398,fraudsters-go-all-out-for-social-networkers.aspx&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-108785811443755756?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=XSrJl2DhaTM:QOJWIVrLps4:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=XSrJl2DhaTM:QOJWIVrLps4:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=XSrJl2DhaTM:QOJWIVrLps4:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=XSrJl2DhaTM:QOJWIVrLps4:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=XSrJl2DhaTM:QOJWIVrLps4:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=XSrJl2DhaTM:QOJWIVrLps4:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/XSrJl2DhaTM/highlights-from-recent-sans-news-bites.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2007/09/highlights-from-recent-sans-news-bites.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-7291502305338754690</guid><pubDate>Thu, 09 Aug 2007 23:33:00 +0000</pubDate><atom:updated>2007-08-11T09:14:30.431-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Internet Security</category><title>The Game Is Not Over -- Security for your web site</title><description>&lt;ol&gt;&lt;li&gt;&lt;a href="http://paranoia.dubfire.net/2007/04/deceit-augmented-man-in-middle-attack.html"&gt;Man-in-the-middle (MITM) attack against SSL plus Sitekey/Passmark&lt;/a&gt; – The &lt;a href="http://www.stop-phishing.com/"&gt;Stop-Phishing Research Group&lt;/a&gt; at Indiana University demonstrates that if you are not very careful about the URL and the SSL certificate, and most people are not, the attacker will be successful&lt;/li&gt;&lt;li&gt;&lt;a href="http://it.slashdot.org/article.pl?sid=07/08/03/1241217"&gt;Sniffing a connection to steal session cookies to bypass user authentication&lt;/a&gt; – Robert Graham of &lt;a href="http://erratasec.blogspot.com/"&gt;ErrataSec&lt;/a&gt;, has demonstrated why you need a security barrier for your laptop at Starbucks (If his name for this attack sticks "side-jacking" then we might as well all give up and start referring to SSL as a condom for your browser)&lt;br /&gt;&lt;/li&gt;&lt;li&gt;If you think you don’t have to worry about these exploit techniques, &lt;a href="http://www.crypto.com/bingo/pr"&gt;then you better have the Security Excuse bingo card&lt;/a&gt; (found on &lt;a href="http://www.schneier.com/blog/archives/2007/08/security_proble_1.html"&gt;Schneier on Security&lt;/a&gt;),&lt;br /&gt;&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;&lt;/p&gt;  &lt;p&gt;It looks pretty bad.  SSL can be bypassed, authentication cookies can be stolen.  If you follow the blogosphere’s impression of the recent Blackhat/Defcon events, it's all useless and there is nothing we can do to stop the crooks. To top it all off, there isn’t just one &lt;a href="http://www.discoverhackistan.com/hackistan/"&gt;Hackistan &lt;/a&gt;(great Yak snacks by the way) there are many Hackistan’s and no &lt;a href="http://www.darkreading.com/document.asp?doc_id=130951&amp;f_src=darkreading_section_296"&gt;web site is to small&lt;/a&gt; or broad-band connected &lt;a href="http://www.darkreading.com/document.asp?doc_id=131329&amp;amp;f_src=darkreading_section_296"&gt;PC to innocent&lt;/a&gt; for them to exploit.&lt;/p&gt;  &lt;p&gt;Truth is, if a malicious hacker with the capabilities of a &lt;a href="http://jeremiahgrossman.blogspot.com/"&gt;Grossman&lt;/a&gt;, &lt;a href="http://www.counterhack.net/who_am_i_.html"&gt;Skoudis &lt;/a&gt;or &lt;a href="http://blog.metasploit.com/"&gt;Moore &lt;/a&gt;is after your site, then you will get hacked.  Lucky for you these guys are busy™.&lt;/p&gt;  &lt;p&gt;&lt;span style="font-weight: bold;"&gt;Solutions?  Focus on your business needs and take some precautionary steps: &lt;/span&gt;&lt;br /&gt;&lt;/p&gt;&lt;ul style="color: rgb(0, 51, 0);"&gt;&lt;li&gt;Run traditional vulnerability scans (because Skoudis and Moore teach us that the old problems are new again)&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;&lt;li&gt;Run a &lt;a href="http://www.blogger.com/www.spidynamics.com"&gt;web application scanner&lt;/a&gt; and use a &lt;a href="http://www.blogger.com/www.fortifysoftware.com"&gt;secure coding&lt;/a&gt; inspection tool, Grossman and Zorkul are better, but it’s foolish not to automate everything you can&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;&lt;li&gt;Use SSL from start to finish on your web-site, you have an obligation to protect the integrity and security of all the data exchanged between your site and your customer’s browser – otherwise your giving it away to any crook with a copycat access point or a promiscuous wireless card&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;&lt;li&gt;Don’t ignore MITM because you think it is hard, it gets easier to do every day – Lucky for all of us, it’s also getting easier to protect against and detect MITM, Pharming, Highjack and Malware Injection, I know someone who can &lt;a href="http://www.catbird.com/"&gt;help&lt;br /&gt;&lt;br /&gt;&lt;/a&gt;&lt;/li&gt;&lt;li&gt;Last but not least, plan on getting hacked, have an &lt;a href="http://en.wikipedia.org/wiki/Computer_security_incident_management"&gt;incident response plan&lt;/a&gt; and be prepared, playing security excuse bingo is a losing strategy&lt;/li&gt;&lt;/ul&gt;         &lt;p style="font-weight: bold;"&gt;Get started today!&lt;/p&gt;  &lt;object height="203" width="249"&gt;&lt;br /&gt;&lt;param name="movie" value="http://www.noendinsightmovie.com/trailer.swf"&gt;&lt;param name="wmode" value="transparent"&gt;&lt;embed src="http://www.noendinsightmovie.com/trailer.swf" type="application/x-shockwave-flash" wmode="transparent" height="240" width="400"&gt;&lt;/embed&gt;&lt;/object&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-7291502305338754690?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=qwXebvukFrk:VtOmuvB1AkU:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=qwXebvukFrk:VtOmuvB1AkU:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=qwXebvukFrk:VtOmuvB1AkU:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=qwXebvukFrk:VtOmuvB1AkU:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=qwXebvukFrk:VtOmuvB1AkU:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=qwXebvukFrk:VtOmuvB1AkU:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/qwXebvukFrk/game-is-not-over.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2007/08/game-is-not-over.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-5067577781941860992</guid><pubDate>Thu, 09 Aug 2007 16:54:00 +0000</pubDate><atom:updated>2007-08-09T10:00:47.229-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Internet Security</category><title>Disregard any pop-up security windows you receive</title><description>I received this in my mail today:&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;Dear Electronic Crimes Task Force Member,&lt;br /&gt;&lt;br /&gt;CSO magazine is conducting a survey in cooperation with the U.S. Secret Service and CERT Coordination Center, the 2007 eCrime Watch.  The purpose of this project is to uncover electronic crime trends.&lt;br /&gt;&lt;br /&gt;CSO magazine’s sister company, IDG Research Services, has been commissioned to help us collect your feedback. Please click on the following URL to begin the survey or copy and paste the URL into your browser:&lt;br /&gt;&lt;br /&gt;https://url-hidden&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold; color: rgb(255, 0, 0);"&gt;Disregard any pop-up security windows you receive.  &lt;span style="color: rgb(0, 0, 153);"&gt;(Emphasis mine)&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Please be assured that any information you provide is confidential and your responses will be used only in combination with those of other survey respondents.  This survey should take no more than 10 minutes of your time. If you have any questions about this survey please contact IDG Research Services at ------@idg.com or ATSAIC ----------, USSS, San Francisco Field Office 415/-------.&lt;br /&gt;&lt;br /&gt;Thank you in advance for your help.&lt;/blockquote&gt;Of course my first thought, was that this was a phishing attack.  I couldn't imagine CSO and the ECTF telling me to "Disregard any pop-up security windows you receive."&lt;br /&gt;&lt;br /&gt;Imagine my surprise and relief, when I went to the site and there were no warnings.  So, they got it right, the SSL certificate was correct and unexpired ... but everyone is so accustomed to that &lt;span style="font-weight: bold;"&gt;not being the case&lt;/span&gt;, that as a matter of course they included the disregard pop-ups message.  Is our infrastructure broken or what?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-5067577781941860992?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=YMqFFGw3sJo:Xr2f7RPC_r0:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=YMqFFGw3sJo:Xr2f7RPC_r0:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=YMqFFGw3sJo:Xr2f7RPC_r0:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=YMqFFGw3sJo:Xr2f7RPC_r0:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=YMqFFGw3sJo:Xr2f7RPC_r0:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=YMqFFGw3sJo:Xr2f7RPC_r0:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/YMqFFGw3sJo/disregard-any-pop-up-security-windows.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2007/08/disregard-any-pop-up-security-windows.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-1767481889467770574</guid><pubDate>Wed, 08 Aug 2007 16:52:00 +0000</pubDate><atom:updated>2007-08-08T16:31:20.328-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Internet Security</category><title>Virtually Secure</title><description>&lt;a href="http://www.linkedin.com/pub/1/104/61"&gt;Christofer Hoff&lt;/a&gt; has a good post &lt;a href="http://rationalsecurity.typepad.com/blog/2007/08/vmware-to-open-.html"&gt;here&lt;/a&gt;.  In particular,&lt;br /&gt;&lt;blockquote&gt;Combine that with NAC agents on the hosts and...whether or not it actually works  is neither here nor there.  They told they story and here it is.  It's good to  be king.&lt;/blockquote&gt;His point being that Cisco doesn't have to worry about when they are going to deliver a product or even how will it will work when they do ...&lt;br /&gt;&lt;br /&gt;Meanwhile, back in your virtualized data center, you can be warm and happy knowing that Cisco's virtually shipping product has you virtually secure already.  Nice, huh?&lt;br /&gt;&lt;br /&gt;What about Real Security -- &lt;a href="http://www.catbird.com/vagent"&gt;Real Security for Virtualized Infrastructures&lt;/a&gt;?  You've deployed half a dozen quad-core systems and thrown out 150 obsolete boxes.  Maybe you had IPS and NAC in your datacenter already, but do you have it now?  If your virtual windows 2000 server get's infected and starts attacking the other systems on the host, how will you know?&lt;br /&gt;&lt;br /&gt;Maybe you will know when the infection begins to spread to other hosts and their virtual servers, but by then you will have a real mess on your hands.&lt;br /&gt;&lt;br /&gt;The right answer involves doing something today, not waiting for a vendor to implement a solution next year.  Here is the pragmatic prescription for today, virtual servers are servers, period. &lt;br /&gt;&lt;br /&gt;If there reliability and security are important to your business then you have to secure them with same mature IT processes that you use for everything else:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;Specify the appropriate security requirements at the start&lt;/li&gt;&lt;li&gt;Determine and implement secure baselines that meet your business and security requirements&lt;/li&gt;&lt;li&gt;Validate/test that the performance and security of your systems meets the stated requirements before you put them in production&lt;/li&gt;&lt;li&gt;After deployment, test them again -- virtualization really helps you here&lt;/li&gt;&lt;li&gt;Use change control and segregation of duties --  (ITIL and ISO 17799 driven) processes and controls to keep working systems, working&lt;/li&gt;&lt;li&gt;Patch management and vulnerability management are a continuous process -- don't treat these problems with a calender ... not unless you like emergencies&lt;/li&gt;&lt;li&gt;Continuously monitor your network and systems, use the protection appropriate to the value of the data or business operations, such as:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Gateway: firewall, anti-spam, anti-malware, content filtering, vpn ...&lt;/li&gt;&lt;li&gt;Network: vulnerability monitoring, IDS/IPS, NAC, Policy management and compliance ...&lt;br /&gt;&lt;/li&gt;&lt;li&gt;Endpoint: Anti-malware, AAA, log analysis, patching, encryption ...&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;/li&gt;&lt;li&gt;Disaster/Business continuity planning, incident response and training have to include your virtual infrastructure -- DR/BP might be a big driver behind your virtualization effort, but nothing substitutes for a good test.&lt;br /&gt;&lt;/li&gt;&lt;/ol&gt;Do all of the above, appropriately to the level you need, don't wait to become the &lt;a href="http://doj.nh.gov/consumer/breaches.html"&gt;next security breach&lt;/a&gt;.   It's more about the process than the tools.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-1767481889467770574?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=HgL-Mol3VV8:kKZtKwuB53s:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=HgL-Mol3VV8:kKZtKwuB53s:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=HgL-Mol3VV8:kKZtKwuB53s:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=HgL-Mol3VV8:kKZtKwuB53s:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=HgL-Mol3VV8:kKZtKwuB53s:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=HgL-Mol3VV8:kKZtKwuB53s:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/HgL-Mol3VV8/virtually-secure.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2007/08/virtually-secure.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-730603153920952473</guid><pubDate>Mon, 06 Aug 2007 15:23:00 +0000</pubDate><atom:updated>2007-08-06T08:43:07.457-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Internet Security</category><title>I hate Passwords #10</title><description>From IP: &lt;a href="http://www.listbox.com/member/archive/247/2007/20070805212602:FEEA4BB6-43BB-11DC-A728-014A2D2D5087/"&gt;link here&lt;/a&gt;&lt;br /&gt;&lt;blockquote&gt;What I think needs to be done is that the public needs to be educated about these sites, and the security risk they pose.&lt;br /&gt;&lt;/blockquote&gt;The "public" is already being educated.  We tell them over and over that they should not share their password with anyone.  The problem is that the public gives up their password all too easily.  We can keep blaming the public, and we will, but we should also try to understand why someone will give up their Yahoo (or other service) password easily, while the same person would never share their ATM PIN.&lt;br /&gt;&lt;br /&gt;I think the public is pretty smart, but they learn best when they experience immediate consequences from their actions.  Right now, I know that identity theft and losses from this behavior are at a tolerable level because most of the public are still willing to give their password away -- where the same public will never forgot to lock their car door at the shopping mall parking lot.&lt;br /&gt;&lt;br /&gt;If the consequences (or at least people's awareness of these consequences) get a lot worse, we will either see a change in behavior or the deployment of technologies to eliminate reliance on passwords (tokens, client-side certificates ...).&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-730603153920952473?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=uznbSRYcQ4I:z2UVfsWZwKc:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=uznbSRYcQ4I:z2UVfsWZwKc:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=uznbSRYcQ4I:z2UVfsWZwKc:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=uznbSRYcQ4I:z2UVfsWZwKc:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=uznbSRYcQ4I:z2UVfsWZwKc:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=uznbSRYcQ4I:z2UVfsWZwKc:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/uznbSRYcQ4I/i-hate-passwords-10.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2007/08/i-hate-passwords-10.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-1762386986766291797</guid><pubDate>Sat, 04 Aug 2007 00:07:00 +0000</pubDate><atom:updated>2007-08-03T17:15:53.849-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Voter Security</category><title>Voting Software Security</title><description>&lt;a href="http://www.crypto.com/blog"&gt;Matt Blaze&lt;/a&gt;'s group &lt;a href="http://www.sos.ca.gov/elections/voting_systems/ttbr/sequoia-source-public-jul26.pdf"&gt;reviewed the Sequoia system's code&lt;/a&gt;.  From his blog:&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;We found significant, deeply-rooted security weaknesses in all three vendors'  software.&lt;br /&gt;&lt;p&gt;The problems we found in the code were far more pervasive, and much more  easily exploitable, than I had ever imagined they would be.&lt;br /&gt;&lt;/p&gt;Deliberate backdoors in these systems, if any existed, would be largely  superfluous&lt;/blockquote&gt;My humble opinion: this is a great opportunity for the open source community to get together with the private sector (&lt;a href="http://www.fortify.net/"&gt;hello Fortify&lt;/a&gt;) to solve this problem.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-1762386986766291797?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=wrppMM3M4Qs:jDg1mEiZJVM:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=wrppMM3M4Qs:jDg1mEiZJVM:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=wrppMM3M4Qs:jDg1mEiZJVM:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=wrppMM3M4Qs:jDg1mEiZJVM:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=wrppMM3M4Qs:jDg1mEiZJVM:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=wrppMM3M4Qs:jDg1mEiZJVM:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/wrppMM3M4Qs/voting-software-security.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2007/08/voting-software-security.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-968722795408899035.post-1408124193405495632</guid><pubDate>Fri, 03 Aug 2007 19:11:00 +0000</pubDate><atom:updated>2007-08-03T12:17:05.368-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">business</category><title>Computer Market will keep growing</title><description>I learned a long time ago that no market grows fast forever....&lt;br /&gt;&lt;blockquote&gt;&lt;p&gt;Toni Sacconaghi, an analyst with Sanford C. Bernstein &amp;amp; Co., has chipped in on the gloom and doom scenario as well in a new research report.&lt;/p&gt;  &lt;p&gt;"As the use of server virtualization rises, a negative impact on x86 server demand appears all but inevitable," he wrote. "While we still forecast positive x86 server unit growth in 2007 and 2008, our forecast calls for shipments to contract in 2009 and for growth to be about zero between 2007 and 2012, compared with historical double-digit gains."&lt;/p&gt;&lt;/blockquote&gt;This analysis varies from wrong, to really really wrong.&lt;br /&gt;&lt;br /&gt;I agree with Ashlee Vance in the Register, virtualization is going to drive the demand for huge well-integrated multi-core systems, but there will still be plenty of need for ever more horsepower on the desktop and for dedicated blade or 1U system in the data center to feed specific CPU intensive applications.&lt;br /&gt;&lt;br /&gt;I think we will eventually see desktop virtualization follow in the server virtualization footsteps, but when I look down the hall and see dedicated 4 core systems on people's desks, I find it hard to believe that we're going to see a sharp reduction in the growth of this market.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/968722795408899035-1408124193405495632?l=grok-security.blogspot.com'/&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=oGBPUg-Ohfk:MesW77ZHvUY:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=oGBPUg-Ohfk:MesW77ZHvUY:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=oGBPUg-Ohfk:MesW77ZHvUY:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=oGBPUg-Ohfk:MesW77ZHvUY:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?i=oGBPUg-Ohfk:MesW77ZHvUY:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Grok-Security?a=oGBPUg-Ohfk:MesW77ZHvUY:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Grok-Security?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description><link>http://feedproxy.google.com/~r/Grok-Security/~3/oGBPUg-Ohfk/computer-market-will-keep-growing.html</link><author>noreply@blogger.com (Michael)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://grok-security.blogspot.com/2007/08/computer-market-will-keep-growing.html</feedburner:origLink></item></channel></rss>
