<?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:dc="http://purl.org/dc/elements/1.1/" version="2.0" xml:base="http://blogs.forrester.com/security_and_risk">
  <channel>
    <title>Security and Risk</title>
    <link>http://blogs.forrester.com/security_and_risk</link>
    <description />
    <language>en</language>
          <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/ForresterSRM" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="forrestersrm" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">ForresterSRM</feedburner:emailServiceId><feedburner:feedburnerHostname xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://feedburner.google.com</feedburner:feedburnerHostname><item>
    <title>What Did We Learn From The Cyber Shockwave…March Madness Can Cripple Our Infrastructure</title>
    <link>http://blogs.forrester.com/usman_sindhu/10-02-19-what_did_we_learn_cyber_shockwave%E2%80%A6march_madness_can_cripple_our_infrastructure</link>
    <description>&lt;p&gt;
	Just this Tuesday, February 16&lt;sup&gt;th&lt;/sup&gt; 2010, the &lt;a href="http://www.bipartisanpolicy.org/" target="_blank"&gt;Bipartisan Policy Center&lt;/a&gt;&amp;nbsp;hosted a mock cyber attack called &lt;a href="http://www.thenewnewinternet.com/2010/02/16/more-must-be-done-to-prepare-us-for-cyber-attack/" target="_blank"&gt;Cyber Shockwave&lt;/a&gt;. The aim of this simulation was to understand the impacts of a cyber attack and assess infrastructure capability during such an incident. There are many &lt;a href="http://smartgridsecurity.blogspot.com/2010/02/cyber-shockwave-post-mortem.html" target="_blank"&gt;articles&lt;/a&gt;&amp;nbsp;explaining the motive and results of this simulation, and post mortem is still coming as we speak.&lt;/p&gt;
&lt;p&gt;
	So, what did the simulation entail?&amp;nbsp;It depicted a war game taking place in 2011 &amp;ndash; basically an application installed on smart phones during &lt;em&gt;&amp;lsquo;March Madness&amp;rsquo;&lt;/em&gt;&amp;nbsp; thatturned out to be a malware. This hypothetical malware affected telecom and IT infrastructure throughout the country, with the result actually bringing down the nation&amp;rsquo;s cellular network...but there is more. According to&amp;nbsp;an article&amp;nbsp;from &amp;lsquo;&lt;a href="http://www.theatlanticwire.com/opinions/view/opinion/3-Ways-Cyber-Warriors-Could-Cripple-the-US-2563" target="_blank"&gt;The Atlantic Wire&amp;rsquo;&lt;/a&gt;:&lt;/p&gt;
&lt;p&gt;
	&lt;em&gt;&amp;ldquo;Later, two bombs disabled the country&amp;#39;s electricity network and destroyed gas pipelines... Soon 60 million cellphones were dead. The Internet crashed, finance and commerce collapsed, and most of the nation&amp;#39;s electric grid went dark. White House aides discussed putting the Army in American cities.&amp;rdquo; &lt;/em&gt;&lt;/p&gt;
&lt;p&gt;
	Also, according to an article&amp;nbsp;from &lt;a href="http://www.darkreading.com/security/cybercrime/showArticle.jhtml?articleID=222900775" target="_blank"&gt;DarkReading&lt;/a&gt;:&lt;/p&gt;
</description>
     <comments>http://blogs.forrester.com/usman_sindhu/10-02-19-what_did_we_learn_cyber_shockwave%E2%80%A6march_madness_can_cripple_our_infrastructure#comments</comments>
 <category domain="http://blogs.forrester.com/category/computerworlduk">ComputerworldUK</category>
 <category domain="http://blogs.forrester.com/category/cso_magazine">CSO Magazine</category>
 <category domain="http://blogs.forrester.com/category/current_affairs">Current Affairs</category>
 <category domain="http://blogs.forrester.com/category/it_risk_management">IT Risk Management</category>
 <category domain="http://blogs.forrester.com/category/it_security">IT security</category>
 <category domain="http://blogs.forrester.com/category/network_security">Network Security</category>
 <category domain="http://blogs.forrester.com/category/privacy">Privacy</category>
 <category domain="http://blogs.forrester.com/category/science">Science</category>
 <category domain="http://blogs.forrester.com/category/web/tech">Web/Tech</category>
 <category domain="http://blogs.forrester.com/security_and_risk">Security and Risk</category>
 <pubDate>Fri, 19 Feb 2010 05:00:00 +0000</pubDate>
 <dc:creator>Usman Sindhu</dc:creator>
 <guid isPermaLink="false">3647 at http://blogs.forrester.com</guid>
  </item>
  <item>
    <title>The Fear Of Four... And The Future Of Fraud Detection</title>
    <link>http://blogs.forrester.com/chris_mcclean/10-02-18-fear_four_and_future_fraud_detection</link>
    <description>&lt;p&gt;
	I had a few great conversations yesterday about the increasing role analytics will play in risk and compliance programs, which brought to mind the article, &lt;em&gt;&lt;a href="http://online.wsj.com/article/SB10001424052748704479704575061481908470618.html?mg=com-wsj" target="_blank"&gt;For Some Firms, a Case of &amp;#39;Quadrophobia&amp;#39;&lt;/a&gt;&lt;/em&gt; appearing earlier this week in the Wall Street Journal and &lt;a href="http://freakonomics.blogs.nytimes.com/2010/02/17/predicting-the-next-enron/" target="_blank"&gt;referenced yesterday&lt;/a&gt; by the NY Times&amp;rsquo; Freakonomics blog.&lt;/p&gt;
