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
Monster.com | El informe BlinnPR

Archive for the 'Monster.com' Category Archivo para la 'Monster.com' Categoría

Is 5 days fast enough when it comes to Crisis Communications? Es de 5 días con la suficiente rapidez cuando se trata de crisis de Comunicaciones?

Monday, August 27th, 2007 Lunes, 27 de Agosto de 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. Si bien jugar 18 hoyos de golf en el Van Cortlandt Park en el Bronx durante el fin de semana, he leído en Internet que tomó Monster.com unos cinco días para revelar una base de datos donde la violación de información personal de todo un lío de gruñón las personas que buscan empleo, con la esperanza de que al publicar sus hojas de vida en Monster daría lugar a una vida de felicidad y prosperidad, fue robado.

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. No puedo responder a la pregunta acerca de si cinco días era demasiado poco o demasiado, pero yo le puede dar una idea acerca de lo que necesitas saber antes de revelar a los clientes, los medios de comunicación y en la mayoría de los casos su banco y compañías de tarjetas de crédito. 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. Usted necesita saber lo que pasó, qué y cuánto fue robada, que se vio afectado, y lo que vas a hacer para asegurarse de que no vuelva a suceder. 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. Tal vez no con un 100% de certeza lo que pasó o que el autor (s), pero lo suficiente como para saber lo que generalmente se rompió, de modo que usted puede asegurar que los clientes solucionar el problema.

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. Este último término se reduce a un juego de confianza, y me gustaría aconsejar a nadie a tener más información (incluso si se toma unos días extra), entonces menos. Saying “we’re screwed, we just don’t know how big the pole is” doesn’t engender confidence in your customer base. Decir que "estamos jodidos, simplemente no sabemos cuán grande es el polo" no generan confianza en su base de clientes. 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. Si usted no puede obtener esa información después de una cierta cantidad de tiempo, entonces usted necesidad de divulgar de todas formas - pero entiendo que va a ser pummeled ala TJX.

That’s why I harp time and time again about crisis communications. Esa es la razón por la que el arpa una y otra vez sobre la crisis de las comunicaciones. It’s going to happen to you, it’s just not clear when. Va a suceder a usted, es justo cuando no estaba claro.

Bookmark to: Guardar:
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

Monster: Oops, Sorry About That Data Theft Monster: ¡Vaya, lo siento acerca de que el robo de datos

Friday, August 24th, 2007 Viernes, 24 de agosto de 2007

Credit for this entry goes to Henry Blodget at the El mérito de esta entrada va a Henry Blodget en la Silicon Alley Insider Silicon Alley las operaciones con información privilegiada

Five days after Ukrainian hackers busted into a “rogue server” and stole contact info for 1.3 million Monster users, Monster told the users. Cinco días después de hackers busted ucraniano en un "servidor de la picaresca" y robó información de contacto de 1,3 millones de usuarios de Monster, Monster dijo a los usuarios. But it did so in one of the most inscrutable Pero lo hizo en uno de los más inescrutable press releases Notas de prensa ever written. nunca por escrito.

Bookmark to: Guardar:
Add 'Monster: Oops, Sorry About That Data Theft' to Del.icio.us Add 'Monster: Oops, Sorry About That Data Theft' to digg Add 'Monster: Oops, Sorry About That Data Theft' to FURL Add 'Monster: Oops, Sorry About That Data Theft' to blinklist Add 'Monster: Oops, Sorry About That Data Theft' to My-Tuts Add 'Monster: Oops, Sorry About That Data Theft' to reddit Add 'Monster: Oops, Sorry About That Data Theft' to Feed Me Links! Add 'Monster: Oops, Sorry About That Data Theft' to Technorati Add 'Monster: Oops, Sorry About That Data Theft' to Socializer


WP-Highlight WP-Resalta