OpenAI Shelves GPT-6.1 Astra After Safety Tests: What Went Wrong?
OpenAI shelved GPT-6.1 Astra after safety tests flagged scope, authorization and action-reporting issues. See what is confirmed and what remains...
Learn how to apply a practical AI risk management process covering risk identification, analysis, prioritization, treatment, control validation, monitoring, and continuous improvement using NIST AI RMF and ISO standards for governance and accountable AI deployment.
Identifying an AI risk is only the beginning of AI risk management. Organizations also need a repeatable way to decide who owns the risk, how serious it is, what response is justified, whether controls work, and when the assessment must be revisited.
An AI risk management process is a structured, repeatable method for identifying, analyzing, evaluating, treating, controlling, monitoring, and documenting risks created or affected by AI systems.
Effective AI risk management should be proportionate to the system's context and potential consequences. A low-impact productivity feature does not require the same assessment depth as an AI system influencing employment, healthcare, finance, safety, or legal rights. The seven-step workflow below moves from context and identification through analysis, prioritization, treatment, control, and ongoing review. It does not end when a mitigation is introduced.
In this blog, you will learn how to apply a seven-step AI risk management process covering context, identification, analysis, prioritization, treatment, control validation, monitoring, and continuous improvement.
Effective AI risk management begins with defined scope, context, ownership, and risk criteria.
Risk identification should consider intended use, foreseeable misuse, stakeholders, and system dependencies.
Risk and impact are related but should not be treated as identical.
Risks should be analyzed and prioritized before mitigation resources are assigned.
Controls must be implemented, tested, and supported by clear accountability.
AI risks and controls require continued monitoring, documentation, and review.
The AI risk management process moves an organization through a repeatable sequence: context, identification, analysis, evaluation, treatment, control, and monitoring. It is a decision process, not simply the creation of a risk register.
A useful process produces evidence. That evidence should show what was assessed, who owns each material risk, which assessment criteria were applied, how risks were prioritized, what treatment was selected, whether controls were effective, who accepted any residual risk, and what monitoring or reassessment is required.
The broader field of AI risk management also covers risk categories, governance structures, recognized frameworks, organizational responsibilities, and lifecycle considerations. This article concentrates on the operational workflow teams can apply to a specific system or use case.
ISO/IEC 23894:2023 supports this integrated approach. It provides guidance for organizations that develop, produce, deploy, or use AI and is intended to help them incorporate AI risk management into relevant activities and functions rather than treat it as an isolated, one-time exercise.
These seven steps synthesize recognized AI and general risk-management practices into an operational workflow. They are not presented as a mandatory sequence prescribed by NIST or ISO.
|
Step |
Main question |
Key output |
|
1. Establish context |
What are we assessing, and who owns it? |
Scope, context, owner, and criteria |
|
2. Identify risks |
What could go wrong and who could be affected? |
Documented risk scenarios |
|
3. Analyze |
How likely and consequential could the risk be? |
Risk analysis |
|
4. Evaluate |
Which risks require action first? |
Priorities and treatment decisions |
|
5. Select treatment |
What should be done about the risk? |
Risk-treatment plan |
|
6. Control |
Are safeguards implemented and effective? |
Controls, evidence, and residual-risk assessment |
|
7. Monitor |
Has the risk, system, or context changed? |
Monitoring results and reassessment decisions |
Define what is being assessed before rating risk. Record the system or use case, purpose, users, stakeholders, business and decision context, relevant data, dependencies, and operating environment. Data pipelines, vendors, integrations, human reviewers, and downstream users can materially change the risk profile.
Assign an owner and define risk criteria or acceptance conditions for later prioritization and residual-risk decisions. A clear AI governance framework should establish who can approve, restrict, escalate, or stop a use case. The voluntary NIST AI Risk Management Framework places governance across its other functions, reinforcing the importance of accountability, policy, processes, and context.
Describe what could go wrong, who could be affected, and when harm may occur. Consider intended use and foreseeable misuse, data, model behavior, human interaction, automation, third parties, cybersecurity, privacy, fairness, reliability, legal exposure, and downstream use.
Do not limit identification to technical failures. A recruitment tool may create inaccurate recommendations, unfair outcomes, privacy problems, inappropriate reliance, or weak human oversight. Write scenarios connecting a source or event to a consequence rather than using labels such as "bias risk."
Assess likelihood, severity, scale, affected people or processes, duration, reversibility, exposure, uncertainty, and existing safeguards. Give controls credit only when evidence shows they are implemented and effective.
Impact is a consequence or effect. Risk incorporates uncertainty about whether it may occur and how consequential it could be. For a deeper explanation of the distinction between AI risk and AI impact, including how the concepts should be used in assessment and prioritization, explore our detailed guide.
Document uncertainty rather than presenting ratings as objective facts. Incomplete data, changing user behavior, and rare outcomes should influence the rating and the need for monitoring or more evidence.
Analysis estimates significance. Evaluation determines action. Compare each risk with organisational criteria, tolerance, legal duties, stakeholder effects, business criticality, severity, and control effectiveness.
Prioritise risks requiring immediate treatment, investigation, senior review, monitoring, or documented acceptance. A numeric score must not hide context. Severe, widespread, or irreversible outcomes may warrant attention even when the likelihood is lower.
Record the decision and rationale so later reviewers can judge whether the response was proportionate.
For each material risk, decide whether to avoid the use, change the system, reduce exposure, improve data or testing, add oversight, limit functionality, alter deployment, or accept residual risk through an authorized route. For a deeper look at treatment options, control measures, and residual-risk decisions, see our guide to AI risk mitigation.
Treatment should address the risk's causes, pathways, or consequences. Generic controls may create activity without reducing exposure. The chosen response should state the intended risk reduction, responsible owner, evidence requirement, completion date, and escalation route.
The EU AI Act provides a regulated example. Article 9 requires iterative risk management for high-risk AI systems within scope, including identification, evaluation, targeted measures, and residual-risk consideration. This is not a universal requirement for every AI application.
Selecting treatment is not the same as implementing an effective safeguard. AI Risk Controls may be technical, organizational, procedural, human, contractual, or monitoring-based. Define each material control's purpose, owner, expected risk reduction, evidence, validation method, limitations, and review frequency.
Test controls under realistic conditions. An unreachable approver, an ignored alert, or a human-review step without enough time and competence provides weak protection despite looking complete.
Reassess residual risk and decide whether it is acceptable, needs more treatment, or requires escalation. Technical, procedural, organizational, and human safeguards should each be traceable to a specific risk cause, pathway, or consequence.
After deployment, monitor performance, incidents, complaints, control failures, emerging risks, data changes, model updates, integrations, new uses, stakeholder effects, and relevant regulatory developments.
Set reassessment triggers for material model changes, new uses, incidents, failed controls, different data, new affected groups, or altered deployment conditions. Risk-based review dates can supplement these triggers.
Document ownership, assessments, treatment decisions, evidence, residual-risk acceptance, monitoring, and review history. The OECD report on advancing accountability in AI links trustworthy AI with lifecycle risk management and tools for defining, assessing, treating, and governing risk.
Continuous review links this workflow to the wider AI risk management lifecycle. The process describes what teams do; the lifecycle explains how that work continues as the system and environment change.

