BIS’s 2015 intrusion proposal reached defenders’ tools; its 2021 rule made banks favorable treatment end users

On May 20, 2015, Commerce proposed export licenses for intrusion software tools to every country but Canada, reaching penetration testing products and exploit research. Its 2021 rule listed banks, insurers, health institutions and U.S. subsidiaries as favorable treatment cybersecurity end users.

Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.

Two-minute summaryThe dek and the first sentence of each section, quoted from the article

On May 20, 2015, Commerce proposed export licenses for intrusion software tools to every country but Canada, reaching penetration testing products and exploit research. Its 2021 rule listed banks, insurers, health institutions and U.S. subsidiaries as favorable treatment cybersecurity end users.

  1. The week The proposal explained its origin.
  2. The definition: what counted, and what was controlled The definition had two prongs.
  3. The tools: which products would have needed a license That reclassification had consequences.
  4. The transfers: what exporters would have filed The proposal asked how many deemed export applications companies would need to file under the rule. [1] In our reading, that question signaled that a U.S. security team could need licenses to share controlled technology with its own foreign-national staff in the United States.
  5. The research: knowledge as a controlled item In our reading, this was the provision with the widest reach, because it reached information as well as products.
  6. How the proposal would have reached different organizations The 2021 rule said Commerce had conducted extensive outreach with financial institutions during the rulemaking. [2] It later named providers of banking and other financial services among the favorable treatment cybersecurity end users. [2] In our reading, a bank that moves tools between its own offices abroad would have faced licensing for internal transfers, and Commerce’s later text named the sector.
  7. Objections, and where the argument stops The review policy favored U.S. companies and certain partners. [1] It did not remove the license requirement. [1] It did not cover every foreign affiliate or vendor, and the proposal set presumptive denial for zero-day capabilities. [1] In our reading, favorable review reduces the risk of denial, not the cost of applying.
  8. With hindsight The proposal drew a heavy response.

The week

On May 20, 2015, the Federal Register published a proposed rule from the Commerce Department’s Bureau of Industry and Security. [1] Its title was “Wassenaar Arrangement 2013 Plenary Agreements Implementation: Intrusion and Surveillance Items.” [1] The Assistant Secretary for Export Administration had signed it on May 11, 2015. [1] Comments were due on or before July 20, 2015. [1]

The proposal explained its origin. It described the Wassenaar Arrangement as a group of 41 like-minded states committed to responsibility and transparency in the global arms trade. [1] It said the United States, as a participating state, had committed to controlling for export all items on the Arrangement’s control lists. [1] It said changes to the lists are approved by consensus at annual December plenary meetings. [1]

In 2013, the Arrangement had agreed to add new items to its list of dual-use goods. [1] They included systems, equipment and components specially designed for the generation, operation or delivery of, or communication with, intrusion software. [1] They included software for those systems, and technology required for the development of intrusion software. [1] They also included internet protocol network communications surveillance systems. [1]

The proposal said Commerce, Defense, State and other agencies had been discussing how to add these items, which it called “cybersecurity items,” to the Commerce Control List. [1] It said they sought to do so without reducing encryption controls. [1] It said the rule was published as a proposal for resource planning, license requirements and internal license review planning. [1]

The proposal would add two new export control classification numbers, 4A005 for hardware and 4D004 for software. [1] It would add a new paragraph, 4E001.c, controlling technology required for the development of intrusion software. [1] It would add 5A001.j for the network surveillance systems. [1] It proposed a license requirement for export, reexport or in-country transfer of these items to all destinations except Canada. [1]

The proposal also wrote the Arrangement’s definition of intrusion software into the regulations. [1] It defined it as software specially designed or modified to avoid detection by monitoring tools, or to defeat protective countermeasures, of a computer or network-capable device. [1] The software also had to extract or modify data, or modify a program’s standard execution path to run externally provided instructions. [1] The proposal said the definition included a note listing items excluded, such as hypervisors, debuggers and software reverse engineering tools. [1]

