Security

CSO

Uncle Sam sanctions Kaspersky's top bosses – but not Mr K himself

Here's America's list of the supposedly dirty dozen


Uncle Sam took another swing at Kaspersky Lab today and sanctioned a dozen C-suite and senior-level executives at the antivirus maker, but spared CEO and co-founder Eugene Kaspersky.

The move prevents US persons and organizations from doing business with the designated individuals. Any non-US financial institution that works with them also risks sanctions under Executive Order 13873.

The US Treasury Department's Office of Foreign Assets Control (OFAC) cited national security threats in designating the 12 individuals as under sanction. In making the announcement, it also noted: "OFAC has not designated Kaspersky Lab, its parent or subsidiary companies, or its CEO."

The Treasury did, however, designate just about every other exec who reports directly to the Moscow-based firm's chief exec "for operating in the technology sector of the Russian Federation economy," which under EO 14024 is a no-no.

It follows Thursday's actions by the Commerce Department that prohibit Kaspersky Lab Inc from providing its software and other security services in America from July 20 — plus years of directives and mandates to kick Kaspersky products out of US government networks.

Kaspersky Lab's operations in Russia and the UK were also on Thursday placed on the US government's Entity List, making it difficult to impossible for US persons and organizations to do business with them. In short, there is a mix of action against Kaspersky, from a ban on sales in the United States to sanctions against its execs in Russia.

In issuing these sanctions and product bans, the Biden White House and previous administrations have argued that the Russia-based antivirus developer could be forced or ordered by Putin to backdoor its products and hand over American individuals and organizations' sensitive information from their PCs to Kremlin intelligence.

The Treasury sanctions followed a similar narrative.

"Today's action against the leadership of Kaspersky Lab underscores our commitment to ensure the integrity of our cyber domain and to protect our citizens against malicious cyber threats," said Under Secretary of the Treasury for Terrorism and Financial Intelligence Brian E. Nelson in a statement.

The 12 individuals named by the US government are: 

Kaspersky Lab declined to comment on the matter. ®

Send us news
17 Comments

Ransomware scum blow holes in Cleo software patches, Cl0p (sort of) claims responsibility

But can you really take crims at their word?

BlackBerry offloads Cylance's endpoint security products to Arctic Wolf

Fresh attempt to mix the perfect cocktail of IoT and Infosec

US reportedly mulls TP-Link router ban over national security risk

It could end up like Huawei -Trump's gonna get ya, get ya, get ya

Microsoft won't let customers opt out of passkey push

Enrollment invitations will continue until security improves

How Androxgh0st rose from Mozi's ashes to become 'most prevalent malware'

Botnet's operators 'driven by similar interests as that of the Chinese state'

Australia moves to drop some cryptography by 2030 – before quantum carves it up

The likes of SHA-256, RSA, ECDSA and ECDH won't be welcome in just five years

Deloitte says cyberattack on Rhode Island benefits portal carries 'major security threat'

Personal and financial data probably stolen

Critical security hole in Apache Struts under exploit

You applied the patch that could stop possible RCE attacks last week, right?

Suspected LockBit dev, facing US extradition, 'did it for the money'

Dual Russian-Israeli national arrested in August

Don't fall for a mail asking for rapid Docusign action – it may be an Azure account hijack phish

Recent campaign targeted 20,000 folk across UK and Europe with this tactic, Unit 42 warns

Boffins trick AI model into giving up its secrets

All it took to make an Google Edge TPU give up model hyperparameters was specific hardware, a novel attack technique … and several days

Phishers cast wide net with spoofed Google Calendar invites

Not that you needed another reason to enable the 'known senders' setting