A cloud service that is not on Japan's ISMAP Cloud Service List is, in principle, outside what Japanese government agencies may procure. ISMAP, the Information system Security Management and Assessment Program, assesses and registers cloud services against government security requirements before agencies buy them. This guide is for cloud and SaaS providers planning a first registration, security teams running the annual renewal, and agency buyers reading a registration. It covers the scheme's governance, the three-part control criteria, the external audit and review cycle, ISMAP-LIU for low-impact SaaS, and what the criteria mean for service accounts, API keys and other machine identities. For how ISMAP sits beside FedRAMP, IRAP and C5, see the Government Cloud Authorisation Schemes Compared.
Status line (checked 14 November 2026): ISMAP has operated since June 2020, the first ISMAP Cloud Service List was published in March 2021 and ISMAP-LIU started in November 2022. The Digital Agency reported updates to the ISMAP Cloud Services List, the ISMAP-LIU list and the Auditor List on 31 August 2026. A draft amendment of the control criteria that cuts the detailed controls to a few hundred was published for comment in late 2025; PwC Japan's reading of the draft schedule puts the revised criteria into effect after March 2027, with transition arrangements still under consideration. Confirm the current documents on the ISMAP portal before you plan an audit.
Key takeaways
- Registration is the gate to government buyers. Government agencies and related agencies are, in principle, required to procure cloud services from the ISMAP Cloud Service List, so registration is a market entry condition, not a badge.
- The criteria have three layers. Governance criteria, management criteria and control measures, built from the JIS Q 27000 series (JIS Q 27001, 27002, 27014 and 27017), the Government Common Standards and NIST SP 800-53.
- It is a yearly cycle. Providers implement controls, are audited by a firm on the ISMAP Assessor List, and are reviewed by the operations support organisation (IPA) before the Steering Committee decides; the cycle repeats every year.
- ISMAP-LIU is lighter, not lax. SaaS for low-risk business and information processing can register under ISMAP-LIU with a reduced external audit scope, but every control objective must still be covered at least once in three years.
- Machine identities sit inside the control measures. The control measures explicitly include access control, account and ID management, and log collection and monitoring, so service accounts, keys and tokens need the same evidence trail as human administrators.
What it is and who it applies to
ISMAP grew out of Japan's Cloud By Default Principle, adopted in the June 2018 Basic Policy on the Use of Cloud Services in Government Information Systems. Instead of each ministry running its own security check on each cloud provider, ISMAP audits a service once and publishes it on a shared list that every agency can use. The brochure published jointly by the National center of Incident readiness and Strategy for Cybersecurity (NISC), the Digital Agency, the Ministry of Internal Affairs and Communications (MIC) and the Ministry of Economy, Trade and Industry (METI) sets out the model.
| Role | Body | What it does |
|---|---|---|
| Policy owners | NISC (now the National Cybersecurity Office), Digital Agency, MIC, METI | Own the scheme and its rules; consult on criteria changes |
| ISMAP Steering Committee | Committee under the ISMAP Basic Regulations | Sets registration rules and makes the final decision on each registration |
| Operations support organisation | Information-technology Promotion Agency, Japan (IPA) | Technical review of applications; hosts the ISMAP portal and the lists |
| ISMAP assessors | Audit firms on the ISMAP Assessor List | External audit against the criteria under the ISMAP Information Security Audit Guidelines; assessor registration is renewed every two years |
| Cloud service providers | IaaS, PaaS and SaaS providers | Implement controls, contract the assessor privately, apply and renew every year |
| Agencies | Government agencies and related agencies | Select services from the list and remain responsible for their own use of the service |
Who needs it: any provider that wants Japanese central government agencies as customers for IaaS, PaaS or SaaS. Foreign providers are eligible and several global platforms publish ISMAP registrations. Who does not: providers selling only to private Japanese firms, although regulated buyers sometimes ask for ISMAP as a proxy. Financial institutions follow their own rules; see the Japan FSA Cyber Security Guidelines.
Structure and key requirements
The ISMAP control criteria are organised in three categories. The current criteria contain more than 1,000 detailed controls: BSA's October 2025 comment counts 1,163 items, and PwC Japan describes just under 1,200 items in total. Detailed controls are numbered to four levels (X.X.X.X).
| Category | What it covers | Typical evidence |
|---|---|---|
| Governance criteria | Top management decisions on security, approval of strategy and policy | Board or executive minutes, approved security policy, risk appetite statement |
| Management criteria | Establishing, operating, maintaining and improving information security management (ISMS style) | Risk assessment, statement of applicability style control selection, internal audit, management review |
| Control measures | Concrete security measures: access control, account and ID management, redundancy, log collection and monitoring, and cloud-specific measures | Configuration records, access lists, log samples, change tickets, test results |
Adopting controls: under the current criteria the provider decides, control by control, whether to adopt each detailed control and records a reason for any it does not adopt. The review can reject a reason and send the provider back to audit. The September 2023 revision allowed reasons for non-adoption to be chosen from set options.
Recent revisions: KPMG Japan lists the changes that shaped today's audit:
- 22 September 2023: multi-year audit cycle and risk-based frequency for the control measures.
- 1 March 2024: generative AI added to the scope of the statement of applicability.
- 1 July 2024: four new detailed controls and four added examples.
- 1 August 2024: multi-year rotation of management criteria audits for providers holding a valid ISO/IEC 27001 certificate, inquiry-only update testing for stable controls, and a simplified list of audit targets.
The pending amendment: the draft amendment moves controls to high-level descriptions, makes them mandatory unless risk analysis shows a control is impossible or unnecessary to apply, moves the four-digit detailed controls to a reference Handbook and proposes a prior confirmation step for planned exclusions. The counts differ between drafts (322 in the version BSA commented on in October 2025, 253 in the December 2025 draft PwC analysed), so treat any number as provisional until the final text is published.
Identity and NHI requirements
ISMAP names account and ID management and access control as core control measures, and the criteria draw on NIST SP 800-53, whose AC and IA families apply to any account, human or not. Auditors sample populations, so every non-human account in scope becomes part of the population.
| NHI type in a cloud service | What the auditor will look for | Control to put in place |
|---|---|---|
| Service accounts for internal platform components | A complete list, an owner and an approval record for each | Inventory reconciled against the identity provider and cloud IAM; named human owner |
| Operator and automation accounts with privileged rights | Least privilege, approval of privileged grants, periodic review | Role-based access through a PAM tool, just-in-time elevation, quarterly review |
| API keys and tokens issued to tenants or integrations | Issuance, expiry, revocation and protection at rest | Short-lived tokens, key rotation policy, secrets vault, revocation on contract end |
| CI/CD pipeline credentials | Change control over production deployment | Workload identity federation instead of stored keys; deployment approval gates |
| Generative AI and agent features | Whether the service is in the generative AI scope added in March 2024 | Separate identities for agents, scoped permissions and logged tool calls |
- Owner for every account: an unowned service account is an audit finding waiting to happen. See How to assign owners to orphaned service accounts.
- Review evidence: keep dated review records for non-human accounts, not just staff. See the How to Run an Access Review for Service Accounts.
- Logging: log collection and monitoring is a named control area; make sure activity by automation accounts is attributable to the account and its owner, and retained for the audit period.
- Offboarding: remove keys and tokens when a component, tenant or contractor leaves. See the NHI Offboarding and Decommissioning Guide.
Implementation steps
- Confirm the route. Decide between ISMAP and ISMAP-LIU. ISMAP-LIU applies only to SaaS that handles confidentiality class 2 information for low-risk use, and starts with the procuring ministry's impact screening under the ISMAP-LIU Business and Information Impact Assessment Guidance.
- Define the service boundary. List the service, regions, data centres, subcontracted infrastructure and support locations in scope. Registration is per service, so a vague boundary multiplies audit work.
- Gap assess against the current criteria. Map existing ISO/IEC 27001, 27017 and SOC 2 controls to the ISMAP criteria and record adopt or not adopt, with reasons, for every detailed control.
- Use the portal's advance consultation. The ISMAP portal offers advance consultation before formal application; use it to test scope and non-adoption reasons early.
- Select an assessor from the ISMAP Assessor List. The audit contract is private between provider and assessor. Agree whether early application of revised criteria is possible; KPMG notes this depends on the audit firm being ready.
- Run the audit period. Operate controls through the audit period and collect evidence continuously, not at the end.
- Apply. Submit the Registration Application Form, the Statement, the Assessment Report and the Improvement Plan through the portal. IPA reviews; the Steering Committee decides; the service appears on the list.
- Plan the renewal on day one. The cycle repeats every year. Use the multi-year rotation options if you hold a valid ISO/IEC 27001 certificate, after consulting the operations support organisation.
Small vs large providers: a small SaaS company with one service and low-impact government use cases should test ISMAP-LIU eligibility with a sponsoring ministry first. A hyperscaler with many services gains most from one shared control set across services and from the multi-year rotation.
Evidence and assessment
| Stage | Output | Common reason for delay |
|---|---|---|
| Control selection | Adopt or not adopt decision per detailed control, with reasons | Non-adoption reasons rejected at review |
| External audit | Assessment Report under the ISMAP Information Security Audit Guidelines | Sample populations incomplete, such as missing service accounts |
| Findings | Improvement Plan | No dates or owners for remediation |
| Review | IPA technical review, Steering Committee decision | Scope description does not match the audited boundary |
| Renewal | Update audit; inquiry-only testing for qualifying stable controls | Control changes not reported, which removes eligibility for inquiry-only testing |
For update testing, KPMG summarises the conditions for inquiry-only procedures: no findings in the prior year's audit, a control that operates weekly or more often or has a population of 53 or more, and no reported change to the control in the update period.
Metrics that show the programme is working:
- Percentage of in-scope non-human accounts with a named owner and a review in the last quarter.
- Number of audit findings per renewal, and the share closed before the next audit period starts.
- Count of non-adoption reasons challenged at review.
- Mean age of API keys and tokens in the service boundary against the rotation policy.
- Days from end of audit period to registration or renewal on the list.
Mapping to other frameworks
ISMAP is built from standards that many providers already hold, which is why certificate reuse is a live policy topic: BSA cites the June 2025 Cabinet Office Regulatory Reform Implementation Plan, which calls for using other certifications to reduce audit items.
| ISMAP area | ISO/IEC 27001:2022 Annex A | NIST SP 800-53 Rev 5 | NIST CSF 2.0 |
|---|---|---|---|
| Account and ID management | 5.16 Identity management, 5.18 Access rights | AC-2, IA-5 | PR.AA-01 |
| Access control and privilege | 5.15 Access control, 8.2 Privileged access rights | AC-6, AC-17 | PR.AA-05 |
| Log collection and monitoring | 8.15 Logging, 8.16 Monitoring activities | AU-6 | DE.CM-03 |
| Use of cloud and suppliers | 5.23 Information security for use of cloud services | SA-9 | GV.SC-07 |
Related deep dives: the ISO 27001 Certification Guide, the NIST SP 800-53 Guide, the SOC 2 to ISO 27001 Mapping Guide and the FedRAMP Guide.
Common pitfalls
- Treating the ISO certificate as the audit. ISO/IEC 27001 helps with the management criteria rotation, but the control measures are audited against ISMAP's own detailed controls.
- Weak non-adoption reasons. "Not applicable" without risk reasoning is rejected and costs a re-audit.
- Missing machine accounts in samples. If the auditor's population for account management excludes service accounts and keys, the sample is incomplete and evidence must be rebuilt.
- Unreported control changes. A changed control loses inquiry-only update testing, and an unreported change becomes a finding.
- Planning for the old criteria only. The pending amendment changes control selection from optional adoption to mandatory with justified exclusions; design controls so they survive both.
- Using ISMAP-LIU outside its eligibility. LIU depends on the ministry's impact screening; a service later used for higher-impact work needs full ISMAP.
Practitioner checklist
- Confirm ISMAP or ISMAP-LIU route with the sponsoring ministry and the portal guidance.
- Write a service boundary that matches how the service is sold and operated.
- Record adopt or not adopt, with reasons, for every detailed control in the current criteria.
- Add every service account, API key, token and pipeline credential to the access control populations.
- Give each non-human account a named owner and a dated quarterly review.
- Select an assessor from the current ISMAP Assessor List and agree the audit period.
- Track the criteria amendment and map controls to the draft high-level controls now.
- Keep an Improvement Plan with owners and dates for every finding.
Standards and references
- NISC, Digital Agency, MIC and METI: ISMAP brochure
- Digital Agency: ISMAP-LIU
- Digital Agency: Updated ISMAP cloud service list
- ISMAP portal: About ISMAP
- BSA: Comments on the draft amendment of the ISMAP Control Criteria
- KPMG Japan: ISMAP revisions of August 2024
- PwC Japan: Explanation of the ISMAP criteria revision
Related NHI Mgmt Group resources: Government Cloud Authorisation Schemes Compared · South Korea ISMS-P and CSAP Guide · Japan APPI Guide · Non-Human Identity (NHI) Guide. This guide summarises Japan's ISMAP scheme as at 14 November 2026 and is not legal advice.