Codify — Article

Bill would require licenses for exporting synthetic DNA/RNA sequence files to foreign entities of concern

The bill adds a one-year deadline to place digital DNA/RNA sequence files under Export Control Reform Act licensing when sent to foreign entities of concern, forcing sequence providers, cloud hosts, and researchers to change workflows.

The Brief

The Biological Intellectual Property Protection Act of 2025 amends the Export Control Reform Act to require licenses for the export, reexport, or in‑country transfer of digital sequence files for synthetic DNA and RNA when those files go to a ‘‘foreign entity of concern.’’ The statutory change inserts a new section (1758A) that sets a one‑year deadline for the responsible Secretary to implement the licensing regime, creates tailored definitions for ‘‘digital sequence,’’ ‘‘synthetic DNA or RNA,’’ and ‘‘foreign entity of concern,’’ and includes a carve‑out tied to existing Export Administration Regulations (EAR) text.

This is a narrowly drafted export‑control measure with broad operational reach. It targets the transmission of sequence data — not physical samples — which places sequence providers, DNA synthesis companies, cloud and bioinformatics platforms, and research institutions squarely in scope.

For compliance teams, the bill converts a data governance problem into an export‑control obligation with licensing, screening, and recordkeeping consequences that could slow collaborations and commercial workflows if implemented without tailored procedures or resources.

At a Glance

What It Does

The bill adds section 1758A to the Export Control Reform Act, requiring a license for exporting, reexporting, or making in‑country transfers of digital files that encode synthetic DNA or RNA to foreign entities of concern. It directs the Secretary to put the licensing regime in place within one year and preserves an exception for materials covered by EAR 734.3(b).

Who It Affects

Primary targets include DNA sequence design firms, commercial DNA synthesis providers, cloud-based sequence repositories and analysis platforms, and researchers who share sequence files with collaborators located in or controlled by foreign countries of concern. Secondary effects will reach legal and compliance teams, customs and export offices, and federal licensing authorities tasked with enforcement.

Why It Matters

The bill shifts export control focus from biological materials to digital sequence data — a modern vector for IP transfer and dual‑use risk — and extends existing export controls into routine data transfers. That pivot creates compliance obligations where previously most sequence data moved freely, creating potential operational disruption in life‑science R&D and bio-manufacturing supply chains.

More articles like this one.

A weekly email with all the latest developments on this topic.

Unsubscribe anytime.

What This Bill Actually Does

The bill amends the Export Control Reform Act by inserting a new, standalone licensing requirement specific to digital sequence files that represent synthetic DNA or RNA. It captures any binary or other digital representation that records the identity, order, and chemical modifications of each nucleotide position — the files companies already exchange to design, synthesize, or analyze genetic constructs.

The requirement covers exports, reexports, and in‑country transfers to ‘‘foreign entities of concern,’’ a defined category that includes governments, persons subject to the jurisdiction of a designated country of concern, and entities owned, directed, or controlled by those groups.

Implementation is time‑bound: the Secretary named in the Export Control Reform Act must adopt the licensing rule within one year of enactment. The bill does not itself prescribe the licensing criteria, approval timelines, or fee structures — it delegates those details to the Secretary’s rulemaking and administrative capacity.

The bill also incorporates an exception that points users to section 734.3(b) of the EAR, meaning some publicly available or otherwise exempt categories of information may fall outside the new license requirement depending on existing EAR definitions.The statutory definitions are consequential. ‘‘Digital sequence’’ is defined narrowly as the machine‑readable file encoding base identity and modifications, which brings into scope standard oligonucleotide orders, sequence design outputs from AI tools, and files exchanged between academic collaborators. The ‘‘synthetic DNA or RNA’’ definition explicitly covers recombinant nucleic acids and chemically synthesized or modified nucleic acids that can base pair with natural molecules.

The ‘‘foreign country of concern’’ is referenced by cross‑statute to the Research and Development, Competition, and Innovation Act, which domestic regulators already use when identifying countries subject to heightened scrutiny.Operationally, compliance will require sequence providers and hosting platforms to add screening for recipient status, build export licensing workflows, and decide when file transfers or in‑country shares trigger license filings. Because the bill targets files rather than physical samples, cloud transfers, API endpoints, and remote access arrangements become focal points for enforcement.

The absence of explicit funding or processing metrics in the bill raises a practical question about how the Commerce Department (which administers the ECRA) will manage licensing volume and timeliness once the rule is in effect.

The Five Things You Need to Know

1

The bill inserts a new section 1758A into the Export Control Reform Act that creates a license requirement for covered sequence files.

2

It requires the responsible Secretary to implement the licensing requirement within one year of enactment; the statute itself does not set approval standards or fees.

3

The license requirement applies to exports, reexports, and in‑country transfers of digital sequence files for synthetic DNA/RNA when the recipient is a ‘‘foreign entity of concern.’, The statute defines ‘‘digital sequence’’ as the binary or other digital representation specifying identity, order, and any chemical modification at each position, explicitly capturing machine‑readable design files and AI outputs.

4

An exception preserves coverage of information described in EAR section 734.3(b), so categories already exempted under that EAR provision may remain licensable‑free depending on existing EAR interpretations.

Section-by-Section Breakdown

Every bill we cover gets an analysis of its key sections. Expand all ↓

Section 1

Short title

