Checklist: counterparty due diligence for vendors and data brokerage under the DOJ Data Security Program
Ten steps under 28 CFR part 202 for checking who is on the other side of a data deal: the knowingly standard, covered-person screening, looking through vendors to their staff, refusing and reporting prohibited brokerage, the onward-transfer clause, CISA’s vendor-agreement requirement, and the diligence records the rule requires.
What this checklist covers, and what it does not
The Justice Department’s Data Security Program, 28 CFR part 202, went into effect on April 8, 2025 under Executive Order 14117 [3]. It prohibits some transactions that give a country of concern or a covered person access to government-related data or bulk U.S. sensitive personal data, and allows vendor, employment and investment agreements with them only under security requirements issued by CISA [1] [2]. This checklist covers one slice: the diligence a U.S. person does on vendors and data-brokerage counterparties. The wider duties, from mapping covered data and the bulk thresholds to CISA’s controls, the full data compliance program, audits and annual reports, are in our checklist for covered data and restricted transactions. It is labeled carefully because the rule uses “due diligence” in a narrow sense. Section 202.1001, headed due diligence for restricted transactions, applies only to U.S. persons engaging in restricted transactions [1]. The other steps rest on the prohibitions and on the rule’s knowingly standard; the rule does not prescribe a general vendor-screening procedure, and where a step goes beyond its text it says it is our suggestion.
The rule text dates the data compliance program, the audit and the reports from October 6, 2025 [1]; the Department’s program page gives October 5, 2025 for the same requirements [3]. The steps use the rule’s date.
Reading the steps
Each step cites the section of part 202, from the current eCFR text checked on November 14, 2026, or the part of CISA’s Security Requirements for Restricted Transactions (January 2025) it rests on [1] [2]. The owner under each step is a typical role, not one the rule names, unless the step says the rule names it. This checklist explains the rule; it is not legal advice, and counsel should confirm how it applies to a given deal.
Moraph’s teams help organizations with work like this. See our solutions.
The checklist
Tick the steps as you go. The ticks are kept in this browser only; nothing is sent to us.
General counsel with the Chief Compliance Officer
The prohibitions and restrictions apply to transactions a U.S. person engages in knowingly. Section 202.230 defines knowingly as actual knowledge or what the person reasonably should have known [1]. A written diligence standard per counterparty type is our suggestion for showing what the organization reasonably could know.
Privacy lead with procurement
Section 202.214 defines data brokerage as selling or licensing access to data where the recipient did not collect it directly from the individuals; section 202.258 defines a vendor agreement as any arrangement to provide goods or services, including cloud computing, for payment. The class decides whether a deal is prohibited (section 202.301) or restricted (section 202.401) [1].
Third-party risk management
Section 202.211(a) sets the covered-person tests, built on the countries of concern listed in section 202.601, and adds any person the Attorney General designates. Under section 202.701, a designation takes effect from the Department’s public announcement, publication in the Federal Register gives constructive knowledge, and the list is not exhaustive of all covered persons [1]. Rescreening on a schedule is our suggestion.
Procurement with the CISO
The examples in section 202.230(b) turn on these facts: where a U.S. service provider primarily controls a customer’s bulk data and employs a covered person with access, the provider’s employment agreement is a restricted transaction, and access by covered-person IT staff to encrypted bulk human genomic data is treated as prohibited. Section 202.305 separately bars knowingly directing such a transaction. Where a vendor that is not a covered person employs a covered person and grants access without the U.S. person’s knowledge or direction, and nothing points to evasion, neither the vendor agreement nor the employment agreement is a restricted transaction (section 202.401(c), Example 3) [1]. The vendor questionnaire itself is our suggestion.
Chief Compliance Officer with the business owner of the data product
Section 202.301 prohibits a U.S. person from knowingly engaging in a covered data transaction involving data brokerage with a country of concern or covered person, unless authorized under subparts E or H (exemptions and licenses). Section 202.1104 requires the report from U.S. persons that, on or after October 6, 2025, receive and affirmatively reject such an offer, including by software or other automated tools, and lists its contents, including the ownership, citizenship or primary residence of the parties [1].
Legal with the business owner
Section 202.302(a) requires a contractual bar on the foreign person engaging in a later covered data-brokerage transaction of the same data with a country of concern or covered person. Section 202.302(b) requires a report within 14 days of becoming aware of a known or suspected violation, with the listed contents [1]. How to monitor the counterparty is our suggestion.
CISO
Section 202.401 makes such an agreement a restricted transaction that requires compliance with the security requirements incorporated by section 202.248 [1]. CISA’s organizational-level requirements include documenting and maintaining all vendor and supplier agreements for covered systems, including contractual IT and cybersecurity requirements (Section I.A.4), and its data-level requirements must together fully and effectively prevent covered persons and countries of concern from accessing covered data that is linkable, identifiable, unencrypted or decryptable (Section II) [2].
Chief Compliance Officer
Section 202.1001(b)(1)(ii) and (b)(2) require these risk-based procedures, logged in an auditable manner, as part of the data compliance program that U.S. persons engaging in restricted transactions must have by October 6, 2025 [1].
Records management with compliance
Section 202.1101(b)(4) and (11) require documentation of the due diligence, including the direct and indirect ownership of entities or citizenship or primary residence of individuals, and an annual certification of the completeness and accuracy of the due diligence records by an officer, executive or other employee responsible for compliance. Section 202.1101(a) keeps records of each transaction available for at least 10 years, and section 202.1002(e) requires the annual audit to examine these records [1].
General counsel
Section 202.304 prohibits transactions that have the purpose of evading or avoiding the rule, attempts and conspiracies. Section 202.901 lets a U.S. person party to an actual, not hypothetical, transaction request an advisory opinion, with the parties’ identities and ownership, data types and volumes, end-use and transfer method [1]. The Department’s program page lists its FAQs and compliance guide as current resources [3].
Spotted an error? Tell us and we will check it and correct the checklist where needed.