# Checklist: meeting the DOJ Data Security Program’s duties for covered data and restricted transactions

Thirteen steps under 28 CFR part 202: finding the covered data and the bulk thresholds, sorting transactions into prohibited, restricted and exempt, applying CISA’s security requirements, and running the data compliance program, audits, records and reports the rule requires.

Checklist · Cross-sector · Data & AI. Published November 14, 2026. Last reviewed November 14, 2026.

## The rule and its dates

The Justice Department’s National Security Division issued 28 CFR part 202 to implement Executive Order 14117 [1] [3]. The part took effect at 12:01 a.m. ET on April 8, 2025 (section 202.216) [1]. It bars U.S. persons from 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 others, called restricted transactions, only when the U.S. person meets security requirements issued by CISA [1] [2]. The rule text dates the data compliance program, the audit, the annual report and the report on rejected transactions from October 6, 2025 (sections 202.1001 to 202.1002 and 202.1103 to 202.1104) [1]. The Department’s program page gives October 5, 2025 for the same requirements [3]; the steps below use the rule’s date.

## Reading the steps

The steps run from finding the data, through sorting each transaction, to the program, audit, records and reports. Each cites the section of part 202 or the part of CISA’s Security Requirements for Restricted Transactions (January 2025, incorporated by reference in section 202.248) that it rests on [1] [2]. Where a step is our suggestion rather than a requirement, it says so. The owner shown under each step is a typical role, not one the rule names, unless the step says the rule names it. Sections and dates are from the current eCFR text as checked on November 14, 2026. This checklist explains the rule; it is not legal advice, and counsel should confirm how it applies to a given organization.

