- ClassificationCategoryCloud SecurityDomainCloud SecurityFramework FamilyOther
- Regulatory ContextTypeFrameworkLegal InstrumentProgramSectorGovernment SectorIndustryGovernment & Public Sector
- Region / PublisherRegionAsia-PacificRegion DetailJapanPublisherGovernment of Japan: National Cybersecurity Office (Cabinet Secretariat), Digital Agency, MIC and METI; operation support by IPA
- VersioningVersionISMAP Control Standards of June 3, 2020, last revised August 1, 2024; ISMAP-LIU from November 1, 2022; revision released for public comment September 2025Effective DateJune 2020 (operation began); first Cloud Service List March 2021Issue DateJanuary 30, 2020 (basic framework decision); rules of June 3, 2020
- AdoptionAdoption ModelIndustry RequirementImplementation ComplexityHigh
- Official ReferenceOpen Link in New TabSource
License included / downloadable: Yes
The ISMAP rules, Control Standards and lists are published free by the Japanese government on the ISMAP portal; controls taken from JIS Q 27017 and JIS Q 27014 are not published for copyright reasons. The platform links to the government's page.
Framework text is licensed by its publisher and is included only where stated above.
- ISMAP is the Japanese government's program for evaluating and registering cloud services against the government's security requirements.
- Operation began in June 2020 and the first Cloud Service List was published in March 2021; it is not a statute.
- The National Cybersecurity Office, the Digital Agency, MIC, and METI run it through the ISMAP Steering Committee, with IPA supporting daily operation.
- A provider states its compliance with the ISMAP Control Standards, a registered audit body audits the statement, and the Committee registers the service.
- Agencies procure, in principle, from the ISMAP lists, including the ISMAP-LIU list for low-risk SaaS since November 1, 2022.
Overview
ISMAP (Information system Security Management and Assessment Program, in Japanese the Security Evaluation Scheme for Government Information Systems) is the Japanese government's program for evaluating and registering cloud services against the government's security requirements, so that national agencies can procure from a list of pre-assessed services. It is not a statute: the Cyber Security Strategic Headquarters decided its basic framework on 30 January 2020, operation began in June 2020, and the first Cloud Service List was published in March 2021. Government agencies generally procure from the ISMAP lists, so a cloud provider that wants to sell to them seeks registration.
Four bodies are responsible for the program: the Cabinet Secretariat's National Cybersecurity Office (NCO, named as NISC in the 2020 rules), the Digital Agency, the Ministry of Internal Affairs and Communications (MIC) and the Ministry of Economy, Trade and Industry (METI). They set up the ISMAP Steering Committee under them, which decides registrations and rules, and the Information-technology Promotion Agency (IPA) runs the daily operation as the ISMAP operation support agency. A provider states its compliance with the ISMAP Control Standards, an ISMAP-registered audit body audits the statement, and the Steering Committee registers the service after an IPA technical review.
ISMAP has two lists: the ISMAP Cloud Service List and, since 1 November 2022, the ISMAP-LIU list for low-risk SaaS (ISMAP for Low-Impact Use). The Control Standards were last revised on 1 August 2024 and a larger revision was released for public comment from 18 September to 17 October 2025; the Steering Committee was still deciding the schedule for that revision on 28 August 2026.
Why does it matter?
ISMAP turns a government procurement preference into a defined path: Basic Regulation section 2.3 says agencies procure, in principle, from the ISMAP lists, and the lists are public, so registration is how a provider shows an agency that its controls were audited against the government's own standard.
Key benefits include:
- A route into government procurement
Registered services appear on the public ISMAP lists, and agencies in principle buy from those lists; an agency does not have to check the provider's controls itself.
- An audited assertion, not a self-assessment
The provider asserts compliance with the Control Standards (Standards 2.2) and a registered audit body examines design (design evaluation) and operation (operating effectiveness evaluation).
- Continuing obligations
Registered providers must promptly report incidents with a serious impact on users (Basic Regulation 3.7) and notify material control changes (3.8).
- Public transparency
The list shows the service name, scope, audit period and which control objectives apply, so agencies see what the registration covers.
- Two tiers
ISMAP-LIU, in operation since 1 November 2022, gives low-impact SaaS a separate registration rule.
How does it work?
The program separates roles. The Steering Committee sets the Control Standards and the registration rules and decides every registration (Basic Regulation 7.1); IPA handles the work under the ministries' supervision (9.3); audit bodies are registered separately and must meet the ISMAP audit body requirements (Chapter 4); and procuring agencies keep responsibility for the security of the overall system they procure (7.5).
A provider declares scope and controls in a written statement, selects a registered audit body, and receives an audit report (3.2). It then applies to the Steering Committee (3.1). The committee accepts the application, reviews it and, if appropriate, registers the service on the public list (3.3 to 3.6). IPA's technical review checks, among other points, that the basic assertion requirements are met and that any minor findings have an improvement plan.
Registration is valid until one year and four months after the last day of the audited period, and the provider must apply to renew before then (3.5). The Steering Committee can monitor, require re-audit, require re-application, and suspend or remove a registration (5.1 to 5.4).
Key Elements
- Control Standards structure
Governance criteria for executive management (based on JIS Q 27014), management criteria (plan, do, check, act and risk communication) and control criteria, made of control objectives (three-digit numbers) and detailed controls (four-digit numbers).
- Basic assertion requirements
Governance and management criteria apply in principle in full; all control objectives apply unless a reason makes one inapplicable; detailed controls ending B or PB apply in principle, and other detailed controls are selected with reasons recorded.
- Source standards
The standards build on the 2016 cloud information security control standards (JIS Q 27001:2014, JIS Q 27002:2014, JIS Q 27017:2016) and reference the government's common cybersecurity standards and NIST SP 800-53 Rev. 4; they assume Confidentiality Class 2 information.
- Audit period and validity
The audit period is at most one year and consecutive periods must have no gap; a shorter period needs a three-month minimum operating period; registration lasts to one year and four months after the period ends.
- Registered lists
The ISMAP Cloud Service List, the ISMAP-LIU Cloud Service List and the ISMAP Audit Body List, all public, published on the ISMAP portal run by IPA.
- Revision in progress
The 2025 draft revision reflects the revised JIS Q 27001 and 27002, references the 2025 government common standards and NIST SP 800-53 Rev. 5, and reduces the number of controls.
What does it cover?
ISMAP applies to cloud services offered to Japanese national government agencies, independent administrative agencies and designated corporations, which are the procuring bodies named in Basic Regulation 1.4.7. It covers one named cloud service and a defined scope, region and audit period, and any underlying cloud service outside the assertion must itself be on an ISMAP list (Standards 2.2.2). The Control Standards assume Confidentiality Class 2 information, the class most handled by government, and ISMAP-LIU covers SaaS used for lower-risk work and information. Private organizations may refer to the public lists but are not bound by ISMAP.
What are its objectives?
ISMAP's stated purpose is to ensure the security level of government cloud procurement by evaluating and registering cloud services in advance, so that cloud services can be adopted smoothly (Basic Regulation 1.2).
Evaluate and register cloud services that meet the government's security requirements before agencies procure them.
Build the evaluation on information security audit methods that the private sector already uses, by registered audit bodies.
Give agencies public, comparable information on each service's scope and controls instead of separate checks.
Keep registrations current through monitoring, incident reporting, change notification and annual re-audit.
Offer a lighter route for low-impact SaaS through ISMAP-LIU.
Framework in Context
ISMAP sits within the government's cloud-by-default policy and its common cybersecurity standards. The Control Standards map to the government's common standards (annex tables 4 and 5) and to NIST SP 800-53 (tables 6 and 7), and rest on ISO/IEC 27001, 27002, 27014 and 27017 through their Japanese JIS Q equivalents. An ISO/IEC 27001 certificate does not register a service: ISMAP requires its own written assertion, audit and Steering Committee decision. Because the program is a procurement scheme, not a law, its scope changes by Steering Committee decision, which the NCO publishes as minutes.
Common Framework Mappings
Organizations map ISMAP to the frameworks below so one set of controls and audit evidence serves the Japanese government's audit and other assurance programs.
Mapped frameworks include:
CSA STAR
FedRAMP Rev. 5
ISO 27001:2022
ISO 27017
ISO 27018
ISO 27701
NIST CSF 2.0
NIST 800-53 Rev.5
How SmartSuite Supports ISMAP
SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.
Use Compliance Management to hold the ISMAP Control Standards as requirements with owners, linked controls, testing and evidence, and Third Party Risk Management to track the underlying services and suppliers a cloud service depends on. A provider preparing for audit can keep its assertion scope, audit period, findings and improvement plans in one place. This supports an audit; it does not register a service, and SmartSuite makes no ISMAP registration claim.
Assertion Scope Register
Record the cloud service name, scope, region and the underlying services used, with owners, as the written statement of Standards 2.2 requires.
Control Objective and Detailed Control Selection
Hold governance, management and control criteria with the B and PB controls marked, and record the reason for every excluded objective or unselected detailed control.
Audit Period and Registration Calendar
Track the audit period (maximum one year, no gaps), the three-month minimum for shorter periods and the expiry set at one year and four months after the period ends.
Findings and Improvement Plans
Log audit findings with owners, the improvement plan and the deadline, which IPA's review expects within two months of the report date for minor findings.
Incident and Change Notifications
Run a record for incidents with a serious impact on users (Basic Regulation 3.7) and material control changes (3.8) with notice dates and responsible people.
Underlying Service Oversight
Track each underlying cloud service in Third Party Risk Management and whether it is on an ISMAP list, as Standards 2.2.2 requires for services outside the assertion.
Related frameworks

