US House Committee on Science, Space and Technology sets hearing on Kaspersky Lab for Oct. 25
Dustin Volz / Reuters :
Context & Ripple Effects
This hearing is the escalation of a months-long congressional squeeze on Kaspersky Lab. In May, sources reported a secret notice from the Senate Intelligence Committee warning the AG and DNI about the Russian firm's large US market share, and Eugene Kaspersky responded by offering to testify and hand over source code. In July, the House Science Committee itself demanded risk assessments and contractor names dating back to 2013 from 22 US agencies.
Scheduling a public hearing for Oct. 25 moves the inquiry from closed-door document requests to open testimony — the stage where findings get formalized into policy. The trajectory matters because it ends in the DHS ban and Kaspersky's subsequent due-process lawsuit against the Trump administration.
First-order effects
- Kaspersky Lab now faces public congressional scrutiny it cannot manage privately — its May offer of testimony and source code becomes directly relevant as the committee prepares witnesses.
- The 22 agencies that received the July document demands must produce their Kaspersky risk assessments and contractor lists ahead of the hearing, exposing how widely the software is embedded in federal systems.
Second-order effects
- A public record of agency risk assessments gives DHS and other buyers the evidentiary basis to remove Kaspersky products from government networks, converting congressional concern into procurement bans.
- Other Russian-origin security vendors selling into US government and critical-infrastructure markets face the same scrutiny template — document demands, then hearings, then bans — regardless of their own conduct.
Third-order effects
- If the pattern holds, US cybersecurity procurement splits along vendor nationality lines, with congressional committees acting as de facto certification bodies for foreign software.
- Kaspersky's eventual lawsuit frames the structural question: whether foreign firms can be excluded from US markets through informal congressional and agency pressure without formal due process — a precedent that cuts both ways for any multinational vendor.
The trend: Washington's posture toward Russian software firms is shifting from quiet intelligence warnings to public congressional action ending in outright procurement bans.