<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Stratfor Hacking Underscores Need for Fast Communications Response</title>
	<atom:link href="http://www.davidhenderson.com/2011/12/25/stratfor-hacking-underscores-need-for-fast-communications-response/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.davidhenderson.com/2011/12/25/stratfor-hacking-underscores-need-for-fast-communications-response/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=stratfor-hacking-underscores-need-for-fast-communications-response</link>
	<description>Writer, communications strategist, Emmy Award winning former CBS News correspondent</description>
	<lastBuildDate>Tue, 22 May 2012 15:13:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: DH</title>
		<link>http://www.davidhenderson.com/2011/12/25/stratfor-hacking-underscores-need-for-fast-communications-response/#comment-33926</link>
		<dc:creator>DH</dc:creator>
		<pubDate>Tue, 27 Dec 2011 20:49:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidhenderson.com/?p=10494#comment-33926</guid>
		<description>Nick,

In answer to your question, Stratfor could have shown accountability, accept responsibility and demonstrated a level of empathy and active support for clients whose credit cards have been compromised by the company&#039;s lack of security. Just telling customers that, &quot;opps but we permitted credit card information to fall into the wrong hands&quot; is not good enough.

Contacting non-specific law enforcement and hiring a security consultant they should have already had on retainer are irrelevant.

Quite honestly, I would be surprised if Stratfor can survive their own lack of accountability and transparency.