&lt;p&gt;	The article covers a study of quarterly earnings reports over a nearly 30 year period, which found a statistically low number of results ending in four-tenths of a cent. The implication here is that companies fudge their numbers slightly to report earnings ending in five-tenths, which can then be rounded up... clever. Even more interesting, authors of the study found that these &amp;ldquo;quadrophobes&amp;rdquo; are &amp;ldquo;more likely to restate financials and to be named as defendants in SEC Accounting and Auditing Enforcement Releases (AAER)&amp;rdquo;... not clever.&lt;/p&gt;
&lt;p&gt;
	The report encourages the SEC to enhance its oversight with a new department dedicated solely to detailed quantitative analysis that might catch this type of behavior. It also occurs to me that many corporations would like to identify such trends within their four walls to detect and prevent potentially damaging behavior.&lt;/p&gt;
&lt;p&gt;
	Clearly, the cultural/human aspects of risk management and compliance &amp;ndash; policies, attestations, training, awareness, whistleblowing, etc. &amp;ndash; are essential. But as the number and complexity of business transactions continue to grow, companies will be looking more and more for ways to analyze massive amounts of data for damaging patterns and trends.&lt;/p&gt;
</description>
     <comments>http://blogs.forrester.com/chris_mcclean/10-02-18-fear_four_and_future_fraud_detection#comments</comments>
 <category domain="http://blogs.forrester.com/category/grc">GRC</category>
 <category domain="http://blogs.forrester.com/security_and_risk">Security and Risk</category>
 <pubDate>Thu, 18 Feb 2010 05:00:00 +0000</pubDate>
 <dc:creator>Chris McClean</dc:creator>
 <guid isPermaLink="false">3648 at http://blogs.forrester.com</guid>
  </item>
  <item>
    <title>Don't Sign Here Please</title>
    <link>http://blogs.forrester.com/john_kindervag/10-02-10-dont_sign_here_please</link>
    <description>&lt;p&gt;
	Visa just announced the expansion of their &lt;a href="http://corporate.visa.com/media-center/press-releases/press990.jsp" target="_blank"&gt;No Signature&lt;/a&gt; program. Citing its &amp;quot;popularity&amp;quot;, Visa notes that: &amp;quot;According to a Visa Inc. survey, 69 percent of participants surveyed cited either convenience or speed as the primary reason for using their credit or debit card.&amp;quot;&amp;nbsp; Wow.&lt;/p&gt;
&lt;p&gt;
	What this seems to signal is that Visa, and perhaps the other card brands, feel that they will make more money by eliminating barriers to the sale, such as the 2.2 seconds needed to sign your name, than it would lose in fraudulent transactions, considering this program is for transactions of US$25 or less. Also, it appears that people no longer know how to &lt;a href="http://www.newsweek.com/id/184751" target="_blank"&gt;sign their names&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;
	I have often heard (in low, barely audible whispers) that US consumers were too lazy to care about security, which is why the US will probably never have CHIP and PIN transactions for enhanced credit card authentication.&amp;nbsp; We Americans are too darn busy to push 4 numbers on a key pad (4.3 second).&amp;nbsp; This drives folks in the other parts of the world crazy as they are &lt;a href="http://usa.visa.com/personal/using_visa/european_travel_tips.html" target="_blank"&gt;in love with CHIP and PIN&lt;/a&gt; and, mistakenly, think that this technology eliminates all transaction risk.&amp;nbsp; CHIP and PIN cards still have a mag stripe that can be scanned, and skimming is still a problem. It&amp;#39;s a great authentication method, however, and would really help reduce some of the smaller, card-present CC frauds were we to adopt it.&lt;/p&gt;
&lt;p&gt;
	Americans need more paranoia about credit card theft. We are much more likely to suffer some type of credit card fraud or be affected by a major credit card breach than a terrorist attack, but for some reason we are unwilling to punch in a few numbers to help protect ourselves.&lt;/p&gt;