The proposal asked four questions. It asked how many more license applications companies would file each year, and how many deemed export applications. [1] It asked whether the rule would hurt legitimate vulnerability research, audits, testing or screening, and companies’ ability to protect their own or clients’ networks. [1] It asked how long companies would need to answer the new application questions. [1]

The proposal also took a position on procedure. It said the Administrative Procedure Act’s notice and comment requirements did not apply, because the regulation involved a military and foreign affairs function. [1] It said Commerce was offering the public an opportunity to comment anyway. [1] It designated the rule a significant regulatory action under Executive Order 12866. [1]

In our reading, the question about vulnerability research was the heart of the proposal for security teams. The agency had asked, in its own text, whether the rule would get in the way of defense. [1]

The Commerce Department’s May 2015 proposal is easy to read as a rule for spyware vendors. Its stated targets were tools for delivering intrusion software and systems for network surveillance. [1] Its text reached further. It said the new hardware and software entries “include network penetration testing products that use intrusion software to identify vulnerabilities of computers and network-capable devices.” [1] It said the technology entry includes “proprietary research on the vulnerabilities and exploitation of computers and network-capable devices.” [1]

Those are tools and work that defenders use. A bank’s red team, a health system’s penetration testing vendor and an agency’s vulnerability researchers buy or produce them. The proposal would have required a license for these items to every destination except Canada, with no license exceptions beyond certain government uses. [1]

Our argument is that the 2015 text controlled capabilities by what they could do, and that the same exploit code can serve an authorized test or an attack. In our reading, the proposal drew its line around the technique, while the later rule drew it around the user and the purpose. The 2021 rule defined U.S. subsidiaries, providers of banking and other financial services, insurance companies and civil health and medical institutions as favorable treatment cybersecurity end users. [2] That status lifted one restriction of its new license exception, on non-government end users in Country Groups D:1 and D:5, for certain items. [2] That is a different design, and it came only after the United States renegotiated the text at the Arrangement. [2]

The proposal mattered to sectors that never export a product. A bank, health system or agency exports when its people carry tools abroad, share exploit details with a foreign colleague or send code to an affiliate. In our reading, the 2015 text turned ordinary security operations in global organizations into export events. That is the lens we use here.

We take the 2015 proposal in four parts:

  1. The definition: what counted as intrusion software, and what the control actually covered.
  2. The tools: which products would have needed a license.
  3. The transfers: what an exporter would have had to file, and how Commerce would review it.
  4. The research: how the technology control reached vulnerability work.

The parts do not overlap. The first is the legal term, the second the products, the third the licensing process and the fourth the knowledge behind the products. After them we look at how the proposal would have reached banks, health systems and agencies, take the objections, and end with checks.

The definition: what counted, and what was controlled

Intrusion software itself

The definition had two prongs. Software had to be specially designed or modified to avoid detection by monitoring tools or to defeat protective countermeasures. [1] It also had to extract or modify data, or change a program’s standard execution path so that externally provided instructions run. [1] Both were required. [1]

The definition’s technical notes gave examples. Monitoring tools included antivirus products, endpoint security products, intrusion detection and prevention systems and firewalls. [1] Protective countermeasures were techniques designed to ensure the safe execution of code, such as data execution prevention, address space layout randomization or sandboxing. [1]

The defender’s stack in the definition

The technical notes read like a list of what a security team buys. Antivirus, endpoint products, intrusion detection and prevention systems and firewalls were the monitoring tools. [1] Data execution prevention, address space layout randomization and sandboxing were the protective countermeasures. [1]

In our reading, that list explains the reach. A tester who checks whether an organization’s endpoint product detects an attack must use software designed to avoid that product. A red team that tests a sandbox must try to defeat it. The definition’s first prong describes the purpose of an authorized test as well as an attack.

Software that was not intrusion software

