Hello, this is Ryuta Hamamoto from TIMEWELL.
Across this series I have written 10 country and region AI regulation pieces, 7 certification guides, 3 level-specific deep dives, and 2 incident analyses. That is 22 articles in total. Each stands alone. But readers keep telling me the same thing: without a single overview, "where do we start?" never becomes clear. Today that full map lives in one place.
As of May 2026, global AI regulation is completely fragmented. The EU leans hard on penalties. The US under Trump debates federal preemption. China mandates content labeling. Korea has an AI Basic Act in force. Japan runs AI Promotion Act Guidelines v1.2. On the certification side, ISO/IEC 27001, ISO/IEC 42001 (AIMS), ISMAP, and CSA STAR L1 through L3 all run in parallel. "Comply with everything" is not a plan. Priority is the only viable strategy.
This master guide links the 22 articles and lays out three things: a region × regulatory stance × effective-date matrix, a certification portfolio overview, and three priority axes for Japanese companies. I close with what the series taught me, and what I see as the strategic core for 2026–2027.
TL;DR
- Global AI regulation converges on three philosophies: rights-based (EU, Korea), innovation-first (US, Japan, ASEAN), state control (China)
- Maximum penalties: EU AI Act €35 million / 7% of worldwide revenue; China product blocks + registration removal; US California state-by-state
- Certifications run on two tracks: horizontal base (ISO 27001, ISMS) and vertical depth (ISO 42001 AIMS, CSA STAR, ISMAP)
- Japanese priorities are set by product export footprint, cross-border data, and customer scale
- Reading all 22 still does not create implementation skill. Implementation comes from hands-on drills (WARP SECURITY)
Full map of the 22-article series
Four clusters. Links below.
Cluster A: Regional AI regulation (PR-1–3)
Country-by-country deep dives into regulatory stance.
- EU AI Act Digital Omnibus (Regulation (EU) 2026/1744) — Annex III high-risk AI moves to December 2, 2027; Annex I to August 2, 2028; Article 50 transparency duties stay at August 2, 2026
- US federal AI policy and Trump preemption — xAI v. Weiser, NIST downgrade, federal preemption status
- California SB 53 / AB 2013 / SB 942 — Frontier model law, training-data transparency, industry stance split
- Colorado CAIA repeal and SB 26-189 ADMT — First comprehensive US state AI law repealed pre-effective date; narrower automated decision-making return
- Texas TRAIGA × New York RAISE — Republican vs Democratic state regulatory philosophies
- US state AI law patchwork (Illinois, Utah, Massachusetts) — Map of proliferating state laws without a federal statute
- UK AI regulation DUA Act × AI Growth Lab 2026 — Sector-based stance updates
- Canada after AIDA and PIPEDA — Post-AIDA federal gap; interim reliance on existing privacy law
- Japan AI Promotion Act and Business Guidelines v1.2 — No penalties; cooperation-based Japan model
- China AI-generated content labeling rules 2026 — Mandatory labeling from September; algorithm registration
- Korea AI Basic Act January 2026 — Second rights-based force after EU AI Act
- Vietnam AI law—ASEAN’s first comprehensive regime — Hard-law pioneer in ASEAN
- Singapore agentic AI governance — IMDA soft law plus implementation guidance
- India DPDP × AI governance guidelines — DPDP Act combined with AI Sutras
- LatAm / Middle East / Oceania regulation roundup — Peripheral-region trends
Cluster B: Certification guides (PR-4–5)
Systems for certifications worth obtaining.
- ISMS / ISO/IEC 27001 beginner guide — Information security management foundations
- ISO/IEC 27001 certification complete guide 2026 — Process, cost, transition schedules
- ISO/IEC 42001 AIMS primer 2026 — Structure of AI management system certification
- ISMAP government cloud security 2026 — Required for Japanese government procurement
- CSA STAR Level 1 self-assessment — Entry certification for cloud providers
- CSA STAR Level 2 third-party audit — Attestation vs Certification choice
- CSA STAR Level 3 continuous auditing — Not formally released; design to prepare, not wait
Cluster C: Incident analysis (existing)
Learning from real harm.
- Arup deepfake BEC: $25 million incident — BEC × generative AI × video conference harm
- EchoLeak indirect prompt injection CVE-2025-32711 — Microsoft Copilot vulnerability structure
- Slopsquatting AI hallucination abuse — npm/PyPI fake-package attacks
- Shadow AI in 71% of workplaces — Practical internal policy design
Cluster D: Implementation pieces (existing)
- EU AI Act August 2026: five steps for Japanese companies — Japanese roadmap
AI Security training, taken seriously
A 2-day intensive course fully aligned with OWASP, NIST, ISO/IEC 42001, and METI. Take it as executives, practitioners, or both.
Region × stance × effective-date matrix
Here are the regional regulation articles collapsed into one table, as of May 2026.
| Region | Main regime | Stance | Effective dates | Max penalties | Extraterritorial |
|---|---|---|---|---|---|
| EU | EU AI Act + Digital Omnibus | Rights-based | Aug 2, 2026 partial (transparency etc.); Dec 2, 2027 Annex III; Aug 2, 2028 Annex I | €35M / 7% revenue | Yes |
| US federal | NIST AI RMF (voluntary) + EO | Innovation-first | Voluntary | None | No |
| US California | SB 53 / AB 2013 / SB 942 | Rights-leaning | Phased 2026 | Litigation / injunction | Limited |
| US Colorado | SB 26-189 ADMT | Automated decisions only | Planned 2027 | Civil sanctions | No |
| US Texas | TRAIGA | Innovation-first | Sep 2026 | Administrative | No |
| US NY | RAISE Act | Rights-based | Under consideration | TBD | No |
| UK | DUA Act + AI Growth Lab | Sector-based | Phased 2026 | Sector statutes | Limited |
| Canada | Post-AIDA; PIPEDA operation | Interim | Existing | Privacy-law based | Yes |
| Japan | AI Promotion Act Guidelines v1.2 | Innovation-first (cooperation) | In operation 2026 | None (cooperation duties) | Limited |
| China | AI content labeling rules | State control | Sep 2025 | Product blocks / delisting | Yes |
| Korea | AI Basic Act | Rights-based | Jan 2026 | Administrative fines | Yes |
| Vietnam | AI law | Hard law | Phased 2026 | Administrative fines | Yes |
| Singapore | IMDA agentic AI governance | Soft law | Voluntary | None | No |
| India | DPDP + AI Sutras | Privacy-based | In operation 2026 | DPDP penalties | Limited |
I take three structural reads from this. First, the EU and Korea rights-based camp has real bite: penalties and extraterritorial reach hit Japanese firms hard. Second, the US is state-by-state with no federal statute. Third, China and Vietnam hard-law models can deliver commercial kill-shots through product blocks.
My forecast is blunt. 2026–2027 does not unify global rules. It locks in fragmentation. EU, US, and China as poles. Korea, Japan, ASEAN, Middle East, and LatAm each orbit one of them. Full unification is not near-term reality.
Certification portfolio: horizontal base and vertical depth
Alongside regional rules, you need the certification-side structure. The seven certifications in Cluster B, by purpose:
Horizontal base (foundation for any operator)
| Certification | Scope | Timeline | Cost (approx.) |
|---|---|---|---|
| ISO/IEC 27001 | Information security management overall | 6–12 months | ¥5–20 million |
| ISMS (Japan ISO 27001 path) | Domestic information security | ~6 months | ¥3–15 million |
These are base certifications regardless of business type. Upper certifications without them are effectively impossible.
Vertical depth (specialized by business type)
| Certification | Target operators | Relation to existing certs | Timeline |
|---|---|---|---|
| ISO/IEC 42001 (AIMS) | AI system developers/providers | Extends/embeds ISO 27001 | 6–12 months |
| ISMAP | Government cloud providers | ISO 27001 + government-specific | 12–18 months |
| CSA STAR Level 1 | Cloud service providers | Self-declaration (free) | 2–4 weeks |
| CSA STAR Level 2 | Cloud service providers | SOC 2 Type 2 or ISO 27001 + CCM | 6–12 months |
| CSA STAR Level 3 | Cloud service providers | Level 2 + continuous auditing | Not formalized |
A two-axis portfolio, horizontal base plus vertical depth, is the core certification strategy.
Recommended combinations by business type:
- Domestic-only SaaS: ISO 27001 → ISO 42001 (if AI operator)
- Overseas SaaS: ISO 27001 → CSA STAR Level 2 → ISO 42001
- Government cloud: ISO 27001 → ISMAP → CSA STAR Level 2
- AI model providers: ISO 27001 → ISO 42001 → CSA STAR Level 2
Details live in each certification guide. "Obtain everything" is budget- and resource-unrealistic. Narrow to two or three matched to customer base and regional strategy.
Three priority axes for Japanese companies: products, data, customers
This is the highlight of the piece. After 22 articles, the most common question is still "so where do we start?" My answer has not changed. Judge on three axes.
Axis 1: Geographic footprint of products / SaaS
- Selling into the EU → EU AI Act first (up to €35M penalties)
- Selling into the US → California statute cluster plus Texas, New York, and other states
- Selling into China → China AI content labeling (product-block risk)
- Selling into Korea → Korea AI Basic Act (in force Jan 2026; extraterritorial)
- Japan only → Japan AI Promotion Act guidelines suffice
Priority order: EU > China > Korea > US California > other states > Japan. That ranking is driven by penalty strength and extraterritorial reach.
Axis 2: Cross-border data
- Processing EU user data → EU AI Act + GDPR + EU Data Act
- Processing China user data → China cross-border data rules (special regimes)
- Storing customer data in the US → state privacy + AI rules
- Domestic data only → ISMS / Personal Information Protection Act baseline
Data that crosses borders triggers regimes separate from product placement. Even without EU product sales, using EU user data for AI training can trigger parts of the EU AI Act.
Axis 3: Customer scale and sector
- Large finance, pharma, federal government → CSA STAR Level 2 effectively required
- Government agencies → ISMAP required
- Providing AI models → ISO 42001 recommended
- SMB customers → ISO 27001 often enough (CSA STAR optional)
Larger customers mean stricter procurement security. Whether "ISO 27001 alone is enough" is decided by the largest customer's RFP requirements.
Combining the three axes
Field decision flow I actually use:
- Axis 1 hits EU, China, or Korea → prioritize that region's regime
- Axis 2 hits cross-border data → add that region's data-protection law
- Axis 3 hits large or government customers → add matching certifications (CSA STAR, ISMAP, etc.)
- None apply → Japan AI Promotion Act + ISO 27001 minimum set
Example: "SaaS sold in the EU with large financial customers" → EU AI Act + ISO 27001 + CSA STAR Level 2 as a required three-pack. If you also provide AI models, add ISO 42001.
Budget ranges: small next to penalties
Standard answer to "what does full response cost?" For mid-size SaaS (¥1–5 billion revenue):
| Item | Year-1 cost | Annual maintenance |
|---|---|---|
| ISO 27001 | ¥8–15 million | ¥2–4 million |
| ISO 42001 | ¥6–12 million | ¥2–4 million |
| CSA STAR Level 2 | ¥7–20 million | ¥3–8 million |
| EU AI Act (internal build) | ¥5–20 million | ¥2–5 million |
| China AI content labeling | ¥2–8 million | ¥1–3 million |
| Korea AI Basic Act | ¥2–8 million | ¥1–3 million |
| Full stack total | ¥30–83 million | ¥11–27 million |
Looks expensive until you put it next to the EU AI Act max of €35 million (~¥5.6 billion). Response cost is one to two orders of magnitude smaller. Including sales effects (vendor DD labor cuts, enterprise win-rate lift), I estimate 2–3 year payback.
Narrowing to the top three priorities compresses year-1 cost to roughly ¥15–30 million. That is the realistic investment decision.
Series takeaways: three principles against "regulation fatigue"
What I learned writing 22 articles:
Start from "you cannot keep studying all regulation." Only large firms with specialist teams can track the world. Deeply cover 3–5 regions that matter to you.
Share with executives that regulation is not "the security team's job." EU AI Act extraterritoriality, China product blocks, Korea penalties all hit sales and management decisions. InfoSec alone is structurally underpowered.
Certification is a beginning, not an ending. Taking ISO 27001 or CSA STAR and then relaxing leads to failed re-certification three years later for stale controls. Continuous operation is organizational culture.
Across the series, the conversion I most want is this: treat regulation as ally, not enemy. As pure cost, organizations exhaust. As sales weapon and change catalyst, response itself becomes competitive strength.
WARP SECURITY: filling "read 22, still cannot implement"
Writing 22 pieces confirmed a limit I already suspected. Knowledge of rules and certifications transfers via articles. Implementation skill does not.
TIMEWELL's WARP SECURITY offers a 3–6 month "implementation conversion" program for readers of the series:
- Regulation-mapping drills — Two-day workshop where participants judge which of the 22 regimes apply to their business, practicing the three-axis method.
- Certification hands-on — Simulated ISO 27001, ISO 42001, and CSA STAR Level 2 audits with real auditors. What will they ask, and how do you answer?
- Continuous-monitoring culture — Level 3 continuous-audit prep, ISMS PDCA, AI Act monitoring duties. Not "obtain and stop." Workshops include executives.
I position the program as a device to grow an in-house regulation-response team in 3–6 months. Articles are the map. Training is walking with the map.
Closing: what this series tried to say
After 22 articles, the point I most wanted to stress:
Japanese companies are two to three years behind the world on regulation response. The EU AI Act started with prohibited practices on February 2, 2025, added GPAI model rules and the penalty provisions on August 2, 2025, and picks up transparency duties (Article 50) on its general application date of August 2, 2026. Substantive high-risk obligations come later still: December 2, 2027 for Annex III and August 2, 2028 for Annex I. Korea's AI Basic Act took effect January 2026. China implemented labeling rules in September 2025. Many Japanese firms still think "we are a Japanese company, so this is not our problem."
That reading is fatally wrong. In the extraterritorial era, where you sell products, collect data, or serve customers, if any of those is overseas, regulation triggers. Operators who can truly say "no overseas footprint, not our issue" are already a minority.
If this series helps move Japanese regulation response from "two to three years behind" to "running alongside global standard," writing it was worthwhile. Start with any one article that matches your business. You do not need all 22. Use the depth and breadth your business needs.
That is the real purpose of this master guide.
Latest as of August 1, 2026
Since publication, the matrix "EU" row has advanced one stage. First, the Digital Omnibus this article originally described as a May 2026 provisional political agreement is now law: Regulation (EU) 2026/1744 (adopted July 8, 2026; published in the Official Journal as OJ L 2026/1744 on July 24, 2026; in force July 27, 2026).
August 2, 2026 is the EU AI Act's general application date, not a date of full application. What starts then is Chapter IV (Article 50 transparency duties), Chapter III Section 5 (Articles 40–49 on harmonised standards, conformity assessment, CE marking, and registration), and Article 101 (the European Commission's power to fine general-purpose AI (GPAI) model providers), among others. Those sanctions top out at €15 million or 3% of worldwide turnover (EU AI Act regulatory framework (European Commission)), which differs in target and ceiling from the €35 million / 7% maximum for prohibited practices referenced in the body.
Substantive high-risk obligations do not begin on August 2, 2026. Chapter III Sections 1–3 apply from December 2, 2027 for Annex III systems (Article 6(2)) and from August 2, 2028 for Annex I product-embedded systems (Article 6(1)). The authorised representative (Article 22), value chain (Article 25), deployer (Article 26), and fundamental rights impact assessment (Article 27) duties follow the same dates. The transitional rule for systems already placed on the market (Article 111(2)) is likewise no longer pinned to a fixed August 2, 2026 date: it now bites only where designs undergo significant changes on or after the Chapter III application date.
For reference, Chapter V on GPAI models and Chapter XII on penalties (Articles 99 and 100) have applied since August 2, 2025. On December 2, 2026 the newly added prohibited practices (Article 5(1)(ba) and (bb)) start, and providers of synthetic-content-generating AI placed on the market before August 2, 2026 must be compliant with Article 50(2) by that date (Article 111(4)). Article 50 itself remains an August 2, 2026 obligation; it was neither accelerated nor given a shortened grace period.
Domestically, a Personal Information Protection Act amendment bill covering AI training data use and surcharge systems was submitted to the Diet in April 2026; track it alongside certification and regulation work (Personal Information Protection Act three-year review). Enactment timing is not fixed; treat it as watch-and-wait on Diet debate.






