Sources: Senate Intel Committee sent a secret notice to US AG and DNI warning of potential risks of Kaspersky software, given Russian firm's huge market share
Mike Levine / ABC News :
Context & Ripple Effects
The Senate Intelligence Committee's secret notice to the Attorney General and Director of National Intelligence is the opening move in what became a two-front pressure campaign against Kaspersky Lab. Within weeks, Eugene Kaspersky offered to testify in the US and hand over source code in a direct response to those concerns, while the House Armed Services side escalated with its own document demands.
The pattern then went international and institutional: a leaked UK memo warned departments off Kaspersky for anything touching national security, and years later the White House was still split over sanctions because enforcement is complicated by the company's large installed base — exactly the market-share problem the Senate flagged in this notice.
First-order effects
- The AG and DNI are now formally on record internally as holding the risk assessment, putting them under pressure to act on or justify continued federal tolerance of widely deployed Russian antivirus software.
- Kaspersky's large US market share stops being a commercial asset and becomes the core argument against it — scale itself is cited as the risk vector.
Second-order effects
- Congressional committees pile on: the House soon demands five years of risk assessments and contractor names from 22 US agencies, turning an intelligence warning into a compliance burden across the federal customer base.
- Allied governments calibrate off the same concern, with the UK restricting Kaspersky in national-security-related departments, shrinking the company's government business beyond the US.
Third-order effects
- If the pattern holds, advisories harden into bans: the trajectory runs from secret notices to sales prohibitions, forced customer migration to US-owned replacements like Pango's UltraAV, and staff layoffs as Kaspersky winds down American operations.
- Security software procurement structurally splits along geopolitical lines, with vendors' country of origin treated as a first-order risk factor alongside product quality — a template other nations apply to their own critical infrastructure.
The trend: Western governments are converting quiet intelligence warnings about Russian-origin security software into formal bans and forced market exits, making vendor nationality a procurement criterion.