</description>
     <comments>http://blogs.forrester.com/john_kindervag/10-02-10-dont_sign_here_please#comments</comments>
 <category domain="http://blogs.forrester.com/category/it_security">IT security</category>
 <category domain="http://blogs.forrester.com/security_and_risk">Security and Risk</category>
 <pubDate>Wed, 10 Feb 2010 05:00:00 +0000</pubDate>
 <dc:creator>John Kindervag</dc:creator>
 <guid isPermaLink="false">3649 at http://blogs.forrester.com</guid>
  </item>
  <item>
    <title>Trends in Mobile Payments Are Frightening</title>
    <link>http://blogs.forrester.com/john_kindervag/10-02-08-trends_mobile_payments_are_frightening</link>
    <description>&lt;p&gt;
	Question: Do I really want someone with an iPhone taking my credit card info?&lt;a href="http://techcrunch.com/2010/01/28/verifone-iphone-square/?utm_source=feedburner&amp;amp;utm_medium=feed&amp;amp;utm_campaign=Feed:+Techcrunch+%28TechCrunch%29" target="_blank"&gt;&lt;br /&gt;
	Enormous&lt;/a&gt; &lt;a href="http://techcrunch.com/2010/01/28/verifone-iphone-square/?utm_source=feedburner&amp;amp;utm_medium=feed&amp;amp;utm_campaign=Feed:+Techcrunch+%28TechCrunch%29" target="_blank"&gt;buzz&lt;/a&gt; &lt;a href="http://www.mobilecrunch.com/2009/12/30/mophie-to-take-on-square-with-their-own-iphone-credit-card-reader/?utm_source=feedburner&amp;amp;utm_medium=feed&amp;amp;utm_campaign=Feed:+Techcrunch+%28TechCrunch%29" target="_blank"&gt;lately&lt;/a&gt; &lt;a href="http://techcrunch.com/2009/12/10/verifone-rushes-to-announce-square-competitor-jack-dorsey-comments/" target="_blank"&gt;about&lt;/a&gt; &lt;a href="http://www.mobilecrunch.com/2009/12/30/mophie-to-take-on-square-with-their-own-iphone-credit-card-reader/?utm_source=feedburner&amp;amp;utm_medium=feed&amp;amp;utm_campaign=Feed:+Techcrunch+%28TechCrunch%29" target="_blank"&gt;all&lt;/a&gt; &lt;a href="http://www.spartadata.com/" target="_blank"&gt;of the&lt;/a&gt; &lt;a href="http://www.paywaremobile.com/" target="_blank"&gt;new&lt;/a&gt; &lt;a href="https://squareup.com/" target="_blank"&gt;players&lt;/a&gt; &lt;a href="http://www.mophie.com/product-p/1113_mp-ip3g-blk.htm" target="_blank"&gt;trying&lt;/a&gt; to turn iPhones and other mobile devices into credit card swipe terminals.&amp;nbsp;Very scary.&amp;nbsp;Just because &lt;a href="http://www.youtube.com/watch?v=sVOzysmxhyM&amp;amp;feature=player_embedded" target="_blank"&gt;someone can create a website&lt;/a&gt; does not mean they understand payments.&lt;br /&gt;
	So many questions:&lt;/p&gt;
</description>
     <comments>http://blogs.forrester.com/john_kindervag/10-02-08-trends_mobile_payments_are_frightening#comments</comments>
 <category domain="http://blogs.forrester.com/security_and_risk">Security and Risk</category>
 <pubDate>Mon, 08 Feb 2010 05:00:00 +0000</pubDate>
 <dc:creator>John Kindervag</dc:creator>
 <guid isPermaLink="false">3650 at http://blogs.forrester.com</guid>
  </item>
  <item>
    <title>Online Shopping Sites May Be Sharing Your Credit Card Data</title>
    <link>http://blogs.forrester.com/john_kindervag/10-02-05-online_shopping_sites_may_be_sharing_your_credit_card_data</link>
    <description>&lt;p&gt;
	The Attorney General of New York is investigating a large group of online retailers to see if they have been sharing your credit card data with third parties without your knowledge or permission.&amp;nbsp;In a &lt;a href="http://www.ag.ny.gov/media_center/2010/jan/jan27a_10.html" target="_blank"&gt;press release&lt;/a&gt;, the AG&amp;#39;s Office details the scheme, including the fact that you may unknowingly be giving someone other than the retailer you are shopping with your credit card number:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;
	&amp;quot;Information about joining the membership program and its ramifications, including the fact that the consumer is agreeing to transfer his or her credit or debit card account information, is buried in fine print and cluttered text.&amp;quot;&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;
	My gut tells me that this violates the spirit, if not the letter, of the PCI Data Security Standard.&amp;nbsp; According to the PCI DSS:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;
	&amp;quot;Additionally, merchants and service providers must manage and monitor the PCI DSS compliance of all associated third parties with access to cardholder data.&amp;quot;&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;
	It is probably safe to assume that the business agreement around the data sharing identified by the New York AG&amp;#39;s office did not include language surrounding PCI compliance.&lt;br /&gt;
	An &lt;a href="http://www.msnbc.msn.com/id/35221235/ns/business-consumer_news//" target="_blank"&gt;MSNBC story&lt;/a&gt; on the investigation puts it this way:&lt;/p&gt;