The definition’s note excluded three groups. Hypervisors, debuggers and software reverse engineering tools were excluded. [1] So was digital rights management software. [1] So was software installed by manufacturers, administrators or users for asset tracking or recovery. [1] The note also said network-capable devices include mobile devices and smart meters. [1]

In our reading, the exclusions show what the drafters feared catching. Each excluded category does something the definition’s prongs could describe. A debugger changes execution flow. Asset recovery software can extract data. The note carved them out by name rather than by a general test of purpose.

New exporters

The proposal expected the rule to reach companies new to export controls. It proposed adding a cross-reference to the definitions section in the new entries. [1] It said the rule “may be of interest to many new exporters” that would not otherwise know where the regulations define their double-quoted terms. [1] It proposed a license requirement note to alert exporters to include all relevant information in classification requests and license applications. [1]

In our reading, Commerce was signaling that security software firms new to export controls would now need classification work. A firm that had never asked for a commodity classification would have to learn the process before shipping its product abroad.

The control was on the platform, not the payload

The proposal did not control intrusion software as such. It controlled systems, equipment and software specially designed for the generation, operation or delivery of, or communication with, intrusion software. [1] It also controlled technology required for developing intrusion software. [1] The 2021 rule later described the 2013 controls the same way, as controls on the command and delivery platforms. [2]

In our reading, this choice is the source of the reach into defense. A penetration testing product generates and delivers exploit code to a target, with the owner’s permission. Its function matches the control text. The proposal said so directly when it listed penetration testing products within the new entries. [1]

Why a technique-based line appealed

A line drawn around technique has advantages for a multilateral list. Participating states can apply the same words to products without knowing who will use them. A licensing officer can classify a product from its specifications. [1] In our reading, that is why the Arrangement’s text described functions such as evading monitoring tools and changing execution paths.

The cost of that approach falls on dual-use cases. When the same function serves defense and attack, a technique-based line catches both. The proposal tried to manage the cost through review policy, favoring U.S. companies and named partners. [1] In our reading, review policy can soften a line, but it cannot move it. The product still needs a license.

What the definition part means for a security leader

The definition part shows why a technical description is a poor proxy for intent. Exploit code run by an authorized tester and by a criminal can be the same code. In our reading, any control that depends on the code’s behavior, and not on authorization, will reach both. The 2021 rule later added an end-use restriction about use without authorization by the system’s owner. [2]

The tools: which products would have needed a license

Penetration testing products

The proposal said the new hardware and software entries include network penetration testing products. [1] It said certain penetration testing products were already classified as encryption items because of their cryptographic or cryptanalytic functions. [1] Under the proposal, they would be classified in the new cybersecurity entries instead. [1]

That reclassification had consequences. The proposal said cybersecurity items using encryption would still have to satisfy the encryption registration, review and reporting requirements. [1] It said one effect was that these items would not be eligible for License Exception ENC, the encryption license exception. [1] It said Commerce anticipated licensing broad authorizations to certain types of end users and destinations to counterbalance that loss. [1]

Encryption review stacked on top

The proposal did not replace encryption controls. It said cybersecurity items with encryption functionality must also satisfy the encryption registration, review and reporting requirements, including submissions to the ENC Encryption Request Coordinator at Fort Meade, Maryland. [1] It said those encryption steps had to be completed before a license application for a cybersecurity item would be considered. [1]

The proposal stated what it did not know. It said that because most of the affected items have encryption capabilities, Commerce believed they were already controlled under the encryption category. [1] It said the impact of the rule was unknown to it, and that it was issuing a proposal to gather comments on that impact. [1] In our reading, an agency that says it does not know a rule’s impact is asking industry to supply the evidence.

What a buyer could ask a vendor

A security leader buying testing tools had questions to ask under the proposal’s terms. In our reading, they included the product’s classification under the export rules and any classification ruling number. They also included whether the vendor held licenses for the countries where the buyer’s teams work. The proposal required classification ruling or license numbers in license applications for these items. [1]

