Skip to content

Other ways to search: UTHSC News

Controlled Items, Biologics, Software, Encryption

Controlled Items, Equipment, & Materials

Many items, equipment, and materials (collectively, “items”) are closely controlled under export regulations. In most cases foreign persons may interact with those items and no export license is needed. However, there are several situations where an export license may be required for a foreign person to access items, equipment, and/or materials on campus:

  • The item is controlled under the ITAR, even when used to perform fundamental research
  • The item is controlled at a high level under the EAR, and one of the following is true:
    • The item is produced in the course of restricted (i.e. not fundamental) research or proprietary service activity
    • The foreign national is interacting with the item in a manner that meets all aspects of “use” as defined in the EAR, so as to gain the underlying control features of the item.

Faculty and staff who purchase and/or receive equipment, items, and materials should ensure the export classification of such items is clearly known and documented. The best way to determine the classification is to ask the manufacturer. If the manufacturer cannot or will not provide this information Office of Research Security (ORS) can help determine the level of control and any necessary controls required.


Controlled Biologics

The following biologics (viruses, bacteria, toxins, and fungi) are controlled under the U.S. Department of Commerce Export Administration Regulations (EAR) Commerce Control List. These biologics are referred to as “Controlled Biologics” and may include biologics commonly used in the laboratory or contained in Biosafety Level 2 labs.

While these biologics can generally be used on-campus to facilitate student, staff, and faculty research, the transfer of these biologics to a foreign country is prohibited without an export license.  

List of items that may also be controlled
  • Genetic elements or genetically modified organisms for all Controlled Biologics (1C353)
  • Vaccinations containing, or designed to be used against, a Controlled Biologic (1C991)
  • Medical products containing certain toxins (1C991)
  • Diagnostics and food testing kits containing certain toxins (1C991)
  • Technology for the development or production of Controlled Biologics (1E001)
  • Technology for the disposal of Controlled Biologics (1E351)
  • Controlled Biologics which are physically modified, formulated, or produced (ITAR Cat XIV). Such Biologics must be:
    • 1-10 micron particle size
    • Particle-absorbed or combined with nano-particles
    • Having coatings/surfactants
    • My microencapsulation
Controlled Biologics in Research

Use of a Controlled Biologics is generally permitted without an export license, unless such use occurs in the course of a restricted-research project, and the use would constitute a ‘deemed export’ of technology to the foreign national.  Research qualifies as ‘Fundamental Research’ under U.S. export controls, when there are no restrictions on the institutions right to release and/or publish the research data, and there are no restrictions on foreign national participation in the research.  However, where research is subject to publication restrictions, such work is considered ‘restricted’ or export-controlled research.

Questions?

Contact Research Security to determine whether a biologic is controlled, a license is required, and if so, obtaining an export license. Export licenses generally take 6+ weeks to obtain; advance notice will help facilitate your proposed exports.


Controlled Software & Encryption

Export control regulations enumerated in the ITAR and the EAR govern both software and encryption. Both the physical export of software and encryption, as well as the sharing of software and encryption may be highly controlled under export regulations. This applies to software and encryption that is received from another party, as well as software and encryption that is developed at the university.

Export Controls and “Strong” Encryption[LD1] 

Strong dual-use encryption, addressed in Category 5 Part II of the EAR’s  Commerce Control List (CCL) at 5A002 (encrypted hardware) and 5D002 (encryption software), is defined as:

  • Employing a symmetric algorithm with a key length in excess of 56-bits
  • Employing an asymmetric algorithm based on:
    • A factorization of integers in excess of 512 bits (i.e. RSA);
    • Computation of discrete logarithms in a multiplicative group of a finite field of size greater than 512 bits (i.e. Diffie-Hellman over Z/pZ)
    • Discrete logarithms in a group in excess of 112 bits (i.e. Diffie-Hellman over an elliptic curve)
  • Designed or modified to perform dual-use cryptanalytic functions
  • Designed or modified to use quantum cryptography
  • Specially designed or modified to reduce the compromising emanations of information bearing signals beyond that necessary for health, safety or electromagnetic interference
  • Using cryptographic techniques to generate the spreading code for dual-use spread spectrum systems including the hopping code for frequency hopping systems
  • Using cryptographic techniques to generate channelizing codes, scrambling codes or network identification codes for systems using ultra-wideband modulation techniques
  • Using cryptography in communications cable systems designed or modified to detect surreptitious intrusion using mechanical, electrical or electronic means.

Strong dual-use encryption software is NOT:

  • Cryptographic code limited to authentication and digital signature including associated key management functions
  • Software using fixed data compression or coding techniques
  • Encryption/decryption code designed to protect libraries, design attributes or associated data for the design of semiconductor devices or integrated circuits.

It is important to note that many encryption products contain “strong” encryption.

The sharing, shipping, transmission, or transfer of almost all dual-use encryption software in either source code or object code is subject to the Export Administration Regulations. Even most of today’s publicly available dual-use encryption software, which uses “strong” encryption, is captured by the EAR and requires the availability of a License Exception to exit the U.S. If you wish to send or transmit products containing strong encryption to a foreign person, please contact ORS for assistance.

Publicly available software containing strong encryption[LD2] 

The release of even publicly available strong encryption software is carefully regulated. While publicly available (i.e. open-source) software is exempt from export control, when that software contains strong encryption export controls may still apply. Before strong dual-use encryption code is made publicly available via the internet or otherwise placed electronically in the public domain, exporters must provide the U.S. government with either a copy of the strong dual-use encryption code or a one-time notification of the internet location (URL) of the code. This must be done before making the software publicly available. Notification after transmission or transfer of the software outside the U.S. is an export control violation.

Software Received or Purchased from Another Party[LD3] 

Before purchasing or receiving non-public software, UT Health Sciences personnel should determine the export control classification of the software. The classification may be listed on the manufacturer’s website, and the manufacturer should be able to provide this information. If the export classification (ECCN or USML#) cannot be obtained on the web or by phone, please contact Research Security for assistance.

Providing access to export-controlled software to a foreign person may constitute an export violation, even when that access occurs on-campus. In many cases, control is only required around the software source code, and users can access the software interface without restrictions. Export Control will work with faculty and staff to determine how to make controlled software as accessible as possible. If you know or determine that software is controlled and/or contains strong encryption, please contact Research Security before providing access to the software.

Software Developed at or by UTHSC[LD4] 

Most software developed at or by UT Health Sciences is the product of non-proprietary, fundamental research and will be made publicly available. To reinforce this, researchers should upload UT Health Sciences-generated software onto a publicly available website as soon as possible. Access to the code must not include login requirements or other password or authentication procedures. Prior to uploading software that contains “strong” encryption (see above), please contact Research Security for assistance.

Software developed during the course of controlled research (such as proprietary software developed for an industry sponsor) is export controlled and must not be uploaded to a cloud-based system or to a website without approval from the Office of Research Security. Research Security will work with faculty and ITS [LD5] to determine appropriate procedures for working with and sharing controlled software.

Lastly, U.S. researchers should also be aware that without government approval, they are prohibited from providing technical assistance (i.e., instruction, skills training, working knowledge, consulting services) to a foreign person with the intent to assist in the overseas development or manufacture of dual-use encryption software or hardware employing strong encryption code. This prohibition does NOT limit UT Health Sciences personnel from teaching or discussing general information about cryptography software development that arises during UT Health Sciences fundamental research.

 

Nov 17, 2026