</description>
     <comments>http://blogs.forrester.com/john_kindervag/10-02-05-online_shopping_sites_may_be_sharing_your_credit_card_data#comments</comments>
 <category domain="http://blogs.forrester.com/category/current_affairs">Current Affairs</category>
 <category domain="http://blogs.forrester.com/security_and_risk">Security and Risk</category>
 <pubDate>Fri, 05 Feb 2010 05:00:00 +0000</pubDate>
 <dc:creator>John Kindervag</dc:creator>
 <guid isPermaLink="false">3651 at http://blogs.forrester.com</guid>
  </item>
  <item>
    <title>MiFi Pwned!</title>
    <link>http://blogs.forrester.com/john_kindervag/10-02-03-mifi_pwned</link>
    <description>&lt;p&gt;Wireless hacking Guru, &lt;a href="http://www.willhackforsushi.com/" target="_blank"&gt;Josh Wright&lt;/a&gt;,has just announced that he has &lt;a href="http://www.willhackforsushi.com/?p=417" target="_blank"&gt;created havoc with a MiFi personal access point&lt;/a&gt;.MiFi is a little device that turns 3G wireless signals into WiFi.&amp;nbsp; The cool thing is that the wireless signal can be shared with other nearby computers.&amp;nbsp; According to Josh, he has found a way that, &amp;quot;An attacker can recover the default password from any MiFi device.&amp;quot; This is big news because anyone who is involved with wireless ne&lt;/p&gt;
</description>
     <comments>http://blogs.forrester.com/john_kindervag/10-02-03-mifi_pwned#comments</comments>
 <category domain="http://blogs.forrester.com/category/it_security">IT security</category>
 <category domain="http://blogs.forrester.com/security_and_risk">Security and Risk</category>
 <pubDate>Wed, 03 Feb 2010 05:00:00 +0000</pubDate>
 <dc:creator>John Kindervag</dc:creator>
 <guid isPermaLink="false">3652 at http://blogs.forrester.com</guid>
  </item>
  <item>
    <title>The changing nature of governance, risk, and compliance</title>
    <link>http://blogs.forrester.com/chris_mcclean/10-02-02-changing_nature_governance_risk_and_compliance</link>
    <description>&lt;p&gt;In my ongoing work with clients, I try as often as possible to stress the importance of flexibility in GRC programs. Internal processes and technology implementations must be able to accommodate the perpetually fluctuating aspects of business, compliance requirements, and risk factors. If GRC investments are made without consideration for likely requirements 1 to 2 years down the road, decision makers aren&amp;rsquo;t doing their job. And if vendors don&amp;rsquo;t offer that flexibility, they shouldn&amp;rsquo;t be on the shortlist.&lt;/p&gt;
&lt;p&gt;News outlets over the past year have given us almost daily examples of change in the GRC landscape. The recent stories coming out of Davos have been no exception... giving us some truly fascinating debates on the necessity and detriment of regulations. As quoted in a &lt;a href="http://online.wsj.com/article/SB10001424052748703762504575036634012161608.html?mod=WSJ_Small%20Business_IndustryNews"&gt;Wall Street Journal article&lt;/a&gt; on Sunday, Deutsche Bank AG Chief Executive Josef Ackermann argued against heavy-handed regulation, saying, "We should stop the blame game and we should start looking forward... if you don't have a strong financial sector to support the this recovery... you're making a huge mistake and you will regret that later on," he said. French President Nicholas Sarkozy summed up the opposing argument in his keynote, explaining, "There is indecent behavior that will no longer be tolerated by public opinion in any country of the world... That those who create jobs and wealth may earn a lot of money is not shocking. But that those who contribute to destroying jobs and wealth also earn a lot of money is morally indefensible."&lt;/p&gt;
</description>
     <comments>http://blogs.forrester.com/chris_mcclean/10-02-02-changing_nature_governance_risk_and_compliance#comments</comments>
 <category domain="http://blogs.forrester.com/category/grc">GRC</category>
 <category domain="http://blogs.forrester.com/security_and_risk">Security and Risk</category>
 <pubDate>Tue, 02 Feb 2010 05:00:00 +0000</pubDate>
 <dc:creator>Chris McClean</dc:creator>
 <guid isPermaLink="false">3499 at http://blogs.forrester.com</guid>
  </item>
  <item>
    <title>Is 3-D Secure Insecure?</title>
    <link>http://blogs.forrester.com/john_kindervag/10-02-01-3_d_secure_insecure</link>
    <description>&lt;p&gt;
	&lt;a href="http://www.lightbluetouchpaper.org/2010/01/26/how-online-card-security-fails/" target="_blank"&gt;Security Researchers&lt;/a&gt; in the UK say that the &lt;a href="https://partnernetwork.visa.com/vpn/global/category.do?categoryId=85&amp;amp;documentId=117&amp;amp;userRegion=" target="_blank"&gt;3-D Secure&lt;/a&gt; (3DS) system&amp;nbsp;for credit card authorization, a protocol that was &amp;quot;developed by Visa to improve the security of Internet payments,&amp;quot; has significant security weaknesses. It is used by both of the ginormous card brands, known as &amp;quot;Verified by Visa&amp;quot; and &amp;quot;MasterCard SecureCode.&amp;quot;&lt;/p&gt;