A buyer with teams abroad would also need to know whether the vendor’s license covered transfers within the buyer’s own group. In our reading, a license to deliver a product to a U.S. bank does not by itself cover the bank’s movement of that product to its foreign branches. Those are separate transfers, and the proposal’s licensing reached exports, reexports and in-country transfers. [1]

Mass-market products

The proposal removed cybersecurity software from the mass-market provision of License Exception TSU. [1] It said this was consistent with the existing encryption exclusion. [1] In our reading, that meant a widely sold product that met the new definitions would not be freed from licensing because it was sold to the public.

Product versions

In our reading, a vendor facing these controls had choices. It could seek licenses for each destination. It could build export versions without the controlled functions. It could move development to a country where the item was not yet controlled, if that country had not yet implemented the Arrangement’s list. Each choice affects what a foreign affiliate of a U.S. bank or health system could buy. The proposal did not discuss these choices; they follow from its terms.

Surveillance systems

The proposal added 5A001.j for internet protocol network communications surveillance systems. [1] It said these systems intercept and analyze messages to produce personal, human and social information from communications traffic. [1] It said the entry was restricted to products performing all of the listed functions. [1] The 2021 rule later said these items had drawn far fewer comments than the intrusion items. [2]

Monitoring products and 5A001.j

The surveillance entry raised a question for defenders too. Security teams run network monitoring to find intrusions. The 2015 proposal limited 5A001.j to products performing all of its listed functions. [1] It described the target as systems that produce personal, human and social information from communications traffic. [1]

Commenters later asked for clarity. The 2022 final rule said one commenter asked whether 5A001.j would control cybersecurity incident detection and monitoring software. [5] Commerce answered with frequently asked questions and said it did not expect the entry to control a large number of products. [5] In our reading, the question had been open since 2015, because the proposal’s text did not address defensive monitoring.

Software for developing the tools

The proposal also amended 4D001 to control software specially designed or modified for the development or production of equipment controlled by 4A005. [1] It removed License Exceptions TSR and STA for that software. [1] In our reading, the reach extended from the tool to the software used to build the tool.

What the tools part means for a buyer

A bank, health system or agency that buys penetration testing tools from abroad would not be the exporter. A domestic buyer is affected when it sends tools, or the people who use them, across borders. In our reading, the proposal’s reach mattered to buyers with global security teams, overseas testing vendors or security operations centers abroad, if they moved tools between countries.

The transfers: what exporters would have filed

A license to every destination but Canada

The proposal controlled the new hardware and software entries for national security, regional stability and anti-terrorism reasons to all destinations except Canada. [1] It said no license exceptions would be available except certain provisions of License Exception GOV, such as exports by or on behalf of the U.S. government. [1] It applied the same license requirement to development technology under 4E001. [1]

Deemed exports

The proposal asked how many deemed export applications companies would need to file under the rule. [1] In our reading, that question signaled that a U.S. security team could need licenses to share controlled technology with its own foreign-national staff in the United States.

A letter of explanation

The proposal added application requirements for cybersecurity items. [1] Applicants were to write “Cybersecurity Item” in block 9 of the application. [1] They were to submit a letter of explanation covering, among other things, any encryption functionality and earlier classifications. [1] If no classification or license had been done, they were to answer three questions in the letter. [1]

The proposal also said that, on request, applicants must provide the sections of source code and other software that implement or invoke the controlled functionality. [1] In our reading, a security vendor would weigh that request against its own protection of proprietary code.

The paperwork

The proposal relied on an existing form. It said the multi-purpose application carried a burden estimate of 58 minutes for a manual or electronic submission. [1] It said the added technical information in paragraph (z) was the usual technical information submitted to describe an item’s abilities. [1] It said that information lets the licensing officer verify the classification and judge the effect on national security and foreign policy. [1]

In our reading, the per-application estimate understates the work for a security team. The application is the last step. Before it come classification, encryption registration, gathering technical answers and, on request, source code. [1]

