TIMEWELL
Solutions
Free ConsultationContact Us
TIMEWELL

Unleashing organizational potential with AI

ISO/IEC 27001 (ISMS) certification mark (SGS / ISMS-AC)

ISO/IEC 27001:2022 certified Certificate No. JP26/00000255 Scope: Planning, development and operation of SaaS products utilizing AI technology

Services

  • ZEROCK
  • TRAFEED
  • TIMEWELL BASE
  • WARP
  • WARP 1Day
  • WARP NEXT Corporate
  • WARP BASIC
  • WARP ENTRE
  • Alumni Salon
  • WARP for Schools
  • Alumni Ventures
  • FDE
  • AI Consulting
  • EMC GLOBAL

Company

  • About Us
  • Team
  • Why TIMEWELL
  • News
  • Contact
  • Free Consultation

Content

  • Insights
  • Knowledge Base
  • Case Studies
  • Whitepapers
  • Events
  • Solutions
  • AI Readiness Check
  • ROI Calculator

Legal

  • Privacy Policy
  • Manual Creator Extension
  • WARP Terms of Service
  • WARP NEXT School Rules
  • Legal Notice
  • Security
  • Anti-Social Policy
  • ZEROCK Terms of Service
  • TIMEWELL BASE Terms of Service

Newsletter

Get the latest AI and DX insights delivered weekly

Your email will only be used for newsletter delivery.

© 2026 株式会社TIMEWELL All rights reserved.

Contact Us
HomeTRAFEED MediaExport Control for SaaS and Software Companies: Deemed Export, ISMAP, and Cloud Regulations in Practice [2026 Edition]
TRAFEED Media

Export Control for SaaS and Software Companies: Deemed Export, ISMAP, and Cloud Regulations in Practice [2026 Edition]

Published2026-04-24Updated2026-11-22Checked against sources2026-11-22Ryuta Hamamoto
SaaSSoftware Export ControlISMAPDeemed ExportCloud RegulationTRAFEED

Working through this series on industry-specific export control has reminded me how unusual SaaS is. The goods don't move, but the technology does.

Export Control for SaaS and Software Companies: Deemed Export, ISMAP, and Cloud Regulations in Practice [2026 Edition]
Share

(November 22, 2026) We corrected, to match the primary sources, our descriptions of how METI's Service Transaction Circular (Appendix 1-2) treats cloud services, the EAR encryption thresholds (key lengths) and de minimis percentages, the article number in Japan's Act on the Protection of Personal Information, how the Digital Agency's DS-310 treats overseas data centers, and the specified categories under deemed export control.

Hello, this is Hamamoto from TIMEWELL. Over the past year, I have heard the line "we're SaaS, so export control doesn't apply to us" more times than I can count. I understand the instinct. You don't ship physical goods, you have no warehouse, and there is no customs entry. In reality, though, SaaS and software sit deeper inside the export control net than almost any other field.

Update, November 20, 2026: Added that the worldwide license requirement for advanced computing items was replaced, by the interim final rule of November 19, 2026 (91 FR 74970), with five-country and other license requirements and a data-center control. Otherwise the body reflects the situation as of July 2026.

Working through this series on industry-specific export control has reminded me how unusual SaaS is. The goods don't move, but the technology does. An API with an embedded cryptographic algorithm crosses a border the moment its client sits overseas. Hire a remote engineer overseas, and the deemed export issue is triggered at the instant of onboarding. On top of that, Japan has its own government procurement gate — ISMAP — whose standards were substantially revised at the end of 2025. This article organizes what SaaS and software companies need to get right as of July 2026, in five practical topics.

Work through where your encryption-bearing SaaS lands under the EAR: A fill-in working sheet covering "subject to the EAR? -> ECCN on the CCL? -> EAR99?", the cases where an EAR99 item still needs a license (embargoed destinations, end-use, end-user), de minimis / FDP, counterparty screening, and the two-track cross-check with Japan's classification. You can keep it as a filled-in record for your own items and destinations rather than re-deriving the flow each time. → Download the EAR flow & EAR99 checklist (Free. Registration with your company name and work email address is required.)

SaaS is a party to export control even when it thinks it isn't

The first thing SaaS companies trip on is the definition of "export." Both Japan's Foreign Exchange and Foreign Trade Act and the U.S. EAR cover not only goods, but also technology and services. SaaS doesn't move goods, but delivering technology is its entire business, so it sits at the center of the control perimeter rather than outside it.

