The BIS advanced semiconductor rule changes how chip exporters, cloud providers, data centers, and semiconductor manufacturers must evaluate remote computing access. Effective November 19, 2026, the rule targets advanced computing capacity supplied to restricted companies through third countries while adding licensing and reporting obligations for several major technology markets.
Remote Data Center Access Becomes a Controlled End Use
The central compliance development is a new end-use control for advanced Super Intelligence, or SI, items used in data centers. The control applies to exports, reexports, and in-country transfers involving items classified under ECCNs 3A090, 4A090, and related .z paragraphs when the required knowledge standard is met.
The 12 Million Aggregate TPP Threshold
A license is generally required when a data center provides more than 12 million aggregate total processing performance, or TPP, to a company headquartered in Macau or Country Group D:5. The same applies when the customer's ultimate parent is headquartered in one of those jurisdictions.
The threshold can be measured at one site or across linked data centers. As a result, operators cannot necessarily assess compliance facility by facility. Capacity delivered through digitally connected locations, affiliated operators, reserved clusters, or coordinated cloud environments may need to be aggregated.
The rule reaches remote access rather than only physical shipment. A compliant initial deployment can also become a controlled transfer if the customer, ultimate parent, or end use later changes. Data centers already providing covered computing capacity before publication generally have 90 days from the effective date to obtain authorization if they intend to continue.
Ownership, Control, and Knowledge
Exporters, data centers, foundries, and other covered parties must investigate direct and indirect ownership or control involving Macau and Country Group D:5. Compliance cannot stop with the immediate purchaser, reseller, or account holder. Ultimate-parent analysis and end-use verification are essential.
Where a prohibited end use is known, parties generally cannot rely on de minimis concepts to avoid the control. Exporters shipping covered items without a license must also notify recipients of the applicable end-use requirement, making downstream communication part of the control framework.
Five Countries Face New Destination License Requirements
The rule establishes a destination-based license requirement for advanced SI items exported, reexported, or transferred to or within Indonesia, Malaysia, Singapore, Thailand, and Brazil. These jurisdictions are treated as presenting elevated diversion risk because they host expanding data center, cloud, server integration, and semiconductor supply chain activity.
U.S.-Headquartered Company Exception
The destination requirement generally does not apply when the consignee or end user is headquartered in the United States or has a U.S.-headquartered ultimate parent, provided the exporter satisfies monthly reporting requirements. Corporate affiliation alone is therefore insufficient. The exception depends on accurate reporting and supportable ultimate-parent information.
Monthly reports are due by the first business day of the following month. Required data generally includes the parties and their ultimate parents, destination, applicable ECCN paragraph, product name, SKU, TPP, quantity, and transaction date. Exporters relying on the exception need structured data collection across order management, classification, customer onboarding, and shipping systems.
The rule also replaces the prior worldwide license requirement with a more targeted framework covering Country Groups D:1, D:4, and D:5, subject to stated exclusions, as well as certain transactions involving the United Arab Emirates. Companies should not interpret that change as broad deregulation. Destination, end-use, end-user, and remote-access restrictions can overlap.
Foundries, Designers, and OSATs
Front-end fabricators and outsourced semiconductor assembly and test providers face tighter controls for advanced-node integrated circuits. Certain designers located in, or ultimately owned from, the listed country groups or five newly designated countries can no longer use previous pathways to overcome the presumption associated with 3A090.a items.
Advanced-node IC production for designers that are not approved or authorized may require a license. Foundries and OSATs should validate designer identity, ultimate ownership, technical specifications, authorization status, and intended customers before accepting or continuing covered work.
Building an Operational Compliance Response
The rule takes effect upon publication on November 19, 2026, although public comments remain open for 60 days. Because the obligations affect existing infrastructure and continuing services, companies should treat implementation as an immediate operational project rather than a conventional policy update.
Map Products, Capacity, and Connected Facilities
The first step is identifying products classified under ECCNs 3A090, 4A090, and related .z paragraphs. Classification records should connect each SKU to its TPP, destination, customer, consignee, end user, and data center deployment.
Data center operators should map linked facilities and determine whether capacity must be aggregated. That assessment should include dedicated clusters, reserved cloud capacity, affiliated locations, and environments through which a customer can access computing resources remotely.
The commercial recommender systems exception should be applied narrowly. It generally covers systems used only to rank, filter, or suggest products, services, or content and is subject to reporting. Systems that generate text, images, audio, video, or software do not qualify. Providers offering mixed workloads should avoid assuming that a recommendation function protects an otherwise generative environment.
Strengthen Customer and End-Use Controls
Customer due diligence should capture legal name, headquarters, ultimate parent, beneficial ownership, control relationships, intended workload, expected TPP, deployment location, and access rights. Contracts should require notification of ownership changes, customer substitutions, capacity increases, and workload changes.
Ongoing monitoring is equally important. A transaction that was permissible at shipment may later become controlled when capacity crosses the threshold or access shifts to a restricted organization. Compliance teams should establish escalation triggers for account transfers, parent-company changes, linked-site expansion, and unusual usage patterns.
The rule includes a savings clause for qualifying shipments already en route on the publication date. Such shipments may generally proceed under prior eligibility if completed within 30 days. Companies relying on this provision should retain dated shipping, routing, authorization, and delivery records demonstrating that every condition was met.
- On November 16, 2026, BIS issued an interim final rule (RIN 0694-AK50) addressing remote access to advanced semiconductors (also called Super Intelligence or SI items), scheduled for Federal Register publication and effective on November 19, 2026, with a 60-day comment period.* The rule, directed by Treasury and the National Security Council, amends multiple EAR parts and aims to close loopholes allowing China-headquartered or D:5 companies to access U.S. chips via third-country data centers.
- A new data center end-use control (15 CFR 744.24) requires a license for exports, reexports, or in-country transfers of advanced items (ECCNs 3A090, 4A090 and related) if there is knowledge they will be used in any data center providing more than 12 million aggregate TPP (roughly 760 Nvidia H100 equivalents) to companies headquartered in Macau or Country Group D:5, including across linked or digitally connected facilities.* Existing providers above the threshold have 90 days from the effective date to obtain a license. Case-by-case review applies, with exceptions for certain commercial recommender systems. Data centers and exporters must conduct due diligence on customer ownership and control.
- The rule adds license requirements for advanced semiconductors to five diversion-risk countries (Indonesia, Malaysia, Singapore, Thailand, and Brazil), with an exception for U.S.-headquartered companies or those with U.S. ultimate parents that meet monthly reporting rules.* It also tightens foundry and packager presumptions for advanced-node chips.
- The IFR formally rescinds the never-enforced Biden-era AI Diffusion Rule and adopts "Super Intelligence" terminology consistent with Executive Order 14434.* Law firm alerts from Nixon Peabody, KPMG, and others on November 16-17 outlined immediate compliance obligations for chipmakers, data center operators, and cloud providers worldwide.
- Practitioner discussions on X from November 16-17 focused on implementation details, including the 90-day transition, KYC/ownership tracing requirements, and impacts on Southeast Asian data centers, Taiwanese foundries like TSMC, Chinese AI firms (e.g., ByteDance, Alibaba), and U.S. cloud/neocloud providers.* Analysts noted potential stranded capacity in Malaysia and Singapore data centers serving restricted customers, plus heightened due diligence burdens.
Frequently Asked Questions
What Items Are Covered by the Remote Access Rule?
The control generally covers advanced SI items classified under ECCNs 3A090, 4A090, and related .z paragraphs. This can include advanced processors, computers, servers, and other products meeting the relevant technical parameters. Classification should be completed at the specific product and ECCN paragraph level rather than by broad product category.
Does the Rule Apply When No Chip Is Shipped to China?
Yes. The end-use control is designed to reach remote computing access provided from data centers located anywhere. A license may be required when qualifying capacity is made available to a company headquartered in Macau or Country Group D:5, or to a company whose ultimate parent is headquartered there.
Is Every Shipment to the Five Named Countries Licensed?
Not necessarily. The new requirement focuses on covered advanced SI items sent to or within Indonesia, Malaysia, Singapore, Thailand, and Brazil. An exception may apply to U.S.-headquartered consignees or end users, including entities with U.S. ultimate parents, when the exporter completes the required monthly reporting.
What Happened to the AI Diffusion Rule?
The January 15, 2025 AI Diffusion Rule is formally rescinded. Its country tiers, Data Center VEU structure, License Exceptions AIA and LPP, ECCN 4E091 model-weight classification, and associated foreign direct product rule are removed. License Exception ACM and the advanced computing foreign direct product rule remain in place.
What Is the Main Compliance Risk for Data Centers?
The principal risk is treating remote access as a static customer-screening issue. Operators must assess aggregate TPP, connected facilities, ultimate-parent location, workload, and subsequent account changes. A permitted relationship can become controlled when capacity expands, ownership changes, or computing resources are reassigned to a restricted end user.
How Stable Software Can Help
Supporting More Consistent Trade Compliance Workflows
The new BIS controls make accurate party identification and ownership analysis increasingly important for exporters, brokers, and trade compliance teams. Organizations reassessing those controls can review Stable Software's denied-party screening platform as part of a broader evaluation of their compliance technology stack.
Stable Software also makes DrawbackAI, flat-license duty drawback software that U.S. customs brokers can white-label for importer clients and use to file under their own filer codes. Stable Software charges a flat software license and never takes a percentage of the refund. Customs brokers seeking technology that preserves control over client relationships and filing operations can explore how Stable Software fits within their wider trade technology strategy.
Resources
| Type | Resource |
|---|---|
| Source | Primary source |