&lt;p&gt;
	This could be a big deal.&lt;/p&gt;
&lt;p&gt;
	In a &lt;a href="http://www.cl.cam.ac.uk/%7Erja14/Papers/fc10vbvsecurecode.pdf" target="_blank"&gt;recent paper&lt;/a&gt;, the researcher calls out 3-D Secure as a security failure that was pushed on consumers by financially incentivized merchants because, &amp;quot;its use is encouraged by contractual terms on liability: merchants who adopt 3DS have reduced liability for disputed transactions. Previous single sign-on schemes lacked liability agreements, which hampered their take-up.&amp;quot;&lt;/p&gt;
&lt;p&gt;
	According to the authors:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;
		&amp;quot;3-D Secure has lousy technology, but got the economics right (at least for banks and merchants); it now boasts hundreds of millions of accounts. We suggest a path towards more robust authentication that is technologically sound and where the economics would work for banks, merchants, and customers - given a gentle regulatory nudge.&amp;quot;&lt;/p&gt;
&lt;/blockquote&gt;</description>
     <comments>http://blogs.forrester.com/john_kindervag/10-02-01-3_d_secure_insecure#comments</comments>
 <category domain="http://blogs.forrester.com/category/identity_and_access_management">Identity and access management</category>
 <category domain="http://blogs.forrester.com/security_and_risk">Security and Risk</category>
 <pubDate>Mon, 01 Feb 2010 05:00:00 +0000</pubDate>
 <dc:creator>John Kindervag</dc:creator>
 <guid isPermaLink="false">3653 at http://blogs.forrester.com</guid>
  </item>
  <item>
    <title>Virtual Network Segmentation for PCI?</title>
    <link>http://blogs.forrester.com/john_kindervag/10-01-29-virtual_network_segmentation_pci</link>
    <description>&lt;p&gt;
	Several clients have recently been asking about &amp;quot;Virtual Network Segmentation&amp;quot; products that claim to segment networks to reduce PCI compliance. They may use ARP or VLANs to control access to various network segments.&amp;nbsp; These type of controls work at Layer 2 and the hacker community is well versed at using tools such as &lt;a href="http://ettercap.sourceforge.net/" target="_blank"&gt;Ettercap &lt;/a&gt;or &lt;a href="http://www.oxid.it/cain.html" target="_blank"&gt;Cain &amp;amp; Abel&lt;/a&gt; to bypass those controls.&amp;nbsp; We&amp;#39;ve recently written about &lt;a href="http://www.forrester.com/rb/Research/pci_x-ray_network_segmentation/q/id/48414/t/2" target="_blank"&gt;Network Segmentation for PCI&lt;/a&gt; as part of the PCI X-Ray series.&lt;br /&gt;
	While rereading the &lt;a href="https://www.pcisecuritystandards.org/pdfs/PCI_DSS_Wireless_Guidelines.pdf" target="_blank"&gt;PCI Wireless Guidance&lt;/a&gt; document, I came across this nugget that puts a nail in the coffin of using VLANs as a security control:&amp;quot;Relying on Virtual LAN (VLAN) based segmentation alone is not sufficient. For example, having the CDE on one VLAN and the WLAN on a separate VLAN does not adequately segment the WLAN and take it out of PCI DSS scope. VLANs were designed for managing large LANs efficiently. As such, a hacker can hop across VLANs using several known techniques if adequate access controls between VLANs are not in place. As a general rule, any protocol and traffic that is not necessary in the CDE, i.e., not used or needed for credit card transactions, should be blocked. This will result in reduced risk of attack and will create a CDE that has less traffic and is thus easier to monitor.&amp;quot;&lt;/p&gt;