Consider an AI system that ranks job applicants. During Step 1, the organization defines the hiring purpose, applicant population, decision influence, data sources, provider, accountable HR owner, and acceptance criteria. Step 2 identifies scenarios involving discriminatory ranking, inaccessible applications, privacy loss, inaccurate recommendations, recruiter overreliance, and ineffective appeals.
In Step 3, the team analyses subgroup performance, data representativeness, exposure, severity, reversibility, uncertainty, and the reliability of existing human review. Step 4 prioritizes risks that could materially affect employment opportunities or legal rights. Step 5 may restrict the system's role, improve data and testing, require applicant notice, or introduce reconsideration and appeal routes.
Step 6 tests whether recruiters can identify weak recommendations, override them, document decisions, and escalate concerns under realistic workloads. Step 7 monitors subgroup outcomes, overrides, complaints, appeals, provider changes, and model updates. A material threshold breach triggers investigation, restriction, remediation, and reassessment rather than waiting for the next scheduled review.
This example shows why the process must follow the complete decision workflow. A technically accurate model can still create material risk if the data, interface, user behaviour, oversight, or downstream decision process is weak.
Professionals and teams seeking guided learning can explore AI Risk Management with NIST and ISO 42001. This three-hour online course connects risk identification, assessment, treatment, controls, monitoring, vendor risk, NIST AI RMF, ISO/IEC 42001, and continual improvement. It is designed for governance, risk, compliance, audit, privacy, security, and technical and business professionals and includes a certificate upon successful completion.
Course learning should be applied alongside organization-specific policies, evidence, risk criteria, and qualified legal or technical advice. It supports professional capability but does not certify an AI system or prove compliance.
Proportionality changes assessment depth, stakeholder involvement, testing, approval authority, evidence, monitoring, control strength, and reassessment triggers. The chosen effort still needs justification.
A low-impact productivity tool may justify a lighter process than AI influencing employment, healthcare, finance, safety, legal rights, or essential services. However, "low risk" should be an assessment outcome, not an assumption based on a familiar interface. Sensitive data or consequential downstream use can change the result.
The NIST Generative AI Profile illustrates contextual tailoring by adapting AI RMF 1.0 to generative AI risks and suggested actions. Organizations can similarly adapt their process to the technology, users, sector, and consequences.
The seven-step workflow can align with recognized frameworks and standards rather than replace them.
NIST uses Govern, Map, Measure, and Manage. Conceptually, Govern supports accountability and context; Map supports risk identification; Measure supports analysis and testing; and Manage supports prioritization, treatment, controls, and monitoring. This is not a rigid mapping.
The NIST AI RMF Playbook provides voluntary suggested actions aligned with those four functions. NIST explicitly states that the Playbook is neither a checklist nor a set of steps to be followed in its entirety. For a complete explanation of the functions, categories, implementation approach, and current revision status, read the NIST AI Risk Management Framework guide.
ISO/IEC 23894 supplies AI-specific guidance for organizations developing, producing, deploying, or using AI. It can inform how this operational process is integrated and adapted.
ISO/IEC 42001:2023 has a broader management-system purpose. It specifies requirements for establishing, implementing, maintaining, and continually improving an AI management system, including management of AI-related risks and opportunities.
ISO/IEC 42001:2023 has a broader management-system purpose. It specifies requirements for establishing, implementing, maintaining, and continually improving an AI management system, including management of AI-related risks and opportunities. Organizations can use ISO/IEC 42001 to structure the management system while drawing on NIST AI RMF for risk outcomes and activities. For a practical explanation of using NIST and ISO 42001 together, including how to align governance, risk processes, controls, evidence, and continual improvement, see our detailed integration guide.

