United States

US Interagency MRM Guidance (SR 26-2, formerly SR 11-7)

Supervisory Guidance on Model Risk Management (Federal Reserve SR 26-2, OCC Bulletin 2026-13, FDIC FIL-15-2026), superseding SR 11-7

The three US federal bank regulators' 2026 principles for managing the risk of relying on models, which replaced the 2011 SR 11-7 guidance and covers traditional and non-generative AI models but leaves generative and agentic AI out of scope.

SupervisoryRegulatory GuidanceDevelopers and deployersNot an AI-specific law
Regulator
Board of Governors of the Federal Reserve System, Office of the Comptroller of the Currency (OCC), Federal Deposit Insurance Corporation (FDIC)
Adopted
17 Apr 2026
In force
Not yet, or no single date
Sectors
Financial services
Penalties
None. The guidance says it sets no enforceable standards and non-compliance with it alone will not lead to supervisory criticism. Supervisory action remains possible for violations of law or unsafe or unsound practices caused by poor model risk management.
Last verified
19 Oct 2026Official source

Summary

  • SR 11-7 is no longer current. On 17 April 2026 the Federal Reserve, OCC and FDIC issued revised "Supervisory Guidance on Model Risk Management" (Fed SR 26-2, OCC Bulletin 2026-13, FDIC FIL-15-2026). It rescinds and supersedes SR 11-7 (4 April 2011), OCC Bulletin 2011-12 and several related items.
  • The new text is shorter and risk-based: practices should scale with each bank's model risk profile, size and complexity. It is expected to be most relevant to banking organisations with over USD 30 billion in total assets.
  • It narrows the definition of a model to complex quantitative methods based on statistical, economic or financial theory, and excludes simple spreadsheet arithmetic and deterministic rule-based software.
  • AI coverage is split: traditional statistical models and non-generative, non-agentic AI models (for example a gradient-boosted credit model) are in scope. Generative AI and agentic AI are out of scope because they are "novel and rapidly evolving"; banks should govern them through their general risk management. The OCC says the agencies plan a request for information (RFI) covering banks' use of AI; no issued RFI was found as of 2026-10-19 (secondary sources only).
  • It is explicitly non-binding: it sets no enforceable standards, and non-compliance with the guidance alone will not produce supervisory criticism.

Who it applies to

  • Banking organisations supervised by the Federal Reserve, OCC and FDIC. The OCC version names national banks, federal savings associations and federal branches and agencies of foreign banking organisations; the FDIC version covers FDIC-supervised institutions.
  • Expected to be most relevant above USD 30 billion in total assets. At or below that size it generally does not apply, unless the bank has significant model risk because of complex models or activities beyond traditional community banking.
  • Most useful for models that support significant business lines, operations, services and functions.
  • Vendors are not addressed directly; banks must validate and monitor vendor and third-party models (Section VII).
  • Not extraterritorial. A non-US company is reached only as a vendor to a US banking organisation.

History: SR 11-7 (2011 to 2026)

  • SR 11-7 "Guidance on Model Risk Management" was issued by the Federal Reserve on 4 April 2011, jointly with OCC Bulletin 2011-12; the FDIC adopted it in 2017 (FIL-22-2017).
  • For fifteen years it was the global reference text for model risk management, organised around model development, implementation and use; model validation (including "effective challenge"); and governance, policies and controls.
  • Its broad model definition and supervisory use meant AI and ML models in US banks were already routinely run through SR 11-7 inventories and validation.
  • Status: rescinded on 17 April 2026. The SR 11-7 and OCC 2011-12 pages on federalreserve.gov and occ.gov returned "not found" when checked on 2026-10-19, so this history summary relies on the 2026 agency documents and general knowledge; the original text was not re-read.

Key dates

  1. Federal Reserve SR 11-7 and OCC Bulletin 2011-12 issue the original interagency model risk guidance
  2. Interagency statement on model risk management for BSA/AML systems (SR 21-8, OCC 2021-19, FDIC FIL-27-2021)
  3. Revised guidance issued as SR 26-2, OCC Bulletin 2026-13 and FDIC FIL-15-2026; SR 11-7, OCC 2011-12 and related items rescinded
Full date record
Date Event
2011-04-04 SR 11-7 and OCC Bulletin 2011-12 issued
2017 FDIC adopts the guidance (FIL-22-2017); exact date not confirmed
2021-04-09 Interagency BSA/AML model risk statement (SR 21-8, OCC 2021-19, FIL-27-2021)
2026-04-17 Revised guidance issued (SR 26-2, OCC 2026-13, FIL-15-2026); SR 11-7, SR 21-8, OCC 2011-12, OCC 2021-19, OCC 1997-24, the Comptroller's Handbook MRM booklet, FIL-22-2017 and FIL-27-2021 rescinded
Pending Planned interagency RFI on model risk management and banks' use of AI, including generative and agentic AI (announced in OCC 2026-13; not found issued as of 2026-10-19)