CSA STAR is the Cloud Security Alliance's public registry for cloud assurance: a CAIQ self-assessment at Level 1, an ISO/IEC 27001 or SOC 2 audit at Level 2, built on CCM v4.1.

FedRAMP Rev5 is the legacy FedRAMP certification type: NIST SP 800-53 Rev. 5 baselines, 3PAO assessment and agency authorization for cloud services used by U.S. agencies.

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

ISO/IEC 27017:2026 gives cloud security control guidance for customers and providers, built on ISO/IEC 27002:2022, with four cloud-specific controls; it replaced the 2015 edition.

ISO/IEC 27018:2025 gives guidelines for protecting PII in public clouds acting as PII processors, built on ISO/IEC 27002:2022 with an extended control set.

ISO/IEC 27701:2025 specifies requirements for a stand-alone privacy information management system (PIMS) for PII controllers and processors, replacing the 2019 edition.
Frequently Asked Questions For Japan ISMAP (Information System Security Management and Assessment Program)
ISMAP, the Information system Security Management and Assessment Program, is the Japanese government's program for evaluating and registering cloud services that meet its security requirements. The National Cybersecurity Office, the Digital Agency, MIC and METI are responsible for it, a Steering Committee decides registrations, and IPA is the operation support agency (Basic Regulation 1.4 and 9.3).
It is not a law, and registration is not mandatory for providers in general. Procuring government agencies are expected, in principle, to buy from the ISMAP lists (Basic Regulation 2.3), so a provider that wants to sell cloud services to national agencies needs a registered service. A registration is a decision of the Steering Committee, not an ISO-style certificate.
The provider states its compliance with the ISMAP Control Standards, selects a registered audit body, and receives the audit report (Basic Regulation 3.2). It applies to the Steering Committee, which reviews the application with IPA's technical review and, if appropriate, registers the service on the list (3.3 to 3.6). Registration is valid to one year and four months after the end of the audited period (3.5).
ISMAP for Low-Impact Use (ISMAP-LIU) is a track within ISMAP for SaaS services used for low-risk work and information. It has its own registration rule and list, and it has been in operation since 1 November 2022 (Basic Regulation 1.3 and 1.4.13).
They build on the 2016 cloud information security control standards, which follow JIS Q 27001:2014, JIS Q 27002:2014 and JIS Q 27017:2016, with JIS Q 27014:2015 for governance, and reference the government's common standards and NIST SP 800-53 Rev. 4. The last revision was on 1 August 2024. A draft revision reflecting the revised JIS Q 27001 and 27002 and NIST SP 800-53 Rev. 5 went to public comment from 18 September to 17 October 2025.

Put this framework to work in SmartSuite
Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.