</description>
     <comments>http://blogs.forrester.com/john_kindervag/10-01-29-virtual_network_segmentation_pci#comments</comments>
 <category domain="http://blogs.forrester.com/category/current_affairs">Current Affairs</category>
 <category domain="http://blogs.forrester.com/security_and_risk">Security and Risk</category>
 <pubDate>Fri, 29 Jan 2010 05:00:00 +0000</pubDate>
 <dc:creator>John Kindervag</dc:creator>
 <guid isPermaLink="false">3654 at http://blogs.forrester.com</guid>
  </item>
  <item>
    <title>Plain speaking about industrial spying</title>
    <link>http://blogs.forrester.com/andrew_jaquith/10-01-25-plain_speaking_about_industrial_spying</link>
    <description>&lt;p&gt;
	&lt;strong&gt;Or: why &amp;ldquo;advanced persistent threat&amp;rdquo; is the wrong phrase&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;
	Google&amp;#39;s revelation that it was hacked by (likely) Chinese actors has helped propel another round of stories, blog posts, and analyses about &lt;a href="http://blogs.forrester.com/srm/2010/01/the-aurora-attack-on-google-what-it-means.html" target="_blank"&gt;What It Means&lt;/a&gt;. I have participated in some of these &lt;a href="http://taosecurity.blogspot.com/2010/01/what-is-apt-and-what-does-it-want.html" target="_blank"&gt;discussions&lt;/a&gt;, and my colleague Chenxi Wang has written &lt;a href="http://blogs.forrester.com/srm/2010/01/update-google-calls-and-confirms-the-vpn-story.html" target="_blank"&gt;several&lt;/a&gt; &lt;a href="http://blogs.forrester.com/srm/2010/01/why-google-and-microsoft-not-cloud-computing-were-at-fault-for-the-google-hack.html" target="_blank"&gt;illuminating&lt;/a&gt; posts about the nature of the attacks.&lt;/p&gt;
&lt;p&gt;
	The specific means of compromise, a zero-day Internet Explorer exploit, has raised awareness of a phenomenon referred to as the &amp;ldquo;Advanced Persistent Threat,&amp;rdquo;&amp;nbsp;&lt;a href="http://blogs.sans.org/computer-forensics/2009/07/22/security-intelligence-introduction-pt-1/" target="_blank"&gt;concisely described by Lockheed Martin&amp;rsquo;s Mike Cloppert&lt;/a&gt; as &amp;ldquo;any sophisticated adversary engaged in information warfare in support of long-term strategic goals.&amp;rdquo; In his posts, Mike also nearly always uses APT in conjunction with the word &amp;ldquo;actor&amp;rdquo; (as in: APT actor) because he means a particular adversary. Mike&amp;#39;s definitions are important because they help clarify what APT is, and what it is not. Expanding on his definition a bit, here is what I believe APT is:&lt;/p&gt;
</description>
     <comments>http://blogs.forrester.com/andrew_jaquith/10-01-25-plain_speaking_about_industrial_spying#comments</comments>
 <category domain="http://blogs.forrester.com/category/computerworlduk">ComputerworldUK</category>
 <category domain="http://blogs.forrester.com/category/cso_magazine">CSO Magazine</category>
 <category domain="http://blogs.forrester.com/category/incident_response">Incident response</category>
 <category domain="http://blogs.forrester.com/category/it_security">IT security</category>
 <category domain="http://blogs.forrester.com/category/network_security">Network Security</category>
 <category domain="http://blogs.forrester.com/security_and_risk">Security and Risk</category>
 <pubDate>Mon, 25 Jan 2010 05:00:00 +0000</pubDate>
 <dc:creator>Andrew Jaquith</dc:creator>
 <guid isPermaLink="false">3655 at http://blogs.forrester.com</guid>
  </item>
  <item>
    <title>Cyber security sees the light of day in the NIST smart grid interoperability standard</title>
    <link>http://blogs.forrester.com/usman_sindhu/10-01-22-cyber_security_sees_light_day_nist_smart_grid_interoperability_standard</link>
    <description>&lt;p&gt;
	Just this week on Tuesday, NIST published &lt;a href="http://www.smartgridnews.com/artman/uploads/1/NIST_Issues_First_Release_of_Framework.pdf" target="_blank"&gt;release 1.0 of the smart grid interoperability standards.&lt;/a&gt; Most notably, this is the first attempt to address cyber security in smart grid deployments. This release points to various standards that can be used for implementing interoperability and security controls, and it&amp;rsquo;s fair to say that it plants the seeds for what should become comprehensive, control-driven guidelines for implementing various aspects of smart grid.&lt;/p&gt;
&lt;p&gt;
	The timing of this report is perfect, as current smart grid rollouts are often &lt;a href="http://smartgridsecurity.blogspot.com/2009/12/smart-grid-security-confidence-game.html" target="_blank"&gt;criticized for lack of proper security controls.&lt;/a&gt; Our utility customers have shown similar concern about the lack of planning for information security before the roll out phase. This lack of security and risk management perspective in the smart grid ecosystem can jeopardize the overall objective of these &lt;a href="http://www.barackobama.com/issues/newenergy/index.php" target="_blank"&gt;smart energy initiatives&lt;/a&gt;, and it&amp;rsquo;s about time that we devise a game plan going forward.&lt;/p&gt;
&lt;p&gt;
	The NIST publication will be an important piece of work as it brings various standards, bodies, and regulators like IEEE, NERC, and FERC to the table. Note, this is not a control based standard like others published by NIST, but a guideline to other frameworks that should be referenced when working in a smart ecosystem. A more control based work on cyber security in smart grid is in development and the draft of these standards is available for &lt;a href="http://csrc.nist.gov/publications/drafts/nistir-7628/draft-nistir-7628.pdf" target="_blank"&gt;public review.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	A few important highlights to pay close attention to in the cyber security sections are:&lt;/p&gt;