Penalties and enforcement

  • No penalties. The guidance states it sets no enforceable standards or prescriptive requirements, and non-compliance with it will not result in supervisory criticism (Section I).
  • Footnote 1 points to the agencies' rules on the role of supervisory guidance (12 CFR Part 4 Subpart F Appendix A for the OCC, 12 CFR Part 262 Appendix A for the Board, 12 CFR Part 302 Appendix A for the FDIC).
  • The same footnote keeps a real backstop: supervisory action may still follow for violations of law or unsafe or unsound practices that stem from poor model risk management.
  • Separate laws still bite on model outputs, for example fair lending or BSA/AML rules; this guidance does not replace them.

What it means for an Indian company

  • Indian banks with US branches or agencies: OCC-licensed federal branches of foreign banks are named in the OCC bulletin. Most such branches are likely below the USD 30 billion relevance line (check your own balance sheet), so the guidance will usually be a benchmark, not a central expectation. A branch with complex models (for example AML transaction monitoring or treasury pricing) should still keep a proportionate MRM framework.
  • IT, analytics and AI vendors serving US banks: Section VII says banks should understand a vendor model's conceptual soundness, design, development data and performance even when code is proprietary, and run their own ongoing monitoring and outcomes analysis. Expect due diligence questionnaires, validation data requests and requests to document any customisation.
  • GenAI and agent vendors: the carve-out does not mean US banks will skip diligence. Footnote 3 says banks should apply their broader risk management to tools outside the guidance, and the planned RFI signals future expectations. Keep model cards, red-team results and monitoring evidence ready.
  • Comparison with RBI: RBI's draft model risk guidance (24 June 2026, still draft as of 2026-10-19) covers AI and ML models and builds on RBI FREE-AI. The US moved the other way: it narrowed scope and removed generative and agentic AI. An Indian bank or vendor working across both should design for the stricter scope (RBI draft, OSFI E-23, PRA SS1/23) and treat US guidance as the floor.
  • Customers in New York may also ask about AI cyber risks under NYDFS AI Cybersecurity Letter 2024, which sits alongside this guidance.

Obligations

The guidance uses "sound practice" language rather than "must"; these are supervisory expectations, not enforceable rules. References are to sections and footnotes of the SR 26-2 attachment.

Showing 25 of 25
IDObligationReferenceApplies toControls
USMRM-01Decide whether and how far the guidance applies, using total assets (most relevant above USD 30 billion), model risk exposure and complexity; focus on models supporting significant business linesSections I and IIDeployer
USMRM-02Use the guidance's model definition (complex quantitative methods based on statistical, economic or financial theory) to set scope, excluding simple arithmetic and deterministic rule-based softwareSection IIBoth
USMRM-03Apply the principles to traditional statistical models and non-generative, non-agentic AI models; govern generative and agentic AI tools through the bank's wider risk management and controlsFootnote 3Both
USMRM-04Assess each model's risk from its inherent risk (assumptions, complexity, input quality, data limits), exposure and purpose; use exposure plus purpose to set materialitySection IIIBoth
USMRM-05For models judged immaterial, still identify them and watch for conditions that could make them material; apply more rigorous oversight to higher materiality modelsSection IIIDeployer
USMRM-06Assess model risk in aggregate, including dependencies between models and shared assumptions, data or methodsSection IIIDeployer
USMRM-07Provide effective challenge across the lifecycle by people with the right expertise, enough independence and the standing to force changeSection IIIDeployer
USMRM-08Start development with a clear statement of purpose and involve model users to bring business contextSection IV, Model DevelopmentDeveloper
USMRM-09Test models during development (for example out-of-sample, out-of-time, alternative assumptions, data quality review) with rigour matched to complexity and materialitySection IV, Model DevelopmentDeveloper
USMRM-10Use models with a clear grasp of their limitations; before extending a model beyond its original purpose, analyse the new use and review controlsSection IV, Model UseDeployer
USMRM-11Validate models to assess reliability and limitations, with rigour matched to approach, use and materiality; consider adjustment, recalibration or redevelopment when performance drifts meaningfullySection VDeployer
USMRM-12Validate before first use; if urgent business need forces earlier use, pay closer attention to limits, tell stakeholders and add controls such as usage limits or closer monitoringSection VDeployer
USMRM-13Make sure validators have the technical knowledge and modelling expertise to critique models properly; quality matters more than org chartSection VDeployer
USMRM-14Users of model output should understand and communicate remaining limitations, monitor performance and supplement output with other analysisSection VDeployer
USMRM-15Assess and document conceptual soundness (design choices, assumptions, judgements, data selection, developmental testing); interpretability measures or benchmarking can be used where theory review is impracticalSection V, Conceptual SoundnessBoth
USMRM-16Run outcomes analysis comparing outputs with real outcomes (for example back-testing, outlier analysis) against set performance thresholdsSection V, Outcomes AnalysisDeployer
USMRM-17Monitor models on an ongoing basis for changes in products, exposures, clients, data relevance or markets, with a plan covering limitations and response procedures; apply overlays or redevelopment per policySection V, Ongoing Model MonitoringDeployer
USMRM-18Set policies that define model risk expectations and a framework for sizing model risk, with procedures for monitoring, control and resourcingSection VIDeployer
USMRM-19Define roles and accountability across development, validation and monitoring, and manage conflicts of interest between developers and validatorsSection VI, Roles and ResponsibilitiesDeployer
USMRM-20Where internal audit is involved, have it judge whether MRM is rigorous and effective rather than redo development or validationSection VI, Roles and ResponsibilitiesDeployer
USMRM-21Oversee and integrate any external resources used for model risk work, with clear delegated rolesSection VI, Roles and ResponsibilitiesDeployer
USMRM-22Keep a model inventory with enough information to understand risks individually and in aggregateSection VI, Model InventoryDeployer
USMRM-23Keep documentation that supports continuity and tracks recommendations, responses, exceptions and remediationSection VI, DocumentationBoth
USMRM-24Validate vendor and third-party models (internally or via outside parties), understanding their soundness, design, development data and performance despite proprietary limitsSection VIIDeployer
USMRM-25Monitor vendor models and run outcomes analysis on them; document, justify and validate any customisationSection VIIDeployer

