{"id":4146,"date":"2024-06-21T16:33:19","date_gmt":"2024-06-21T21:33:19","guid":{"rendered":"https:\/\/www.darkreading.com\/cybersecurity-operations\/kaspersky-us-customers-deadline-govt-ban"},"modified":"2024-06-21T16:33:19","modified_gmt":"2024-06-21T21:33:19","slug":"kasperskys-us-customers-face-tight-deadline-following-govt-ban","status":"publish","type":"post","link":"https:\/\/ddi.mohflo.net\/index.php\/2024\/06\/21\/kasperskys-us-customers-face-tight-deadline-following-govt-ban\/","title":{"rendered":"Kaspersky’s US Customers Face Tight Deadline Following Govt. Ban"},"content":{"rendered":"
<\/a><\/div>\n
<\/div>\n

US businesses and consumers using Kaspersky’s antivirus software products and services have until Sept. 29 to stop using them, following a Biden Administration ban earlier this week on sales of the company’s technologies in the country over national security concerns.<\/span><\/p>\n

Companies and individuals that continue to use Kaspersky products past that date will be doing so at their own \u2014 considerable \u2014 risk, because Kaspersky will no longer be able to offer any support or updates for its products after the deadline.<\/span><\/p>\n

“It’s a good time for CISOs along with other C-suite executives and board members to revisit their organizational use of the software and, frankly, to begin preparing for this to be a long-term aspect of government commercial cybersecurity regulation,” says Andrew Borene, executive director at threat intelligence firm Flashpoint. “That means immediately evaluating the scope of any Kaspersky deployment, capturing current requirements, and identifying alternatives for delivering on those requirements once the ban takes full effect at the end of September.”<\/span><\/p>\n

US Concerns About Kaspersky’s Moscow Ties<\/h2>\n

In a first-of-its-kind move, the US Department of Commerce, on June 20 <\/span>formally banned<\/a><\/span> Kaspersky from selling its products and services in the US, citing continued use of the company’s software as presenting an “undue or unacceptable national security risk.”<\/span><\/p>\n

The Commerce Department’s concerns have to do with Kaspersky being a Russian company and therefore apparently being obligated to turn over customer data to the government there, whenever asked for it.<\/span><\/p>\n

“Russia has shown time and again they have the capability and intent to exploit Russian companies, like Kaspersky Lab, to collect and weaponize sensitive US information,” the Commerce department said.<\/span><\/p>\n

The ban marks the first time the Commerce Department has used its authority under a Trump Administration 2019 Executive Order on <\/span>Securing the Information and Communications Technology and Services Supply Chain<\/a><\/span> (ICT).<\/span><\/p>\n

As part of its action, the department also “designated” Kaspersky entities in Russia and the UK, meaning that US organizations and individuals are restricted from transacting business with them. In a related announcement, the US Department of Treasury placed similar restrictions on 12 key executives at Kaspersky, but notably not on the company’s founder Eugene Kaspersky.<\/span><\/p>\n

A Kaspersky spokesman described the Department of Commerce decision as likely motivated by the “current geopolitical climate and theoretical concerns rather than on a comprehensive evaluation of the integrity of Kaspersky’s products and services.” Kaspersky will pursue all available legal options to fight the decision, the spokesman said in an emailed statement. He added, “Kaspersky does not engage in activities which threaten US national security and, in fact, has made significant contributions with its reporting and protection from a variety of threat actors that targeted US interests and allies.”<\/span><\/p>\n

The US government decision does not impact Kaspersky’s ability to continue selling its threat intelligence services or its cybersecurity training programs in the US, the statement noted.<\/span><\/p>\n

Death Knell for Kaspersky in the US?<\/h2>\n

Even so, the US government’s moves this week could effectively mean the end for Kaspersky in the country. In September 2017 the <\/span>US Department of Homeland Security banned Kaspersky<\/a><\/span> from selling to US federal civilian executive branch agencies over <\/span>similar national security concerns<\/a><\/span>. Though the company appealed that decision, the Federal Acquisition Regulation Council made it an official and <\/span>permanent ban <\/a><\/span>in September 2019. With this week’s actions, the US government has formally blocked it from selling to US private sector companies and individuals as well.<\/span><\/p>\n

“The US government has had its eye on Kaspersky for quite a while, so the ban is not particularly surprising,” says Eric Parizo, an analyst with Omdia. The 2019 Executive Order bans the use of IT products and services that are owned or directed by a foreign adversary and pose an unacceptable risk to US national security, he says.<\/span><\/p>\n

This week’s US government action does not explicitly prohibit US individuals and organizations from using Kaspersky products after Sept. 29, 2024. But since the vendor cannot provide software updates for existing customers after that date, continued use of the product would represent a clear security risk, Parizo says. “In light of these events, it would be prudent for Kaspersky customers in the US to immediately seek alternatives.” What heightens the urgency is the fact that Kaspersky’s software products \u2014 like all anti-virus tools \u2014 have a lot of access to sensitive data on systems on which they are installed, he says.<\/span><\/p>\n

Countdown to Kaspersky Sunset<\/h2>\n

Adam Maruyama, field CTO at Garrison Technology, recommends that companies which need to replace Kaspersky software make sure to catalog and identify unmanaged corporate devices that may be running the company’s software. This includes looking at systems belonging to contractors on the corporate network as well as employees using personal devices at work.<\/span><\/p>\n

“In the longer term, companies need to be conscious that a ‘rip and replace’ of antivirus software may not fully remove root-level access points from their systems, as antivirus programs often require root level access that is not easily removed by uninstallers,” Maruyama cautions.<\/span><\/p>\n

Given the concerns that the Commerce Department has raised about data theft and the potential weaponization of Kaspersky software, organizations should closely monitor network security suites and technical behavior of systems where Kaspersky was previously installed, he says.<\/span><\/p>\n

The focus should be on anomalous behavior such as continued callbacks to Kaspersky or other unidentified servers. “For users with the highest levels of access to high-risk data and administrative privileges, organizations with a critical infrastructure mission may even want to consider replacing devices that previously used Kaspersky antivirus products to guard against residual risk,” he says.<\/span><\/p>\n

Source<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

US businesses and consumers using Kaspersky’s antivirus software products and<\/p>\n","protected":false},"author":12,"featured_media":4147,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[809],"class_list":["post-4146","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-dark-reading"],"featured_image_urls":{"full":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/06\/kasperskys-us-customers-face-tight-deadline-following-govt-ban.jpg?fit=1800%2C1013&ssl=1",1800,1013,false],"thumbnail":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/06\/kasperskys-us-customers-face-tight-deadline-following-govt-ban.jpg?resize=150%2C150&ssl=1",150,150,true],"medium":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/06\/kasperskys-us-customers-face-tight-deadline-following-govt-ban.jpg?fit=300%2C169&ssl=1",300,169,true],"medium_large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/06\/kasperskys-us-customers-face-tight-deadline-following-govt-ban.jpg?fit=640%2C360&ssl=1",640,360,true],"large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/06\/kasperskys-us-customers-face-tight-deadline-following-govt-ban.jpg?fit=640%2C360&ssl=1",640,360,true],"1536x1536":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/06\/kasperskys-us-customers-face-tight-deadline-following-govt-ban.jpg?fit=1536%2C864&ssl=1",1536,864,true],"2048x2048":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/06\/kasperskys-us-customers-face-tight-deadline-following-govt-ban.jpg?fit=1800%2C1013&ssl=1",1800,1013,true],"chromenews-featured":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/06\/kasperskys-us-customers-face-tight-deadline-following-govt-ban.jpg?fit=1024%2C576&ssl=1",1024,576,true],"chromenews-large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/06\/kasperskys-us-customers-face-tight-deadline-following-govt-ban.jpg?resize=825%2C575&ssl=1",825,575,true],"chromenews-medium":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/06\/kasperskys-us-customers-face-tight-deadline-following-govt-ban.jpg?resize=590%2C410&ssl=1",590,410,true]},"author_info":{"display_name":"Dark Reading","author_link":"https:\/\/ddi.mohflo.net\/index.php\/author\/darkreading\/"},"category_info":"Uncategorized<\/a>","tag_info":"Uncategorized","comment_count":"0","jetpack_featured_media_url":"https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/06\/kasperskys-us-customers-face-tight-deadline-following-govt-ban.jpg?fit=1800%2C1013&ssl=1","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/4146","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/comments?post=4146"}],"version-history":[{"count":0,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/4146\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media\/4147"}],"wp:attachment":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media?parent=4146"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/categories?post=4146"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/tags?post=4146"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}