Artificial Intelligence Policy Tracker
Voluntary guidance AI risk management United States Voluntary standard

Prioritise, respond to and monitor AI risks (Manage)

Download: JSON · MarkdownUnder NIST AI RMF, MANAGE function

Source-linked · linked to the official source, not yet confirmed by a reviewer (a factual check against the official source, not a legal review or legal advice)
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.
Verification policy and current standing · a factual check, not legal advice.
No change recorded as of 26 Sep 2026 · official source last checked
On this page 9 sections

In brief

Prioritise, respond to and monitor AI risks (Manage) is a voluntary measure under the NIST AI RMF in the United States (MANAGE function). Manage allocates resources to mapped and measured risks, plans responses including decommissioning, manages third-party risks, and documents post-deployment monitoring, incident response and communication. The record carries 1 evidence example and mappings to 1 framework.

Instrument
NIST AI RMF
Jurisdiction
United States
Nature
Voluntary guidance
Source reference
MANAGE function
Who it binds
Provider / developer, Deployer / user organisation
Evidence examples
1
Framework mappings
ISO/IEC 42001:2023
Controls that meet it
3
Official source
Open official text
Verification
Source-linked

What does it require?

Manage allocates resources to mapped and measured risks, plans responses including decommissioning, manages third-party risks, and documents post-deployment monitoring, incident response and communication.

Practical action

Maintain a risk-treatment plan and an incident and monitoring log per system.

Who does it apply to?

Voluntary; any organisation adopting the framework.

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.

  • satisfiesProcessAI system owner · once per ai system
    AI risk assessment and lifecycle risk register

    Serves 12 recorded duties · evidence: AI system risk assessment, Per-system AI risk register, Residual-risk acceptance

    Risk treatment planning and resource allocation for mapped and measured risks.

  • supportsProcessIncident coordinator · continuous
    AI incident management and regulatory reporting

    Serves 14 recorded duties · evidence: AI incident response playbook, AI incident record, Incident report to an authority

    Incident response and communication outcomes.

  • supportsProcessProcurement or vendor risk lead · once per ai system
    Vendor and third-party AI due diligence

    Serves 6 recorded duties · evidence: AI supplier due-diligence assessment, AI supplier and component register, Supplier onboarding decision

    Third-party risk management outcomes.

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.

All 6 templates that cover it →

What evidence would a reviewer expect?

Evidence examples
EvidenceTypeNotes
Risk treatment and monitoring plandocument

Framework mappings

Original editorial crosswalks. They cite clause numbers only and reproduce no standard text; confidence reflects how direct the mapping is.

See every United States duty mapped this way →

Framework mappings table
FrameworkReferenceNoteConfidence
ISO/IEC 42001:2023Clauses 8 and 10Operation and improvement.medium

Frequently asked questions

Is this a legal requirement?

No. It is voluntary guidance under NIST AI RMF; following it is expected or recommended rather than required by law.

Who must comply with this obligation?

Voluntary; any organisation adopting the framework.

What evidence shows compliance?

A reviewer would expect: Risk treatment and monitoring plan.

Which frameworks map to this obligation?

It is mapped to ISO/IEC 42001:2023 Clauses 8 and 10. These are editorial crosswalks with a stated confidence, not official mappings.

Which controls satisfy this obligation?

AI risk assessment and lifecycle risk register; AI incident management and regulatory reporting; Vendor and third-party AI due diligence.

What should an organisation do in practice?

Maintain a risk-treatment plan and an incident and monitoring log per system.

Cite this record

AIPolicyTracker (2026). “Prioritise, respond to and monitor AI risks (Manage) (NIST AI RMF)” [AIPT-OBL-0115, verified 26 September 2026 by Bhaskar Bhatt]. https://aipolicytracker.org/id/AIPT-OBL-0115 (accessed 27 October 2026). Data licensed CC BY 4.0.

Permanent id AIPT-OBL-0115: it never changes or gets reused, and its address keeps working if this page moves.

Cite the official text alongside it: Artificial Intelligence Risk Management Framework (AI RMF 1.0), National Institute of Standards and Technology, https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf.

BibTeX
@misc{aipolicytracker2026_prioritiserespondtoandmo,
  author       = {{AIPolicyTracker}},
  title        = {{Prioritise, respond to and monitor AI risks (Manage) (NIST AI RMF)}},
  year         = {2026},
  howpublished = {\url{https://aipolicytracker.org/obligations/us-nist-ai-rmf-manage}},
  url          = {https://aipolicytracker.org/obligations/us-nist-ai-rmf-manage},
  urldate      = {2026-10-27},
  note         = {Data licensed CC BY 4.0. Accessed 27 October 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

Disclaimer: informational only, not legal advice. Verify every claim against the linked official sources and consult a qualified lawyer before acting.