Starting with controls can produce safeguards that miss the real risk pathway. Treating the risk register as finished confuses documentation with management. Confusing risk with impact distorts priorities, while untested assumptions about existing controls misstate exposure.
Implementation is not completion. Controls need testing, residual-risk decisions, and monitoring. A scheduled review may be inadequate if the model, data, integration, use, or stakeholder impact changes sooner.
A strong process creates a traceable chain: risk → assessment → decision → treatment → control → evidence → monitoring. If one link is missing, the organization may struggle to demonstrate why its response was reasonable or whether it reduced risk.
Effective AI risk management requires more than listing possible harms. The operational process is to establish context, identify, analyze, evaluate, select treatment, implement controls, and monitor.
Each material risk should have an owner, evidence-based assessment, treatment decision, appropriate controls, residual-risk decision, and reassessment trigger. The process should remain proportionate to risk and repeat whenever material changes affect the system or its context. That discipline turns risk identification into accountable action.
Ready to build a clearer, framework-aligned approach to AI risk? Enroll in AI Risk Management with NIST and ISO 42001 to strengthen your understanding of risk assessment, treatment, control design, monitoring, vendor risk, and continual improvement through one focused online course.
The seven steps are to establish context and ownership, identify risks, analyze their likelihood and impacts, evaluate and prioritize them, select treatment, implement and validate controls, and monitor and reassess the results.
Responsibility depends on the organization and use case. System owners, business owners, risk, legal, privacy, security, compliance, technical teams, and senior decision-makers may hold different responsibilities. One accountable owner should coordinate the response for each material risk.
Prioritization should consider likelihood, severity, affected stakeholders, uncertainty, business criticality, existing controls, legal duties, and organizational risk criteria. A numeric score can support comparison, but it should not replace contextual judgement.
Frequency should reflect the system's risk and context. Material model updates, new uses, changed data, incidents, control failures, new stakeholder effects, or significant deployment changes should trigger reassessment where relevant.
No. NIST AI RMF uses Govern, Map, Measure, and Manage. The seven-step structure in this article is a practical workflow that can align with NIST and other risk-management guidance, not a sequence prescribed by NIST.
OpenAI shelved GPT-6.1 Astra after safety tests flagged scope, authorization and action-reporting issues. See what is confirmed and what remains...
AI Law
Learn AI compliance requirements, key risks, the EU AI Act, NIST AI RMF, ISO 42001, and practical steps to build...
AI Law
Understand AI regulation in the United States in 2026, including federal rules, state AI laws, privacy, discrimination and practical compliance...