How Commerce would review

The proposal set a review policy for regional stability controls. [1] Applications would be reviewed favorably if destined to a U.S. company or subsidiary outside Country Groups D:1 and E:1. [1] They would also be reviewed favorably for foreign commercial partners in Country Group A:5, and for government end users in Australia, Canada, New Zealand and the United Kingdom. [1] Others would be reviewed case by case, including for the foreign policy interest of promoting human rights. [1]

The proposal also stated a hard line. It said there is a policy of presumptive denial for items that have or support rootkit or zero-day exploit capabilities. [1] In our reading, a penetration testing product that includes exploits for unpatched flaws could fall under that policy.

Travel and tools of the trade

A tester who carries a laptop with testing tools to an office abroad is exporting those tools. The proposal offered no license exception for that case beyond certain government uses. [1] The 2021 rule later noted that, when License Exception ACE is not available, other exceptions may be. [2] It named License Exception TMP, which authorizes exports of tools of the trade in certain situations. [2]

In our reading, travel was one of the plainest operational problems in the 2015 text. Incident response teams travel to where an incident is. Under the proposal, their tools would have needed a license for every destination but Canada. [1]

Partners named and unnamed

The review policy named four governments for favorable treatment: Australia, Canada, New Zealand and the United Kingdom. [1] It said those governments had partnered with the United States on cybersecurity policy and issues. [1] It also favored foreign commercial partners in Country Group A:5, and proposed a note describing that term. [1]

In our reading, an organization with operations in other allied countries had less certainty. Its transfers would be reviewed case by case, including against foreign policy interests such as human rights. [1] The 2021 rule later used Country Group A:6, which it said includes Cyprus, Israel and Taiwan, in some of its exclusions. [2]

What the transfers part means for a security leader

For a multinational bank or health system, the transfers part described paperwork for moving tools between its own offices. The favorable review for U.S. subsidiaries would have helped. [1] It still required a license application. [1] In our reading, a security team that shares tools with an affiliate abroad would have needed export compliance staff in the loop for routine work.

The research: knowledge as a controlled item

Technology for developing intrusion software

The proposal added 4E001.c to control technology required for the development of intrusion software. [1] It said that includes proprietary research on the vulnerabilities and exploitation of computers and network-capable devices. [1] It applied a license requirement to all destinations except Canada and removed TSR and STA eligibility. [1]

In our reading, this was the provision with the widest reach, because it reached information as well as products. A report describing how to exploit a flaw, shared with a foreign colleague, could be technology for the development of intrusion software.

What stayed outside

The proposal did not change the general rules on what is outside the regulations. The 2021 rule later said software and technology that is published in the public domain and meets the regulations’ requirements is not subject to them. [2] In our reading, that left proprietary research inside the control and published research outside it. Details of a flaw shared privately with a vendor before publication would fall on the proprietary side.

The question the proposal asked

The proposal asked directly whether the rule would have negative effects on legitimate vulnerability research, audits, testing or screening. [1] It asked whether it would affect companies’ ability to protect their own or clients’ networks. [1] In our reading, that question showed Commerce knew where the risk lay.

Coordinated disclosure and incident response

In our reading, two activities depend on sharing exploit knowledge privately. One is telling a vendor about a flaw so it can be fixed. The other is sharing details of an attack with responders in other countries. The 2015 text had no carve-out for either. [1] The 2017 changes later added one, excluding technology exchanged for vulnerability disclosure or cyber incident response. [2]

Incident response across borders

Incident response sends information in both directions. A responder collects logs, malware samples and attacker tools from a victim’s systems. In our reading, some of those artifacts could themselves be controlled items, and sending them to a foreign responder or regulator could be an export. The 2015 proposal did not address that case. [1]

