Operators of AI above the compute threshold must run lifecycle risk management and report safety results
Download: JSON · MarkdownUnder AI Basic Act, Article 32
What this label means
- Verified
- — a named reviewer opened the official source and confirmed the record; the date and the reviewer are shown.
- Pending review
- — linked to the official source and in the queue for a reviewer to confirm.
- Source-linked
- — linked to the official source, not yet confirmed by a reviewer.
On this page 9 sections
In brief
Operators of AI above the compute threshold must run lifecycle risk management and report safety results is a legal requirement under AI Basic Act in South Korea (Article 32). It applies from 22 January 2026. The record carries 2 evidence examples and mappings to 2 frameworks.
- Instrument
- AI Basic Act
- Jurisdiction
- South Korea
- Nature
- Legal requirement
- Source reference
- Article 32
- Applies from
- 22 January 2026
- Who it binds
- Provider / developer, General-purpose AI model provider
- Evidence examples
- 2
- Framework mappings
- NIST AI Risk Management Framework 1.0, ISO/IEC 42001:2023
- Controls that meet it
- 3
- Official source
- Open official text
- Verification
- Verified against the official source 26 Sep 2026
What does it require?
An AI business operator whose AI system's cumulative training computation exceeds the threshold set by Presidential Decree must identify, assess and mitigate risks across the system's life cycle, build a risk management system to monitor and respond to safety incidents caused by the AI, and submit the results of these measures to the Minister of Science and ICT. The threshold and reporting form are set in the Decree.
Practical action
Track training compute against the decree threshold and prepare a safety report covering risk identification, mitigation and incident monitoring for submission to the ministry.
Who does it apply to?
Operators of AI systems whose cumulative training compute exceeds the Presidential Decree threshold, in practice frontier-scale model developers.
- Sectors
- Cross-sector / all sectors
- Use cases
- Generative AI and foundation models
Applies from:
Which controls meet this duty?
Satisfies: the control, operated properly, does the work the duty asks for. Supports: it contributes but the duty needs more. Each control page lists every other duty it serves, so work done once can be counted once.
-
satisfiesPolicyHead of AI safety · annualFrontier model safety and security framework
Serves 9 recorded duties · evidence: Published frontier safety framework, Dangerous-capability evaluation report, Threshold notification to an authority
Compute tracking, lifecycle risk assessment and reporting to the authority.
-
supportsTechnical measureAI security or safety lead · at launch and on material changeAdversarial and red-team testing for generative AI
Serves 8 recorded duties · evidence: Red-team exercise report, Red-team rules of engagement and scenario library, Adversarial findings tracker
Evidence for the risk identification step.
-
supportsProcessIncident coordinator · continuousAI incident management and regulatory reporting
Serves 14 recorded duties · evidence: AI incident response playbook, AI incident record, Incident report to an authority
Incident monitoring and response arm of the risk management system.
Templates that cover this duty
Generated from the records. Free · no account · links emailed to your work address. This duty is cited in each file with its source reference and a link back here.
- AI Risk Register (MIT AI Risk Repository taxonomy)
Register · XLSX · v4
- ISO/IEC 42001 Gap Assessment and Statement of Applicability
Assessment · XLSX · v3
- NIST AI RMF ↔ EU AI Act ↔ ISO/IEC 42001 Crosswalk
Crosswalk · XLSX · v5
- AI Audit Evidence Tracker
Register · XLSX · v1
What evidence would a reviewer expect?
| Evidence | Type | Notes |
|---|---|---|
| Lifecycle risk assessment and mitigation record | report | |
| Safety measures report submitted to the ministry | report |
Framework mappings
Original editorial crosswalks. They cite clause numbers only and reproduce no standard text; confidence reflects how direct the mapping is.
See every South Korea duty mapped this way →
| Framework | Reference | Note | Confidence |
|---|---|---|---|
| NIST AI RMF 1.0 | MAP 5.1, MEASURE 2.6, MANAGE 1.3, MANAGE 4.3 | Safety evaluation, risk treatment and incident response. | medium |
| ISO/IEC 42001:2023 | Clause 6.1.2, 6.1.3, 9.1 | Risk assessment, treatment and monitoring. | medium |
Frequently asked questions
Is this a legal requirement?
Yes. It is a legal requirement under AI Basic Act (Article 32).
Who must comply with this obligation?
Operators of AI systems whose cumulative training compute exceeds the Presidential Decree threshold, in practice frontier-scale model developers.
When does this obligation apply?
It applies from 22 January 2026.
What evidence shows compliance?
A reviewer would expect: Lifecycle risk assessment and mitigation record; Safety measures report submitted to the ministry.
Which frameworks map to this obligation?
It is mapped to NIST AI Risk Management Framework 1.0 MAP 5.1, MEASURE 2.6, MANAGE 1.3, MANAGE 4.3, ISO/IEC 42001:2023 Clause 6.1.2, 6.1.3, 9.1. These are editorial crosswalks with a stated confidence, not official mappings.
Which controls satisfy this obligation?
Frontier model safety and security framework; Adversarial and red-team testing for generative AI; AI incident management and regulatory reporting.
What should an organisation do in practice?
Track training compute against the decree threshold and prepare a safety report covering risk identification, mitigation and incident monitoring for submission to the ministry.
Cite this record
AIPolicyTracker (2026). “Operators of AI above the compute threshold must run lifecycle risk management and report safety results (AI Basic Act)” [AIPT-OBL-0062, verified 26 September 2026 by Bhaskar Bhatt]. https://aipolicytracker.org/id/AIPT-OBL-0062 (accessed 8 November 2026). Data licensed CC BY 4.0.
Permanent id AIPT-OBL-0062: it never changes or gets reused, and its address keeps working if this page moves.
Cite the official text alongside it: Framework Act on the Development of Artificial Intelligence and Establishment of a Foundation for Trust (AI Basic Act, Act No. 20676), Korea Ministry of Government Legislation, National Law Information Center, https://www.law.go.kr/lsInfoP.do?lsiSeq=268543.
BibTeX
@misc{aipolicytracker2026_operatorsofaiabovethecom,
author = {{AIPolicyTracker}},
title = {{Operators of AI above the compute threshold must run lifecycle risk management and report safety results (AI Basic Act)}},
year = {2026},
howpublished = {\url{https://aipolicytracker.org/obligations/south-korea-ai-basic-act-art-32-safety-measures-for-high-performance-ai}},
url = {https://aipolicytracker.org/obligations/south-korea-ai-basic-act-art-32-safety-measures-for-high-performance-ai},
urldate = {2026-11-08},
note = {Data licensed CC BY 4.0. Accessed 8 November 2026}
}
Change history
No change to this record's tracked fields has been recorded since 15 October 2026, when field-level history began.
Similar obligations in other instruments
- Manage systemic risk for high-impact general-purpose models — EU AI Act, European Union
- Large frontier developers must publish a frontier AI framework — California SB 53, California (United States)
- Large frontier developers must send periodic summaries of catastrophic-risk assessments to the state — California SB 53, California (United States)
- Measure and test trustworthiness characteristics (Measure) — NIST AI RMF, United States (voluntary)
Disclaimer: informational only, not legal advice. Verify every claim against the linked official sources and consult a qualified lawyer before acting.