Provides the Act’s name: the Biological Intellectual Property Protection Act of 2025. This is a conventional short‑title clause with no operational effect but signals the statute’s targeted purpose: protecting biological IP at the data level.

Section 2

Sense of Congress — findings about foreign threats

Lists congressional findings framing the national‑security rationale, focusing on the People’s Republic of China, military‑civil fusion laws, and the risk that export of DNA/RNA sequences enables intellectual property theft and dual‑use technology transfer. While non‑binding, this section narrows the perceived policy target and will guide agency rulemaking priorities and interagency coordination by emphasizing particular countries and legal authorities.

Section 3(a) (new 1758A(a))

License requirement for covered sequence transfers

Creates a licensing obligation for exports, reexports, and in‑country transfers of digital sequence files encoding synthetic DNA/RNA when the recipient is a foreign entity of concern. Practically, that converts routine digital transfers into controlled exports, requiring exporters and platforms to determine recipient status against statutory criteria and to file for licenses where appropriate. The provision delegates implementation mechanics — classification, licensing processes, and conditions — to the Secretary tasked under the Export Control Reform Act.

2 more sections
Section 3(b) (new 1758A(b))

Exception referencing EAR 734.3(b)

Creates a specific carve‑out: the new licensing requirement does not apply to information described in EAR section 734.3(b). That EAR provision concerns categories of publicly available information and other narrowly defined exceptions; the bill therefore relies on existing EAR interpretive frameworks to limit reach. Whether that exception materially narrows the new control will depend on how agencies apply EAR 734.3(b) to modern sequence data and machine‑readable design files.

Section 3(c) (new 1758A(c))

Definitions that shape scope and compliance

Defines key terms: 'digital sequence' (binary files representing identity, order, and modifications), 'foreign country of concern' (pointer to section 10612(a) of the R&D Competition Act), 'foreign entity of concern' (government entities, persons subject to or organized under a country of concern, and entities owned/controlled by them), and 'synthetic DNA or RNA' (recombinant, chemically synthesized/modified nucleic acids that can base pair or replicate). These definitions determine which data products and which recipients trigger licensing obligations and extend control to AI‑designed sequences and derivatives from replication.

At scale

This bill is one of many.

Codify tracks hundreds of bills on Technology across all five countries.

Explore Technology in Codify Search →

Who Benefits and Who Bears the Cost

Every bill creates winners and losers. Here's who stands to gain and who bears the cost.

Who Benefits

  • U.S. biotechnology and pharmaceutical companies that hold proprietary sequence IP — by creating a statutory export control aimed at preventing foreign acquisition of design files that reveal proprietary constructs and workflows.
  • Federal national‑security and export‑control authorities — by giving them an explicit tool to regulate a modern pathway (digital sequences) for technology transfer and to align export controls with concerns about dual‑use biological design.
  • Domestic DNA synthesis companies and secure‑synthesis service providers that can offer vetted, licensed channels — they gain a competitive advantage if customers require compliant, controlled synthesis and transfer services.
  • Investors and manufacturers focused on onshoring sensitive design and manufacturing — the law raises the cost of offshoring certain data transfers, which could encourage domestic processing and storage of critical sequence design work.

Who Bears the Cost

  • Commercial DNA synthesis firms and oligo providers — they will need to screen orders, identify recipients’ status, and file export licenses for covered transfers, adding compliance costs and potential delays in fulfillment.
  • Cloud‑based sequence repositories, bioinformatics platforms, and API providers — protecting against controlled transfers will require new recipient verification, geofencing, or blocking features and additional legal reviews.
  • Academic researchers and university tech transfer offices — cross‑border collaborations that share design files with collaborators in flagged countries could face new administrative barriers and slowed publication or licensing timelines.
  • The Commerce Department and other implementing agencies — the statute creates a licensing workload without specifying resources or processing standards, potentially producing backlogs and enforcement challenges.

Key Issues

The Core Tension

The central dilemma is protecting nationally important biological IP and limiting dual‑use transfer versus preserving the speed and openness of modern scientific collaboration and commerce; controlling sequence data reduces export risk but also imposes frictions on legitimate research, commercial timelines, and cloud‑native business models without clear, funded mechanisms to process or narrow licenses.

The bill focuses on digital sequence files, which is both its strength and weakness. Controlling data transfers addresses a clear vector for IP and dual‑use transfer, but the chosen statutory language raises immediate implementation questions: how to treat derivative data (e.g., encoded designs, intermediate representations), how to identify AI‑generated sequences versus human‑designed ones, and how to police cloud‑based transfers and mirrors.

The EAR 734.3(b) exception may exempt some categories of ‘‘publicly available’’ information, but the interplay between that exception and the new section could produce inconsistent agency interpretations and legal uncertainty for exporters.

The delegation to the Secretary to define licensing mechanics creates a second set of trade‑offs. Agencies will need to decide whether to adopt narrowly tailored license review standards, automated screening rules, and expedited pathways for research collaborations — or apply broad, case‑by‑case reviews that slow commerce.

The bill contains no funding provision or statutory performance metrics for processing licenses, raising the realistic prospect of administrative bottlenecks. Finally, by referencing the R&D Competition Act for the list of countries of concern, the statute ties biological data control to an already politicized framework, increasing the risk of diplomatic friction, supply‑chain relocation, and uneven enforcement across allied jurisdictions.

Try it yourself.

Ask a question in plain English, or pick a topic below. Results in seconds.