Model risk regulation: where a validation team finds each item
Last updated 16 November 2026
What four model risk rules say about models from a supplier, and where GIAnalyzer and the Gamma Impact API publish what each asks for. This is our reading of each rule, for information; none of the regulators has reviewed it, and it does not replace your own validation.
Bank of Israel: Directive 369
Proper Conduct of Banking Business Directive 369, Management of Model Risk. Each clause is taken in detail on the Directive 369 page.
| Directive 369 | What it asks | Where |
|---|---|---|
| §38, §93(b) | Documentation that allows validation: components, design and intended use | Coverage & models, one methodology page per area, and the function reference |
| §47 | The methodology, with its mathematical specification and sources | Each methodology page names its models and ends with its references |
| §93(b) | Test results | A worked example for every function; in GIAnalyzer, the Manual Calculations workbooks |
| §93(b) | Limitations and assumptions | The "What the models do not do" section of each methodology page |
| §93(e) | Sensitivity analysis and benchmarking where the code is not open | Every input and parameter returned with the result; sensitivities on any argument; models named, so they can be implemented independently |
| §93(g), §93(h) | Data and assumptions from the supplier | None bundled: market data and histories come from you; defaults are stated on the methodology pages |
| §93(f) | Adjustments made for the bank | Parameters the bank sets, returned with every result |
| §93(c) | Ongoing monitoring and updates | A message to clients with each release; each client chooses when to upgrade; each methodology page states its version |
| §93(i) | Contingency if the product is no longer supported | Runs and licenses offline; a licence keeps working until its expiry date, with support until then; source-code escrow on request |
| §93(d) | Internal knowledge to continue if the relationship ends | The user guide, FAQ and glossary; training for clients |
United States: interagency guidance, April 2026
Supervisory Guidance on Model Risk Management, 17 April 2026: Federal Reserve SR 26-2, OCC Bulletin 2026-13, FDIC FIL-15-2026. It replaces SR 11-7.
| Section VII | What it asks | Where |
|---|---|---|
| Vendor products | Model risk principles apply even where the bank does not receive the vendor's code, data or methodology | The methodology is published; every input and parameter is returned with the result |
| Vendor products | An understanding of the model's conceptual soundness and design | The methodology pages and the function reference |
| Vendor products | An understanding of its development data | The pricing models are standard published models, not estimated from a data set: they are calibrated at each run to the market data you supply. Value at Risk is computed on histories you supply |
| Vendor products | An understanding of its performance | Worked examples and manual calculations |
| Vendor products | Ongoing monitoring and outcomes analysis by the bank | Results run on your own positions and market data, with the inputs behind each one |
| Vendor products | Customisations documented, justified and evaluated | Every setting is a parameter, returned with the result |
United Kingdom: PRA SS1/23
Supervisory Statement SS1/23, Model risk management principles for banks, updated April 2026.
| SS1/23 | What it asks | Where |
|---|---|---|
| 2.6(b)(i) | The firm satisfies itself that vendor models are validated to its own standards | The methodology pages, their limitations sections and the test evidence |
| 2.6(b)(ii) | The relevance of vendor-supplied data and assumptions is verified | No data bundled; defaults stated on the methodology pages |
| 2.6(b)(iii) | The firm validates its own use, with monitoring and outcomes analysis on its own outcomes | Results run on your own data, with every input returned |
| 3.5(a) | Vendor documentation detailed enough to validate the firm's use | The methodology pages, the function reference and the inputs returned with each result |
| 4.3(a)(i) | Input data represents what the model is used for | Inputs come from you |
Canada: OSFI Guideline E-23
Guideline E-23, Model Risk Management (2027), in effect from 1 May 2027.
| E-23 | What it asks | Where |
|---|---|---|
| C.1, Appendix 1 | Vendor models recorded with their data sources and limitations | Market data from you; limitations on each methodology page |
| D.2, model review | Review of conceptual soundness and performance, including third-party models | The methodology pages, worked examples and manual calculations |
| D.2, model monitoring | Changes in external dependencies, such as version updates, tracked | A message with each release; you choose when to upgrade; each methodology page states its version |
| D.2, model monitoring | Contingency plans for model unavailability | Runs and licenses offline; escrow on request |
| Response to consultation | Adequate documentation from vendors, and controls on whether a vendor solution gives an appropriate response | The documentation is public; every result comes back with the inputs that produced it |
