Hello, this is Ryuta Hamamoto from TIMEWELL.
“We want government deals. They told us to get ISMAP.” SaaS vendors have brought that line more often since around 2024. On the buy side—central ministries and government-related bodies—I also hear “ISMAP-LIU or full ISMAP—which services should we use?” This piece maps the whole program from both provider and user sides.
ISMAP (Information system Security Management and Assessment Program) is Japan’s own cloud security assessment regime, live since June 2020. As of June 2025, 77 services were on the cloud service list (see Codebook).
Why ISMAP exists — the logic of “government cloud first”
The 2018 Cabinet decision on basic policy for cloud use in government information systems set a cloud-by-default principle: cloud services as first choice. Ministry-by-ministry security assessments were inefficient and inconsistent.
ISMAP created a common front door: procure from cloud services the government has pre-assessed and listed. That raises procurement efficiency and a shared security floor (see National Center of Incident Readiness and Strategy for Cybersecurity).
Operating structure:
- ISMAP Steering Committee: decision body (NISC, Digital Agency, MIC, METI)
- ISMAP-MO (operations support): IPA
- Audit bodies: registered auditors run individual assessments
In my experience, SaaS firms eyeing government deals spend six months or more just deciding whether to pursue registration. Cost and effort are large. If I had to pick one early decision, it is whether your product actually needs full ISMAP or can start on LIU.
ISMAP vs ISMAP-LIU — which track to aim for
| Item | ISMAP (full) | ISMAP-LIU |
|---|---|---|
| Launch | June 2020 | November 2022 |
| Scope | All IaaS/PaaS/SaaS | SaaS for lower-risk work only |
| Management standards | ~1,000 controls | Reduced (~500) |
| External audit scope | Full set | Limited subset |
| Typical prep | 12–18 months | 6–9 months |
| Rough cost | Tens of millions of yen | ¥10–20 million |
ISMAP-LIU targets lower security-risk uses—light collaboration tools, e-learning, survey SaaS—not heavy all-ministry confidential document processing (see Digital Agency).
If you want government work but full ISMAP is too heavy, start with LIU and build a track record. Full registration makes sense when your core product will sit in government business-critical systems.
On the user side, systems handling information roughly equivalent to Confidentiality Level 3 tend to use full-ISMAP services; Level 2 processing often uses LIU-listed services.
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.
The ~1,000 management standards — what they actually are
Full ISMAP standards integrate and extend ISO/IEC 27001, ISO/IEC 27017 (cloud), NIST SP 800-53, and related material into about 1,000 controls, broadly:
- Governance (~100): leadership accountability, risk management structure
- Management (~400): ISMS-style processes, training, internal audit
- Controls (~500): technical, physical, and operational measures
External auditors evaluate that volume, including on-site checks. More than ten times ISO/IEC 27001’s 93 controls, re-evaluated in annual maintenance audits. That is the weight of ISMAP.
2023–2024 reviews produced the latest “ISMAP Management Standards (2024 revision)” (see PwC Japan), with stronger AI service and supply-chain risk language.
Three sticking points on Japanese implementation sites
1. Overlap with ISO/IEC 27001
Because ISMAP embeds 27001, certified companies often assume “~70% is reusable.” Reality is harsher. ISMAP-specific items (explicit cloud user responsibilities, sub-cloud provider management, and so on) do not reuse a 27001 SoA as-is. In cases I supported, more than 30% of documentation was rewritten from scratch even with 27001 already in place.
2. Working with the registered auditor
ISMAP external audit is denser than 27001 certification: risk assessment document exchange, sampling design, evidence formats—practices vary by auditor. Pick the wrong auditor first and annual surveillance stays painful. I have watched that choice haunt a program for years.
3. Responsibility boundaries when AI services are chained
This has become a major 2025+ field issue. If an ISMAP-listed SaaS calls OpenAI API or Azure OpenAI Service, how do you place third-party AI responsibility against the management standards? No clear public guideline yet; each provider invents a position. For AI-feature SaaS seeking ISMAP, transparency of data handling and explicit AI-output disclaimers are non-negotiable.
I see AI-feature SaaS ISMAP registration as a 2026 hard problem. Running ISO/IEC 42001 (AIMS) in parallel with ISMAP is the cleanest approach I can recommend today. Details: ISO/IEC 42001 AIMS beginner’s guide.
Buyer-side practice (government and local government)
For central ministries, selection from the ISMAP list is the principle—but if no listed service has the needed function, ministry-level alternative procurement is still possible. That “exception” is a field headache.
Local governments are not legally bound by ISMAP, but in practice “if the center uses it, we feel safer” drives municipal DX procurement. Since 2024, several ordinance-designated cities have written ISMAP-equivalent requirements into municipal cloud RFPs.
Buyer checklist:
- Set confidentiality level first: Level 3 → full ISMAP; Level 2 → LIU; lower → general cloud
- Check registration category: IaaS / PaaS / SaaS
- Continuity risk: annual surveillance can delist
- Multi-service chains: how ISMAP SaaS calling non-ISMAP services is treated
WARP SECURITY: case study on “ISMAP application reality”
Providers seriously considering ISMAP often tell TIMEWELL they “don’t know where to start.” The WARP SECURITY ISMAP track is case-study based, not pure lecture.
- Classification of the 77 listed services — categories, SoA patterns
- Product GAP workshop — draft self-assessment against ~1,000 controls in ~4 hours
- Auditor selection criteria — compare registered-auditor practices
- AI-feature SaaS strategy — document design when running ISO/IEC 42001 in parallel
I deliberately do not spend time on clause recitation. You can read the text. The hard part is implementing it in your business and negotiating with auditors.
Details: WARP SECURITY.
Latest as of July 2026
Anchors for AI-feature SaaS seeking ISMAP are slowly forming. On March 31, 2026, MIC and METI published AI Business Guidelines v1.2 (METI, March 31, 2026). As of July 2026 this remains soft law, but while ISMAP standards still do not fully spell out third-party AI responsibility, it is usable as a shared language for data handling and disclaimers. Separately, the Personal Information Protection Act amendment for AI training / statistical use (PPC; Cabinet decision and Diet submission April 7, 2026) is under deliberation—if enacted, design assumptions for AI-integrated SaaS can shift. See PIP Act 2026 amendment explained. Avoid overclaiming; watch implementation and final text.
Key takeaways — ISMAP is the government cloud “qualifier”; the main event is surveillance
- ISMAP launched June 2020; 77 services listed as of June 2025
- ISMAP-LIU (November 2022) is the reduced low-risk track—roughly half the controls and cost of full ISMAP
- ~1,000 management standards; more than 10× ISO/IEC 27001 volume; annual surveillance continues evaluation
- Even with 27001, ISMAP-specific items need separate build-out
- AI-feature SaaS ISMAP registration is a 2026 hard problem; parallel ISO/IEC 42001 is a strong approach
- Local governments are not legally in scope, but designated cities are writing ISMAP-equivalent requirements
My view: for providers chasing government procurement, ISMAP registration is only qualifying. The main match is quality under annual surveillance. “Get it once and stop” tends to crack around year three. Plan the surveillance calendar before you celebrate the listing.
Related: ISMS beginner’s guide, ISO/IEC 27001 certification complete guide, ISO/IEC 42001 AIMS beginner’s guide.
