{"id":16645,"date":"2019-09-12T18:25:37","date_gmt":"2019-09-12T12:55:37","guid":{"rendered":"https:\/\/www.kaspersky.co.in\/blog\/incident-communications\/16645\/"},"modified":"2019-11-22T15:27:11","modified_gmt":"2019-11-22T09:57:11","slug":"incident-communications","status":"publish","type":"post","link":"https:\/\/www.kaspersky.co.in\/blog\/incident-communications\/16645\/","title":{"rendered":"Kaspersky Incident Communications"},"content":{"rendered":"<p>I remember that day like it was yesterday: Our CEO called me into his office, asking me to leave my smartphone and laptop at my desk.<\/p>\n<p>\u201cWe\u2019ve been hacked,\u201d he said bluntly. \u201cThe investigation is still ongoing, but we can confirm that we have an active, extremely sophisticated, nation-state sponsored attacker inside our perimeter.\u201d<\/p>\n<p><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/36\/2019\/09\/12182555\/Kaspersky-speaking.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-16646\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/36\/2019\/09\/12182555\/Kaspersky-speaking.jpg\" alt=\"\" width=\"3000\" height=\"2003\"><\/a><\/p>\n<p>To be honest, this wasn\u2019t totally unexpected. Our specialists had been dealing with our clients\u2019 security breaches for quite a while already, and as a security company, we were a particular target. Yet, it was an unpleasant surprise: Someone had penetrated an information security company\u2019s cyberdefenses. You can read about it <a href=\"https:\/\/www.kaspersky.com\/blog\/kaspersky-statement-duqu-attack\/8997\/\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">here<\/a>. Today, I want to talk about one of the key questions that arose immediately: \u201cHow do we communicate about it?\u201d<\/p>\n<h2><strong>Five stages of learning to live with it: Denial, anger, bargaining, depression, and acceptance<\/strong><\/h2>\n<p>As it happened, pre-GDPR, every organization actually had a choice \u2014 whether to communicate publicly or deny an incident had even occurred. The latter wasn\u2019t an option for Kaspersky, a transparent cybersecurity company that promotes responsible disclosure. We had consensus throughout the C-suite and started preparing for the public announcement. Full steam ahead.<\/p>\n<p>It was the right thing to do, too, particularly as we watched the widening geopolitical rift and saw clearly that the mighty powers behind the cyberattack would definitely use the breach against us \u2014 the only unknown elements were <em>how<\/em> and <em>when<\/em>. By proactively communicating the breach, we not only deprived them of this opportunity, but we also used the case in our favor.<\/p>\n<p>They say there are two types of organizations \u2014 those that have been hacked and those that don\u2019t even know they were hacked. In this realm, the paradigm is simple: A company shouldn\u2019t hide a breach. The only shame is in keeping a breach from the public and thus threatening customers\u2019 and partners\u2019 cybersecurity.<\/p>\n<p>Back to our case. Once we established the involved parties \u2014 legal and information security teams versus communications, sales, marketing, and technical support \u2014 we began the tedious work of preparing the official messaging and Q&amp;A. We did that simultaneously with the ongoing <a href=\"https:\/\/securelist.com\/the-mystery-of-duqu-2-0-a-sophisticated-cyberespionage-actor-returns\/70504\/\" target=\"_blank\" rel=\"noopener noreferrer\">investigation by Kaspersky\u2019s GReAT<\/a> (Global Research and Analysis Team) experts; involved team members conducted all communications over encrypted channels to exclude the possibility of compromising the investigation. Only when we had most of the A\u2019s covered in the Q&amp;A doc did we feel ready to come out.<\/p>\n<p>As a result, various media outlets published almost 2,000 pieces based on a news break we initiated ourselves. Most (95%) were neutral, and we saw a remarkably small amount of negative coverage (less than 3%). \u00a0The balance of coverage is understandable; the media had learned the story from us, our partners, and other security researchers all working with the right information. I don\u2019t have the exact stats, but from the way the media reacted to the story of a <a href=\"https:\/\/www.kaspersky.com\/blog\/hydro-attacked-by-ransomware\/26028\/\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">ransomware attack<\/a> against Norwegian aluminum giant Hydro earlier this year, it seems the handling of those news stories was suboptimal. The moral of the story is, never keep skeletons in the closet.<\/p>\n<h2><strong>Lesson learned \u2014 and passed on<\/strong><\/h2>\n<p>The good news is that we\u2019ve learned from the 2015 cyberattack not only about the technical capabilities of the most advanced cyberthreat actors, but also how to react to and communicate about the breach.<\/p>\n<p>We had time to investigate the attack thoroughly and learn from it. We had time to pass through the anger and bargaining stages \u2014 I mean, to prepare the company for what we were going to say to the public. And the entire time, communication between the cybersecurity folks and corporate communication experts was ongoing.<\/p>\n<p>Today, the time frame for getting ready for a public announcement has shortened dramatically: For example, GDPR requires that companies operating with customer data not only inform authorities about security breaches, but do so within 72 hours. And a company under cyberattack has to be prepared to go public from the very moment they inform the authorities about it.<\/p>\n<p>\u201cWhom should we communicate with inside the company? What channels can we use, and which should we avoid? How should we act?\u201d These and many others are questions we\u2019ve had to answer during the ongoing investigation. You may not have the luxury to work out these questions by yourself in the short time you have at your disposal. But this information and our valuable experience form the foundation of the <a href=\"https:\/\/www.kaspersky.com\/advert\/enterprise-security\/cyber-incident-response-communication?redef=1&amp;THRU&amp;reseller=gl_inccom_acq_ona_smm__onl_b2b__wpplaceholder_______\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">Kaspersky Incident Communications Service<\/a>.<\/p>\n<p>In addition to standard training by certified communication specialists covering strategy and advising on external messaging, the service provides opportunities to learn from our <a href=\"https:\/\/great.kaspersky.com\/\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">GReAT<\/a> experts. They have up-to-date information about communication tools and protocols, and they can advise you on how to behave in a breach situation.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In case of a cybersecurity incident, whom should you communicate with inside the company? Which channels should you use \u2014 and which ones should you avoid? And how should you react?<\/p>\n","protected":false},"author":188,"featured_media":16648,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[2036,2610],"tags":[870,2828],"class_list":{"0":"post-16645","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-business","8":"category-smb","9":"tag-breach","10":"tag-incident"},"hreflang":[{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/incident-communications\/16645\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/incident-communications\/14038\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/incident-communications\/18613\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/incident-communications\/16685\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/incident-communications\/15418\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/incident-communications\/19320\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/incident-communications\/18004\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/incident-communications\/28649\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/incident-communications\/12319\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/incident-communications\/12364\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/incident-communications\/20232\/"},{"hreflang":"nl","url":"https:\/\/www.kaspersky.nl\/blog\/incident-communications\/24255\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/incident-communications\/23367\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/incident-communications\/23279\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.co.in\/blog\/tag\/breach\/","name":"breach"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/16645","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/users\/188"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/comments?post=16645"}],"version-history":[{"count":3,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/16645\/revisions"}],"predecessor-version":[{"id":17018,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/16645\/revisions\/17018"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/media\/16648"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/media?parent=16645"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/categories?post=16645"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/tags?post=16645"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}