The Justice Department’s Data Security Program (28 CFR part 202), explained

Since April 8, 2025, U.S. persons may not sell or license bulk sensitive personal data or government-related data to six countries of concern or covered persons, and may give them access through vendor, employment or investment agreements only under CISA’s security requirements. Under the rule text, due diligence, audit and reporting duties followed on October 6, 2025.

What the program is

The Data Security Program, run by the Justice Department’s National Security Division, sets what the Department calls effectively export controls on data. It prohibits or restricts transactions that could give countries of concern, and persons tied to them, access to U.S. government-related data or Americans’ bulk sensitive personal data [3]. The Department issued it under the International Emergency Economic Powers Act (IEEPA) and Executive Order 14117 of February 28, 2024 [3]. The final rule was published on January 8, 2025, at 90 FR 1636, and took effect on April 8, 2025 [1] [2]. It is codified at 28 CFR part 202 [2].

The rule turns on four defined terms: who the other party is, what data is involved, how much of it, and what kind of transaction gives access to it.

The other party: countries of concern and covered persons

The Attorney General, with the concurrence of the Secretaries of State and Commerce, has named six countries of concern: China, Cuba, Iran, North Korea, Russia and Venezuela [2]. China includes the Special Administrative Regions of Hong Kong and Macau [2].

A covered person is, in summary [2]:

  • a foreign entity 50% or more owned, directly or indirectly, by a country of concern or by covered persons, or organized or with its principal place of business in a country of concern;
  • a foreign individual who is an employee or contractor of a country of concern or of such an entity;
  • a foreign individual primarily resident in a country of concern;
  • any person, wherever located, whom the Attorney General designates.

Sensitive personal data means covered personal identifiers, precise geolocation data, biometric identifiers, human ’omic data, personal health data, personal financial data, or any combination of them [2]. The definition excludes, among other things, data lawfully available to the public from government records or in widely distributed media, personal communications, and informational materials [2]. The data counts whether or not it is anonymized, pseudonymized, de-identified or encrypted [2].

It is “bulk” when it meets these thresholds at any point in the preceding 12 months, in one transaction or added up across transactions between the same U.S. person and the same foreign or covered person [2]:

  • human ’omic data on more than 1,000 U.S. persons, or human genomic data on more than 100;
  • biometric identifiers on more than 1,000 U.S. persons;
  • precise geolocation data on more than 1,000 U.S. devices;
  • personal health data or personal financial data on more than 10,000 U.S. persons;
  • covered personal identifiers on more than 100,000 U.S. persons.

Government-related data has no threshold. It covers precise geolocation data for areas on the Attorney General’s Government-Related Location Data List, and any sensitive personal data that a party markets as linked or linkable to current or recent former U.S. government employees or contractors, or former senior officials, including the military and the Intelligence Community [2].

The transactions: prohibited and restricted

A covered data transaction is one that gives a country of concern or covered person access to government-related data or bulk U.S. sensitive personal data through data brokerage, a vendor agreement, an employment agreement or an investment agreement [2].

Prohibited

  • Data brokerage with a country of concern or covered person: selling or licensing access to data the recipient did not collect directly from the people it describes [2].
  • Onward transfer. Data brokerage of such data with any other foreign person is prohibited unless the contract bars that person from reselling it to a country of concern or covered person, and the U.S. person reports known or suspected breaches of that term [2].
  • Human ’omic data and biospecimens. Any covered data transaction giving a country of concern or covered person access to bulk human ’omic data, or to biospecimens from which it could be derived [2].
  • Evasion, attempts, causing violations and conspiracies [2].

Restricted

Vendor agreements (including cloud-computing services), employment agreements (including board and executive roles) and investment agreements that give such access are allowed only if the U.S. person meets the security requirements and the rule’s other conditions [2]. The security requirements are CISA’s Security Requirements for Restricted Transactions of January 2025, incorporated into the rule by reference [2] [3]. Passive investments, such as certain holdings of publicly traded securities, fall outside the definition of an investment agreement [2].

Exemptions and licenses

Subpart E exempts data transactions to the extent they involve, among others: personal communications; informational materials; travel; official U.S. government business; activity ordinarily incident to financial services; administrative operations within a corporate group, such as human resources and payroll; telecommunications services; and certain regulatory submissions and clinical-investigation data for drugs, biological products and devices [2]. Each exemption has its own conditions, and some reporting duties still apply. The Department may also issue general and specific licenses [2].

Effective dates and the compliance program

The prohibitions and restrictions apply from 12:01 a.m. Eastern Time on April 8, 2025 [2]. The rule text dates the affirmative program duties from October 6, 2025 [2]:

  • Data compliance program. By October 6, 2025, anyone engaging in restricted transactions must have one. It includes risk-based procedures to verify and log data types and volumes, the identity of the parties and the end use of the data; procedures to verify vendors’ identity; and written policies on the program and on the security requirements, each certified annually by a responsible officer or employee.
  • Audit. An independent, qualified auditor who is not a covered person must audit restricted transactions once for each calendar year in which they occur, covering the preceding 12 months, and report in writing within 60 days of completing the audit.
  • Annual reports from U.S. persons engaged in restricted transactions involving cloud-computing services that are 25% or more owned by a country of concern or covered person.
  • Reports on rejected offers of prohibited data brokerage, within 14 days of rejecting them.

Anyone engaging in a transaction subject to the rule must keep full and accurate records for at least 10 years [2]. Violations carry the civil and criminal penalties in section 206 of IEEPA [2].

The Department also published a compliance guide and an implementation and enforcement policy for the period through July 8, 2025, both dated April 11, 2025, and has since updated its frequently asked questions [3]. The Division’s page says those later duties became effective on October 5, 2025 [3], while the rule text says October 6, 2025 [2]; this page follows the rule text.

Where it bites first

Because the rule covers vendors, employees and investors as well as buyers of data, it reaches ordinary operating arrangements. The rule’s own examples include a U.S. medical facility contracting with a company headquartered in a country of concern for IT services, and a consumer genomic-testing company employing a team of citizens of, and primary residents in, a country of concern to provide back-end services [2]. An inventory of where bulk sensitive data goes, who can reach it and under which contracts is the starting point for applying the thresholds; that is a practical step, not a requirement stated in this form by the rule. Whether a given arrangement is prohibited, restricted or exempt is a question for counsel. This page explains the rule and is not legal advice.

Moraph’s teams help organizations with work like this; see our solutions.

Spotted an error? Tell us and we will check it and correct the explainer where needed.

  • DOJ Data Security Program
  • 28 CFR part 202
  • Executive Order 14117
  • bulk sensitive personal data
  • countries of concern
  • data brokerage
  • CISA security requirements