Chip Security Act 2026: AI Hardware Importers and Data Centre Operators

The Chip Security Act, H.R. 3447, passed the House Foreign Affairs Committee by a unanimous 42-0 vote on 26 March 2026, and as at 14 October 2026 it has not been enacted. For AI hardware importers, data centre operators and cloud providers that import, host or operate advanced GPU infrastructure outside the United States, including equipment subject to US export controls, the time to prepare is before it becomes law. Its built-in timeline is short.

The short version. As introduced, the bill would require Commerce, within 180 days of enactment, to make covered AI chips and listed computers carry location verification before export, reexport or in-country transfer to or in a foreign country. Licence and authorisation holders would have to report credible information about a location different from the one specified in the application, diversion to another user, or tampering or attempted tampering. Reports in July 2026 said the Senate’s FY2027 defence bill would carry it, but that bill has not reached the Senate floor. BIS rescinded its earlier country tiers in May 2025.

Carra Globe provides importer of record, exporter of record, delivered duty paid and freight forwarding services, so we have a commercial interest in your answer. What follows is written to be usable whether or not you ever speak to us.

The reason to prepare early is the bill’s 180-day timeline. Within 180 days of enactment, Commerce would have to require location verification on covered products before they are exported, reexported or transferred to or in a foreign country. For businesses operating GPU clusters in India, Malaysia, Singapore, the UAE and Saudi Arabia, 180 days is not enough time to build the supporting records and controls from scratch.

This guide covers what the bill would require and what it means operationally for AI hardware importers. It also sets out where the bill stands, what the enforcement context looks like, and the steps to take before enactment.

What the Chip Security Act actually requires

H.R. 3447 was introduced by Representative Bill Huizenga on 15 May 2025 and passed the House Foreign Affairs Committee 42-0 on 26 March 2026. The Senate companion, S. 1705, was introduced by Senator Tom Cotton on 8 May 2025 and referred to the Senate Banking Committee.

The bill’s definition of a covered product has three limbs. It covers integrated circuits classified under ECCN 3A090 or 3A001.z, computers and other products under ECCN 4A090 or 4A003.z, and, under the third limb, an integrated circuit or computer, or a product containing one, classified under a successor or substantially similar ECCN. Whether a particular server falls within the definition depends on its classification and on how that third limb is applied, so check each product rather than assuming.

As introduced, the bill would direct the Secretary of Commerce to act within the timeframes below. The full text is published on GovInfo.

• Location verification within 180 days. Commerce must require covered products to carry a chip security mechanism that implements location verification, using techniques feasible and appropriate at enactment, before export, reexport or in-country transfer to or in a foreign country. The bill defines a chip security mechanism broadly, as software-, firmware- or hardware-enabled or physical, but leaves the actual method and standards to Commerce’s rules.
• Reporting within 180 days. A person granted a licence or other authorisation to export, reexport or in-country transfer a covered product must promptly report credible information that it sits somewhere other than the location in the licence application, has been diverted to another user, or has been tampered with, including attempts to disable, spoof, manipulate, mislead or circumvent location verification or other chip security mechanisms.
• Ownership and location records. Commerce may verify the ownership and location of covered products sent to or within a foreign country, keep a record that includes each product’s location and current end user, and require licence holders to provide the information that record needs.
• Secondary mechanisms. Within one year, Commerce must assess further measures such as anti-tampering, workload verification and ways to modify illicitly acquired products, then report to Congress. Measures judged appropriate must be implemented within two years of that assessment.
• Annual reviews. Starting within two years of enactment, and then annually for three years, Commerce must assess new chip security mechanisms and report to Congress.

As introduced versus as amended. The list above follows the introduced text. The Congressional Budget Office’s May 2026 estimate of the committee-amended bill describes security mechanisms that could include on-site audits, legal attestations or location trackers, and a requirement for parties that need no licence but take part in producing, selling or transferring advanced AI chips to give Commerce information on request. The final wording may differ, especially if the bill becomes law through the defence bill.

