Deprecated: Assigning the return value of new by reference is deprecated in /home/blinnpr2/public_html/blog/wp-settings.php on line 512

Deprecated: Assigning the return value of new by reference is deprecated in /home/blinnpr2/public_html/blog/wp-settings.php on line 527

Deprecated: Assigning the return value of new by reference is deprecated in /home/blinnpr2/public_html/blog/wp-settings.php on line 534

Deprecated: Assigning the return value of new by reference is deprecated in /home/blinnpr2/public_html/blog/wp-settings.php on line 570

Deprecated: Assigning the return value of new by reference is deprecated in /home/blinnpr2/public_html/blog/wp-includes/cache.php on line 103

Deprecated: Assigning the return value of new by reference is deprecated in /home/blinnpr2/public_html/blog/wp-includes/query.php on line 61

Deprecated: Assigning the return value of new by reference is deprecated in /home/blinnpr2/public_html/blog/wp-includes/theme.php on line 1109

Warning: Parameter 1 to photopress_actions::pp_add_query_var() expected to be a reference, value given in /home/blinnpr2/public_html/blog/wp-includes/plugin.php on line 166

Deprecated: Function eregi() is deprecated in /home/blinnpr2/public_html/blog/wp-content/plugins/statpress-reloaded/statpress.php on line 1719

Deprecated: Function eregi() is deprecated in /home/blinnpr2/public_html/blog/wp-content/plugins/statpress-reloaded/statpress.php on line 1723

Deprecated: Function eregi() is deprecated in /home/blinnpr2/public_html/blog/wp-content/plugins/statpress-reloaded/statpress.php on line 1727

Deprecated: Function eregi() is deprecated in /home/blinnpr2/public_html/blog/wp-content/plugins/statpress-reloaded/statpress.php on line 1731

Deprecated: Function ereg() is deprecated in /home/blinnpr2/public_html/blog/wp-content/plugins/statpress-reloaded/statpress.php on line 1427

Deprecated: Function eregi_replace() is deprecated in /home/blinnpr2/public_html/blog/wp-content/plugins/translator/translator.php(15) : eval()'d code on line 988
數據突破口 | BlinnPR報告

檔案為『數據突破口』類別

噢男孩,數據丟失能危害公司的品牌…

星期三, 2007年9月5日

星期,在勞動節總是一個緩慢的新聞週期,但事之前一定真正地爬行在特別慢的速度為 InformationWeek 刊登這個故事…

故事的要義是 消費者的百分之八十七說他們根據400個消費者InfoSurv的調查丟失了對企業的尊敬,在那些公司失去了顧客』個人信息之後。 Tablus,為保護的軟件提供系統的公司,支持勘測和宣佈結果的星期二。 根據Tablus,應答者』評論表明個人信息損失合計事務損失,因為消費者相信企業在維護的信任和他們的信息的機密應該安置特別優先權。 實際上, 96%應答者認為那保護的顧客從數據突破口應該是公司的重要性。 應答者的百分之九十五說那裡是沒有說的借口為暴露顧客』機要信息和93%企業被強制保護敏感內容。 應答者的百分之九十四說是否有技術防止機要和個人信息損失,所有企業應該使用它。

為什麼不是這新聞? 首先,因為它是老新聞。 一次簡單的Google查尋將顯示此。 並且公司例如 Forrester研究, Gartner 并且 Protegrity (充分的透露, Protegrity是BlinnPR客戶)現在談論這個主題幾個月。 實際上, Forrester和Protegrity實際上計算了以真正的美元共計數據突破口可能花費公司。 并且最後,緊密跟隨安全和數據突破口的任何人知道作為公開討論一部分,在RSA 2006年和2007年這個題目被提出了。 我怎麼知道? 是,我是在RSA,但我也是專題討論參加者兩歲月。

這不是關於打擊 InformationWeek 或是什麼的最後裁決者他們應該或不應該報告。 我將留下那由是傳奇在他們自己的頭腦裡的人決定。

不,我的點是這。 我們已經知道數據突破口對公司的品牌是有害的。 什麼應該真正地牽涉我們到做數據突破口零件公司的危機通信計劃。 我可以告訴您從第一手知識數據突破口不是,并且他們應該是。

書簽:
增加『Oh男孩,數據丟失能危害公司的品牌…』 對Del.icio.us Add 'Oh boy, data loses can harm a company’s brand…' to digg Add 'Oh boy, data loses can harm a company’s brand…' to FURL Add 'Oh boy, data loses can harm a company’s brand…' to blinklist Add 'Oh boy, data loses can harm a company’s brand…' to My-Tuts Add 'Oh boy, data loses can harm a company’s brand…' to reddit Add 'Oh boy, data loses can harm a company’s brand…' to Feed Me Links! Add 'Oh boy, data loses can harm a company’s brand…' to Technorati Add 'Oh boy, data loses can harm a company’s brand…' to Socializer

Is 5 days fast enough when it comes to Crisis Communications?

Monday, August 27th, 2007

While playing 18 holes of golf at Van Cortlandt Park in the Bronx over the weekend, I read online that it took Monster.com about five days to disclose a data breach where the personal information of a whole mess of grumpy job seekers, hoping that posting their resumes on Monster would result in a life of happiness and prosperity, got stolen.

I can’t answer the question about whether five days was too little or too much, but I can give you an idea about what you need to know before you disclose to customers, the media and in most cases your bank and credit card companies. You need to know what happened, what and how much was stolen, who was affected, and what you are going to do to make sure it doesn’t happen again. Maybe not with 100% certainty what happened or who the perpetrator(s) were, but enough to know generally what broke, so that you can assure customers you will fix it.

This ultimately comes down to a trust game, and I’d advise anyone to have more information (even if it takes a few days extra), then less. Saying “we’re screwed, we just don’t know how big the pole is” doesn’t engender confidence in your customer base. If you can’t get that information after a certain amount of time, then you need to disclose anyway - but understand you’re going to be pummeled ala TJX.

That’s why I harp time and time again about crisis communications. It’s going to happen to you, it’s just not clear when.

Bookmark to:
Add 'Is 5 days fast enough when it comes to Crisis Communications?' to Del.icio.us Add 'Is 5 days fast enough when it comes to Crisis Communications?' to digg Add 'Is 5 days fast enough when it comes to Crisis Communications?' to FURL Add 'Is 5 days fast enough when it comes to Crisis Communications?' to blinklist Add 'Is 5 days fast enough when it comes to Crisis Communications?' to My-Tuts Add 'Is 5 days fast enough when it comes to Crisis Communications?' to reddit Add 'Is 5 days fast enough when it comes to Crisis Communications?' to Feed Me Links! Add 'Is 5 days fast enough when it comes to Crisis Communications?' to Technorati Add 'Is 5 days fast enough when it comes to Crisis Communications?' to Socializer


WP-Highlight