</description>
     <comments>http://blogs.forrester.com/usman_sindhu/10-01-22-cyber_security_sees_light_day_nist_smart_grid_interoperability_standard#comments</comments>
 <category domain="http://blogs.forrester.com/category/computerworlduk">ComputerworldUK</category>
 <category domain="http://blogs.forrester.com/category/cso_magazine">CSO Magazine</category>
 <category domain="http://blogs.forrester.com/category/current_affairs">Current Affairs</category>
 <category domain="http://blogs.forrester.com/category/it_risk_management">IT Risk Management</category>
 <category domain="http://blogs.forrester.com/category/it_security">IT security</category>
 <category domain="http://blogs.forrester.com/category/network_security">Network Security</category>
 <category domain="http://blogs.forrester.com/category/privacy">Privacy</category>
 <category domain="http://blogs.forrester.com/category/science">Science</category>
 <category domain="http://blogs.forrester.com/security_and_risk">Security and Risk</category>
 <pubDate>Fri, 22 Jan 2010 05:00:00 +0000</pubDate>
 <dc:creator>Usman Sindhu</dc:creator>
 <guid isPermaLink="false">3657 at http://blogs.forrester.com</guid>
  </item>
  <item>
    <title>(Update) Google calls and retracts the VPN story</title>
    <link>http://blogs.forrester.com/chenxi_wang_ph_d/10-01-21-update_google_calls_and_retracts_vpn_story</link>
    <description>&lt;p&gt;
	Google called again after I posted the latest follow up to the Google hack story. Wow, two calls from Google AR in the span of an hour! They were uncomfortable about the way I characterized the involvement of the corporate VPN in the Google attack. The official on-the-record word from Google is: &amp;quot;This is not accurate.&amp;quot;&amp;nbsp;So, I should rephrase how the attack happened:&lt;/p&gt;
&lt;p&gt;
	a) A Google employee&amp;#39;s machine that was running IE v6 was compromised via the IE vulnerability.&lt;/p&gt;
&lt;p&gt;
	b) The attacker used the compromised machine to somehow gain access to Google servers (some of which housed critical information). The method of access, at some point, may have involved VPN, but Google does not agree with the characterization that &amp;quot;the compromised client used their corporate VPN to gain access to the servers.&amp;quot; At Google&amp;#39;s request, I retract that particular statement.&lt;/p&gt;
&lt;p&gt;
	This is what we do know factually:&lt;/p&gt;
&lt;p&gt;
	1) The attack on the Google server happened.&lt;/p&gt;
&lt;p&gt;
	2) Google immediately decided to do an emergency update of their entire corporate VPN infrastructure.&lt;/p&gt;
&lt;p&gt;
	Could these two things be entirely unrelated? I doubt it. But Google isn&amp;#39;t going on the record to say that the attack came in via the VPN, and that&amp;#39;s their official position.&lt;/p&gt;
&lt;p&gt;
	On a positive note, Google is actively trying to schedule the security interview with me. So hopefully I&amp;#39;ll have more to report shortly.&lt;/p&gt;
</description>
     <comments>http://blogs.forrester.com/chenxi_wang_ph_d/10-01-21-update_google_calls_and_retracts_vpn_story#comments</comments>
 <category domain="http://blogs.forrester.com/category/it_security">IT security</category>
 <category domain="http://blogs.forrester.com/security_and_risk">Security and Risk</category>
 <pubDate>Thu, 21 Jan 2010 06:00:00 +0000</pubDate>
 <dc:creator>Chenxi Wang, Ph. D.</dc:creator>
 <guid isPermaLink="false">3658 at http://blogs.forrester.com</guid>
  </item>
  <item>
    <title>Why Google and Microsoft, not cloud computing, were at fault for the Google hack</title>
    <link>http://blogs.forrester.com/chenxi_wang_ph_d/10-01-21-why_google_and_microsoft_not_cloud_computing_were_fault_google_hack</link>
    <description>&lt;p&gt;
	By now, much has been written about last week&amp;rsquo;s attack on Google, Yahoo, and more than 30 other companies. Google&amp;rsquo;s stark reaction to the attack has put the company at the forefront of this news story. At stake is one of the world&amp;rsquo;s largest Internet markets, as well as the already tenuous relationship between&amp;nbsp;US and China - it is no wonder this attack is drawing the attention of headlines worldwide.&lt;/p&gt;
&lt;p&gt;
	Why isn&amp;rsquo;t this an attack on cloud computing?&lt;/p&gt;