Why the bill is moving and where it stands

The 42-0 vote did not happen in isolation. On 19 March 2026, the Department of Justice announced charges against three people, including a co-founder of a publicly traded US server manufacturer. Prosecutors allege that servers ordered for a purported Southeast Asian end user were routed through Taiwan and Southeast Asia to China. These are allegations, and the defendants are presumed innocent. The House Select Committee on China also points to a November 2025 indictment of three Chinese nationals accused of routing chips through Thailand and Malaysia to China.

Enforcement has sharpened alongside the legislation. The Select Committee, which backed the bill, says its own report concluded that DeepSeek used advanced Nvidia chips restricted from export to China. In February 2026, BIS imposed a penalty of about USD 252 million on Applied Materials for unlicensed reexports of ion implanters, which are chipmaking equipment rather than AI chips, to China through its Korean subsidiary. That case was brought under existing export law, not the bill, and BIS calls it its second-highest penalty ever. The bill has cosponsors from both parties.

Since the committee vote, the bill has been looking for a vehicle. The Congressional Budget Office scored it on 1 May 2026. In July 2026, press reports republished by Senator Jim Banks said the Senate’s manager’s amendment to the FY2027 National Defense Authorization Act would include it, alongside two other chip bills.

The defence bill itself has since stalled. On 14 July 2026, the Senate failed 50-46 to invoke cloture on the motion to proceed to its version. The House passed its own FY2027 defence bill 216-212 on 22 July 2026, which does not by itself show that this text is included. As at early October the Senate bill had still not reached the floor, and any final defence bill now looks likely to wait for the post-election session. We found no record of enactment as at 14 October 2026.

What it means for AI hardware importers specifically

Most coverage of the bill focuses on chip manufacturers and exporters. The operational impact on AI hardware importers and data centre operators outside the United States has received far less attention. Here is what it would mean for businesses that import, receive, host or operate covered GPU infrastructure in a foreign country.

Covered imports would carry location verification from day one

Once Commerce implements the rule, covered products could not be exported, reexported or transferred to or in a foreign country without a location verification mechanism already in place. Covered products, which may include servers depending on their classification, would be expected to arrive at your data centre with that mechanism built in. The question for importers is whether your facility’s network design, security protocols and physical access controls can support location verification and reporting under whatever technical standard Commerce ultimately sets.

Reporting sits with licence holders, and operators feed it

The bill places the reporting duty on the person holding the relevant licence or authorisation. If that is you, you would have to report credible information about an unauthorised location, diversion or tampering. If you are the end user or facility operator, expect the licence holder, often the exporter, to ask for location data and to write notice of moves or tampering into your contract.

Day-to-day events are not reportable just because they happen, but some can feed a report. A maintenance visit or a failed access attempt does not, on its own, show tampering. A move between facilities is different, because it may itself mean a covered product now sits somewhere other than the location in the licence application. The bill does not spell out how location or credible information would be judged, so record every move and security incident and give the licence holder what it needs to decide whether a trigger has been met.

Your importer of record structure needs to support the records

The bill would let Commerce verify the ownership and location of covered products sent abroad and keep records of each product’s location and current end user. That makes it worth checking that your Importer of Record structure, the legal entity named on the import declaration, fits with the records your facility keeps.

The IOR carries the import obligations set by destination law and the contract, which is the core of what an importer of record does. Acting as IOR does not, by itself, attract the bill’s reporting duty, which follows whoever holds the export, reexport or in-country transfer licence or authorisation. Because the owner, operator, exporter and importer may each keep part of the records, your contracts should name who maintains location and end-user data and who supplies it on request.

The 180-day timeline is not enough time to build from scratch