The 2021 rule did. It defined digital artifacts as items found on an information system that show past or present activity relating to its use or compromise. [2] It let them go, in defined cases, to police or judicial bodies in certain countries when the incident involved a favorable treatment end user’s systems. [2] It also allowed exports to national computer security incident response teams in those countries for incident response and vulnerability disclosure. [2]

Disclosure programs and threat intelligence

In our reading, two kinds of program sit close to the 4E001.c line. A vulnerability disclosure or bug bounty program receives exploit details from researchers, some of them abroad. A threat intelligence team exchanges indicators and attack details with peers and vendors in other countries. The proposal’s text did not address either. [1]

Receiving information from abroad is not an export. Sending a proof of concept back to a foreign researcher, or sharing exploit analysis with a foreign peer, could be. In our reading, the risk sat in the reply, not the report. The 2017 note on vulnerability disclosure and incident response later addressed both kinds of exchange. [2]

The line between a report and a weapon

A vulnerability report can be a description, a proof of concept or a working exploit. In our reading, the further along that line a document goes, the closer it comes to technology required for developing intrusion software. The proposal gave no test for where the line falls. [1] It asked commenters whether the rule would hurt vulnerability research, which leaves the line to the comments that followed. [1]

For a security leader, this is a records question. Teams that write up findings decide how much exploit detail to include. In our reading, a habit of separating the description of a flaw from the code that exploits it makes any later export question easier to answer.

What the research part means for a security leader

The research part reached the people a security organization depends on. In our reading, a bank’s threat intelligence team, a health system’s medical device security researchers and an agency’s vulnerability disclosure program all exchange the kind of information 4E001.c described. Under the proposal, an exchange with a foreign person could have needed a license.

How the proposal would have reached different organizations

Banks and other financial institutions

The 2021 rule said Commerce had conducted extensive outreach with financial institutions during the rulemaking. [2] It later named providers of banking and other financial services among the favorable treatment cybersecurity end users. [2] In our reading, a bank that moves tools between its own offices abroad would have faced licensing for internal transfers, and Commerce’s later text named the sector.

Insurers

Insurance companies were also named as favorable treatment end users in 2021. [2] In our reading, insurers that test their own networks or assess clients’ security share the banks’ exposure.

In our reading, an insurer also meets these tools as a buyer of assessments. An insurer that commissions penetration tests of its own systems, or reviews test results from insured clients abroad, handles the kind of technical information the proposal controlled. [1]

Health systems and life sciences

Civil health and medical institutions providing medical treatment or practicing medicine, including medical research, were named too. [2] In our reading, a health system’s exposure came through testing vendors, device security research and incident response with partners abroad.

Government agencies

U.S. government exports had a path through License Exception GOV in the proposal. [1] State and local agencies were not covered by that path in the text we read. In our reading, a state agency would meet the controls when it hired foreign testing vendors or shared incident details abroad.

Federal agencies’ contractors

License Exception GOV, the one exception the proposal kept, covered exports to or on behalf of the U.S. government under the cited provision. [1] In our reading, a contractor testing a federal agency’s systems abroad would need to check whether its export fell within that provision. A contractor testing a state agency or a private client would have no such path.

Security vendors

Vendors of penetration testing products were the direct exporters. [1] They faced reclassification, loss of ENC eligibility and new application requirements. [1] Their customers would have felt it through delivery delays or restricted features.

Managed security providers

A managed security provider that runs a security operations center abroad for U.S. clients moves tools and threat data across borders as its service. In our reading, it would have faced licensing on both its tools and the technical information it shares with its own staff. Its clients would have felt the effect through the provider’s delivery model.

Universities and research hospitals

Academic researchers publish vulnerability work, and published information was outside the regulations. [2] In our reading, the exposure for a university or research hospital lay in unpublished work shared with foreign collaborators or foreign-national students before publication. The 2021 rule’s definitions later named medical research among the activities of favorable treatment health institutions. [2]

Objections, and where the argument stops

“It was a proposal, so it never applied”