DH</description>
		<content:encoded><![CDATA[<p>Nick,</p>
<p>In answer to your question, Stratfor could have shown accountability, accept responsibility and demonstrated a level of empathy and active support for clients whose credit cards have been compromised by the company&#8217;s lack of security. Just telling customers that, &#8220;opps but we permitted credit card information to fall into the wrong hands&#8221; is not good enough.</p>
<p>Contacting non-specific law enforcement and hiring a security consultant they should have already had on retainer are irrelevant.</p>
<p>Quite honestly, I would be surprised if Stratfor can survive their own lack of accountability and transparency.</p>
<p>DH</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Selby</title>
		<link>http://www.davidhenderson.com/2011/12/25/stratfor-hacking-underscores-need-for-fast-communications-response/#comment-33919</link>
		<dc:creator>Nick Selby</dc:creator>
		<pubDate>Tue, 27 Dec 2011 16:41:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidhenderson.com/?p=10494#comment-33919</guid>
		<description>David,
I think that you are conflating the previous activities - crap security, dunderheaded management choices, clearly idiotic and unforgivable decisions especially including your #4 above but also many, many other things - with their incident response.  As someone who consults very large enterprises on how to deal with incidents similar to this from a security standpoint (not, I admit, from a communications standpoint, and I don;&#039;t challenge your credentials here), and as an analyst, I would say that you need to de-couple your damnation of their rubbish before the breach when you look at their behavior after the breach. 

Realistically, they had no idea that they were breached until it hit. Again this is due entirely to their terrible security-fu to begin with (all the more galling since they claim expertise not just in OSINT but also in Cyber OSINT), however it seems to be the case: they were all home fat, dumb and happy when the thing hit. 

Pragmatically speaking, they lost any chance to get ahead of the buzz because the buzz alerted them. So while it&#039;s great to sit in an ivory tower and curse them for not getting ahead, we need to judge them based on what was possible for them, in their situation. And what they did, in my opinion, was exemplary. They admitted it nearly immediately and gave everyone the &quot;We&#039;ve been pwn3d, we lost your info, panic now, details to follow&quot; almost immediately; they did not overcommit, they promised to look into it. Then they followed up on the 25th, and promised to follow up again on the 28th. You say that they waited 18 hours and were repetitive - I respectfully disagree. On the 25th they stated that they were preparing to offer credit monitoring, they gave specific steps to take for those clueless enough not to understand the exposure, and they mentioned their work with law enforcement (and STRATFOR has some pretty good connections there), AND they committed to do better in the future, telling us they hired a firm much like mine to help them not suck any more.

Their customers are almost entirely in the industry, and as such, know how to get their own luggage off the carousel. I don&#039;t see among my colleagues even a hint of the great vengeance and furious anger you stated would be forthcoming - we&#039;re all security and intelligence professionals and we all know that everyone gets hacked. We don&#039;t forgive what they did, but we understand that they did it, and they&#039;ve promised to fix it. 

On Twitter, the conversations have been mixed until you recognize universal, violent agreement: every one of us in the business believe that they should be flogged with a bullwhip for what they did pre-breach. And all of us recognize that post-breach, w

So I would ask you to be more specific. What specifically could STRATFOR do now to get ahead of this, in your opinion. I&#039;m sure you don&#039;t mean merely to kick someone when he&#039;s down: let&#039;s get specific. In the past 36 hours they&#039;ve:

* Admitted a breach and informed those they believe may be affected
* Contacted law enforcement and are conducting and cooperating with an active investigation
* Arranged for credit monitoring for those affected
* Given basic tips for all customers
* Engaged a team of security consultants to help them get their house in order going forward
* Promised to ensure that in the future, they will be better stewards of the information we entrust them with. 
* Promised to come back with more information tomorrow. 

What else should they be doing, in your opinion, to stay ahead of this? I am being neither sarcastic nor rhetorical, I honestly think they&#039;ve done a good job so far.

Kind regards,
Nick Selby</description>
		<content:encoded><![CDATA[<p>David,<br />
I think that you are conflating the previous activities &#8211; crap security, dunderheaded management choices, clearly idiotic and unforgivable decisions especially including your #4 above but also many, many other things &#8211; with their incident response.  As someone who consults very large enterprises on how to deal with incidents similar to this from a security standpoint (not, I admit, from a communications standpoint, and I don;&#8217;t challenge your credentials here), and as an analyst, I would say that you need to de-couple your damnation of their rubbish before the breach when you look at their behavior after the breach. </p>
<p>Realistically, they had no idea that they were breached until it hit. Again this is due entirely to their terrible security-fu to begin with (all the more galling since they claim expertise not just in OSINT but also in Cyber OSINT), however it seems to be the case: they were all home fat, dumb and happy when the thing hit. </p>
<p>Pragmatically speaking, they lost any chance to get ahead of the buzz because the buzz alerted them. So while it&#8217;s great to sit in an ivory tower and curse them for not getting ahead, we need to judge them based on what was possible for them, in their situation. And what they did, in my opinion, was exemplary. They admitted it nearly immediately and gave everyone the &#8220;We&#8217;ve been pwn3d, we lost your info, panic now, details to follow&#8221; almost immediately; they did not overcommit, they promised to look into it. Then they followed up on the 25th, and promised to follow up again on the 28th. You say that they waited 18 hours and were repetitive &#8211; I respectfully disagree. On the 25th they stated that they were preparing to offer credit monitoring, they gave specific steps to take for those clueless enough not to understand the exposure, and they mentioned their work with law enforcement (and STRATFOR has some pretty good connections there), AND they committed to do better in the future, telling us they hired a firm much like mine to help them not suck any more.</p>
<p>Their customers are almost entirely in the industry, and as such, know how to get their own luggage off the carousel. I don&#8217;t see among my colleagues even a hint of the great vengeance and furious anger you stated would be forthcoming &#8211; we&#8217;re all security and intelligence professionals and we all know that everyone gets hacked. We don&#8217;t forgive what they did, but we understand that they did it, and they&#8217;ve promised to fix it. </p>
<p>On Twitter, the conversations have been mixed until you recognize universal, violent agreement: every one of us in the business believe that they should be flogged with a bullwhip for what they did pre-breach. And all of us recognize that post-breach, w</p>
<p>So I would ask you to be more specific. What specifically could STRATFOR do now to get ahead of this, in your opinion. I&#8217;m sure you don&#8217;t mean merely to kick someone when he&#8217;s down: let&#8217;s get specific. In the past 36 hours they&#8217;ve:</p>
<p>* Admitted a breach and informed those they believe may be affected<br />
* Contacted law enforcement and are conducting and cooperating with an active investigation<br />
* Arranged for credit monitoring for those affected<br />
* Given basic tips for all customers<br />
* Engaged a team of security consultants to help them get their house in order going forward<br />
* Promised to ensure that in the future, they will be better stewards of the information we entrust them with.<br />
* Promised to come back with more information tomorrow. </p>
<p>What else should they be doing, in your opinion, to stay ahead of this? I am being neither sarcastic nor rhetorical, I honestly think they&#8217;ve done a good job so far.</p>
<p>Kind regards,<br />
Nick Selby</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.davidhenderson.com/2011/12/25/stratfor-hacking-underscores-need-for-fast-communications-response/#comment-33860</link>
		<dc:creator>David</dc:creator>
		<pubDate>Mon, 26 Dec 2011 19:45:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidhenderson.com/?p=10494#comment-33860</guid>
		<description>Dear WMichel and Dissent,

Your comments suggest you have no credentials in the area of crisis communications. Are you in IT?

dh</description>
		<content:encoded><![CDATA[<p>Dear WMichel and Dissent,</p>
<p>Your comments suggest you have no credentials in the area of crisis communications. Are you in IT?</p>
<p>dh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WMichel</title>
		<link>http://www.davidhenderson.com/2011/12/25/stratfor-hacking-underscores-need-for-fast-communications-response/#comment-33858</link>
		<dc:creator>WMichel</dc:creator>
		<pubDate>Mon, 26 Dec 2011 17:39:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidhenderson.com/?p=10494#comment-33858</guid>
		<description>I agree with Helgeson.  The main thing they did wrong was #4.  They informed the affected customers VERY quickly.  Everyone else can wait.  These guys http://policeledintelligence.com/2011/12/25/rating-the-stratfor-incident-response/ rated them A- for communication.</description>
		<content:encoded><![CDATA[<p>I agree with Helgeson.  The main thing they did wrong was #4.  They informed the affected customers VERY quickly.  Everyone else can wait.  These guys <a href="http://policeledintelligence.com/2011/12/25/rating-the-stratfor-incident-response/" rel="nofollow">http://policeledintelligence.com/2011/12/25/rating-the-stratfor-incident-response/</a> rated them A- for communication.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dissent</title>
		<link>http://www.davidhenderson.com/2011/12/25/stratfor-hacking-underscores-need-for-fast-communications-response/#comment-33855</link>
		<dc:creator>Dissent</dc:creator>
		<pubDate>Mon, 26 Dec 2011 16:24:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidhenderson.com/?p=10494#comment-33855</guid>
		<description>You wrote, &quot;When a hacking occurs, get out ahead of the social media buzz with openness, swiftness and transparency.&quot;

And that&#039;s why companies may wind up looking more incompetent. As you note, their first e-mail suggested the hack occurred on Christmas Eve.  It didn&#039;t, but now they are on record as having not known for how long they had been compromised. 

On my blog, I encourage breached entities to be transparent, but I also encourage them NOT to rush to statements they may regret. Yes, be prompt, but only tell your customers that you are investigating and will tell them more as soon as you know more. Tell them what to do to err on the side of caution, e.g., &quot;Although we have not verified anything yet, to be safe, we suggest you contact your banks,...&quot;

But don&#039;t make any firm statements about the breach that you haven&#039;t yet verified by forensics.

And no, they do NOT have to get their site back up as quickly as you suggest. And if I were them, I&#039;d leave it down until after a security consultant could arrange to secure it adequately.  And that doesn&#039;t happen within 24 hours - or 48 - or 72.

The only point on which we agree is that Stratfor fscked up royally by not encrypting sensitive info and by storing CVVs at all, much less in clear text.

They will pay dearly for this breach. They need to get their breach response right. Your advice is not only unhelpful, but I think it&#039;s counterproductive.</description>
		<content:encoded><![CDATA[<p>You wrote, &#8220;When a hacking occurs, get out ahead of the social media buzz with openness, swiftness and transparency.&#8221;</p>
<p>And that&#8217;s why companies may wind up looking more incompetent. As you note, their first e-mail suggested the hack occurred on Christmas Eve.  It didn&#8217;t, but now they are on record as having not known for how long they had been compromised. </p>
<p>On my blog, I encourage breached entities to be transparent, but I also encourage them NOT to rush to statements they may regret. Yes, be prompt, but only tell your customers that you are investigating and will tell them more as soon as you know more. Tell them what to do to err on the side of caution, e.g., &#8220;Although we have not verified anything yet, to be safe, we suggest you contact your banks,&#8230;&#8221;</p>
<p>But don&#8217;t make any firm statements about the breach that you haven&#8217;t yet verified by forensics.</p>
<p>And no, they do NOT have to get their site back up as quickly as you suggest. And if I were them, I&#8217;d leave it down until after a security consultant could arrange to secure it adequately.  And that doesn&#8217;t happen within 24 hours &#8211; or 48 &#8211; or 72.</p>
<p>The only point on which we agree is that Stratfor fscked up royally by not encrypting sensitive info and by storing CVVs at all, much less in clear text.</p>
<p>They will pay dearly for this breach. They need to get their breach response right. Your advice is not only unhelpful, but I think it&#8217;s counterproductive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DH</title>
		<link>http://www.davidhenderson.com/2011/12/25/stratfor-hacking-underscores-need-for-fast-communications-response/#comment-33849</link>
		<dc:creator>DH</dc:creator>
		<pubDate>Mon, 26 Dec 2011 14:15:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidhenderson.com/?p=10494#comment-33849</guid>
		<description>Thank you for your perspective. My article is about best practices. A company needs to implement all security safeguards. Stratfor did not. Stratfor is still offline on Monday, December 26.

My #4 point is the most important.  I agree. It was inexcusable for Stratfor to have unencrypted confidential client information on the server. 

DH</description>
		<content:encoded><![CDATA[<p>Thank you for your perspective. My article is about best practices. A company needs to implement all security safeguards. Stratfor did not. Stratfor is still offline on Monday, December 26.</p>
<p>My #4 point is the most important.  I agree. It was inexcusable for Stratfor to have unencrypted confidential client information on the server. </p>
<p>DH</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JRHelgeson</title>
		<link>http://www.davidhenderson.com/2011/12/25/stratfor-hacking-underscores-need-for-fast-communications-response/#comment-33836</link>
		<dc:creator>JRHelgeson</dc:creator>
		<pubDate>Mon, 26 Dec 2011 08:10:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidhenderson.com/?p=10494#comment-33836</guid>
		<description>This entire article is a joke.  I understand that there was an attempt to get something posted quickly, but aside from #4, the whole thing is absurd.

#1 - You cannot mask your IP information, all you can do is mask the domain name ownership, but certainly not the IP.  There appears to be a basic misunderstanding of how DNS works.

#2 - Email was NOT hosted at the same site.  Where did you get your information?  A simple DNS check reveals that strafor.com is hosted at IP 66.219.34.37 - which as you stated appears to have been allocated to Corenap. However, the MX record for stratfor points to mxgw01.stratfor.com, which resolves to 207.71.53.57, which is where the Stratfor mail server resides, right on Time Warner Telecom netblock.  The recommendation to use something secure such as Google made me laugh.

#3 - Stratfor took their own webiste down. This was not a defacement, this was a hack. When you&#039;ve had a breach like this, you take the site down to stop the bleeding. Getting the site back up, such as from a backup would do nothing to help.  They&#039;d be standing up the same exact insecure site that got hacked in the first place.

#4 The only valid comment I could find in this article. Bad form to leave CC# unencrypted. Stratfor could be held liable for all the fraudulent transactions.

#5 The Stratfor server has been owned for several weeks now - Anonymous delayed the release of the hack until Christmas Eve for the express purpose of catching them off guard. So they got caught off guard - on Christmas Day, for crying out loud, very few companies could provide a full response within the first 24 hours given the same circumstances.

Joel Helgeson</description>
		<content:encoded><![CDATA[<p>This entire article is a joke.  I understand that there was an attempt to get something posted quickly, but aside from #4, the whole thing is absurd.</p>
<p>#1 &#8211; You cannot mask your IP information, all you can do is mask the domain name ownership, but certainly not the IP.  There appears to be a basic misunderstanding of how DNS works.</p>
<p>#2 &#8211; Email was NOT hosted at the same site.  Where did you get your information?  A simple DNS check reveals that strafor.com is hosted at IP 66.219.34.37 &#8211; which as you stated appears to have been allocated to Corenap. However, the MX record for stratfor points to mxgw01.stratfor.com, which resolves to 207.71.53.57, which is where the Stratfor mail server resides, right on Time Warner Telecom netblock.  The recommendation to use something secure such as Google made me laugh.</p>
<p>#3 &#8211; Stratfor took their own webiste down. This was not a defacement, this was a hack. When you&#8217;ve had a breach like this, you take the site down to stop the bleeding. Getting the site back up, such as from a backup would do nothing to help.  They&#8217;d be standing up the same exact insecure site that got hacked in the first place.</p>
<p>#4 The only valid comment I could find in this article. Bad form to leave CC# unencrypted. Stratfor could be held liable for all the fraudulent transactions.</p>
<p>#5 The Stratfor server has been owned for several weeks now &#8211; Anonymous delayed the release of the hack until Christmas Eve for the express purpose of catching them off guard. So they got caught off guard &#8211; on Christmas Day, for crying out loud, very few companies could provide a full response within the first 24 hours given the same circumstances.</p>
<p>Joel Helgeson</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DH</title>
		<link>http://www.davidhenderson.com/2011/12/25/stratfor-hacking-underscores-need-for-fast-communications-response/#comment-33825</link>
		<dc:creator>DH</dc:creator>
		<pubDate>Mon, 26 Dec 2011 04:09:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidhenderson.com/?p=10494#comment-33825</guid>
		<description>A private email from Friedman on Christmas Eve suggested the hack occurred then. 

Interesting point about the backup. But they&#039;ve got to get it back soon.</description>
		<content:encoded><![CDATA[<p>A private email from Friedman on Christmas Eve suggested the hack occurred then. </p>
<p>Interesting point about the backup. But they&#8217;ve got to get it back soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DH</title>
		<link>http://www.davidhenderson.com/2011/12/25/stratfor-hacking-underscores-need-for-fast-communications-response/#comment-33824</link>
		<dc:creator>DH</dc:creator>
		<pubDate>Mon, 26 Dec 2011 03:40:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidhenderson.com/?p=10494#comment-33824</guid>
		<description>Jason,

Thank you for your opinion. I know quite a bit about DNS.

There was one email from Friedman on Christmas Eve, not multiple as you suggest incorrectly. And, yes ... organizations that depend on the net get their sites back online as quickly as possible, not 24+ hours later. 

Have you read what The New York Times is reporting? 
http://www.nytimes.com/2011/12/26/technology/hackers-breach-the-web-site-of-stratfor-global-intelligence.html
DH</description>
		<content:encoded><![CDATA[<p>Jason,</p>
<p>Thank you for your opinion. I know quite a bit about DNS.</p>
<p>There was one email from Friedman on Christmas Eve, not multiple as you suggest incorrectly. And, yes &#8230; organizations that depend on the net get their sites back online as quickly as possible, not 24+ hours later. </p>
<p>Have you read what The New York Times is reporting?<br />
<a href="http://www.nytimes.com/2011/12/26/technology/hackers-breach-the-web-site-of-stratfor-global-intelligence.html" rel="nofollow">http://www.nytimes.com/2011/12/26/technology/hackers-breach-the-web-site-of-stratfor-global-intelligence.html</a><br />
DH</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason H</title>
		<link>http://www.davidhenderson.com/2011/12/25/stratfor-hacking-underscores-need-for-fast-communications-response/#comment-33823</link>
		<dc:creator>Jason H</dc:creator>
		<pubDate>Mon, 26 Dec 2011 03:30:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidhenderson.com/?p=10494#comment-33823</guid>
		<description>I am referring to the ridiculousness of the bullet points you posted.  Do you really think the IPs behind domain names can be kept secret?  Do you know anything at all about DNS?

We received private emails from George shortly after they found out about the compromise, not 18 hours later and via facebook as you suggested.

And when your site is cracked, you don&#039;t just restore it from &quot;backup&quot; and continue as usual... you take it offline until the security issues can be addressed.

Your point #4 was valid, but the rest is uninformed and irresponsible.</description>
		<content:encoded><![CDATA[<p>I am referring to the ridiculousness of the bullet points you posted.  Do you really think the IPs behind domain names can be kept secret?  Do you know anything at all about DNS?</p>
<p>We received private emails from George shortly after they found out about the compromise, not 18 hours later and via facebook as you suggested.</p>
<p>And when your site is cracked, you don&#8217;t just restore it from &#8220;backup&#8221; and continue as usual&#8230; you take it offline until the security issues can be addressed.</p>
<p>Your point #4 was valid, but the rest is uninformed and irresponsible.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Content Delivery Network via Amazon Web Services: CloudFront: media.davidhenderson.com

Served from: www.davidhenderson.com @ 2012-05-22 21:32:02 -->
