BIS issues Interim Final Rule restricting remote access to advanced US AI chips
On November 16, 2026, the U.S. Department of Commerce's Bureau of Industry and Security (BIS) issued an Interim Final Rule (IFR) to close the main route by which companies tied to China and other countries listed in the Export Administration Regulations' (EAR) Country Group D:5, and Macau—which BIS lists separately (collectively, Target Countries)—use U.S. AI chips without buying them: renting compute from data centers in third countries.
The IFR takes effect upon publication in the Federal Register, scheduled for November 19, 2026.
Key points for data center operators, AI developers, and their suppliers:
The regulatory changes contained in the IFR—along with opportunities for comment, additional potential regulation, and practical implications for affected industries—are discussed in greater detail below.
The IFR adds EAR § 744.24, which requires a license to export, reexport, or transfer:
The control is triggered by a low aggregate compute (TPP) threshold: The control applies to data centers that provide more than 12,000,000 total processing performance (TPP). 12,000,000 TPP equates to roughly 750 Nvidia H100 GPUs or roughly 330 B200 GPUs, and is aggregated across physically or digitally “linked” data centers, so spreading capacity across sites does not help. This represents a small fraction of a single large training cluster. Any hyperscaler servicing a significant Target Country Company should assume it is in scope.
The control reaches indirect access: Access “for” a Target Country Company includes an intermediary that trains AI models for it, takes part in that training, or provides AI models to such a company. The IFR also does not distinguish cloud providers that own the chips from colocation providers whose tenants own them.
Several other provisions extend the control’s reach:
The rule implicates data privacy considerations: The KYC information at issue may include personal information about customers' owners and controllers. Operators should confirm their privacy notices and customer contracts permit collecting that information with suppliers. These expectations must be assessed in light of local data protection or confidentiality laws that may also apply. Operators and suppliers should consider sharing mechanisms now.
There is a narrow “commercial recommender” exception: The license requirement does not apply where a data center’s compute is provided only for a “commercial recommender system”—an AI tool “exclusively designed and exclusively used” to rank, filter, or suggest commercial products, services, or content) —provided relevant information is reported to BIS. The carve-out excludes any system that includes generative AI.
Data centers that already provide “significant volume” of computing power to Target Country Companies must obtain a license within 90 days “or face future export restrictions.”
A license requirement can also arise after the chips are installed, with no new shipment: BIS treats a switch from a permitted use to a prohibited one as a new “transfer (in-country)” that needs authorization. § 744.24(e) imposes only a notice obligation on the supplier, and a license requirement for the data center operator or other "transferor." Two common scenarios could trigger this: a Target Country Company acquires an existing customer, or an operator shifts capacity so a Target Country Company exceeds the TPP threshold. Operators should screen for these risks in M&A diligence and in customer change-of-control provisions, and condition expansion and capacity-reallocation rights on export control compliance.
The IFR will require a license for covered items to or within Indonesia, Malaysia, Singapore, Thailand, and Brazil, citing “an unacceptable risk of diversion,” with case-by-case review that considers each country’s export control enforcement and cooperation with BIS. This requirement applies to every covered shipment into these countries—whether or not the items are intended for use in a data center, or that center would provide compute to a Target Country Company—and only a short list of license exceptions remains available.
More countries may be added—BIS will monitor for countries that tolerate evasion and may respond with countrywide restrictions in addition to restrictions on the companies responsible.
The requirement does not apply where the ultimate consignee or end user is a U.S.-headquartered company or its subsidiary, provided the exporter, reexporter, or transferor files monthly reports under new § 743.10. Shipments to a U.S.-headquartered operator still need a § 744.24 license if the operator’s data center serves Target Country Companies above the TPP threshold.
The IFR also adds a license requirement for foundries and outsourced assembly and test (OSAT) providers to ship chips specified in ECCN 3A090.a designed by a company that is neither on BIS’s list of approved designers nor an “authorized” designer:
Foundries and OSAT providers that make advanced logic chips (16/14nm node, or below. or with nonplanar transistors) must presume those chips are controlled.
The IFR narrows the options to rebut the presumption. Foundries and OSATs could previously attest that a chip’s transistor count was below set limits (Note 1 to ECCN 3A090.a, paras. b.–c.). That option is no longer available for designers located in (or whose ultimate parent is headquartered in) Country Groups D:1, D:4 or D:5 (which includes Israel, Saudi Arabia, and Vietnam), or the five diversion risk countries (Note 1 to ECCN 3A090.a, paras. b.–c., cross-referencing 15 C.F.R. § 742.6(a)(6)(iii)(A)(1)).
The January 2025 AI Diffusion Rule would have required licenses for advanced AI chips to virtually every country and, for the first time, controlled the “weights” of the most advanced closed AI models. The IFR formally removes the AI Diffusion Rule’s country tiers, License Exceptions AIA and LPP, the Data Center Validated End-User program, and the model-weights controls.
Three existing provisions remain:
BIS also says it will address model-weight risks through destination- and end-use-based controls, so exports to Target Country Companies may still garner regulatory scrutiny.
The IFR takes effect on publication but is subject to modification based on comments submitted within 60 days after publication.
Notably, BIS’s notice accompanying the IFR specifies that the IFR was “written by and at the direction of the Department of [the] Treasury and the National Security Council.” While other agency input into BIS rulemaking is common, such a stark disavowal by BIS is not. The statement suggests that BIS may not be fully satisfied with the IFR and may be particularly receptive to comments from members of the public.
Potential issues for comment by affected industries include:
Remote Access Security Act: The House passed the Remote Access Security Act (RASA, H.R. 2683) 369–22 on January 12, 2026. That bill and its Senate counterpart (S. 3519) are pending in the Senate Banking Committee.
RASA would give BIS express authority to control “remote access” to items subject to the EAR by any foreign person. It would let BIS regulate the cloud service itself, rather than only the hardware shipment, closing the gap for capacity located in the United States. It would also leave the countries, subject items, and compute thresholds to BIS regulations. BIS will likely follow the precedent set by the IFR (and eventual final rule), meaning the IFR comment period may also influence eventual post-RASA rulemaking.
Other developments to watch: Companies should prepare for further country designations, “is informed” notices, and Entity List actions against third-country compute providers. BIS’s Affiliates Rule, which would extend Entity List restrictions to companies 50% or more owned by listed parties, will add a significant layer to data center ownership diligence and is suspended only until January 10, 2027. U.S.-China trade talks, which have shaped the timing of recent BIS actions, may also affect implementation.
Because the IFR takes effect immediately on publication, data center operators, AI developers, and their suppliers should consider the following steps now:
Ashurst Perkins Coie’s International Trade and Data Center teams are closely monitoring the IFR’s publication and implementation. For assistance, please contact the authors or an Ashurst Perkins Coie lawyer.
The information provided is not intended to be a comprehensive review of all developments in the law and practice, or to cover all aspects of those referred to.
Readers should take legal advice before applying it to specific issues or transactions.