The proposal never took effect. [2] The 2021 rule said the United States decided against amending it and returned to the Arrangement instead. [2] We argue from what the text would have done, and from what Commerce later said comments showed. [2]

“The definition excluded defensive tools”

The note excluded hypervisors, debuggers, reverse engineering tools, digital rights management and asset recovery software. [1] It did not exclude penetration testing products. [1] The proposal itself said penetration testing products were within the new entries. [1]

“Favorable review would have solved it”

The review policy favored U.S. companies and certain partners. [1] It did not remove the license requirement. [1] It did not cover every foreign affiliate or vendor, and the proposal set presumptive denial for zero-day capabilities. [1] In our reading, favorable review reduces the risk of denial, not the cost of applying.

“Defenders could rely on published tools”

Published software and technology that meets the regulations’ requirements is not subject to them. [2] A defender could, in principle, rely on public tools. In our reading, that answer does not help with commercial testing products, which the proposal named. [1] It also does not help with private analysis of new attacks, which is the work incident responders share before anything is published.

“Export rules are for vendors, not users”

The proposal’s license requirement covered export, reexport and in-country transfer by anyone. [1] It asked companies about deemed exports and about their ability to protect their own and clients’ networks. [1] Those questions are about users as well as vendors. In our reading, an organization that uses testing tools across borders was an exporter under the text, whether or not it sold anything.

The 2021 rule’s favorable treatment list confirms that reading from the other direction. It named banks, insurers and health institutions as end users. [2] In our reading, Commerce would not have needed to name users if users were outside the rules’ concern.

“Commerce had to implement what the Arrangement agreed”

The proposal said the United States had committed to controlling all items on the Arrangement’s lists. [1] The 2021 rule says the United States decided against amending the proposal and returned to the Arrangement in 2016 and 2017 to negotiate changes to the text. [2] In our reading, the commitment did not fix the domestic design.

“The volume of affected exports was small”

The 2021 rule gave numbers for the existing entries it amended. It said 2020 data showed 980 shipments valued at $39,146,164 under those entries. [2] It said 120 of them, valued at $1,864,699, went to Country Group D:1 or D:5 countries and would need licenses. [2] It said it had no specific shipment data for the new entries and used other data to estimate them. [2]

Those figures describe shipments of products. They do not count internal transfers of tools by testers, or exchanges of technical information. In our reading, the burden the commenters described fell on activity that shipment data does not capture.

Where the argument stops

We do not claim that any organization was penalized under the proposal. It never took effect. We do not claim the 2021 rule removed all burden; it kept a license requirement for some destinations and end users. [2] The argument is limited to the change in design: from controlling a technique everywhere to controlling it by user and purpose.

We also do not claim the 2021 design is complete. Its favorable treatment list names four kinds of end user. [2] An organization outside that list, such as a utility or a state agency abroad, does not get the same treatment. In our reading, the design moved the question from what a tool does to who uses it and why. That is a better fit for defense, but it puts more weight on knowing the end user, which is its own compliance task.

Checks for a security leader

Inventory

  • List the offensive security tools your teams use, where they are stored and which countries they move between.
  • Record which staff and vendors are foreign persons with access to exploit code or vulnerability details.

Process

  • Put export compliance staff in the loop for sharing tools or exploit details with affiliates and vendors abroad.
  • Keep records of the authorization behind each test, since the current rule’s end-use restriction turns on authorization. [2]

Sharing

  • Know which exchanges count as vulnerability disclosure or incident response under the current definitions. [2]
  • Check current status in the regulations before relying on any license exception. [4]

Records

  • Keep classification records for tools you build or modify, and know who in your organization can request a classification.
  • Record the purpose of each exchange of exploit details with foreign persons, so it can be matched to the current exclusions.

Governance

  • Name an owner for export questions in the security organization, with a route to trade compliance staff.
  • Review the export position of each new offensive tool before it is deployed to teams outside the United States.

With hindsight