Moraph’s teams help organizations with work like this. [See our solutions](https://www.moraph.com/solutions).

## The checklist

1. **Map the data the organization holds or sells against the six categories of sensitive personal data and the two kinds of government-related data.** (Privacy officer with data governance) Section 202.249 defines sensitive personal data as covered personal identifiers, precise geolocation data, biometric identifiers, human ’omic data, personal health data and personal financial data, with listed exclusions such as data lawfully available from public government records. Section 202.222 defines government-related data, which includes precise geolocation data for listed government locations regardless of volume [1].
2. **Measure volumes against the bulk thresholds over the preceding 12 months, adding up all transactions with the same foreign counterparty, and count anonymized, pseudonymized, de-identified or encrypted data too.** (Data governance lead) Section 202.205 sets the thresholds: human ’omic data on more than 1,000 U.S. persons (human genomic data on more than 100); biometric identifiers on more than 1,000; precise geolocation data on more than 1,000 U.S. devices; personal health or personal financial data on more than 10,000; covered personal identifiers on more than 100,000; and a rule for combined data. Section 202.206 says bulk data counts regardless of whether it is anonymized, pseudonymized, de-identified or encrypted [1].
3. **Screen counterparties, their owners, and the employees and contractors who could reach the data, against the list of countries of concern and the covered-person tests.** (Third-party risk management with human resources) Section 202.601 names China, Cuba, Iran, North Korea, Russia and Venezuela. Section 202.211 makes covered persons of, among others, foreign entities 50% or more owned by a country of concern or covered persons, or organized or with their principal place of business in a country of concern, and foreign individuals who are employees or contractors of such entities or primarily resident in a country of concern [1].
4. **Classify each data flow that gives such a person access as data brokerage, a vendor agreement, an employment agreement or an investment agreement.** (Legal) Section 202.210 makes a covered data transaction one that gives a country of concern or covered person access to government-related data or bulk U.S. sensitive personal data through one of those four kinds of transaction. Section 202.258 includes cloud-computing services in vendor agreements [1].
5. **Stop the prohibited transactions, after checking whether an exemption in subpart E applies.** (General counsel) Section 202.301 prohibits knowingly engaging in a covered data transaction involving data brokerage with a country of concern or covered person. Section 202.303 prohibits covered data transactions giving access to bulk human ’omic data or to human biospecimens from which it could be derived. Subpart E lists exempt transactions, such as section 202.506 for certain corporate group administrative transactions [1].
6. **For data brokerage with any other foreign person, put the onward-transfer clause in the contract and set up the 14-day report of known or suspected breaches of it.** (Legal with procurement) Section 202.302 requires the U.S. person to contractually require the foreign person not to resell the same data to a country of concern or covered person, and to report known or suspected violations within 14 days of becoming aware of them [1].
7. **Allow a vendor, employment or investment agreement that is a covered data transaction to go ahead only once the CISA security requirements are in place for it.** (CISO with legal) Section 202.401 permits restricted transactions only if the U.S. person complies with the security requirements defined in section 202.248. Its second example says a vendor agreement protected by different controls the company believes mitigate the covered person’s access, instead of the security requirements, is not authorized and is a prohibited transaction [1].
8. **Apply CISA’s organizational and system-level requirements to every covered system: asset inventory, an accountable owner, KEV patching, vendor agreements, network topology, an approved hardware and software list, an incident response plan, access controls and a data risk assessment.** (CISO) Section I of the CISA requirements calls for, among other things, an asset inventory updated no less than monthly for IT assets; a designated individual accountable for cybersecurity and for governance, risk and compliance; remediation of known exploited vulnerabilities in internet-facing systems within 45 calendar days; an allowlist of approved hardware and software; incident response plans reviewed annually; access controls that keep covered persons from covered data; and an internal data risk assessment with a mitigation strategy [2].
9. **Choose the data-level controls for each restricted transaction, and write the data retention and deletion policy.** (Security architect with the data protection officer) Section II of the CISA requirements calls for a combination of data minimization and masking, encryption, privacy-enhancing technologies and identity and access management that together fully and effectively prevent covered persons and countries of concern from reaching covered data that is linkable, identifiable, unencrypted or decryptable. It includes a written data retention and deletion policy reviewed annually [2].
10. **Have a data compliance program in place by the rule’s date, with the two written policies certified each year.** (Chief compliance officer) Section 202.1001 requires U.S. persons engaging in restricted transactions to develop and implement a data compliance program by no later than October 6, 2025. It must include risk-based procedures to verify and log data types and volumes, transaction parties and end use; procedures to verify vendor identity; and written policies on the program and on the security requirements, each annually certified by an officer, executive or other employee responsible for compliance [1].
11. **Commission an independent audit for each calendar year with restricted transactions, and keep the report.** (Internal audit, engaging an independent auditor) Section 202.1002 requires an audit once for each calendar year in which the U.S. person engages in restricted transactions, covering the preceding 12 months. The auditor must be qualified, independent and not a covered person or country of concern, must report in writing within 60 days of completing the audit, and the report is kept for at least 10 years [1].
12. **Keep a full record of each transaction subject to the rule for at least 10 years, and create and maintain the listed records for each restricted transaction.** (Records management with compliance) Section 202.1101(a) requires a full and accurate record of each transaction, available for examination for at least 10 years after the date of the transaction. Section 202.1101(b) lists the records for restricted transactions, including the certified policies, audit results, due diligence documentation, method of transfer, start and end dates, agreements, licenses or advisory opinions, and an annual certification of the completeness and accuracy of the due diligence records [1].
13. **Set up the reports: the annual report due by March 1 where it applies, the 14-day report of rejected data-brokerage offers, and responses to reports the Department demands.** (Chief compliance officer) Section 202.1103 requires an annual report, by March 1 for transactions as of December 31 of the previous year, from a U.S. person engaged in a restricted transaction involving cloud-computing services that is 25% or more owned by a country of concern or covered person. Section 202.1104 requires a report within 14 days of affirmatively rejecting an offer of a prohibited data-brokerage transaction. Section 202.1102 allows the Department to require reports under oath at any time [1].

## Sources

1. Electronic Code of Federal Regulations. 28 CFR part 202, Access to U.S. Sensitive Personal Data and Government-Related Data by Countries of Concern or Covered Persons (current text, checked November 14, 2026). <https://www.ecfr.gov/current/title-28/chapter-I/part-202> Checked November 14, 2026.
2. Cybersecurity and Infrastructure Security Agency. Security Requirements for Restricted Transactions, E.O. 14117 Implementation (January 2025; checked November 14, 2026). <https://www.cisa.gov/resources-tools/resources/EO-14117-security-requirements> Checked November 14, 2026.
3. U.S. Department of Justice. Data Security (National Security Division program page; checked November 14, 2026). <https://www.justice.gov/nsd/data-security> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-doj-data-security-program-restricted-transactions>
Publisher: Moraph Insights