The bill gives Commerce 180 days from enactment to require location verification. A business with no location records for its GPU fleet, no serial-number inventory, no security protocols aligned with export control reporting and no named export compliance lead would struggle to build all of that in 180 days. The businesses that will be ready are the ones that start now. These practical controls are likely to help, although the final rule will set the actual standard.

• Product inventory mapped to chips where possible. Keep serial records for covered servers and boards, and for accelerator cards or individual chips where those numbers are available. Tie each record to its classification, rack or cage, facility, owner and end user, and note where your data cannot identify a single chip.
• Access control and logging. Identity checks for everyone with physical or logical access to covered GPU infrastructure, with logs you can produce on request.
• Location reporting protocol. A defined internal process for what counts as a reportable location change and who tells the licence holder.
• Tamper records. Physical inspection cycles, firmware version history and any anomalies in the location verification mechanism for each covered chip.

Where the combined burden is likely to be heaviest

The proposed provisions are framed around covered products sent to or within any foreign country, but the burden will not fall evenly. An earlier version of this guide described the BIS AI Diffusion Rule’s three country tiers. BIS announced the rule’s rescission on 13 May 2025, so its three tiers and their quantity caps are not in effect. Other controls remain. Licensing still turns on the item, destination, end user and end use under the Export Administration Regulations, and the bill would add its own layer on top.

• Malaysia and Southeast Asia. The cases behind the bill involved routes through Taiwan and Southeast Asia, and the November 2025 indictment named Thailand and Malaysia. Operators in these markets should expect exporters to ask for more detailed location and end-use evidence.
• Singapore. As a regional AI infrastructure hub, Singapore operators would carry the same location verification and reporting implications as any destination. For the wider cost picture, see our guide to reducing import duty in Singapore.
• India. Location verification would sit alongside India’s own import rules. Some IT and electronics products fall under the Bureau of Indian Standards compulsory registration scheme, so confirm the exact model against the current order before shipping.
• UAE and Saudi Arabia. Large sovereign AI deployments under US licences would bring end-user and location records into scope. In Saudi Arabia, product and shipment conformity on the SABER platform runs separately, and the route depends on the product and the technical regulation that covers it.

What to do before the bill is enacted

1. Build a serial-level inventory of covered equipment in your foreign facilities. Pull purchase records, import declarations and asset registers for all GPU infrastructure in each country, and identify every product classified under 3A090, 3A001.z, 4A090 or 4A003.z, down to card or chip level where the data allows. If you cannot produce this list today, you cannot answer an ownership and location request quickly. Build it now while you can do it methodically.
2. Audit your IOR structure in each country against the record-keeping power. Check that the Importer of Record named on your customs declarations, the facility operator and the licence holder can together produce location and end-user documentation on request. Where the IOR has no link to the facility where the chips sit, agree in writing who holds which records before the bill takes effect.
3. Implement access logging and tamper records for every covered chip facility. A licence holder’s reporting duty starts with credible information. Without logging, nobody will know when a reportable event has happened. Access logs, firmware version records and physical inspection records are a sensible baseline.
4. Consider BIS’s Data Center Validated End-User (VEU) programme where it fits. It is not a blanket approval. BIS reviews each application and approves specific facilities to receive specified items under set conditions. For operators running covered chips at scale, it may be worth assessing now. It does not guarantee any particular treatment under the bill, whose interaction with VEU status is not yet settled. See our guide to AI GPU import compliance 2026 for more on VEU.

Moving GPU servers into a new data centre? Send the model list, the destination, the end user and your delivery date, and we will tell you which classification, screening and end-use documents to line up before the hardware ships. Request a pre-shipment check.

How Carra Globe supports AI hardware importers

Carra Globe acts as importer of record and exporter of record for businesses moving covered AI hardware into data centres abroad. Our global trade compliance team checks ECCN classification and denied party screening, reviews supplier and end-use documentation, and flags gaps before a delivery date is agreed. What we can take on depends on the product, the destination, local rules and the authorisations the transaction needs, and none of our services stands in for a US export licence or other regulatory approval.