Evidence an auditor will ask for

  • A scoping memo showing how the bank applied the USD 30 billion relevance line and its own model risk profile.
  • The model definition in policy, with the rule for excluding spreadsheets and deterministic tools, and a separate governance route for generative and agentic AI.
  • Model inventory extract with materiality, inherent risk rating, owner and validation status, plus an aggregate risk view.
  • Development files with purpose statements, test results and data quality review.
  • Validation reports covering conceptual soundness, outcomes analysis and limitations; records of any use before validation and the compensating controls.
  • Monitoring reports, threshold breaches and overlay or redevelopment decisions.
  • Role descriptions and evidence of conflict-of-interest handling between developers and validators.
  • Internal audit reports on MRM effectiveness.
  • Vendor model files: due diligence, validation evidence, ongoing monitoring and customisation records.

Common mistakes

  • Still citing SR 11-7 as current. It was rescinded on 17 April 2026; cite SR 26-2, OCC 2026-13 or FIL-15-2026.
  • Reading the generative and agentic AI carve-out as "no rules for LLMs". Footnote 3 still expects governance and controls, and other laws and supervisory expectations still apply.
  • Dropping non-generative AI models from validation; ML credit, fraud and AML models remain squarely in scope.
  • Assuming "non-binding" means "ignore". Unsafe or unsound practices from weak model risk management can still draw supervisory action.
  • Treating the USD 30 billion figure as a hard legal threshold; it is a relevance marker and smaller banks with complex models may still be expected to follow it.
  • Accepting a vendor's proprietary black box without independent understanding or monitoring on the bank's own outcomes.

Glossary

  • SR letter: a Supervision and Regulation letter, the Federal Reserve's way of issuing guidance to examiners and banks.
  • OCC Bulletin / FDIC FIL: the OCC's and FDIC's equivalents for publishing guidance (FIL means Financial Institution Letter).
  • Model: in this guidance, a complex quantitative method that applies statistical, economic or financial theory to turn input data into estimates.
  • Model risk: the chance of financial harm from decisions based on model output.
  • Materiality: how much a model matters, judged from its exposure (size of business affected) and purpose (for example regulatory or risk use).
  • Effective challenge: critical review by objective experts who have the authority to make changes happen.
  • Outcomes analysis: comparing what a model predicted with what actually happened.
  • Overlay: a manual adjustment applied on top of model output.
  • Generative AI: AI that produces new content such as text or images (for example large language models).
  • Agentic AI: AI that can plan and take actions on its own toward a goal.
  • RFI (Request for Information): a public call by regulators for comments before deciding on policy.

Key takeaways

  • SR 11-7 is history: SR 26-2, OCC 2026-13 and FIL-15-2026 replaced it on 17 April 2026.
  • The new guidance is principles-based, explicitly non-binding and aimed mainly at banks above USD 30 billion in assets.
  • Predictive (non-generative, non-agentic) AI models stay in scope; generative and agentic AI are carved out pending a planned RFI.
  • 25 supervisory expectations covering materiality, effective challenge, development, validation, monitoring, governance, inventory, documentation and vendor models.
  • Indian vendors should expect US banks to keep asking for model documentation, development data and monitoring evidence, including for GenAI under general risk management.

Official sources

This is general information, not legal advice. Last verified 19 Oct 2026 against the official source. Laws change; confirm the current position with qualified counsel before acting.

Check your readiness

See where your controls stand today with our free compliance gap assessment.

Start the gap assessment

Talk to us about AI Governance

We map US Interagency MRM Guidance (SR 26-2, formerly SR 11-7) and the other rules that reach you onto one control set, and build the evidence your auditors and customers will ask for.

Explore AI Governance