DHS: A 'vast majority' of agencies on track with Kaspersky directive

Shutterstock image: looking for code. 

A Department of Homeland Security official said that the "vast majority" of federal agencies have met the first of three deadlines imposed by a September directive to eliminate Kaspersky Lab products from federal systems.

Michael Duffy, branch chief for the DHS Office of Cybersecurity and Communications, said that fewer than half of agencies who met the Oct. 13 deadline in the directive reported the presence of Kaspersky Lab software or products.

The Russia-based vendor has been in the hot seat with the U.S. government for months because of allegations of ties to Russian intelligence and specific accusations, denied by Kaspersky, that the company captured classified malware from an intelligence contractor's home computer and shared it with Russian officials.

Speaking to reporters after an Oct. 27 meeting of the National Institute of Standards and Technology's Information Security and Privacy Advisory Board, Duffy declined to provide hard numbers or estimates around overall agency compliance and told the board that it was a "safe assumption" DHS will not be publicly releasing or discussing individual responses.

The directive set a 90-day clock for agencies to begin the process of removing Kaspersky software, but that task is complex. Many other software programs communicate with antivirus software through the application programming interface. Kaspersky's own website boasts about its software's ability to integrate into operating systems and hardware.

Duffy said it was "too soon to tell" how long it will take to finish the job.

Even after agencies remove the products, some residual traces of Kaspersky software and data may remain. James Norton, formerly a senior DHS official during the George W. Bush administration, told FCW that it is notoriously tricky to completely flush all aspects of a software program once it has been installed.

"Probably the best example is anybody who has a home computer and has tried to remove some kind of app they didn't want anymore," Norton said. "It's still in there in some form. It's difficult to clean that up."

The department has publicly released the full text of its last two Binding Operational Directives, a departure from past practice. Duffy said this was done to align with a May 2017 cybersecurity executive order calling for greater coordination between cyber and non-cyber officials and to set clear expectations around what DHS was seeking from agencies as well as other stakeholders in the contracting community. DHS is working with agency chief procurement officers to make sure they are ready for what comes next, Duffy said.

"A big piece of that was knowing that of course in directing removal [of Kaspersky Lab products], we can make the assumption that replacement may be down the line and agencies should start thinking about that," Duffy said.

There's no hard and fast rule about whether contractor systems are subject to the same requirement. Duffy said DHS is content to let individual departments and agencies hash out whether to require a ban affecting contractor devices and networks.

"What we've tried to do is have agencies determine the risk for themselves versus us driving that action," Duffy said.

About the Author

Derek B. Johnson is a former senior staff writer at FCW.


  • FCW Perspectives
    remote workers (elenabsl/

    Post-pandemic IT leadership

    The rush to maximum telework did more than showcase the importance of IT -- it also forced them to rethink their own operations.

  • Management
    shutterstock image By enzozo; photo ID: 319763930

    Where does the TMF Board go from here?

    With a $1 billion cash infusion, relaxed repayment guidelines and a surge in proposals from federal agencies, questions have been raised about whether the board overseeing the Technology Modernization Fund has been scaled to cope with its newfound popularity.

Stay Connected