Where the clause stands (checked November 15, 2026)
| Version | Prohibition clause | Report within | Status |
|---|---|---|---|
| FAR as codified | 52.204-23 (Dec 2023) | 3 business days, then more within 10 business days | In the FAR today (FAC 2026-01) |
| Overhaul class deviations | 52.240-91, Security Prohibitions and Exclusions | 72 hours | In use where an agency adopted the Part 40 text; DoD has |
| Proposed rule, FAR Case 2026-001 | 52.240-3, Security Prohibitions and Exclusions | 72 hours | Proposed June 23, 2026; not final |
The codified clause is prescribed at FAR 4.2004 for all solicitations and contracts. Under the FAR Overhaul, the model Part 40 text moves the prohibition into paragraph (b)(2) of one combined clause, 52.240-91, with the same definitions. DoD's Class Deviation 2026-O0025 tells DoD contracting officers to use that Part 40 text in place of the codified FAR. The proposed rule would make it 52.240-3; we found no final rule. The prohibition itself is the same in all three.
What is covered
The clause implements section 1634 of the National Defense Authorization Act for Fiscal Year 2018, which prohibits government use of any Kaspersky Lab covered article. Two definitions do the work:
- A Kaspersky Lab covered entity is Kaspersky Lab; any successor entity, including under a changed name such as "Kaspersky"; any entity that controls, is controlled by, or is under common control with Kaspersky Lab; and any entity in which Kaspersky Lab has a majority ownership.
- A Kaspersky Lab covered article is any hardware, software or service that is developed or provided by a covered entity, that includes any hardware, software or service developed or provided in whole or in part by one, or that contains components using hardware or software developed in whole or in part by one.
The second definition is the one that catches people: it reaches a product from someone else that has Kaspersky code or components inside it.
What the contractor may not do
- Provide any Kaspersky Lab covered article that the government will use on or after October 1, 2018.
- Use any Kaspersky Lab covered article, on or after October 1, 2018, in the development of data or deliverables first produced in the performance of the contract.
The clause has no dollar threshold, no exception for commercial or COTS items, and no waiver paragraph. It also has no representation for offerors and doesn't define a reasonable inquiry. The Overhaul clause 52.240-91 adds one inquiry standard across all its prohibitions: look at the information in your possession, without needing an internal or third-party audit.
The report
If the contractor identifies a covered article provided to the government during performance, or is told of one by a subcontractor at any tier or any other source, it reports in writing to the contracting officer, or at dibnet.dod.mil for DoD:
- Within 3 business days: the contract number and any order numbers, the supplier name, brand, model number, item description, and any readily available information about mitigation.
- Within 10 business days of that report: further information on mitigation, the efforts made to prevent use or submission of a covered article, the reasons it happened, and what will be done to prevent it again.
Under 52.240-91 this becomes one report within 72 hours. A subcontract template that gives a sub three business days to tell you leaves you nothing if your own clock is 72 hours.
The flow-down
Paragraph (d) has the contractor insert the substance of the clause, including the flow-down paragraph, in all subcontracts, including subcontracts for commercial products and commercial services. Like Section 889, it has no threshold, so it belongs in purchase orders as well as negotiated subcontracts. FAR 52.244-6 lists it among the clauses that go into subcontracts for commercial products and services.
Reporting comes back up: a sub at any tier that tells you it found a covered article starts your clock.
What to collect from each sub
- A signed statement that it will not provide Kaspersky Lab covered articles and will not use them to develop data or deliverables for your work, covering products that contain them
- Confirmation that it flows the clause down to its own subcontracts
- A promise to tell you promptly if it finds one, sized to your own reporting clock
- The date, and a repeat at renewal
Many primes put this in one annual representation with Section 889, the ByteDance prohibition and FASCSA orders, which is how the Overhaul clause groups them.
How Watch helps
You can keep the clauses you flow down as a clause set, have each sub acknowledge the current version through the supplier portal, and use a "Clause set acknowledged" requirement to see who hasn't. Watch has a ready-made Section 889 questionnaire; it has none for this clause, so use your own form for the Kaspersky representation and keep the signed copy on the supplier in Watch.
Watch's daily checks read SAM.gov registrations, SAM.gov exclusions and the Consolidated Screening List. They tell you about the supplier as a company, not about the software it runs or ships, so they can't find a covered article. Reports to the government stay with you.