The U.S. EAR (Export Administration Regulations) sweeps a lot of encryption software into Category 5 Part 2, and if your product implements TLS, VPN, file-based encryption, or end-to-end messaging, it may qualify as 5D002 or 5A002. Integrate a U.S.-origin library, and once the value of controlled U.S.-origin content exceeds 25% of the product (10% for destinations in Country Groups E:1 and E:2), the de minimis rule extends U.S. re-export control to your Japanese entity (§734.4(c) and (d); publicly available encryption source code that meets §742.15(b), for example, does not have to be counted). "We're fully domestic" is a harder claim than most SaaS companies realize.

Under domestic law, METI sets out how cloud services relate to service transactions in Appendix 1-2 of its Service Transaction Circular, "Interpretation of so-called cloud computing services" (the related Q&A entries are dated June 26, 2013). A storage-service contract does not, in principle, constitute a service transaction, even if controlled technology ends up stored on a server abroad, as long as its sole purpose is for the user to store information on the provider's server for its own use. If, however, you sign the contract knowing that the provider can view, obtain, or use the stored technology, the contract is deemed a transaction to provide that technology. Separately, a service that makes a program on a server usable over the internet without downloading it (SaaS and the like) is a transaction for the purpose of provision, so if the program is controlled technology, it is a service transaction (no license is needed for programs that meet the commercially available program exception in Article 9(2)(xiv)(a) of the Ordinance on Trade-Related Invisible Transactions). Providing the encryption technology itself to an overseas base, or handling decryption keys outside Japan, is a separate question from storage.

SaaS often blurs the line between "provision of services" and "provision of a program." Monthly subscription API access tends toward a service transaction; distributing an on-premises installer or virtual appliance tilts toward a program. Companies that offer both models need to run classification per service. In practice, many teams try to manage this in a single spreadsheet and end up with inconsistent granularity. Japanese SaaS companies have not yet matured their export control operations to the level of manufacturing, and viewed through METI's security trade control lens, SaaS feels about a decade behind manufacturing.

ISMAP's 2026 revision reshapes government procurement and cloud provider response

For domestic SaaS operators, ISMAP (Information System Security Management and Assessment Program) is just as unavoidable as export control. The program is meant to assure the security level of cloud services in government procurement, and since its launch in 2020, the major CSPs — AWS, Microsoft Azure, Google Cloud, IIJ, Sakura Internet — have registered.

Without a listing on the ISMAP Cloud Service List, you cannot even enter the bidding round for government platform systems, and some local government procurements are also locked. That has been a meaningful barrier to entry for Japanese SaaS companies, especially mid-sized ones. The cost of acquisition and maintenance has long been called excessive, and on September 18, 2025 the government published a proposal for a broad revision of the control baseline and put it out for public comment through October 17. The results were published on December 25, 2025, with 60 submissions and revisions made to the draft12.

The revision has two main points. First, it imports the governance, management, and control baselines from the Information Security Management Standard (2025 revision), which reflects updates to the international standards, and adds the cloud-specific controls from the Cloud Information Security Management Standard (2016 edition) plus controls drawn from the Common Standards for Government Agencies and NIST SP 800-53 rev.5. Second, the detailed control items are compressed from 1,163 to 322 — roughly a 70% cut3. This reduction is less a lightening of the checklist and more a change of granularity: the detailed controls are pared back to "the minimum description needed to achieve the control objective," and the concrete how-to moves into a newly created implementation guide. The correct reading is that quality was not cut — the granularity changed.

In January 2026, IIJ announced the additional registration of its cloud-based authentication service (IIJ ID Service / Identity Management Option) and its cloud-based web security service4. When the revised baseline will actually apply, and what transitional treatment already-registered providers will receive, was still described in the December 25, 2025 comment response as something the government "will continue to consider carefully, taking into account the views of the parties involved"2. The guidelines and other regulations are also still being drafted. It is a good moment for mid-sized SaaS providers that had passed on ISMAP to revisit the question, but plan on tracking official announcements for the schedule. Honestly, 322 items is still not a low bar. Rather than tackling it solo, a realistic path for SaaS built on AWS is to rely on AWS's ISMAP registration and focus on the controls you actually own.