The proposal drew a heavy response. The 2021 rule said Commerce received almost 300 comments raising substantial concerns about the proposal’s scope and its effect on legitimate cybersecurity research and incident response. [2] It said Commerce also conducted extensive outreach with the security industry, financial institutions and government agencies that manage cybersecurity. [2]

The 2021 rule summarized the comments in three issues. Many commenters said the entries were overly broad and failed to describe the items intended for control. [2] Many said the rule imposed a heavy and unnecessary licensing burden on legitimate transactions that contribute to cybersecurity. [2] Many suggested the control on technology for developing intrusion software “could cripple legitimate cybersecurity research.” [2]

The United States did not finalize the proposal. The 2021 rule said it decided against amending the proposed rule and returned to the Arrangement in 2016 and 2017 to negotiate changes. [2] In December 2017, the Arrangement published the results. [2] The 2021 rule described three changes. [2]

The first change used “command and control” in the control language for hardware and software, to control tools that can be used maliciously more specifically. [2] The second added a note excluding technology exchanged for vulnerability disclosure or cyber incident response. [2] The third excluded products designed and limited to providing basic software updates and upgrades. [2]

Commerce implemented those decisions in an interim final rule published on October 21, 2021. [2] It added a new License Exception Authorized Cybersecurity Exports, known as ACE, authorizing exports of cybersecurity items to most destinations except in described circumstances. [2] The rule was to take effect on January 19, 2022. [2] On January 12, 2022, Commerce delayed the effective date to March 7, 2022, after commenters asked for time to update compliance procedures. [3]

The 2021 rule defined a favorable treatment cybersecurity end user as a U.S. subsidiary, a provider of banking and other financial services, an insurance company, or a civil health and medical institution. [2] Under ACE, the restriction on non-government end users in Country Groups D:1 and D:5 did not apply to certain items exported to those users. [2] The rule also restricted ACE where the exporter knows or has reason to know an item will be used without authorization by the system’s owner, operator or administrator. [2]

The 2021 rule also estimated its cost. It said it expected about 170 new license applications a year and estimated the paperwork cost at $2,520. [2] The 2022 final rule said one commenter called that estimate a gross underestimation, without data or another estimate. [5] It said Commerce had consulted its technical advisory committees on the estimate. [5]

The rule defined vulnerability disclosure and cyber incident response. [2] Vulnerability disclosure meant identifying, reporting or communicating a vulnerability to those responsible for remediation, or analyzing it with them, to resolve it. [2] Cyber incident response meant exchanging necessary information on an incident with those responsible for remediating it. [2]

On May 26, 2022, Commerce published a final rule revising ACE after 12 comments on the interim rule. [5] It added an illustrative list to the definition of government end user and simplified the structure of the restrictions. [5] It corrected a paragraph that, as written, had inadvertently widened the exception for digital artifacts. [5] The 2022 rule also extended the end-use restriction to the encryption license exception. It said License Exception ENC would not be authorized where the exporter knows or has reason to know that network penetration tools and certain other items will be used without the system owner’s authorization. [5]

As checked on November 16, 2026, the electronic Code of Federal Regulations, up to date as of November 12, 2026, listed Section 740.22 as License Exception Authorized Cybersecurity Exports. [4] Its definition of favorable treatment cybersecurity end user still named U.S. subsidiaries, providers of banking and other financial services, insurance companies, and civil health and medical institutions. [4] Its definition of government end user said the term does not include any favorable treatment cybersecurity end user. [4]

What held up from 2015 is the question the proposal asked about vulnerability research. [1] Commerce’s later rules answered it with carve-outs for disclosure and incident response, and favorable treatment for named sectors. [2] What did not hold up was the idea of licensing these tools to every destination but Canada. [1] [2]

Spotted an error? Tell us and we will check it and correct the article where needed.

  • export controls
  • Wassenaar Arrangement
  • intrusion software
  • penetration testing
  • vulnerability research
  • BIS