diff --git a/.github/workflows/validate-docs-site.yaml b/.github/workflows/validate-docs-site.yaml index 194fed4651..f9a7fc80f6 100644 --- a/.github/workflows/validate-docs-site.yaml +++ b/.github/workflows/validate-docs-site.yaml @@ -200,7 +200,7 @@ jobs: run: | test -f site/llm/_llm-output/chatbot-product-map.md test -f site/llm/_llm-output/AGENTS.md - test -f site/llm/_llm-output/about/contributing/using-the-documentation.md + test -f site/llm/_llm-output/about/using-the-documentation.md test ! -f site/llm/_llm-output/about/contributing/validmind-community.md test ! -d site/llm/_llm-output/about/contributing/style-guide diff --git a/AGENTS.md b/AGENTS.md index 271e8e1c83..52f3c75e8c 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -6,7 +6,7 @@ This repository contains the source files for [ValidMind's documentation site](h For an overview of the documentation structure and how to navigate it, see: -**[Using the documentation](https://docs.validmind.ai/about/contributing/using-the-documentation.html)** +**[Using the documentation](https://docs.validmind.ai/about/using-the-documentation.html)** This page explains: - How the documentation is organized diff --git a/site/_quarto.yml b/site/_quarto.yml index 28da8c4f4e..eba558917b 100644 --- a/site/_quarto.yml +++ b/site/_quarto.yml @@ -95,7 +95,7 @@ website: - text: "Model risk management" file: about/use-cases/model-risk-management.qmd contents: - - about/use-cases/sr-11-7.qmd + - about/use-cases/sr-26-2.qmd - about/use-cases/ss1-23.qmd - about/use-cases/e-23.qmd - text: "---" @@ -125,7 +125,7 @@ website: - text: "Software license agreement" file: about/fine-print/license-agreement.qmd - text: "---" - - about/contributing/using-the-documentation.qmd + - about/using-the-documentation.qmd - title: "Support" contents: diff --git a/site/about/contributing/style-guide/conventions.qmd b/site/about/contributing/style-guide/conventions.qmd index 351ed06336..b9656e55f7 100644 --- a/site/about/contributing/style-guide/conventions.qmd +++ b/site/about/contributing/style-guide/conventions.qmd @@ -359,7 +359,7 @@ Use backticks to enclose keyboard commands, parameters, field values, and file n : **Mathematical formula** examples {.hover} ## Proper nouns -In the context of model risk management, proper nouns include specific models, laws, or regulations, such as "Basel IV" or "SR 11-7." These refer to specific frameworks or guidelines and you spell them with initial capital letters or exactly as indicated by official sources. +In the context of model risk management, proper nouns include specific models, laws, or regulations, such as "Basel IV" or "SR 26-2." These refer to specific frameworks or guidelines and you spell them with initial capital letters or exactly as indicated by official sources. - Terms that are not proper nouns include general concepts such as "model validation," "stress testing," "risk assessment," and "backtesting." - These are common terms in the field and are not capitalized unless starting a sentence. diff --git a/site/about/glossary/_models.qmd b/site/about/glossary/_models.qmd index 0bc6ee8e3f..b3a72d4e68 100644 --- a/site/about/glossary/_models.qmd +++ b/site/about/glossary/_models.qmd @@ -5,7 +5,7 @@ SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial --> #### Models model -: SR 11-7^[[SR 11-7: Guidance on Model Risk Management](https://www.federalreserve.gov/supervisionreg/srletters/sr1107.htm)] defines a model as a "quantitative method, system, or approach that applies statistical, economic, financial, or mathematical theories, techniques, and assumptions to process input data into quantitative estimates." +: Under SR 26-2^[[SR 26-2: Interagency Guidance on Model Risk Management for Banking Organizations](https://www.federalreserve.gov/supervisionreg/srletters/SR2602.htm)] (which supersedes SR 11-7), banking organizations focus MRM on *complex quantitative methods* that apply statistical, economic, or financial theories, techniques, and assumptions to produce estimates or inferences that inform business decisions. Simple arithmetic, purely deterministic rules without substantive quantitative theory, or software that does not apply such theories are generally outside the guidance’s model definition. model development : An iterative process in which many models are derived, tested, and built upon until a model fitting the desired criteria is achieved. diff --git a/site/about/overview-model-documentation.qmd b/site/about/overview-model-documentation.qmd index a0e89b280b..2edacee030 100644 --- a/site/about/overview-model-documentation.qmd +++ b/site/about/overview-model-documentation.qmd @@ -144,7 +144,7 @@ How the {{< var validmind.developer >}} works: -[^1]: [Model risk management](overview-model-risk-management.qmd) +[^1]: [Model risk management](use-cases/model-risk-management.qmd) [^2]: [Supported records and frameworks](/developer/supported-records-and-frameworks.qmd) diff --git a/site/about/overview-model-risk-management.qmd b/site/about/overview-model-risk-management.qmd deleted file mode 100644 index 81a6d137ed..0000000000 --- a/site/about/overview-model-risk-management.qmd +++ /dev/null @@ -1,226 +0,0 @@ ---- -# Copyright © 2023-2026 ValidMind Inc. All rights reserved. -# Refer to the LICENSE file in the root of this repository for details. -# SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -title: "Model risk management" -date: last-modified -aliases: - - /guide/overview-model-risk-management.html -listing: - id: quickstart - type: grid - grid-columns: 2 - # image-height: 100% - contents: - - path: ../get-started/get-started.qmd - title: "Get started" - description: "Our quickstarts are the quickest and easiest way to try out our product features." - fields: [title, description, reading-time] ---- - -The {{< var validmind.platform >}} offers an integrated solution to manage validation reports, track artifacts, and report on model risk compliance across your model portfolio. {{< var vm.product >}} enables your organization to monitor and manage models effectively, focusing on mitigating risks, maintaining governance, and ensuring compliance throughout the entire enterprise. - -::: {.attn} - -## {{< fa laptop-code >}} The {{< var validmind.platform >}} - -The {{< var validmind.platform >}} provides a comprehensive suite of tools, guidelines, and best practices. You use {{< var vm.product >}} to review and evaluate models and model documentation to ensure they comply with organizational and regulatory requirements. - - - -![The two main components of {{< var vm.product >}}. The {{< var validmind.developer >}} that integrates with your existing developer environment, and the {{< var validmind.platform >}}.](overview-platform.png){width=80% fig-alt="An image showing the two main components of ValidMind. The ValidMind Library that integrates with your existing developer environment, and the ValidMind Platform."} - -The {{< var vm.platform >}} employs a multi-tenant architecture, hosting the cloud-based user interface, APIs, databases, and internal services. The design ensures efficient resource utilization and offers a highly scalable solution for organizations of varying sizes. - -With the {{< var vm.platform >}}, you can: - -- **Track your model inventory**[^1] — Manage the model lifecycle, track the workflow status for models, plan for upcoming validation dates, and more. -- **Work on validation initiatives**[^2] — Collaborate with developers and validators to review documentation, add artifacts, keep track of review statuses, and generate validation reports. -- **Configure workflows**[^3] — Set up the {{< var validmind.platform >}} to follow your existing model risk management processes, manage statuses for different parts of the workflow, and get an end-to-end view of workflows and who is involved. -- **Use, create, or edit tests, test suites, and templates**[^4] — Create and/or configure required validation tests, test suites, and document templates for specific model use cases, tailoring it to your own specific needs. -- **Integrate with your stack**[^5] — Import and export model documentation and validation reports. - -::: - -## Regulatory requirements - -{{< var vm.product >}} is designed to cater to the regulatory compliance and model risk management (MRM) requirements of financial institutions, facilitating enhanced compliance with government regulations, policies concerning MRM, and emerging legislations addressing AI model risk, including risks associated with the use of large language models (LLMs). - -Examples of regulations or policies include: - -:::: {.flex .flex-wrap .justify-around} - -::: {.w-75-ns} - -### SR 11-7: Guidance on Model Risk Management - -The Supervisory Guidance on model risk management issued by the Board of Governors of the Federal Reserve System and the Office of the Comptroller of the Currency in the United States in 2011. It provides comprehensive guidance to financial institutions on developing and maintaining a robust model risk management framework, covering aspects like model development, implementation, use, and validation. - -::: - -::: {.w-20-ns .content-center} - -![Board of Governors Federal Reserve logo](federal-reserve.svg){width=70% fig-alt="Board of Governors Federal Reserve logo"} - -::: - -:::: - -SR 11-7 is widely recognized and has become a benchmark in the industry for model risk management practices. - -SR 11-7 outlines these core requirements: - -Model Risk Management -: - Identify and mitigate risks associated with incorrect or inappropriate model usage, outputs, or implementation errors. -- Encourage "effective challenge" to identify model limitations and propose necessary changes. -- Consider materiality in model risk management based on the extent of model usage and its impact on the organization's financial condition. - -Model Development, Implementation, and Use -: - Develop with a clear statement of purpose, sound design, theory, and logic. -- Assess rigorously data quality and relevance, robust methodologies, and appropriate documentation. -- Test to ensure accuracy, robustness, stability, and to evaluate limitations and assumptions. - -Model Validation -: - Be an integral part for managing model risk, ensuring models perform as intended. -- Identify and address potential errors or misuses. - -Governance, Policies, and Controls -: - Establish a sound governance framework to oversee model risk management. -- Implement policies and controls for appropriate use and validation of models. - -The regulation also mandates ongoing monitoring and periodic reviews to ensure models remain valid and effective. - -:::: {.flex .flex-wrap .justify-around} - -::: {.w-20-ns .content-center} - -![Bank of England logo](bank-of-england.svg){fig-alt="Bank of England logo"} - -::: - -::: {.w-75-ns} - -### SS1/23 – Model Risk Management Principles for Banks - -A policy issued by the Prudential Regulation Authority (PRA) in the UK. It encapsulates the final model risk management principles following feedback on the earlier consultation paper CP6/22. The statement provides guidelines for banks in the UK on managing model risk effectively, with particular emphasis on strategic planning and technical capabilities. - -::: - -:::: - -It outlines principles and amendments, like clarifications on model complexity factors, senior management function responsibilities, and inclusion of dynamic adjustments in model change management, aiming to standardize MRM practices across UK banks and foster the safe adoption of emerging technologies, such as machine learning, artificial intelligence, and large language models (LLMs). - -SS1/23 outlines these core principles: - -Model Identification and Model Risk Classification -: - Ensure a structured approach to accurately identify and categorize models within the model risk management (MRM) framework. -- Facilitate the proper management and oversight of models, aiding in the alignment of model risk management efforts with organizational risks and objectives. - -Governance -: - Establish a structured oversight mechanism for effective model risk management, delineating clear responsibilities and authorities. -- Ensure accountability, transparency, and effective communication within the organization regarding model risks and controls. - -Model Development, Implementation, and Use -: - Emphasize the correct development, deployment, and utilization of models as per the guidelines laid down in the MRM framework. -- Ensure models are developed and utilized in a manner consistent with their intended purposes and within acceptable risk boundaries. - -Independent Model Validation -: - Stress the importance of independent validation to ascertain model performance, accuracy, and identify potential issues. -- Provide an objective assessment of models to ensure they are functioning as intended and to identify any potential areas of improvement or correction. - -Model Risk Mitigants -: - Underline the necessity for measures to mitigate risks associated with model use, including the identification and implementation of controls. -- Help in reducing the potential adverse impact of model risks on the organization’s financial condition, reputation, and regulatory compliance. - -The regulation encourages a proportionate application of these principles based on the size and complexity of the institution. - -### Around the globe - -Other, similar guidelines and policies that {{< var vm.product >}} is designed to help you with include: - -:::: {.flex .flex-wrap .justify-around} - -::: {.w-50-ns} - -#### Guideline-E23: Enterprise-Wide Model Risk Management for Deposit-Taking Institutions - -Issued by the Office of the Superintendent of Financial Institutions (OSFI) in Canada, it outlines minimum prudent practices for model development, review, approval, use, and modification​​. - -::: - -::: {.w-40-ns} - -#### Principles for Model Risk Management - -Issued by the Financial Services Agency (FSA) in Japan in June 2021, this document was finalized after a consultation period and outlines principles for managing model risk​​​. - -::: - -:::: - -::: {.callout title="Read more:"} -- [SR 11-7](https://www.federalreserve.gov/supervisionreg/srletters/sr1107.htm) -- [SS1/23](https://www.bankofengland.co.uk/prudential-regulation/publication/2023/may/model-risk-management-principles-for-banks-ss) -- [Guideline-E23](https://www.osfi-bsif.gc.ca/Eng/fi-if/rg-ro/gdn-ort/gl-ld/Pages/e23.aspx) -- [Principles for Model Risk Management](https://www.fsa.go.jp/common/law/ginkou/pdf_03.pdf) - -::: - -### Meeting regulatory requirements with {{< var vm.product >}} - - As a robust tool for implementing Model Risk Management (MRM) best practices, including the _three lines of defense_, {{< var vm.product >}} significantly aids organizations in adhering to the regulatory guidelines set forth by SR 11-7 and SS1/23. - -:::: {.flex .flex-wrap .justify-around} - -::: {.w-40-ns} - -First line of defense — model developers -: {{< var vm.product >}} offers a suite of tools for model developers, facilitating thorough documentation and rigorous testing of models, aligning with the regulatory expectations of both SR 11-7 and SS1/23, particularly for models under regulatory purview. - -Second line of defense — model validators -: {{< var vm.product >}} empowers model validators with the ability to independently validate models ensuring adherence to the organization's MRM principles throughout the model lifecycle, a core requirement of these regulations. - -Third line of defense — auditors -: Enabling internal and external audits provides an independent and objective assurance to the organization by assessing the robustness of controls within the model risk management framework. It evaluates how well the first and second lines of defense are functioning, ensuring adherence to regulatory and organizational standards, thereby promoting a robust model risk management environment. - -Model inventory -: The {{< var vm.product >}} **{{< fa cubes >}} Inventory** encapsulates a centralized repository for all models, aiding in streamlined tracking, management, and monitoring, simplifying compliance with the inventory mandates specified in SR 11-7 and SS1/23. - -::: - -::: {.w-50-ns} -Lifecycle management and custom workflows -: {{< var vm.product >}}’s capabilities extend to effective model lifecycle management through configurable workflows. This structured approach to managing model risks across various lifecycle stages significantly aids in meeting the rigorous management and oversight expectations set by SR 11-7 and SS1/23. - -Model documentation automation -: By automating model documentation through configurable templates and test plans, {{< var vm.product >}} ensures consistent and accurate documentation capture, directly aligning with the documentation standards stipulated in these regulatory guidelines. - -Model validation and approval -: With automated validation features and comprehensive risk assessment tools, {{< var vm.product >}} aligns with the effective validation criteria and thorough risk evaluation mandates of SR 11-7 and SS1/23. - -Communication and tracking -: The built-in communication and tracking functionality of {{< var vm.product >}} facilitates seamless collaboration and understanding among stakeholders regarding model usage, limitations, and risks, fostering a collaborative environment as encouraged by these regulations. - -By integrating these features, {{< var vm.product >}} provides a comprehensive suite of tools that not only simplifies the path to compliance with SR 11-7 and SS1/23 but also embeds a culture of rigorous and transparent model risk management within the organization. - -::: - -:::: - -## Ready to try out {{< var vm.product >}}? - -:::{#quickstart} -::: - - - - -[^1]: [Working with the inventory](/guide/inventory/working-with-the-inventory.qmd) - -[^2]: [Preparing validation reports](/guide/validation/preparing-validation-reports.qmd) - -[^3]: [Setting up workflows](/guide/workflows/setting-up-workflows.qmd) - -[^4]: [Working with document templates](/guide/templates/working-with-document-templates.qmd) - -[^5]: [Export documents](/guide/reporting/export-documents.qmd) \ No newline at end of file diff --git a/site/about/use-cases/eu-ai-act.qmd b/site/about/use-cases/eu-ai-act.qmd index 7f34129327..02639a6180 100644 --- a/site/about/use-cases/eu-ai-act.qmd +++ b/site/about/use-cases/eu-ai-act.qmd @@ -28,7 +28,7 @@ The EU AI Act categorizes AI systems by risk level: ### Harmonization with other standards -The EU AI Act requirements overlap with existing model risk management frameworks. Organizations already following SR 11-7, SS1/23, or E-23 can leverage existing documentation and controls but must also comply with the EU AI Act requirements. +The EU AI Act requirements overlap with existing model risk management frameworks. Organizations already following SR 26-2, SS1/23, or E-23 can leverage existing documentation and controls but must also comply with the EU AI Act requirements. ## 1. Risk management system implementation (Article 9) diff --git a/site/about/use-cases/model-risk-management.qmd b/site/about/use-cases/model-risk-management.qmd index cae973dca0..b5d0926c25 100644 --- a/site/about/use-cases/model-risk-management.qmd +++ b/site/about/use-cases/model-risk-management.qmd @@ -4,6 +4,9 @@ # SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial title: "Model risk management" date: last-modified +aliases: + - /about/overview-model-risk-management.html + - /guide/overview-model-risk-management.html listing: id: quickstart type: grid @@ -126,19 +129,19 @@ Lifecycle {{< var vm.product >}} is designed to help organizations comply with MRM regulatory requirements: -### SR 11-7 (United States) +### SR 26-2 (United States) :::: {.columns} ::: {.column width="70%" .pr3} -The Supervisory Guidance on model risk management was issued by the Board of Governors of the Federal Reserve System and the Office of the Comptroller of the Currency. It provides comprehensive guidance on designing and maintaining a robust MRM framework. +*Interagency Guidance on Model Risk Management for Banking Organizations* was issued jointly by the Board of Governors of the Federal Reserve System, the Federal Deposit Insurance Corporation, and the Office of the Comptroller of the Currency. It supersedes SR 11-7 and sets expectations for a risk-based MRM program — including a narrowed model definition, materiality-based tiering, strong ongoing monitoring and outcomes analysis, and a comprehensive enterprise inventory. ::: ::: {.column width="30%" .pl3} -[SR 11-7 implementation guide](sr-11-7.qmd){.button} +[SR 26-2 implementation guide](sr-26-2.qmd){.button} ::: diff --git a/site/about/use-cases/sr-11-7.qmd b/site/about/use-cases/sr-11-7.qmd deleted file mode 100644 index ad4b573fda..0000000000 --- a/site/about/use-cases/sr-11-7.qmd +++ /dev/null @@ -1,226 +0,0 @@ ---- -# Copyright © 2023-2026 ValidMind Inc. All rights reserved. -# Refer to the LICENSE file in the root of this repository for details. -# SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -title: "SR 11-7" -date: last-modified ---- - -Implement SR 11-7 compliance using {{< var vm.product >}}. - -{{< include _use-case-summary.qmd >}} - -## Overview - -SR 11-7 (Supervisory Guidance on Model Risk Management)[^1] provides comprehensive guidance to financial institutions on developing and maintaining a robust model risk management framework. By emphasizing the three lines of defense model and the concept of "effective challenge" — SR 11-7 ensures that models are rigorously questioned and tested. - -This guide is organized around the expectations for the three main areas outlined in SR 11-7: - -1. Model development, implementation, and use - -2. Model validation - -3. Governance, policies, and controls - -## 1. Model inventory setup - -#### Purpose - -Establish a comprehensive model inventory aligned to SR 11-7 requirements. - -### Steps - -1. Establish model definition criteria: - - - Define what constitutes a model in your organization. - - Document inclusion and exclusion criteria. - - Classify models by type and purpose. - -2. Configure inventory fields:[^2] - - - Set up materiality and tiering fields. - - Add fields for model purpose and business use. - - Configure risk rating classifications. - -3. Populate the inventory:[^3] - - - Register existing models. - - Document model ownership and stakeholders. - - Track model lifecycle status. - -## 2. Model development documentation - -#### Purpose - -Document models according to SR 11-7 development standards. - -### Steps - -1. Configure document templates:[^4] - - - Select or create templates aligned to SR 11-7. - - Include sections for purpose, design, theory, and logic. - -2. Document purpose, design, theory, and logic:[^5] - - - Clearly state the model's intended use. - - Document the theoretical basis. - - Explain design choices and methodology. - -3. Document data quality and relevance: - - - Assess and document data sources. - - Evaluate data quality and limitations. - - Document data transformations. - -4. Track assumptions and limitations: - - - Document all model assumptions. - - Identify known limitations. - - Establish conditions under which the model should not be used. - -## 3. Testing and outcomes analysis - -#### Purpose - -Test models for accuracy, robustness, and stability per SR 11-7 requirements. - -### Steps - -1. Run automated testing using the {{< var validmind.developer >}}:[^6] - - - Execute accuracy tests. - - Run robustness and stability tests. - - Document test results. - -2. Perform sensitivity analysis and benchmarking: - - - Test model sensitivity to input changes. - - Compare against benchmarks or challenger models. - - Document performance boundaries. - -3. Evaluate limitations and assumptions: - - - Test assumption validity. - - Identify conditions where performance degrades. - - Document testing coverage. - -## 4. Independent validation (effective challenge) - -#### Purpose - -Implement independent validation aligned to SR 11-7's "effective challenge" concept. - -### Steps - -1. Configure validation workflows: - - - Set up validation initiation triggers. - - Define validation scope and requirements. - - Establish independence requirements. - -2. Prepare validation reports:[^7] - - - Use validation report templates. - - Document validation activities. - - Summarize findings and conclusions. - -3. Track findings and remediation:[^8] - - - Document validation findings. - - Assign remediation owners. - - Track remediation progress. - -## 5. Ongoing monitoring and periodic review - -#### Purpose - -Implement ongoing monitoring per SR 11-7 requirements. - -### Steps - -1. Set up monitoring workflows:[^9] - - - Configure monitoring frequency. - - Define monitoring metrics. - - Establish escalation procedures. - -2. Configure performance tracking and alerts: - - - Set up performance dashboards. - - Configure threshold-based alerts. - - Document alert response procedures. - -3. Schedule periodic reviews:[^10] - - - Establish review frequency by model tier. - - Configure review reminders. - - Document review requirements. - -## 6. Governance, policies, and controls - -#### Purpose - -Establish governance framework aligned to SR 11-7. - -### Steps - -1. Configure role-based access:[^11] - - - Set up roles for three lines of defense. - - Configure permissions by role. - - Ensure appropriate segregation of duties. - -2. Configure approval workflows:[^12] - - - Set up model approval processes. - - Define approval authorities. - - Configure escalation paths. - -3. Enable audit trail and compliance reporting:[^12] - - - Configure activity logging. - - Set up compliance dashboards. - - Generate audit reports. - -## Implementation checklist - -- [x] Model definition criteria established -- [x] Model inventory configured and populated -- [x] Document templates aligned to SR 11-7 -- [x] Testing framework implemented -- [x] Validation workflows configured -- [x] Ongoing monitoring established -- [x] Three lines of defense roles configured -- [x] Approval workflows in place -- [x] Audit trail enabled - - - - -[^1]: - - **Board of Governors of the Federal Reserve System:**
- [SR 11-7: Guidance on Model Risk Management](https://www.federalreserve.gov/supervisionreg/srletters/sr1107.htm) - -[^2]: [Manage inventory fields](/guide/inventory/manage-inventory-fields.qmd) - -[^3]: [Working with the inventory](/guide/inventory/working-with-the-inventory.qmd) - -[^4]: [Working with document templates](/guide/templates/working-with-document-templates.qmd) - -[^5]: [Working with documentation](/guide/documentation/working-with-documentation.qmd) - -[^6]: [Run tests and test suites](/developer/how-to/testing-overview.qmd) - -[^7]: [Preparing validation reports](/guide/validation/preparing-validation-reports.qmd) - -[^8]: [Working with artifacts](/guide/validation/working-with-artifacts.qmd) - -[^9]: [Ongoing monitoring](/guide/monitoring/ongoing-monitoring.qmd) - -[^10]: [Setting up workflows](/guide/workflows/setting-up-workflows.qmd) - -[^11]: [Manage permissions](/guide/configuration/manage-permissions.qmd) - -[^12]: [Working with analytics](/guide/reporting/working-with-analytics.qmd) diff --git a/site/about/use-cases/sr-26-2.qmd b/site/about/use-cases/sr-26-2.qmd new file mode 100644 index 0000000000..a37fd2e594 --- /dev/null +++ b/site/about/use-cases/sr-26-2.qmd @@ -0,0 +1,210 @@ +--- +# Copyright © 2023-2026 ValidMind Inc. All rights reserved. +# Refer to the LICENSE file in the root of this repository for details. +# SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial +title: "SR 26-2" +date: last-modified +aliases: + - /about/use-cases/sr-11-7.html +--- + +Implement SR 26-2 compliance using {{< var vm.product >}}. + +{{< include _use-case-summary.qmd >}} + +## Overview + +SR 26-2 (*Interagency Guidance on Model Risk Management for Banking Organizations*)[^1] was issued jointly by the Board of Governors of the Federal Reserve System, the Federal Deposit Insurance Corporation, and the Office of the Comptroller of the Currency. It supersedes SR 11-7 and reframes U.S. banking agencies’ expectations for model risk management (MRM). + +SR 26-2 keeps core themes from prior guidance — sound development, independent validation, governance, and effective challenge — while emphasizing a risk-based posture: a narrower definition of what counts as a model, an explicit materiality framework, stronger ongoing monitoring and outcomes analysis, and an enterprise model inventory that supports concentration and dependency visibility. + +::: {.callout title="Generative and agentic AI"} +SR 26-2 explicitly excludes generative AI and agentic AI from its scope because these technologies are novel and rapidly evolving. Underlying MRM principles — including materiality, ongoing monitoring, and effective challenge — still apply when you govern those systems alongside traditional models. +::: + +This guide organizes platform actions around four priorities that align with SR 26-2: + +1. **Distinguish models from non-models** — Focus MRM on *complex quantitative methods* that apply statistical, economic, or financial theory, rather than on simple arithmetic, purely deterministic rules, or software without substantive theoretical underpinning. + +2. **Assess and tier models by materiality** — Use model exposure and model purpose so high-materiality models receive commensurate rigor while lower-materiality models can use more automated governance where appropriate. + +3. **Emphasize ongoing monitoring and outcomes analysis** — Treat continuous performance tracking, outcomes testing, and escalation as first-class obligations, not only point-in-time validation events. + +4. **Maintain a comprehensive model inventory** — Keep enterprise visibility into models, dependencies, concentrations, and aggregate risk. + +## 1. Distinguish models from non-models + +#### Purpose + +Apply a clear, documented definition of *model* versus *non-model* so MRM effort targets SR 26-2 scope. + +### Steps + +1. Document inclusion and exclusion criteria: + + - Define which methods count as models under SR 26-2’s narrowed definition. + - Record exclusions (for example, simple spreadsheets, deterministic rules without quantitative theory) and the rationale. + +2. Align inventory registration rules:[^2] + + - Configure inventory fields that capture model type, theoretical basis, and intended analytical use. + - Ensure non-models are not inadvertently treated as in-scope models. + +3. Review the portfolio periodically: + + - Re-evaluate borderline tools when business use or complexity changes. + - Update documentation when classification decisions change. + +## 2. Assess and tier models by materiality + +#### Purpose + +Implement SR 26-2’s materiality lens — combining exposure and purpose — so controls scale with risk. + +### Steps + +1. Configure materiality and tiering fields:[^2] + + - Map organizational tiers to exposure and purpose dimensions. + - Align tiering to validation depth, monitoring frequency, and approval paths. + +2. Document purpose and business use:[^3] + + - Capture how each model affects decisions, capital, liquidity, or customers. + - Link materiality to reporting and committee oversight where required. + +3. Apply tier-aware workflows:[^10] + + - Automate reminders and approvals based on tier. + - Route high-materiality models to stricter documentation and validation templates. + +## 3. Ongoing monitoring, testing, and outcomes analysis + +#### Purpose + +Meet SR 26-2’s heightened expectations for continuous insight into model performance and outcomes, complementing periodic validation. + +### Steps + +1. Run automated testing in the {{< var validmind.developer >}}:[^6] + + - Execute accuracy, robustness, and stability tests on a defined cadence. + - Store results as evidence for monitoring and review. + +2. Configure monitoring and alerts:[^9] + + - Define metrics, thresholds, and escalation paths by materiality tier. + - Integrate outcomes analysis (for example, performance drift, decision quality) into review cycles. + +3. Schedule periodic reviews with monitoring context:[^10] + + - Combine monitoring dashboards, incidents, and validation history in each review. + - Document conclusions and required actions. + +## 4. Model development documentation + +#### Purpose + +Document models so development choices, data, theory, and limitations are transparent and reviewable. + +### Steps + +1. Configure document templates:[^4] + + - Align sections to SR 26-2 expectations for purpose, design, theory, and logic. + - Tier template depth by materiality. + +2. Document purpose, design, theory, and logic:[^5] + + - State intended use and decisions supported. + - Explain methodology, key assumptions, and known limitations. + +3. Document data quality and relevance: + + - Record data sources, transformations, and quality assessments. + - Highlight data gaps that affect reliability. + +## 5. Independent validation (effective challenge) + +#### Purpose + +Preserve effective challenge for in-scope models — independent validation that identifies limitations and supports sound use. + +### Steps + +1. Configure validation workflows: + + - Define independence rules and scope by materiality. + - Trigger validation when models change tier or materiality drivers shift. + +2. Prepare validation reports:[^7] + + - Use templates that capture findings, limitations, and conditions of use. + - Tie conclusions to monitoring metrics where applicable. + +3. Track findings and remediation:[^8] + + - Assign owners, due dates, and retest evidence. + - Close the loop into monitoring and inventory metadata. + +## 6. Governance, policies, and controls + +#### Purpose + +Operate a governance framework — policies, roles, approvals, and auditability — that matches SR 26-2’s risk-based MRM program. + +### Steps + +1. Configure role-based access:[^11] + + - Map the three lines of defense to platform roles. + - Enforce segregation of duties for high-materiality models. + +2. Configure approval workflows:[^12] + + - Encode model approvals, exceptions, and retirements. + - Maintain an audit trail for supervisory and internal review. + +3. Enable audit trail and compliance reporting:[^12] + + - Use activity logs and analytics for evidence of control operation. + - Export reports for committees and audits. + +## Implementation checklist + +- [x] Model versus non-model criteria documented and reflected in the inventory +- [x] Materiality and tiering configured with purpose and exposure fields +- [x] Ongoing monitoring, alerts, and outcomes analysis in place +- [x] Development documentation templates aligned to SR 26-2 +- [x] Validation workflows and effective challenge operating by tier +- [x] Governance roles, approvals, and audit evidence configured + + + + +[^1]: + + **Board of Governors of the Federal Reserve System, FDIC, and OCC:**
+ [SR 26-2: Interagency Guidance on Model Risk Management for Banking Organizations](https://www.federalreserve.gov/supervisionreg/srletters/SR2602.htm) (April 17, 2026; supersedes SR 11-7) + +[^2]: [Manage inventory fields](/guide/inventory/manage-inventory-fields.qmd) + +[^3]: [Working with the inventory](/guide/inventory/working-with-the-inventory.qmd) + +[^4]: [Working with document templates](/guide/templates/working-with-document-templates.qmd) + +[^5]: [Working with documentation](/guide/documentation/working-with-documentation.qmd) + +[^6]: [Run tests and test suites](/developer/how-to/testing-overview.qmd) + +[^7]: [Preparing validation reports](/guide/validation/preparing-validation-reports.qmd) + +[^8]: [Working with artifacts](/guide/validation/working-with-artifacts.qmd) + +[^9]: [Ongoing monitoring](/guide/monitoring/ongoing-monitoring.qmd) + +[^10]: [Setting up workflows](/guide/workflows/setting-up-workflows.qmd) + +[^11]: [Manage permissions](/guide/configuration/manage-permissions.qmd) + +[^12]: [Working with analytics](/guide/reporting/working-with-analytics.qmd) diff --git a/site/about/contributing/using-the-documentation.qmd b/site/about/using-the-documentation.qmd similarity index 98% rename from site/about/contributing/using-the-documentation.qmd rename to site/about/using-the-documentation.qmd index ac46d7acaf..ca5dee30ad 100644 --- a/site/about/contributing/using-the-documentation.qmd +++ b/site/about/using-the-documentation.qmd @@ -4,6 +4,8 @@ # SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial title: "Using the documentation" date: last-modified +aliases: + - /about/contributing/using-the-documentation.html --- This documentation site helps you learn {{< var vm.product >}}, implement it in your organization, govern your AI/ML models, and operate the platform day to day. @@ -25,7 +27,7 @@ Introduces the platform, its use cases, and deployment options. - [About {{< var vm.product >}}](/about/overview.qmd) — Platform overview and capabilities - [AI governance](/about/use-cases/ai-governance.qmd) — EU AI Act compliance and risk classification -- [Model risk management](/about/use-cases/model-risk-management.qmd) — SR 11-7, SS1/23, and E-23 compliance +- [Model risk management](/about/use-cases/model-risk-management.qmd) — SR 26-2, SS1/23, and E-23 compliance - [Library and platform](/about/library-and-platform.qmd) — How the {{< var validmind.developer >}} and {{< var validmind.platform >}} work together - [Deployment options](/about/deployment/deployment-options.qmd) — Multi-tenant cloud vs. Virtual Private {{< var vm.product >}} diff --git a/site/about/contributing/validmind-chatbot.png b/site/about/validmind-chatbot.png similarity index 100% rename from site/about/contributing/validmind-chatbot.png rename to site/about/validmind-chatbot.png diff --git a/site/guide/monitoring/ongoing-monitoring.qmd b/site/guide/monitoring/ongoing-monitoring.qmd index a5546282ea..e4cb438f01 100644 --- a/site/guide/monitoring/ongoing-monitoring.qmd +++ b/site/guide/monitoring/ongoing-monitoring.qmd @@ -40,7 +40,7 @@ listing: Monitoring of model performance in model risk management involves regularly assessing a model's accuracy, stability, and robustness to ensure it remains reliable after deployment. -Monitoring is a critical component of model risk management, as emphasized in regulations such as SR 11-7, SS1/23, and E-24,[^1] and includes: +Monitoring is a critical component of model risk management, as emphasized in regulations such as SR 26-2, SS1/23, and E-24,[^1] and includes: - Tracking key performance indicators, detecting model drift, recalibrating as needed, and validating assumptions. - Backtesting to verify predictive power, maintaining transparent reporting and governance, and ensuring ongoing compliance with regulatory standards. @@ -154,7 +154,7 @@ To try out monitoring, check out the code sample for ongoing monitoring of model -[^1]: [Regulatory requirements](/about/overview-model-risk-management.qmd#regulatory-requirements) +[^1]: [Regulatory requirements](/about/use-cases/model-risk-management.qmd#regulatory-frameworks) [^2]: [Working with documentation](/guide/documentation/working-with-documentation.qmd) diff --git a/site/guide/templates/_what-is-document-checker.qmd b/site/guide/templates/_what-is-document-checker.qmd index bb20d68bee..34206792f1 100644 --- a/site/guide/templates/_what-is-document-checker.qmd +++ b/site/guide/templates/_what-is-document-checker.qmd @@ -46,7 +46,7 @@ As a compliance tool, the {{< var validmind.checker >}} is most useful when your By default, {{< var vm.product >}} supports the following regulations: -- Federal Reserve Supervisory Letter SR 11-7 (United States) +- Federal Reserve Supervisory Letter SR 26-2 (United States) - Bank of England Prudential Regulation Authority (PRA) Supervisory Statement SS1/23 (United Kingdom) - Office of the Superintendent of Financial Institutions (OSFI) Guideline E-23 (Canada) - European Union Artificial Intelligence Act (Regulation (EU) 2024/1689, EU AI Act) diff --git a/site/index.qmd b/site/index.qmd index ac83bb25e9..711d89c7f1 100644 --- a/site/index.qmd +++ b/site/index.qmd @@ -530,7 +530,7 @@ Use [cases]{.pink} ::: {.f4 .blur} -{{< var vm.product >}} gives you the tools for effective [AI governance]{.pink .b} and [model risk management]{.pink .b}, whether you are working toward EU AI Act compliance or managing model risk under SR 11-7, SS1/23, or E-23. +{{< var vm.product >}} gives you the tools for effective [AI governance]{.pink .b} and [model risk management]{.pink .b}, whether you are working toward EU AI Act compliance or managing model risk under SR 26-2, SS1/23, or E-23. ::: diff --git a/site/llm/.quarto/project-cache/deno-kv-file b/site/llm/.quarto/project-cache/deno-kv-file new file mode 100644 index 0000000000..4e86411b58 Binary files /dev/null and b/site/llm/.quarto/project-cache/deno-kv-file differ diff --git a/site/llm/.quarto/project-cache/deno-kv-file-shm b/site/llm/.quarto/project-cache/deno-kv-file-shm new file mode 100644 index 0000000000..c2c3593c0f Binary files /dev/null and b/site/llm/.quarto/project-cache/deno-kv-file-shm differ diff --git a/site/llm/.quarto/project-cache/deno-kv-file-wal b/site/llm/.quarto/project-cache/deno-kv-file-wal new file mode 100644 index 0000000000..f7c8b9ab86 Binary files /dev/null and b/site/llm/.quarto/project-cache/deno-kv-file-wal differ diff --git a/site/llm/README.md b/site/llm/README.md index 83e6ca897b..91bd82bd9c 100644 --- a/site/llm/README.md +++ b/site/llm/README.md @@ -16,7 +16,7 @@ make render-llm This runs `llm/render.sh` (temporary minimal `_quarto.yml`, Quarto → GFM) and `llm/clean.sh` (Pandoc cleanup). Equivalent to the **Validate LLM markdown render** step in `.github/workflows/validate-docs-site.yaml`. -Excluded from the LLM render (among others): notebooks, internal pages, contributor style guide, and most of `about/contributing/`. **Included:** `about/contributing/using-the-documentation.qmd` (docs IA hub for agents). +Excluded from the LLM render (among others): notebooks, internal pages, contributor style guide, and most of `about/contributing/`. **Included:** `about/using-the-documentation.qmd` (docs IA hub for agents). Copied into `_llm-output/` after render: @@ -24,7 +24,7 @@ Copied into `_llm-output/` after render: |------|--------| | `AGENTS.md` | Repo root | | `chatbot-product-map.md` | Generated (see below) | -| `about/contributing/using-the-documentation.md` | Quarto render | +| `about/using-the-documentation.md` | Quarto render | See also [`AGENTS.md`](../../AGENTS.md) for how agents should use the corpus. diff --git a/site/llm/chatbot-product-map.md b/site/llm/chatbot-product-map.md index ad1e484cb6..d1361fcfac 100644 --- a/site/llm/chatbot-product-map.md +++ b/site/llm/chatbot-product-map.md @@ -2,7 +2,7 @@ > Auto-generated. Maps in-product routes to documentation URLs and key sections. > For how documentation is organized by topic, see `AGENTS.md` and -> [Using the documentation](/about/contributing/using-the-documentation.html). +> [Using the documentation](/about/using-the-documentation.html). ## Settings @@ -577,4 +577,4 @@ ## Documentation index (human-oriented) -See `AGENTS.md` and `about/contributing/using-the-documentation.md` in the LLM corpus for guides organized by feature area (Configuration, Workflows, Inventory, etc.). +See `AGENTS.md` and `about/using-the-documentation.md` in the LLM corpus for guides organized by feature area (Configuration, Workflows, Inventory, etc.). diff --git a/site/notebooks/use_cases/agents/document_agentic_ai.ipynb b/site/notebooks/use_cases/agents/document_agentic_ai.ipynb index 5076e93b9e..4b0d6cf915 100644 --- a/site/notebooks/use_cases/agents/document_agentic_ai.ipynb +++ b/site/notebooks/use_cases/agents/document_agentic_ai.ipynb @@ -2073,7 +2073,7 @@ "\n", "### Customize the banking agent for your use case\n", "\n", - "You've now built an agentic AI system designed for banking use cases that supports compliance with supervisory guidance such as SR 11-7 and SS1/23, covering credit and fraud risk assessment for both retail and commercial banking. Extend this example agent to real-world banking scenarios and production deployment by:\n", + "You've now built an agentic AI system designed for banking use cases that supports compliance with supervisory guidance such as SR 26-2 and SS1/23. While SR 26-2 explicitly excludes generative and agentic AI from its scope, underlying principles — materiality, ongoing monitoring, and effective challenge — still apply to governance of these systems. The example covers credit and fraud risk assessment for both retail and commercial banking. Extend this example agent to real-world banking scenarios and production deployment by:\n", "\n", "- Adapting the banking tools to your organization's specific requirements\n", "- Adding more banking scenarios and edge cases to your test set\n", diff --git a/site/releases/2023/2023-oct-25/highlights.qmd b/site/releases/2023/2023-oct-25/highlights.qmd index aa7f6f5d70..26d86b9730 100644 --- a/site/releases/2023/2023-oct-25/highlights.qmd +++ b/site/releases/2023/2023-oct-25/highlights.qmd @@ -215,7 +215,7 @@ We now programmatically embed our Jupyter Notebooks in our documentation site an :::: {.flex .flex-wrap .justify-around} ::: {.w-70-ns} -We expanded our platform overview to provide more background information about what {{< var vm.product >}} offers and how we enable you to comply with policies and regulations such as SR 11-7 and SS1/23. +We expanded our platform overview to provide more background information about what {{< var vm.product >}} offers and how we enable you to comply with policies and regulations such as SR 26-2 and SS1/23. ::: diff --git a/site/releases/2024/2024-dec-06/release-notes.qmd b/site/releases/2024/2024-dec-06/release-notes.qmd index d807996b97..ca302bc3f1 100644 --- a/site/releases/2024/2024-dec-06/release-notes.qmd +++ b/site/releases/2024/2024-dec-06/release-notes.qmd @@ -23,9 +23,9 @@ listing: max-description-length: 250 # image-height: 100% contents: - - path: ../../../about/overview-model-risk-management.qmd + - path: ../../../about/library-and-platform.qmd title: "Learn more —
{{< var validmind.platform >}}" - description: "The {{< var validmind.platform >}} offers an integrated solution to manage validation reports, track findings, and report on model risk compliance across your model portfolio." + description: "The {{< var validmind.platform >}} is an easy-to-use web-based interface that enables you to track the model lifecycle, customize workflows, and collaborate on documentation and validation." fields: [title, description] - id: academy type: grid diff --git a/site/releases/2024/2024-oct-22/release-notes.qmd b/site/releases/2024/2024-oct-22/release-notes.qmd index cbf0130253..ea144ea8d2 100644 --- a/site/releases/2024/2024-oct-22/release-notes.qmd +++ b/site/releases/2024/2024-oct-22/release-notes.qmd @@ -33,7 +33,7 @@ Labels: documentation ---> ### Support for ongoing monitoring -Monitoring is a critical component of model risk management, as emphasized in regulations such as SR 11-7, SS1/23, and E-24. With this release of {{< var vm.product >}}, we officially support ongoing monitoring. You can enable this feature for both existing and new models. +Monitoring is a critical component of model risk management, as emphasized in regulations such as SR 26-2, SS1/23, and E-24. With this release of {{< var vm.product >}}, we officially support ongoing monitoring. You can enable this feature for both existing and new models. ![Ongoing monitoring of a model](/releases/2024/2024-oct-22/358433496-02a6d5b9-0521-4110-b45c-b91e06798a97.png){fig-alt="An image showing some ongoing monitoring data on the ValidMind Platform" .screenshot} diff --git a/site/scripts/generate_chatbot_product_map.py b/site/scripts/generate_chatbot_product_map.py index 5df8f2c5e9..e1d6f51dd5 100644 --- a/site/scripts/generate_chatbot_product_map.py +++ b/site/scripts/generate_chatbot_product_map.py @@ -517,7 +517,7 @@ def render_markdown( "", "> Auto-generated. Maps in-product routes to documentation URLs and key sections.", "> For how documentation is organized by topic, see `AGENTS.md` and", - "> [Using the documentation](/about/contributing/using-the-documentation.html).", + "> [Using the documentation](/about/using-the-documentation.html).", "", ] @@ -581,7 +581,7 @@ def render_section(title: str, section_routes: list[ProductRoute]) -> None: lines.append("## Documentation index (human-oriented)") lines.append("") lines.append( - "See `AGENTS.md` and `about/contributing/using-the-documentation.md` in the " + "See `AGENTS.md` and `about/using-the-documentation.md` in the " "LLM corpus for guides organized by feature area (Configuration, Workflows, " "Inventory, etc.)." ) diff --git a/site/training/ai-governance/compliance-and-oversight.qmd b/site/training/ai-governance/compliance-and-oversight.qmd index 55746c12d3..cdd98a94c4 100644 --- a/site/training/ai-governance/compliance-and-oversight.qmd +++ b/site/training/ai-governance/compliance-and-oversight.qmd @@ -66,7 +66,7 @@ Key governance regulations include: | Regulation | Jurisdiction | Focus | |------------|--------------|-------| | [EU AI Act](https://eur-lex.europa.eu/eli/reg/2024/1689){target="_blank"} | European Union | Risk-based AI regulation | -| [SR 11-7](https://www.federalreserve.gov/supervisionreg/srletters/sr1107.htm){target="_blank"} | United States | Model risk management | +| [SR 26-2](https://www.federalreserve.gov/supervisionreg/srletters/SR2602.htm){target="_blank"} | United States | Model risk management | | [SS1/23](https://www.bankofengland.co.uk/prudential-regulation/publication/2023/may/model-risk-management-principles-for-banks-ss){target="_blank"} | United Kingdom | MRM principles | | [E-23](https://www.osfi-bsif.gc.ca/en/guidance/guidance-library/guideline-e-23-model-risk-management-2027){target="_blank"} | Canada | Enterprise-wide MRM & AI/ML risk | ::: @@ -96,7 +96,7 @@ Use our implementation guides for: ::: {.f4 .pl3 .pt2} [[AI Governance
[[[EU AI ACT]{.green}]{.bubble}]{.f5}](/about/use-cases/ai-governance.qmd){target="_blank"}]{.button .shadow-5-ns .f4 .content-tile style="width: 100%;"} -[[Model Risk Management
[[[SR 11-7]{.green}]{.bubble} [[SS1/23]{.green}]{.bubble} [[E-23]{.green}]{.bubble}]{.f5}](/about/use-cases/model-risk-management.qmd){target="_blank"}]{.button .shadow-5-ns .f4 .content-tile style="width: 100%;"} +[[Model Risk Management
[[[SR 26-2]{.green}]{.bubble} [[SS1/23]{.green}]{.bubble} [[E-23]{.green}]{.bubble}]{.f5}](/about/use-cases/model-risk-management.qmd){target="_blank"}]{.button .shadow-5-ns .f4 .content-tile style="width: 100%;"} ::: ::: @@ -126,7 +126,7 @@ Use our implementation guides for: - [AI governance](/about/use-cases/ai-governance.qmd){target="_blank" .button} - [EU AI Act](/about/use-cases/eu-ai-act.qmd){target="_blank" .button} -- [SR 11-7](/about/use-cases/sr-11-7.qmd){target="_blank" .button} +- [SR 26-2](/about/use-cases/sr-26-2.qmd){target="_blank" .button} - [SS1/23](/about/use-cases/ss1-23.qmd){target="_blank" .button} - [E-23](/about/use-cases/e-23.qmd){target="_blank" .button} --> diff --git a/site/training/program/learning-paths.qmd b/site/training/program/learning-paths.qmd index a7778e5519..8fc4cac2f2 100644 --- a/site/training/program/learning-paths.qmd +++ b/site/training/program/learning-paths.qmd @@ -391,7 +391,7 @@ Take a guided tour of {{< var vm.product >}} and discover how the platform helps #### Section 6
Risk Insights & Regulatory Alignment - Use AI-powered document checker for compliance -- Align with regulatory frameworks like SR 11-7, SS1/23, E-23, and EU AI Act +- Align with regulatory frameworks like SR 26-2, SS1/23, E-23, and EU AI Act - Generate risk assessments with recommendations ::: diff --git a/site/training/risk-governance-fundamentals.qmd/risk-governance-fundamentals.qmd b/site/training/risk-governance-fundamentals.qmd/risk-governance-fundamentals.qmd index 5a9603f32c..09e285d038 100644 --- a/site/training/risk-governance-fundamentals.qmd/risk-governance-fundamentals.qmd +++ b/site/training/risk-governance-fundamentals.qmd/risk-governance-fundamentals.qmd @@ -85,7 +85,7 @@ Get overviews for validation activities and risk exposure. TBD. ::: {.tc} -[Learn more ...](/about/overview-model-risk-management.qmd){.button target="_blank"} +[Learn more ...](/about/use-cases/model-risk-management.qmd){.button target="_blank"} ::: Or, find your next learning resource on [{{< var validmind.training >}}](/training/training.qmd). diff --git a/site/training/what-is-validmind/what-is-validmind-register.qmd b/site/training/what-is-validmind/what-is-validmind-register.qmd index 77dde88c75..1839864d57 100644 --- a/site/training/what-is-validmind/what-is-validmind-register.qmd +++ b/site/training/what-is-validmind/what-is-validmind-register.qmd @@ -103,7 +103,7 @@ Take a guided tour of {{< var vm.product >}} and discover how the platform helps #### Section 6
Risk Insights & Regulatory Alignment - Use AI-powered document checker for compliance -- Align with regulatory frameworks like SR 11-7, SS1/23, E-23, and EU AI Act +- Align with regulatory frameworks like SR 26-2, SS1/23, E-23, and EU AI Act - Generate risk assessments with recommendations ::: diff --git a/site/training/what-is-validmind/what-is-validmind.qmd b/site/training/what-is-validmind/what-is-validmind.qmd index 69767383ef..845c847e62 100644 --- a/site/training/what-is-validmind/what-is-validmind.qmd +++ b/site/training/what-is-validmind/what-is-validmind.qmd @@ -861,7 +861,7 @@ Use {{< var vm.product >}}'s {{< var vm.checker >}} to: - [Guide]{.b} you on how to improve clarity, completeness, and compliance. - [Align]{.b} with regulatory expectations for risk and model governance. - [SR 11-7]{.bubble .smallcaps} [SS1/23]{.bubble .smallcaps} [E-23]{.bubble .smallcaps} [EU AI ACT]{.bubble .smallcaps} + [SR 26-2]{.bubble .smallcaps} [SS1/23]{.bubble .smallcaps} [E-23]{.bubble .smallcaps} [EU AI ACT]{.bubble .smallcaps} ::: @@ -894,7 +894,7 @@ Use our implementation guides for: ::: {.f4 .pl3 .pt2} [[AI Governance
[[[EU AI ACT]{.green}]{.bubble}]{.f5}](/about/use-cases/ai-governance.qmd){target="_blank"}]{.button .shadow-5-ns .f4 .content-tile style="width: 100%;"} -[[Model Risk Management
[[[SR 11-7]{.green}]{.bubble} [[SS1/23]{.green}]{.bubble} [[E-23]{.green}]{.bubble}]{.f5}](/about/use-cases/model-risk-management.qmd){target="_blank"}]{.button .shadow-5-ns .f4 .content-tile style="width: 100%;"} +[[Model Risk Management
[[[SR 26-2]{.green}]{.bubble} [[SS1/23]{.green}]{.bubble} [[E-23]{.green}]{.bubble}]{.f5}](/about/use-cases/model-risk-management.qmd){target="_blank"}]{.button .shadow-5-ns .f4 .content-tile style="width: 100%;"} ::: :::