Carra Globe works through importer-side registrations and local importing structures appropriate to the goods and destinations it accepts, its own in some markets and established local structures in others. Approvals falling outside the available structure are flagged before a delivery date is agreed.

Our delivered duty paid service confirms country-specific certification before freight is booked and models duty, VAT and local charges for each shipment. Our freight forwarding service keeps export documentation and chain-of-custody records from origin to the final facility across 175+ countries. For data centre server and GPU rollouts, including multi-country deployments, we plan each destination’s import route before hardware leaves origin.

Send us the model list, destination, end user and delivery date for your next deployment. Email info@carraglobe.com and we will come back on the classification, screening and documents to prepare. For background, see our guides on importing AI servers and GPU clusters, EAR and ITAR checks on IT hardware shipments and EU dual-use controls on AI hardware.

Frequently asked questions

Has the Chip Security Act been enacted?

Not as at 14 October 2026. It cleared committee 42-0 on 26 March 2026. July reports linked it to the Senate defence bill, but that bill had not reached the Senate floor by early October.

Which chips would the bill cover?

Integrated circuits under 3A090 or 3A001.z, computers or other products under 4A090 or 4A003.z, and items under successor or substantially similar ECCNs. Whether a given server is caught depends on its classification.

What does location verification require from a data centre operator?

The bill leaves the method to Commerce, defining mechanisms only in broad terms. Until rules exist, operators should expect exporters to ask for location data, access controls and notice of moves.

Would it apply to chips already deployed abroad?

The bill does not say expressly. The location verification duty applies before export, reexport or in-country transfer to or in a foreign country, and Commerce may verify ownership and location of products already abroad.

What penalty would apply for failing to report?

The bill sets no penalty of its own. How a failure to report would be enforced depends on how Commerce implements it, though CBO says the bill could expose more people to export law penalties.

How does the bill interact with the BIS country tiers?

BIS is not enforcing the tiers, having announced the AI Diffusion Rule’s rescission in May 2025. Destination-specific licence requirements for advanced computing items remain, and the bill would sit on top of them.

Adjacent ground: importing NVIDIA H200 servers outside the US, export controls across the data centre hardware stack and China’s rare earth controls on server components.

---

Sources and verification

Sources checked on 14 October 2026.

• The bill: H.R. 3447, Chip Security Act, as introduced.
• Sections relied on: Section 3 (definitions and covered ECCNs), Section 4(a) (location verification and reporting), Section 4(b) (secondary mechanisms), Section 4(c) (ownership and location records) and Section 4(d) (annual assessments).
• Committee-amended version: Congressional Budget Office cost estimate, 1 May 2026.
• Senate companion: S. 1705 as introduced, 8 May 2025.
• Committee vote: House Select Committee on China, 26 March 2026.
• Country tiers: BIS announcement rescinding the AI Diffusion Rule.
• Defence bill status: Congressional Research Service, FY2027 NDAA: Status of Legislative Activity (IN12704), updated 1 September 2026, for events to that date. The early October position (no Senate floor action, year-end timing likely) comes from a Holland & Knight analysis dated 9 October 2026, not linked because it is a law firm source.
• Data Center VEU: BIS announcement on the Data Center VEU programme.
• Enforcement: Department of Justice, charges announced 19 March 2026, BIS, Applied Materials penalty, 12 February 2026, and 15 CFR 6.3 civil penalty adjustments.
• Verification note: Bill provisions follow the introduced text, and the committee-amended text may differ. The NDAA route reflects CRS and public reporting through early October 2026, and enactment status was checked on 14 October 2026.

---

Disclaimer: This article is general information about the Chip Security Act and US export controls as at 14 October 2026 and is not legal advice. The bill may change before enactment, and Commerce rules will set the detail, so check the current position and take advice on your specific products before relying on it.