South Korea runs two security certifications that decide who can operate large online services and who can sell cloud to the public sector, and both are being reshaped in 2026 and 2027. ISMS-P (and its security-only subset, ISMS) certifies an organisation's information security and personal information management system against 102 criteria. CSAP, the Cloud Security Assurance Program, certifies cloud services for use by government agencies and public institutions. This guide is for security and compliance leads at Korean and foreign companies, cloud providers targeting the Korean public sector, and auditors. It covers who must certify, the structure of each scheme, the evidence assessors expect, what the criteria mean for service accounts, API keys and other non-human identities, and the announced reforms. For the privacy law behind ISMS-P, see the South Korea PIPA Guide.
Status line (checked 14 November 2026): ISMS-P has been in force since 7 November 2018 under Article 32-2 of the Personal Information Protection Act (PIPA); ISMS is based on Article 47 of the Network Act. On 10 April 2026 the Ministry of Science and ICT (MSIT) and the Personal Information Protection Commission (PIPC) announced mandatory expansion and a three-tier ISMS-P structure, targeted for full implementation in 2027. For CSAP, MSIT and the National Intelligence Service (NIS) announced in April 2026 that CSAP and the separate NIS security review will merge into one NIS verification system, and Korean press reported in September 2026 that CSAP tiers will be replaced by N2SF grades, with implementation expected in the second half of 2027. Existing CSAP certificates are reported to remain valid. Check KISA, PIPC and MSIT notices before relying on any date here.
Key takeaways
- ISMS-P is 80 plus 22. The scheme has 16 management system criteria, 64 protection measure criteria and 22 personal information processing criteria; ISMS certification uses the first 80, ISMS-P all 102.
- Certification is mandatory for some. ISMS is mandatory for listed telecoms and internet data centre operators and for providers above revenue or user thresholds, and the 2026 reforms extend mandatory ISMS-P to large personal information controllers.
- CSAP gates the public sector. Government agencies and public institutions are required to use CSAP-certified cloud services; the Low tier allows logical separation, Medium and High require physical separation.
- Certificates carry annual checks. ISMS and ISMS-P certificates last three years with annual follow-up reviews, and CSAP certificates last five years with an annual reassessment.
- Access rights are an inspection focus. The December 2025 reform names access rights management, external internet-facing asset identification and patch management for intensive annual review, which puts machine accounts and keys squarely in scope.
What it is and who it applies to
| Item | ISMS / ISMS-P | CSAP |
|---|---|---|
| Legal basis | ISMS: Network Act Article 47; ISMS-P: PIPA Article 32-2 | Act on the Development of Cloud Computing and Protection of Its Users, Article 23-2, with an MSIT public notice |
| Policy owners | MSIT and PIPC | MSIT (merging into NIS verification under the announced reform) |
| Operator | Korea Internet and Security Agency (KISA); Financial Security Institute (FSI) for the financial sector | KISA or an assessment body appointed by MSIT |
| Examination bodies | KAIT, TTA and OPA, plus KISA for new and special areas | Evaluation body, then certification committee |
| Subject | The organisation's management system for a defined scope of services | A cloud service (IaaS, SaaS, DaaS) |
| Validity | Three years, annual follow-up review | Five years, annual reassessment |
Mandatory ISMS: Microsoft's compliance summary of the Network Act lists telecoms operators providing network services in Seoul and metropolitan areas, integrated data centre facilities, higher general hospitals and universities above size thresholds, and information network service providers above a sales threshold or with an average of 1 million or more daily users over the previous three months. The thresholds are set in won in the Enforcement Decree; check the decree for the current figures. Financial companies under the Electronic Financial Transactions Act are excluded and follow FSI rules; see South Korea Financial Cyber Rules.
Mandatory ISMS-P (announced): Shin and Kim reports that the April 2026 plan covers major public system operators, identity verification service providers and large personal information controllers above revenue and volume thresholds, in enhanced, standard and simplified tiers, with telecoms carriers and data centre operators expected in the enhanced tier. The live PIPA guide records mandatory certification provisions applying from 1 July 2027.
CSAP: any cloud provider that wants Korean government agencies or public institutions as customers. Under the National Cloud Computing Security Guidelines quoted by Microsoft, High covers matters of national significance and internal administrative operations, Medium covers non-disclosure business documents and operations, and Low covers public data with no personal information.
Structure and key requirements
ISMS-P criteria
| Area | Domains (number of criteria) | Total |
|---|---|---|
| 1. Management system | Setting up the foundation (6), risk management (4), operation (3), inspection and improvement (3) | 16 |
| 2. Protection measures | Policy, organisation and assets (3), personnel (6), outsiders (4), physical (7), authentication and authorisation management (6), access control (7), encryption (2), system introduction and development (6), system and service operation (7), system and service security (9), incident prevention and response (5), disaster recovery (2) | 64 |
| 3. Personal information processing | Collection (7), retention and use (5), provision (3), destruction (4), data subject rights (3) | 22 |
Shin and Kim describes ISMS-P as modelled on ISO/IEC 27001 and 27002. The certification flow published by the PIPC runs: application, preliminary examination and contract, examination team, examination, corrective measures and report, Certification Committee deliberation, certificate issue, then follow-up management.
CSAP tiers and requirements
| Tier | Systems | Separation | Other conditions (per BSA, 2024) |
|---|---|---|---|
| High | National significance, investigation and trial information, internal administration | Physical | Data residency, Korean encryption (ARIA, SEED), operations staff in Korea |
| Medium | Non-disclosure business documents and operations | Physical | As above |
| Low | Public data without personal information | Physical or logical | As above, still applied at Low |
The three tiers date from MSIT's January 2023 amendment. Microsoft's Azure CSAP certification, obtained on 20 November 2024 for Low tier IaaS, covered 64 controls in 14 sections spanning administrative, technical, physical and additional public institution measures. MSIT's 2024 proposed amendment, as summarised by BSA, would separate management consoles from the user service area for all grades and add High tier requirements including external network blocking, integrated security audit log management, and automation of account and access rights.
Announced CSAP reform: per the September 2026 Digital Today report of the NIS briefing, CSAP's High, Medium and Low tiers give way to N2SF grades C (Classified), S (Sensitive) and O (Open); S and O certification would not require physical separation, and S and O would allow overseas operations management and international standard encryption such as AES. Treat these as announced, not in force.
Identity and NHI requirements
Two ISMS-P domains, authentication and authorisation management (6 criteria) and access control (7 criteria), carry most identity obligations, and the encryption and operations domains cover keys and logs. Korean assessors examine user and administrator accounts; in practice, service accounts and API credentials sit in the same populations.
| ISMS-P domain | NHI exposure | Evidence to prepare |
|---|---|---|
| Authentication and authorisation management | Shared, default or unowned service accounts; privileged automation accounts | Account register including non-human accounts, owners, approval records, periodic review results |
| Access control | API keys and tokens reaching personal data stores; database accounts used by applications | Network and database access lists, key scopes, connection logs |
| Encryption | Keys and certificates protecting personal information | Key management procedure, rotation records, vault configuration |
| System and service security management | Credentials in code, pipelines and configuration | Secret scanning results, pipeline identity configuration, log review records |
| Outsider security | Vendor and integration credentials | Contracts, scoped integration accounts, revocation on contract end |
- Revocation risk: the December 2025 MSIT and PIPC measures allow revocation where a PIPA penalty follows harm to more than 10 million people, repeated violations, or intentional or grossly negligent violations, so a credential-led breach can now cost the certificate as well as the fine.
- Annual inspection focus: access rights management is named for intensive review, so a stale service account found in the annual check is a direct finding.
- CSAP automation: the proposed High tier items on automated account and access rights management favour providers that already manage machine identities through code and a central inventory. See the NHI Inventory Reconciliation guide.
- Secrets: keep credentials in a vault with rotation evidence. See the Secrets Management Guide.
Implementation steps
- Decide which certifications apply. Test the ISMS mandatory criteria and the announced ISMS-P thresholds; decide whether CSAP is needed and at which tier, given the reform timeline.
- Set the scope. List services, systems, sites and personal information flows. ISMS-P adds the 22 processing criteria, so map collection, use, provision and destruction for each flow.
- Gap assess against the 102 criteria. Reuse ISO/IEC 27001 controls where they fit, but evidence each Korean criterion; ISO evidence alone is not enough.
- Close identity gaps first. Build one account register covering human and non-human accounts, assign owners, remove shared and default accounts, and move secrets into a vault. These are the findings most likely in the annual check.
- Operate before you apply. Run the management system and controls long enough to produce operating evidence, including at least one internal audit and management review.
- Apply and remediate. Submit to KISA or the designated examination body; fix findings within the corrective measures period; the Certification Committee decides.
- Run follow-up management. Prepare for annual follow-up reviews and three-year renewal. If certification is cancelled, mandatory entities get a one-year grace period to reapply under the December 2025 measures.
- For CSAP, plan for transition. Track the N2SF guidance and grades; existing CSAP certificates are reported to remain valid through their five-year term.
ISMS or ISMS-P: choose ISMS (80 criteria) when the duty comes from the Network Act and the service processes little personal information, for example an infrastructure or data centre operator. Choose ISMS-P (102 criteria) when personal information processing is central to the service, when customers or public bodies ask for it, or when the announced mandatory ISMS-P thresholds may catch you; moving later from ISMS to ISMS-P means a second round of evidence for the 22 processing criteria. CSAP tier choice: the tier follows the customer's system classification, not the provider's preference, so agree the target systems with public sector buyers before designing separation.
Small vs large organisations: a growing online service near the user threshold should track daily users monthly and start ISMS early, since certification takes months. Large operators in the enhanced tier should expect more on-site testing and deeper annual reviews.
Evidence and assessment
| Stage | What assessors check | Typical gap |
|---|---|---|
| Preliminary examination | Scope, documents, readiness | Scope does not match the services actually offered |
| Examination | Criteria by criteria, documents, interviews, technical checks | Service accounts missing from access reviews; secrets in configuration |
| Corrective measures | Proof each finding is fixed | Fix applied to one system, not the pattern |
| Follow-up review | Annual check, with focus on internet-facing assets, access rights and patching | Asset inventory out of date |
| CSAP reassessment | Annual check of certified cloud service | Undocumented changes to separation or console access |
Metrics:
- Share of non-human accounts in the ISMS-P scope with a named owner and a review in the last quarter.
- Findings per annual follow-up review, and days to close.
- Percentage of internet-facing assets in the asset inventory at the annual check.
- Median age of API keys and tokens with access to personal information.
- Daily active users and revenue against mandatory thresholds, tracked monthly.
Mapping to other frameworks
| ISMS-P area | ISO/IEC 27001:2022 Annex A | NIST SP 800-53 Rev 5 | NIST CSF 2.0 |
|---|---|---|---|
| Authentication and authorisation management | 5.16, 5.17, 5.18, 8.2 | AC-2, IA-5 | PR.AA-01 |
| Access control | 5.15, 8.5 | AC-6, AC-17 | PR.AA-05 |
| System and service security management | 8.15, 8.16 | AU-6 | DE.CM-03 |
| Outsider security | 5.19, 5.23 | SA-9 | GV.SC-07 |
For Japan's equivalent government cloud scheme see the Japan ISMAP Guide; for a cross-country view see APAC Cybersecurity Laws Compared and the ISO 27001 Certification Guide.
Common pitfalls
- Assuming ISO/IEC 27001 equals ISMS-P. The Korean criteria include personal information processing and specific protection measures that ISO certificates do not evidence.
- Missing the threshold. Rapid user growth can make ISMS mandatory before anyone notices; monitor the three-month daily user average.
- Human-only account reviews. Reviews that skip service accounts and keys fail the authentication and authorisation management criteria.
- Treating the certificate as protection. Revocation now follows serious PIPA penalties, so certification and breach prevention are linked.
- Building for the old CSAP only. Separation, encryption and personnel location rules are changing under N2SF; design for both until the new guidance is final.
Practitioner checklist
- Check ISMS mandatory criteria and the announced ISMS-P thresholds against current revenue and users.
- Map every personal information flow to the 22 processing criteria.
- Build one account register covering staff, administrators, service accounts, API keys and tokens.
- Assign owners and run quarterly reviews of non-human accounts.
- Keep internet-facing asset inventory and patch records ready for the annual review.
- Store credentials in a vault and keep rotation evidence.
- For CSAP, confirm tier, separation design and the N2SF transition position with your public sector customers.
- Track KISA, PIPC, MSIT and NIS notices quarterly through 2027.
Standards and references
- PIPC: ISMS-P certification
- Microsoft Learn: Korea Cloud Security Assurance Program (CSAP)
- Microsoft Learn: Korea Information Security Management System (K-ISMS)
- BSA: Comments on proposed CSAP amendments (2024)
- Shin and Kim: ISMS-P mandatory expansion (April 2026)
- Asia Economy: ISMS-P revocation measures (December 2025)
- Asia Economy: Government unifies public cloud verification (April 2026)
- Digital Today: Public cloud security certification overhaul (September 2026)
Related NHI Mgmt Group resources: South Korea PIPA Guide · Government Cloud Authorisation Schemes Compared · South Korea AI Basic Act Guide · Non-Human Identity (NHI) Guide. This guide summarises South Korea's ISMS-P and CSAP schemes as at 14 November 2026 and is not legal advice.