</description>
     <comments>http://blogs.forrester.com/chenxi_wang_ph_d/10-01-21-why_google_and_microsoft_not_cloud_computing_were_fault_google_hack#comments</comments>
 <category domain="http://blogs.forrester.com/category/it_security">IT security</category>
 <category domain="http://blogs.forrester.com/security_and_risk">Security and Risk</category>
 <pubDate>Thu, 21 Jan 2010 05:00:00 +0000</pubDate>
 <dc:creator>Chenxi Wang, Ph. D.</dc:creator>
 <guid isPermaLink="false">3659 at http://blogs.forrester.com</guid>
  </item>
  <item>
    <title>The Devil’s Dictionary, InfoSec Edition</title>
    <link>http://blogs.forrester.com/andrew_jaquith/10-01-20-devil%E2%80%99s_dictionary_infosec_edition</link>
    <description>&lt;p&gt;
	&lt;a href="http://en.wikipedia.org/wiki/Ambrose_Bierce" target="_blank"&gt;Ambrose Bierce&lt;/a&gt;&amp;rsquo;s &lt;a href="http://www.thedevilsdictionary.com/" target="_blank"&gt;The Devil&amp;rsquo;s Dictionary&lt;/a&gt; is a wickedly witty piece of work (and website). It slyly redefines common words and phrases, usually with a bitter, contrarian, or comic touch. But why should Mr. Bierce (or more correctly, his estate) have all the fun? It is time for one in the information security field. Here are a few nominations. Most of these are original, but a few were gleefully filched from others:&lt;/p&gt;
&lt;blockquote class="webkit-indent-blockquote"&gt;&lt;p&gt;
		&lt;strong&gt;ALE&lt;/strong&gt;: an intoxicating liquor that gives imbibers perceived omniscience and discernment, but with one unfortunate side effect: it causes their pants to spontaneously fall down&lt;/p&gt;
&lt;p&gt;
		&lt;strong&gt;Advanced persistent threat&lt;/strong&gt;:&amp;nbsp;a security product manager hyping new categories&lt;/p&gt;
&lt;p&gt;
		&lt;strong&gt;Blended threat:&lt;/strong&gt;&amp;nbsp;a hemlock smoothie&lt;/p&gt;
&lt;p&gt;
		&lt;strong&gt;Claims&lt;/strong&gt;:&amp;nbsp;a more expensive form of &lt;em&gt;assertions,&lt;/em&gt;&amp;nbsp;officially sanctioned with George Orwell&amp;rsquo;s posthumous blessing. &lt;em&gt;cf&lt;/em&gt;&amp;nbsp;&amp;ldquo;flatbread&amp;rdquo; v. &amp;ldquo;pizza&amp;rdquo;&lt;/p&gt;
&lt;p&gt;
		&lt;strong&gt;Collective intelligence&lt;/strong&gt;: the dawning epiphany that the cyber-villains have already won&lt;/p&gt;
&lt;p&gt;
		&lt;strong&gt;Data leak prevention&lt;/strong&gt;: adult undergarments for stopping electronic incontinence&lt;/p&gt;
&lt;p&gt;
		&lt;strong&gt;Device control&lt;/strong&gt;: using Super Glue to plug holes in the sides of laptops&lt;/p&gt;
&lt;p&gt;
		&lt;strong&gt;Full disclosure debate&lt;/strong&gt;: a ritualistic Kabuki performance that ends with a fist-fight amongst members of the audience&lt;/p&gt;
&lt;p&gt;
		&lt;strong&gt;Actionable&lt;/strong&gt;: providing information of sufficient detail and clarity to enable one party to sue another*&amp;nbsp;&lt;/p&gt;
&lt;p&gt;
		&lt;strong&gt;Full disk encryption&lt;/strong&gt;: spray-on auditor repellent&lt;/p&gt;
&lt;/blockquote&gt;</description>
     <comments>http://blogs.forrester.com/andrew_jaquith/10-01-20-devil%E2%80%99s_dictionary_infosec_edition#comments</comments>
 <category domain="http://blogs.forrester.com/category/current_affairs">Current Affairs</category>
 <category domain="http://blogs.forrester.com/security_and_risk">Security and Risk</category>
 <pubDate>Wed, 20 Jan 2010 05:00:00 +0000</pubDate>
 <dc:creator>Andrew Jaquith</dc:creator>
 <guid isPermaLink="false">3660 at http://blogs.forrester.com</guid>
  </item>
  <item>
    <title>The Attack on Google: What It Means</title>
    <link>http://blogs.forrester.com/andrew_jaquith/10-01-15-attack_google_what_it_means</link>
    <description>&lt;p&gt;
	Unless you have been living under a rock for the past few days, you probably have heard about some big changes Google has made regarding an attack on its infrastructure. Here is what we know:&lt;/p&gt;
</description>
     <comments>http://blogs.forrester.com/andrew_jaquith/10-01-15-attack_google_what_it_means#comments</comments>
 <category domain="http://blogs.forrester.com/security_and_risk">Security and Risk</category>
 <pubDate>Fri, 15 Jan 2010 05:00:00 +0000</pubDate>
 <dc:creator>Andrew Jaquith</dc:creator>
 <guid isPermaLink="false">3662 at http://blogs.forrester.com</guid>
  </item>
  </channel>
</rss>
