{"id":23315,"date":"2018-07-31T06:00:54","date_gmt":"2018-07-31T10:00:54","guid":{"rendered":"https:\/\/www.kaspersky.com\/blog\/?p=23315"},"modified":"2019-11-15T06:34:54","modified_gmt":"2019-11-15T11:34:54","slug":"kaspersky-lab-appeal","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com\/blog\/kaspersky-lab-appeal\/23315\/","title":{"rendered":"Why we fight and will keep on fighting"},"content":{"rendered":"<p>Two months ago, a U.S. District Court dismissed our challenge to the Department of Homeland Security (DHS) Directive and the provisions in the FY18 National Defense Authorization Act that ban the use of our products by federal agencies. As you\u2019d expect, we\u2019re appealing the court\u2019s dismissal.<\/p>\n<p>Now, you might wonder why we\u2019re doing that. Why do we keep getting up after every punch when we could just move on and save ourselves a great deal of time, money, and frustration?<\/p>\n<p>Well, the answer\u2019s twofold \u2014 and very close to my heart.<\/p>\n<p>First, we believe it\u2019s the right thing to do. Kaspersky Lab has never, and will never, help anyone in the world with their offensive security efforts. Put simply, we protect our customers with the very <a target=\"_blank\" href=\"https:\/\/www.kaspersky.com\/blog\/kaspersky-top3-2017\/21208\/\" rel=\"noopener noreferrer nofollow\">best<\/a> cybersecurity solutions and services in the world. Allegations \u2014 without <em>any<\/em> supporting evidence of <em>any<\/em> wrongdoing \u2014 have harmed our reputation and negatively affected our commercial interests and those of our business partners. And because we feel that these actions have violated our constitutional rights and protections, we absolutely must challenge them in court.<\/p>\n<p>Second, we\u2019re doing it to protect our own industry: This situation sets a dangerous precedent. One of the concerns about us relates to our Russian origins. Labeling a company as a national security risk just because of its country of origin does little to address real cybersecurity risks. Think about it: IT supply chains are global by nature, and governments around the world recognize that cyberthreats can originate from anywhere and that threat actors don\u2019t limit their activities to certain countries or companies. Former National Security Advisor Michael Hayden recently <a target=\"_blank\" href=\"https:\/\/www.cyberscoop.com\/kaspersky-switzerland-bill-evanina\/\" rel=\"noopener noreferrer nofollow\">said<\/a> that he \u201chope[s] to God [the U.S. intelligence services] have a case rather than just a concern\u201d regarding KL; otherwise, they would \u201clegitimate people all over the world to possibly reject American technology simply because it\u2019s American.\u201d But not one real case has been presented. And that is why we\u2019re forced to act as we have, with legal action. Today it\u2019s KL at the top of the list of companies causing \u201cconcern,\u201d but you can be sure other companies will be there in the future.<\/p>\n<p>The cybersecurity industry may become balkanized: slowly fragmented into insulated areas through company-specific or geography-specific bans and restrictions. Of course, countries facing advanced cyberadversaries are fearful of what they might expect next. And there\u2019s a natural inclination for those legitimate concerns to result in protectionist barriers. We fully support the need to better protect governments, businesses, and consumers against increasingly sophisticated cyberthreats. But we must ask ourselves if the solutions being implemented to address these valid concerns actually result in stronger cybersecurity.<\/p>\n<p>We\u2019d like to suggest an alternative to country- or company-specific prohibitions on technology: Stick all those bans and restrictions in the trash and develop a cybersecurity risk management and <a target=\"_blank\" href=\"https:\/\/encyclopedia.kaspersky.com\/knowledge\/strategies-for-mitigating-advanced-persistent-threats-apts\/?utm_source=kdaily&amp;utm_medium=blog&amp;utm_campaign=termin-explanation\" rel=\"noopener noreferrer\">mitigation strategy<\/a> that relies on independent testing and validation processes. Create a framework that assesses the integrity of security products throughout their lifecycle \u2014 regardless of their origin. (I repeat: regardless of their origin!) And focus on criteria that produce evidence-based results so we can continue meaningful dialogue about cyberthreats.<\/p>\n<p>We applaud those that share this vision of working together to promote transparency and accountability. This is how we promote security \u2014 not fear, uncertainty, and doubt.<\/p>\n<p>Just to recap: We\u2019ve done nothing wrong, no evidence has ever been presented against us (and it won\u2019t \u2014 there isn\u2019t any), and so we\u2019re forced to take legal action.<\/p>\n<p>But back to our core business: We know the value of worldwide cybersecurity collaboration. That\u2019s because we\u2019re one of a select handful (about 10) of leading security vendors. And it\u2019s only these 10 that have the global reach to conduct the extensive threat research needed to monitor and protect the global landscape. But each of us still sees just part of the picture. We need to be able to continue to share and collaborate. Balkanization in IT security would break these valuable connections among researchers around the world, not just by keeping them from talking to each other, but also by making them afraid to do so.<\/p>\n<p>We know that our ongoing litigation is adversarial and looks like a fight with the world\u2019s largest and most powerful government. However, we have publicly asked for meetings with concerned government stakeholders to answer their questions, and have repeatedly offered to work with them to address any perceived risks that they\u2019ve identified. So far, the phone\u2019s been pretty quiet. Nevertheless, our offer of cooperation, collaboration, and real dialogue stands.<\/p>\n<p>So we fight \u2014 and will go on fighting: for our business, colleagues, partners, and customers, and for the global cybersecurity industry that we love and believe in. We\u2019re here forever to save the world.<\/p>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"kis-top3\">\n","protected":false},"excerpt":{"rendered":"<p>As Kaspersky Lab\u2019s legal challenge continues, Eugene Kaspersky considers why cybersecurity companies must fight for the industry to stay open and collaborative<\/p>\n","protected":false},"author":13,"featured_media":20445,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[5,2684],"tags":[2791,72,352,2691],"class_list":{"0":"post-23315","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-news","8":"category-special-projects","9":"tag-dhs","10":"tag-eugene-kaspersky","11":"tag-kaspersky-lab","12":"tag-north-america"},"hreflang":[{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/kaspersky-lab-appeal\/23315\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/kaspersky-lab-appeal\/13764\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/kaspersky-lab-appeal\/11519\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/kaspersky-lab-appeal\/15818\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/kaspersky-lab-appeal\/14100\/"},{"hreflang":"pl","url":"https:\/\/plblog.kaspersky.com\/kaspersky-lab-appeal\/9541\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/kaspersky-lab-appeal\/20681\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/kaspersky-lab-appeal\/20679\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com\/blog\/tag\/kaspersky-lab\/","name":"Kaspersky Lab"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/23315","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=23315"}],"version-history":[{"count":2,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/23315\/revisions"}],"predecessor-version":[{"id":29672,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/23315\/revisions\/29672"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/20445"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=23315"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=23315"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=23315"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}