House-Passed Remote Access Bill Awaits Senate Committee Action as Chip Licensing Rules Set Conditions
H.R.2683 remains a proposal, not law; Commerce’s January rule allows conditional case-by-case review for some exports and IaaS use, while senators seek records on diversion allegations.

The Remote Access Security Act has cleared the House but is not law. Congress.gov’s record for H.R.2683 shows Representative Michael Lawler introduced the measure on April 7, 2025, the House passed it 369 to 22 on January 12, 2026, and the Senate received it the following day and sent it to the Banking, Housing, and Urban Affairs Committee. The status displayed is Passed House, not Became Law. A Congressional Research Service summary says the bill would apply the Export Control Reform Act’s architecture to networked and cloud-based access and let Commerce license and penalize conduct in that area. Those are proposed authorities. The record neither establishes enactment nor supports a conclusion that every earlier remote-computing deal was legal. [1]
A Senate referral is a procedural step, not a verdict on the bill. The retrieved record does not show committee approval, floor debate, a final Senate vote or a presidential signature. It also does not show rejection. A House vote of 369 to 22 measures chamber sentiment at one stage; it does not change the legal status. The distinction matters because the bill’s proposed reach over remote access cannot be enforced as current law, and its referral cannot make a statute retroactive to past transactions. Existing license conditions continue to operate on their own terms regardless of what happens to H.R.2683. [1]
Those conditions were revised in a Bureau of Industry and Security final rule published and effective January 15, 2026. The rule shifted license review for certain advanced-computing exports to China and Macau from a presumption of denial to case-by-case treatment. It covered Nvidia’s H200, AMD’s MI325X and less capable chips if they were commercially available in the United States when the rule published and the exporter made required certifications. The covered performance band was total processing performance below 21,000 and total DRAM bandwidth below 6,500 gigabytes per second. The certifications addressed adequate U.S. supply, avoidance of diversion from global foundry capacity needed for U.S. customers, recipient security procedures and independent testing in the United States. The rule retained a presumption of denial for reexports and in-country transfers to Macau or Country Group D:5, and for exports to entities headquartered or parented in those places even when their end users were elsewhere. [3]
The case-by-case route is tightly conditioned. An applicant must report how many units were shipped to U.S. commercial customers and provide performance specifications. It must show that exports will not delay existing or new U.S. orders and that foundry capacity for similar or more advanced chips for U.S. end users will not be diverted. The rule caps China and Macau shipments at half of comparable U.S. end-use shipments, while the application supplement frames the ceiling in aggregate processing performance. The applicant must confirm that the transaction involves no listed military, military-intelligence, nuclear, missile, or chemical or biological weapons purpose or recipient; no restricted transaction party; and no remote access by restricted parties. It must supply Know Your Customer procedures, physical-security information, a list of intended Infrastructure-as-a-Service remote users and controls on model-weight movement and restricted-party access to trained algorithms. A qualified U.S.-based testing laboratory must review each shipment before export. BIS said it would routinely check certifications by methods it chooses. [3]
Advertisement
The current Export Administration Regulations add application-level detail. Under Part 748, Supplement 2, paragraph (dd), an applicant seeking case-by-case treatment must certify the absence of listed military, military-intelligence and weapons uses or users, the absence of restricted transaction parties, and no restricted-party remote access. The ultimate consignee must provide Know Your Customer procedures. The applicant must identify intended Infrastructure-as-a-Service remote users in eight jurisdictions—Belarus, China, Cuba, Iran, Macau, North Korea, Russia and Venezuela—or entities headquartered there or with an ultimate parent headquartered there. That disclosure is meant to prevent unauthorized remote access; it does not by itself declare every listed user barred. Where IaaS is offered, the applicant must verify that the consignee or IaaS end user will not move trained model weights to undisclosed recipients or without BIS authorization, and will not give restricted parties direct or indirect access to algorithms developed using the chips. A testing lab needs U.S. headquarters, freedom from control by a D:5 or Macau entity, no financial stake in the deal and relevant expertise. BIS may revoke a lab’s qualification at any time, suspending case-by-case availability for exporters using it until a qualified replacement is named. [2] [3]
These provisions are bounded to a particular license path, not a general declaration that every remote-computing arrangement is banned or allowed. The current EAR edition also does not prove that identical wording governed earlier transactions. A physical GPU shipment and remote cloud access raise different factual and legal questions. Whether a deal was permissible depends on the rule, hardware, destination, end user, end use and license in force at the time. Hardware can be assessed under rules for a shipment; cloud access can raise separate questions about who uses the chip, for what purpose and under which license terms. The record supports neither a claim that all commerce with China is illegal nor one that all remote access is legal. A current rulebook cannot substitute for the rulebook in force years earlier. [2] [3]
On November 11, 2026, Senator Michael Bennet sent an oversight letter that attributed intelligence claims about Alice Huang, also called Huang Le, to New York Times reporting. The letter separated alleged physical chip diversion from remote computing access. Bennet cited reports that Malaysian and Indonesian subsidiaries of Megaspeed bought at least $4.6 billion in NVIDIA products from 2023 onward, and that a late-2024 BIS inspection found boxed hardware, which he described as a possible diversion indicator rather than proof. He also pointed to reports that Southeast Asian data centers were offering remote access to Chinese clients and called that a regulatory gap. Bennet requested an investigation update by November 24, consideration of Entity List action, information on interagency intelligence sharing and coordination with Singapore, Malaysia and Indonesia. These are allegations and requests; neither proves a shipment violated the law nor validates every remote transaction. [4]
Also on November 11, 2026, Senators Elizabeth Warren and Christopher A. Coons asked Howard Lutnick at Commerce, Marco Rubio at State and Stephen Miller at the White House to preserve NVIDIA-related export and intelligence records. They sought written confirmation by November 17 that preservation instructions had been issued, plus congressional briefings. The requested categories included license decisions, diversion investigations, enforcement, intelligence assessments, interagency deliberations, communications with NVIDIA, inventory verifications and choices to transfer, suspend or terminate investigations. Their narrative ascribed suspected intelligence activity and possible diversion to newspaper reporting published October 29, November 6, November 8 and November 9; those are source-report dates, not dates of Cali Reporter publication. A preservation demand does not itself prove wrongdoing. [5]
Advertisement
The legal backdrop is layered. The Export Control Reform Act of 2018 became law as part of the fiscal 2019 National Defense Authorization Act bearing John S. McCain’s name and is codified at 50 U.S.C. 4801-4852. The January BIS rule cites ECRA as authority for regulating exports, reexports and transfers, for the control list and for license requirements. Section 1753 covers regulation of exports, reexports and transfers; Section 1754 covers the control list and licensing; Section 1762 allowed the changes by final rule without prior notice and comment. The rule also cites authority to inform the public of policy and regulatory changes and to take other necessary action. H.R.2683’s summary would apply that framework to networked and cloud access. That remains a proposal, not a statement of current law. [1] [3]
A claim that rules leave a gap does not confer immunity, and it does not show that any specific company met its obligations. H.R.2683 remains a proposal, not an enacted statute. Existing export rules carry end-user, end-use and license conditions, and the January rule created a conditional path rather than an open door. A senator’s gap concern may identify a policy issue that physical-export controls do not fully reach remote access; it is not an adjudication that no other authority applies. Nor does it establish that a shipment or cloud transaction violated the law. The public record supports neither sweeping conclusion. A policy gap can be real without proving misconduct in a particular case, and a company’s compliance is a separate factual question. [1] [2] [3] [4]
Several questions remain unresolved in the public record. What specific intelligence underlies the claims that Bennet’s letter attributes to newspaper reporting? Did the late-2024 inspection lead to an enforcement action, and if so, what action? Will Commerce act on the requested Entity List consideration? Will the Senate Banking, Housing, and Urban Affairs Committee take up H.R.2683, and will the bill reach the Senate floor or become law? What will the requested records preservation and briefings produce? The public documents do not include the underlying intelligence assessment or inspection report. Lack of public evidence in this record is not proof that no classified evidence exists. The documents establish requests and allegations, not answers. [1] [4] [5]
Specific markers will show whether the policy and oversight questions move. The next Senate action on H.R.2683 beyond the January 13 referral, and any committee or floor step that changes its Passed House status, will indicate whether the proposal advances. BIS implementation of the January rule and the paragraph (dd) certification process will show whether applicants disclose IaaS remote users and whether the agency grants, denies or conditions licenses. Bennet’s November 24 response deadline and the Warren-Coons November 17 confirmation request are concrete oversight dates. Later public documents could show Entity List action, briefings, enforcement findings or no change; the record does not predict which will occur. [1] [3] [4] [5]
Advertisement
Sources
Congress.gov H.R.2683 Remote Access Security Act, status and summary
BIS Export Administration Regulations Part748, current retrieved edition
BIS January2026 final rule as published in Federal Register
Senator Bennet oversight statement and allegations
Senate Banking minority records-preservation request
Prepared with AI assistance from the cited sources.
The Cali Reporter newsletter
The stories worth your time.
California, the country, and what comes next. Join our free newsletter for reporting that keeps you informed.
More in Artificial Intelligence
- Mellanox Deal Terms, Israel-1 and NVIDIA’s Interim Leadership
NVIDIA agreed to buy Mellanox in March 2019 at a $6.9 billion enterprise value and completed the deal in April 2020 at a $7 billion transaction value. Eyal Waldman led Mellanox; Colette Kress, a finance executive, is NVIDIA’s interim CEO in 2026.
- Reuters Reports Second Unnamed Employee Relationship Involving Former NVIDIA CEO Huang
Reuters reported Nov. 12, citing two people familiar with the matter, that Jensen Huang, now NVIDIA's former CEO, had an intimate relationship with a second unnamed employee. The account is attributed, not adjudicated; Huang's Nov. 8 message admitted infidelity without naming anyone, and the board's stated investigation concerns reported foreign-intelligence concerns.
- NVIDIA Sets Nov. 17 Earnings Release as Kress Leads Interim CEO Role
The fiscal 2027 third-quarter report is scheduled for Nov. 17; August revenue, margin, spending and cash-flow figures plus the company’s outlook provide concrete comparisons for readers.