On a side note, I get occasional questions that conflate ISMAP with JC-STAR (IPA's IoT security labeling scheme). JC-STAR targets IoT products; ISMAP targets cloud services — they cover different things. JC-STAR's Level 1 and Level 2 both run on vendor self-declaration and are currently accepting new applications. For Level 3, which requires third-party evaluation, IPA published the security requirements for communication equipment and network cameras on February 6, 2026, and the conformance requirements for those same two product types on June 12, 20265. Pure SaaS is outside JC-STAR's scope, but B2B SaaS vendors whose products pair with hardware should watch both.

Replace siloed classification work with AI.

METI's FY2024 data shows 52% of foreign exchange law violations stem from classification errors. Download the TRAFEED product catalog covering features and rollout.

Download Product CatalogContact About TRAFEED

The deemed export trap: hiring overseas engineers pulls the trigger

SaaS lives or dies by its engineers. Almost no company can staff entirely from domestic talent anymore, and fully remote hiring from India, Vietnam, or Ukraine is now routine. This is where deemed export steps in.

Article 25(1) of the Foreign Exchange and Foreign Trade Act treats the provision of technology by a resident in Japan to a non-resident as an "export" of controlled technology, and a revision of the Service Transaction Circular applied from May 1, 2022 clarified how this works6. The key point: even a resident falls under deemed export control if they are under the strong influence of a foreign government or foreign entity through an employment contract, economic benefits or similar ties (the "specified categories"). There are three: (1) a person who, under an employment or other contract with a foreign government or foreign entity, follows its direction or owes it a duty of care (with exceptions, such as where it is agreed that the Japanese employer's direction takes priority); (2) a person who receives, or has agreed to receive, money or other benefits from a foreign government amounting to 25% or more of their annual income; and (3) a person who receives instructions or requests from a foreign government regarding their conduct in Japan (Circular 1(3)(sa)). A student whose study is funded by a foreign government is given as an example of category (2).

Here is what SaaS HR actually encounters. You want to hire a strong backend engineer who holds Chinese nationality. The individual has lived in Japan for a long time and is treated as a resident. But if they earned a doctorate on a scholarship from their home government and still receive support from that government amounting to 25% or more of their annual income, they fall into category (2) and within deemed export control. Someone who only received a foreign-government scholarship before being hired is, in principle, not in category (2) (METI Q&A on clarifying deemed export control, Q50). Hiring is not prohibited. What you need is a design that controls access to relevant technology (encryption, AI, defense-related functionality) and a mechanism to assess whether prior METI licensing is required.

On January 31, 2025, METI published a draft amendment to the ministerial ordinance, and the revised supplementary export controls took effect on October 9, 20257. The catch-all controls were tightened there, which also affects deemed export decisions. What SaaS companies should do now is add "relationship with foreign governments, militaries, and foreign companies," "source of funding," and "current residence and travel history" to the hiring checklist, and formalize consents and declarations. Beyond paperwork, you need a design that scopes access by attribute — GitHub branch permissions, Snowflake roles, Kubernetes namespaces — so that scope can be narrowed by candidate profile.

I wrote more detail in A Practical Guide to Deemed Export Risk, but the scariest deemed export pattern is the one you notice after the hire. By the time you realize, the person has already touched the source repository, the audit trail is there, and you cannot walk it back. Whether HR, engineering, and legal can sit at the same table and discuss cases together is the real firewall.

The data residency, encryption, and API-delivery trio

When you talk about SaaS export control, data residency, encryption, and API delivery are inseparable. Each gets discussed on its own, but in operation they must be designed as a set — otherwise you will leave gaps.

On data residency, Japan has no restriction on the storage location itself under the Act on the Protection of Personal Information. But when you handle personal data in a foreign country, you must understand that country's personal information protection regime and then take the necessary and appropriate security control measures (Article 23, and section 10-7, "Understanding the external environment," of the Personal Information Protection Commission's General Guidelines). Providing personal data to a third party in a foreign country generally requires the individual's consent (Article 28). Note that an act amending the APPI and related laws passed the Diet on July 10, 2026 and was promulgated on July 17, 2026; apart from certain provisions it takes effect on a date to be fixed by cabinet order within two years of promulgation, so cross-border transfer practice will need to track the forthcoming cabinet orders, commission rules, and guidelines8. For government information systems, Digital Society Promotion Standard Guideline DS-310 (September 2023) applies. Using the government cloud within the regions and services its policy allows "keeps use within Japan," and for other cloud services, data centers are "in principle to be located in Japan"9. The exception is where redundancy or backup data centers abroad are desirable for availability or disaster recovery, provided the governing law and international jurisdiction have been checked and the specific litigation risk is low, or user data is otherwise protected by contract. Even then, user data stored in an overseas cloud whose leakage would pose a clear risk must be encrypted with a cipher on the latest CRYPTREC cipher list (e-Government recommended ciphers) or an equivalent, and depending on its sensitivity, protected with the user's own keys and key management (BYOK). Encryption and key management are not what permits an overseas data center; they are measures that must be taken when one is used.

Next, encryption. The cryptography covered by EAR Category 5 Part 2 (5A002.a) includes a symmetric algorithm with a key length in excess of 56 bits, an asymmetric algorithm based on factoring integers in excess of 512 bits (such as RSA), and elliptic-curve discrete logarithms in excess of 112 bits (technical note to 5A002, Supplement No. 1 to Part 774). Modern algorithms like AES-256, RSA-4096, and ECC almost all cross that line (subject to exceptions such as the Cryptography Note, Note 3, which excludes items generally sold to the public without restriction at retail). Japanese SaaS companies rarely implement these themselves; in practice they use AWS KMS, Azure Key Vault, or Google Cloud KMS. In that case, the division of responsibility for export control matters. The CSP has handled classification and filings at the infrastructure layer, but if you implement additional cryptographic features at the application layer, that layer is yours to classify.

Third, API delivery. Under Appendix 1-2(2) of the Service Transaction Circular discussed above, making a program usable through SaaS is itself a transaction for the purpose of provision, and if the program is controlled technology, it is a service transaction. Concretely: providing API specifications and technical manuals to overseas customers, providing implementation support as a customer success function to overseas engineers, and contributing technical know-how in joint development are all service transaction questions. Under the catch-all controls covering conventional weapons and WMD, screening whether your customer falls into a restricted country or a suspect end user is a must.

Running this trio on manual spreadsheets is honestly at its limit.

AI SaaS cannot relax, even "post-AI-Diffusion rescission"

In January 2025, the Biden administration published the "Framework for Artificial Intelligence Diffusion." It was an ambitious package that controlled the flow of AI model weights and advanced compute chips, reaching even into access controls via IaaS (Infrastructure as a Service). Many AI SaaS companies braced for impact — I remember it well.

But on May 13, 2025, BIS issued guidance rescinding that framework. Since then BIS has enforced the worldwide license requirement on advanced computing items (ECCNs 3A090.a, 4A090.a and related ".z" entries) only for destinations in Country Groups D:1, D:4, and D:5 — excluding those also listed in A:5 or A:6 — and for entities headquartered, or with an ultimate parent headquartered, in Country Group D:5 or Macau, wherever located10. The interim final rule of November 19, 2026 (91 FR 74970) then removed that worldwide requirement and replaced it with license requirements for Indonesia, Malaysia, Singapore, Brazil, and Thailand and for D:1, D:4, and D:5 (excluding A:5 and A:6) and the UAE, an end-use control for entities headquartered in D:5 or Macau (§744.23(a)(3)(i)(A)), and a control on data centers providing large volumes of compute to companies headquartered in D:5 or Macau (§744.24) (added November 20, 2026). Then on January 15, 2026, BIS's final rule "Revision to License Review Policy for Advanced Computing Commodities" was published in the Federal Register and took effect the same day. It moves the license review policy for exports from the United States to end users located in China or Macau of items at the NVIDIA H200 / AMD MI325X level (TPP under 21,000 and total DRAM bandwidth under 6,500 GB/s) from a presumption of denial to a conditional case-by-case review11. Read in isolation, that looks like loosening.

However, the parts that concern AI SaaS have not really loosened. Even the January 2026 final rule keeps a presumption of denial for reexports (including exports from abroad) and in-country transfers destined for Macau or a Country Group D:5 destination, and for entities headquartered or ultimately parented in Macau or a Country Group D:5 destination. On top of that, a license applicant must submit a list of "IaaS remote end users" located in — or whose ultimate parent is headquartered in — Belarus, China, Cuba, Iran, Macau, North Korea, Russia, or Venezuela, and BIS and the reviewing agencies decide on that basis case by case11. A Japanese AI SaaS offering a large language model via API that issues API keys to a mainland Chinese startup is already in the scope of that question. User-onboarding KYC (Know Your Customer), IP-based geoblocking, token usage limits, and audit log retention need to be designed together.

My personal read is that the AI Diffusion Rule rescission is best interpreted as "the framework is rescinded, but the individual rules continue and intensify." Let the surface-level easing news push you into "our AI SaaS is fine" and you may eat heavy penalties later. Civil penalties for EAR violations are capped, under the Export Control Reform Act (ECRA, 50 U.S.C. 4819), at the greater of twice the transaction value or a statutory maximum that is adjusted for inflation every year; as of July 2026 that maximum is USD 374,474 under ECRA and USD 377,700 under IEEPA (50 U.S.C. 1705(b))12. Add revocation of licenses and a prohibition on exporting, reexporting, or transferring items subject to the EAR (50 U.S.C. 4819(c)(1)(B) and (C)), and these become management risks that hit the top line directly.

Domestically, METI is likewise moving to explicitly cover AI and cloud APIs, as I laid out in The 2026 Amendments to AI, Semiconductor, and Cloud Export Controls. Combined with tighter security requirements in government and local government procurement, which I covered in Japan's local-government IT procurement rule taking effect in July 2027, export control infrastructure is becoming an upfront investment for Japanese AI SaaS to survive domestic government and municipal markets. The shift is from "do it to differentiate" to "do it or be cut in the first round."

Also readDeemed Exports and the "Specified Categories" in 5 Minutes | Hiring, Secondments and Joint Research Risks After the 2022 AmendmentWhat should we check when hiring engineers from overseas?

If you start on SaaS export control today in 2026

Running through these five topics, the common thread is that SaaS tends to become a party to export control before it notices. Unlike manufacturing, there is no physical customs event, so the trigger is hard to see. That invisibility is the biggest risk, and once an issue surfaces, customer churn and brand damage can be worse than the equivalent in physical goods smuggling.

A realistic starting sequence. First, refresh classification for your SaaS at the product level. EAR applicability, Foreign Exchange Act applicability, encryption classification — just holding these three in a single table moves the internal discussion forward. Second, embed an overseas-hire deemed export check into the hiring process. Don't leave it to HR alone; pull in legal and engineering, and close the loop all the way to post-hire access control. Third, re-evaluate ISMAP. The start date for the revised baseline has not been fixed yet, but the direction — detailed controls consolidated from 1,163 to 322 — is already on the table, so companies that had given up should re-read the requirements now.

Fourth, systematize customer screening. Manual effort cannot keep up with the pace of sanctions list updates and will miss entries. Offload it to a system such as an AI agent and let people focus on review and judgment. SaaS as a business now moves too fast for manual export control operations to keep up, which means export control operations need to run at the same cadence.

Export control is often seen as being at odds with "offensive" management, but watching the past three years — U.S.-China confrontation, the economic security trend, the EU AI Act, Japan's tightening of catch-all controls — I would say that companies that have built out their export control are precisely the ones who can accelerate overseas expansion. Reframe it not as defensive spend but as the ground floor for taking your product overseas. For SaaS companies, 2026 is the year that turning point lands.

If you want customer screening and the record of classification decisions to run as a routine process, you can contact us about TRAFEED. An overview of its features is in the TRAFEED product catalog (PDF).

References

Footnotes

  1. PwC Japan, "New developments in ISMAP: the broad revision of the ISMAP control baseline and the outlook for ISMAP going forward" https://www.pwc.com/jp/ja/knowledge/column/awareness-cyber-security/explanation-of-ismap2.html ↩

  2. e-Gov Public Comment, "Results of the public comment on the draft ISMAP Control Baseline and related documents," case no. 060250918 (draft published September 18, 2025 / comments closed October 17, 2025 / results published December 25, 2025 / 60 submissions) https://public-comment.e-gov.go.jp/pcm/1040?CLASSNAME=PCM1040&Mode=1&id=060250918 ↩ ↩2

  3. National Cyber Office, Digital Agency, MIC and METI, "[Reference] On the revision of the ISMAP Control Baseline (draft)," September 18, 2025 (detailed controls cut from 1,163 to 322) https://public-comment.e-gov.go.jp/pcm/download?seqNo=0000299114 ↩

  4. IIJ, "Cloud-based authentication service and cloud-based web security service registered with ISMAP" January 13, 2026 https://www.iij.ad.jp/news/pressrelease/2026/0113.html ↩

  5. IPA, "Security Requirements Compliance Assessment and Labeling Scheme (JC-STAR)" https://www.ipa.go.jp/security/jc-star/index.html ↩

  6. METI Trade Control Department, "Clarification of deemed export control operations" https://www.meti.go.jp/policy/anpo/law_document/minashi/meikakukanitsuite2.pdf ↩

  7. EY Japan, "METI publishes draft amendments — strengthening security trade control including catch-all controls" https://www.ey.com/ja_jp/technical/ey-japan-tax-library/tax-alerts/2025/tax-alerts-02-06-03 ↩

  8. Personal Information Protection Commission, "Promulgation of the Act Partially Amending the Act on the Protection of Personal Information and Related Acts (July 17, 2026)" https://www.ppc.go.jp/news/press/2026/260717/ ↩

  9. Digital Agency, "Digital Society Promotion Standard Guideline DS-310: Basic policy on appropriate use of cloud services in government information systems" https://www.digital.go.jp/assets/contents/node/basic_page/field_ref_resources/e2a06143-ed29-4f1d-9c31-0f06fca67afc/5167e265/20230929_resources_standard_guidelines_guideline_01.pdf ↩

  10. U.S. Bureau of Industry and Security, "Enhanced Favorable Treatment for the United Arab Emirates Under the Export Administration Regulations," Federal Register, July 14, 2026 (states the enforcement scope based on BIS guidance of May 13, 2025 and May 31, 2026) https://www.federalregister.gov/documents/2026/07/14/2026-14132/enhanced-favorable-treatment-for-the-united-arab-emirates-under-the-export-administration ↩

  11. U.S. Bureau of Industry and Security, "Revision to License Review Policy for Advanced Computing Commodities," Federal Register, published and effective January 15, 2026 (document no. 2026-00789) https://www.federalregister.gov/documents/2026/01/15/2026-00789/revision-to-license-review-policy-for-advanced-computing-commodities ↩ ↩2

  12. 15 CFR § 6.3 (U.S. Department of Commerce civil monetary penalty inflation adjustments; USD 374,474 under ECRA and USD 377,700 under IEEPA in the current eCFR) https://www.ecfr.gov/current/title-15/subtitle-A/part-6 ↩

This article was produced with the help of AI. A human verified the primary sources and edited the text before publication.

Read next

Articles that answer the question you are likely to have next.

  1. 1ISMAP and the SCS Evaluation System Explained from Scratch: Security Requirements for Government Procurement and Supply ChainsI want to understand government procurement security requirements from scratch.
  2. 2Deemed Exports and the "Specified Categories" in 5 Minutes | Hiring, Secondments and Joint Research Risks After the 2022 AmendmentWhat should we check when hiring engineers from overseas?
  3. 3Generative AI and Export Controls: 20 FAQs on Classification AI, Deemed Exports, and Cloud LLM PoliciesDoes pasting drawings or specifications into a generative AI tool count as a technology transfer under export control law?

This article is part of TRAFEED Media, our practical media on export controls and economic security

Back to TRAFEED MediaThis week's regulatory updates

52% of FY2024 export-control violations stem from classification errors. Is your team covered?

METI FY2024 data shows over half of violations stem from classification. Start with a free 5-question light check (~2 min, no email), then continue to the full 10-question report.

Contact About TRAFEED
Contact About TRAFEEDContact form (about 3 min)TRAFEED product briefFeatures & rollout in PDF

Share this article if you found it useful

Share

Newsletter

Get the latest AI and DX insights delivered weekly

Your email will only be used for newsletter delivery.

Free download

Recommended materials

China MOFCOM Lists (Control & Watch): 80-Entity Reference Sheet (through the 29 Jun 2026 wave)

All 80 entities on China MOFCOM's Control List and Watch List, in official / Chinese / English names. Being listed is a regulatory designation, not a judgment of the company — useful both for counterparty screening and for listed companies to understand where they stand. Based on primary sources (Announcements No. 11/12/27/28); as of 20 November 2026 there had been no additions or removals (checked through No. 56).

The BIS Affiliates Rule (50 Percent Rule) Readiness Checklist (2026)

A fill-in working checklist for trade compliance teams preparing for the BIS Affiliates Rule. Covers what the rule actually does (aggregation across owners and across lists, cascade/carry-forward, the rule of most restrictiveness, and why exactly 50% is in while below 50% is not automatically out), what is stayed and what is in effect now, where ownership data typically breaks, and a six-phase preparation list from scoping through governance. The stay was due to end on 9 November 2026; on that day BIS published a rule extending it to 10 January 2027 (91 FR 70789). The sheet is built to work whether the rule then returns, is stayed again, or is modified (as of 21 November 2026). Based on primary sources (90 FR 47201, 90 FR 50857, 91 FR 70789, 15 CFR, and China's Ministry of Commerce). Designation is a regulatory classification, not a judgement about a company; final determinations rest with your export-control officer and the authorities' current guidance.

EAR Classification Flow & EAR99 Practical Checklist (for exporters from Japan, 2026)

A fill-in working sheet covering "subject to the EAR? → ECCN on the CCL? → EAR99?", the crucial "when EAR99 still needs a license" (embargoes, end-use, end-user), de minimis / FDP, counterparty screening, and the two-track cross-check with Japan's classification (FEFTA / Appended Table 1). Based on primary sources (15 CFR, the Federal Register, BIS, METI); the EAR changes frequently, so treat the authorities' latest guidance and your export-control officer as authoritative.

See all materials

Related Knowledge Base

Export Control Guide

Solutions

Strengthen Export ComplianceStreamline compliance with complex export regulations

Talk with us about export-control operations

Share your screening, classification, or compliance workflow. We will map where TRAFEED can help—via our contact form (no cold booking).

Contact UsDownload Catalog

Related Articles

ISMAP and the SCS Evaluation System Explained from Scratch: Security Requirements for Government Procurement and Supply Chains

ISMAP and the SCS Evaluation System Explained from Scratch: Security Requirements for Government Procurement and Supply Chains

A beginner's guide to ISMAP, the pass-list for government cloud procurement, and the SCS evaluation system (★3/★4) launching around FY2026's end.

2026-07-16
Generative AI and Export Controls: 20 FAQs on Classification AI, Deemed Exports, and Cloud LLM Policies

Generative AI and Export Controls: 20 FAQs on Classification AI, Deemed Exports, and Cloud LLM Policies

Does pasting drawings or specifications into a generative AI tool count as a technology transfer under export control law?

2026-02-12
[2026 Edition] Export Control for Technical Drawings and Design Data | A Practical Guide to Deemed Export and Technology Transfer

[2026 Edition] Export Control for Technical Drawings and Design Data | A Practical Guide to Deemed Export and Technology Transfer

A practical guide to export control for drawings and design data, anchored on Japan’s deemed-export clarification effective 1 May 2022, with the penalty provision (FEFTA Article 69-7) and the separate technology management scheme, checked against the statutes as of November 2026.

2026-01-23
China Will Restrict Exit for Technology Cases from September 15: State Council Order No. 841

China Will Restrict Exit for Technology Cases from September 15: State Council Order No. 841

China brought State Council Order No. 841 into force on 15 September 2026. Its authorities may now bar Chinese citizens from leaving when they have violated export control or technology import-export rules and may endanger industrial or technological security. I read the text against the US deemed export rule and Japan's specified categories, and set out what is known as of 6 November 2026.

2026-08-09
What Are Dual-Use Items? A Plain Guide to Classification, Catch-All Controls and Why "We Only Make Commercial Products" Does Not Hold

What Are Dual-Use Items? A Plain Guide to Classification, Catch-All Controls and Why "We Only Make Commercial Products" Does Not Hold

A plain guide to dual-use items in Japanese export control, covering why commercial products are regulated, the four regimes, list and catch-all controls, classification, deemed export, and the penalty for exporting without a license, checked against the statutes as of November 2026.

2026-07-24
SpaceX's NCNT Supply Chain and Nationality Demands: Where Contract Terms End and Law Begins

SpaceX's NCNT Supply Chain and Nationality Demands: Where Contract Terms End and Law Begins

What would you do if a customer told you to remove people of a particular nationality from your factory floor?

2026-08-07