Control 3.8: Model Risk Management Alignment (SR 26-2 / OCC Bulletin 2026-13, applying SR 11-7 / OCC 2011-12 principles to generative AI)
Control ID: 3.8 Pillar: Compliance & Audit Regulatory Reference: SR 26-2 / OCC Bulletin 2026-13 (Revised Guidance on Model Risk Management, April 2026 — supersedes SR 11-7 / OCC Bulletin 2011-12 but explicitly excludes generative and agentic AI; firms using historical SR 11-7 / OCC Bulletin 2011-12 principles for Copilot should treat them as an internal-policy reference unless counsel approves a current supervisory-source mapping), OCC Bulletin 2025-26 (Model Risk Management — Community Bank Proportionality), ECOA (Equal Credit Opportunity Act), Fair Housing Act
Last Verified: 2026-09-23 Regulatory Applicability: Firm/counsel determination — see Regulatory Applicability Questions Governance Levels: Baseline / Recommended / Regulated
Regulatory update notice (April 2026): On April 17, 2026, the Federal Reserve, OCC, and FDIC jointly issued SR 26-2 (Federal Reserve) and OCC Bulletin 2026-13 (OCC) — Revised Guidance on Model Risk Management — which supersedes SR 11-7 and OCC Bulletin 2011-12. The revised guidance applies a risk-based approach scaled to institution size and complexity (most relevant to banking organizations with over $30B in total assets) and explicitly excludes generative and agentic AI models pending further regulatory consideration. Because Microsoft 365 Copilot is a generative AI system, the operative MRM expectations for Copilot remain undefined under the revised interagency framework; firms that continue to use SR 11-7 / OCC Bulletin 2011-12 principles for Copilot should document them as an internal-policy reference unless legal/MRM owners approve a current supervisory-source mapping. Organizations should monitor for forthcoming agency guidance on generative AI MRM and update their Copilot governance accordingly. See 3.8 Additional Resources for SR 26-2 link.
Companion control — generative-AI MRM (control 3.8a)
Generative-AI–specific governance is provided by the companion control 3.8a — Generative AI Model Governance, which pairs historical SR 11-7 / OCC Bulletin 2011-12 principles used as an internal-policy reference with genAI-specific frameworks (NIST AI RMF 1.0, ISO/IEC 42001). Because SR 26-2 / OCC Bulletin 2026-13 explicitly excludes generative and agentic AI, the operative interagency MRM expectations for Copilot remain undefined; 3.8 and 3.8a are therefore co-dependent and should be operated as a single integrated program rather than competing frameworks — 3.8 anchors the legacy MRM baseline while 3.8a supplies the genAI overlay. Regulatory-source mapping and current supervisory applicability: confirm.
Continue to monitor for forthcoming agency guidance on generative-AI MRM (which would fill the SR 26-2 / OCC 2026-13 exclusion). The framework's regulatory monitor (scripts/regulatory_monitor.py) tracks Federal Register publications from these agencies; for supervisory guidance issued outside the Federal Register (SR letters, OCC bulletins), watch federalreserve.gov/supervisionreg/srletters.htm and occ.gov/news-issuances/bulletins directly. See GitHub issue #3 for the decision record. See 3.8 Additional Resources for SR 26-2 link.
Regulatory applicability
Regulatory citations identify commonly referenced requirements. Applicability, record classification, and retention periods are a firm and counsel determination; this framework does not assert that any regulation applies or is satisfied. See the Regulatory Applicability Questions appendix.
Objective
Align Microsoft 365 Copilot governance with the firm's approved model risk management (MRM) policy, using OCC Bulletin 2011-12 and Federal Reserve SR 11-7 as historical internal-policy references where approved, including model inventory, validation scope, ongoing monitoring, and documentation -- while recognizing that Microsoft 365 Copilot is a vendor-provided model with limited internal validation scope, and focusing governance on usage controls and output monitoring. Address fair lending and ECOA considerations where counsel confirms Copilot outputs intersect with lending, advisory, or customer service contexts. Apply the proportionality guidance from OCC Bulletin 2025-26 as context where approved by legal/MRM owners.
Why This Matters for FSI
OCC Bulletin 2011-12 and Federal Reserve SR Letter 11-7 define model risk management expectations for banking organizations. These frameworks require institutions to identify, manage, and control the risks associated with models used in decision-making, reporting, and risk management activities. While the guidance was written before the widespread adoption of large language models (LLMs), regulatory expectations have expanded to include AI systems that influence or support business decisions.
Microsoft 365 Copilot presents a unique MRM challenge: it is a general-purpose LLM provided by Microsoft as a vendor service, not a model developed in-house for a specific quantitative purpose. SR 11-7 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." Copilot straddles this definition — it processes input and produces output, but it is not a traditional quantitative model designed for a specific financial decision. Institutions cannot validate the model's internal architecture, training data, or algorithmic mechanics in the traditional MRM sense. However, institutions can govern how the model is used, monitor its outputs, document its limitations, and implement compensating controls for known risks; regulator-expectation framing: confirm.
OCC Bulletin 2025-26 proportionality guidance: In 2025, the OCC issued community-bank model risk management clarification emphasizing flexibility for community banks to tailor validation frequency and scope to risk exposure, business activities, and model-use complexity. OCC Bulletin 2026-13 later superseded/rescinded the 2011 model-risk guidance while citing the community-bank proportionality context. For community banks and smaller institutions deploying Copilot, any simplified MRM approach should be documented as institution policy based on actual usage scope, recognizing that the 2026 revised guidance explicitly excludes generative and agentic AI models. Larger institutions with more complex Copilot deployments (client-facing activities, lending workflows, regulated advisory) should obtain model-risk/legal approval for the applicable internal framework.
The fair lending dimension adds urgency to MRM alignment. If Copilot generates customer communications, assists with lending decisions, or supports advisory activities, its outputs could inadvertently reflect biases relevant to the Equal Credit Opportunity Act (ECOA) or the Fair Housing Act. Approved use cases that participate in credit, housing, advisory, or other regulated decisions and the required monitoring: confirm.
Control Description
This control addresses the MRM framework alignment for Microsoft 365 Copilot, organized around the three pillars of OCC Bulletin 2011-12: model development (adaptation for vendor models), model validation, and ongoing monitoring.
Generative AI scope: Generative AI–specific governance is addressed by Control 3.8a — Generative AI Model Governance, which extends this control with NIST AI RMF 1.0, ISO/IEC 42001, and the SR 26-2 / OCC Bulletin 2026-13 generative AI exclusion mappings.
Copilot's Model Status Under SR 11-7 / OCC Bulletin 2011-12 (interim framework for generative AI)
The foundational question for any institution's MRM program is whether Microsoft 365 Copilot meets the SR 11-7 definition of a "model." Copilot occupies a gray zone: it processes input data and produces output, but it is not a traditional quantitative model built to generate specific financial estimates. One firm policy approach is to register Copilot in the model inventory as a limited-scope or lower-tier model, with governance focused on usage controls, output monitoring, and vendor due diligence rather than the validation infrastructure designed for in-house quantitative models; firms should confirm the classification with legal/MRM owners.
An illustrative approach is to classify Copilot as a Tier 3 (limited-scope) model when used primarily for internal productivity (document drafting, meeting summaries, research support), with escalation to Tier 2 or Tier 1 when deployed in client-facing, lending, or advisory workflows. This tier assignment should be documented in the model inventory with supporting rationale and confirmed with legal/MRM owners.
MRM Framework Adaptation for Vendor-Provided LLMs
| Traditional MRM Element | Microsoft 365 Copilot Adaptation |
|---|---|
| Model development and implementation | Vendor due diligence (Microsoft), usage policy definition, scope limitation |
| Model validation | Output quality monitoring, use-case-specific testing, vendor attestation review |
| Ongoing monitoring | Copilot output monitoring, usage analytics, bias detection, performance tracking |
| Model inventory | Register Copilot in the enterprise model inventory with usage scope and risk tier |
| Model documentation | Document Copilot capabilities, limitations, intended uses, and prohibited uses |
| Model governance | AI governance committee oversight, periodic review, risk appetite alignment |
Model Inventory Entry for Microsoft 365 Copilot
| Field | Value |
|---|---|
| Model name | Microsoft 365 Copilot |
| Model type | Large language model (LLM) -- vendor-provided SaaS |
| Vendor | Microsoft Corporation |
| Model owner (internal) | [CTO / Head of AI Governance] |
| Risk tier | Firm-approved example: Tier 3 (limited-scope) for internal productivity; Tier 2 for business unit decision support; Tier 1 for client-facing or lending workflows; confirm tiering with legal/MRM owners |
| Use cases | Document generation, communication drafting, data summarization, financial analysis assistance, research, meeting support |
| Prohibited uses | Autonomous investment recommendations, unsupervised lending decisions, compliance certifications without human review |
| Validation approach | Output monitoring, use-case testing, vendor attestation review |
| Validation frequency | Firm-approved example: quarterly output review; annual comprehensive assessment; confirm cadence with legal/MRM owners |
| Data inputs | Microsoft Graph (user's emails, files, chats, calendar), real-time prompt context |
| Outputs | Natural language text, document content, summaries, analysis |
| Known limitations | Hallucination risk, no real-time market data, potential bias in generated content, no guaranteed factual accuracy |
| Compensating controls | Human review requirements, output verification procedures, Communication Compliance monitoring, DLP policies |
Validation Scope for Vendor-Provided Models
Since institutions cannot perform traditional model validation (reviewing source code, training data, or algorithm mechanics), the validation scope focuses on:
- Vendor due diligence: Review Microsoft's responsible AI documentation, model cards, safety reports, and third-party audits (see Control 1.10)
- Use-case testing: Test Copilot outputs for specific FSI use cases to identify quality, accuracy, and bias issues
- Output monitoring: Continuously monitor Copilot outputs for hallucinations, inaccuracies, and biased language
- Boundary testing: Verify that Copilot respects configured guardrails (DLP, sensitivity labels, information barriers)
- Performance benchmarking: Establish baseline metrics for Copilot output quality and track over time
Fair Lending and ECOA Considerations
| Risk Area | Description | Monitoring Approach |
|---|---|---|
| Lending communications | Copilot-drafted communications to loan applicants may use language that differs based on applicant demographics | Sample Copilot-drafted lending communications for disparate language patterns |
| Customer segmentation | Copilot-generated analysis may reflect historical biases in customer data | Review Copilot-assisted segmentation outputs for protected class disparities |
| Product recommendations | Copilot-assisted product suggestions may vary based on customer characteristics reflected in grounding data | Test product recommendation outputs across diverse customer profiles |
| Complaint responses | Copilot-drafted complaint responses may exhibit different tone or helpfulness based on customer demographics | Sample and compare Copilot responses across customer segments |
| Marketing content | Copilot-generated marketing may inadvertently target or exclude protected classes | Review Copilot marketing content for fair lending compliance |
Copilot Surface Coverage
| Copilot Surface | MRM Relevance | Risk Level | Monitoring Focus |
|---|---|---|---|
| Word Copilot | High -- generates financial documents, loan documents, client proposals | High | Output accuracy, bias in generated language, factual correctness |
| Excel Copilot | High -- generates formulas, financial analyses, calculations | High | Calculation accuracy, formula correctness, analytical soundness |
| Outlook Copilot | High -- drafts client communications, lending correspondence | High | Language bias, UDAAP compliance, fair lending language |
| Microsoft Copilot Chat | Moderate -- research and analysis supporting decisions | Moderate | Hallucination rate, source attribution, factual accuracy |
| Teams Copilot | Moderate -- meeting recaps, client conversation summaries | Moderate | Accuracy of summaries, completeness, bias in summarization |
| PowerPoint Copilot | Moderate -- client presentations, investment reviews | Moderate | Data accuracy in generated slides, balanced presentation |
| Copilot Pages | Low-Moderate -- collaborative content creation | Low | Content accuracy when used for decision-support documents |
| Copilot Notebooks | Low-Moderate -- collaborative content creation | Low | Content accuracy when used for decision-support documents |
Governance Levels
Baseline
Applies to institutions of all sizes, calibrated to actual Copilot usage scope. OCC Bulletin 2025-26 is a community-bank clarification that remains relevant to proportionality and is referenced by OCC Bulletin 2026-13, while OCC Bulletin 2026-13 / Federal Reserve SR 26-2 supersedes and rescinds the 2011 model-risk guidance for traditional models and explicitly excludes generative and agentic AI. Annual validation is not mandatory for community banks solely because a fixed annual cadence was inferred from prior model-risk guidance; any Copilot-specific cadence should be approved as firm policy:
- Register Microsoft 365 Copilot in the enterprise model inventory with tier classification (Tier 3 for internal productivity, with documentation of the proportionality rationale for community banks per OCC Bulletin 2025-26). The AI inventory entry should include: tool name, version, purpose, business owner, deployment date, and risk classification
- Document Copilot's intended uses and prohibited uses within the institution
- Document the usage scope and confirm it aligns with the selected model tier, applying the proportionality principle — validation rigor scales with risk complexity and materiality:
- Custom AI (credit scoring, fraud detection): Full SR 11-7 validation required
- Microsoft 365 Copilot for productivity (no automated decision-making): Lower-risk; vendor due diligence + AI inventory entry sufficient
- Copilot in regulated workflows (loan memos, customer communications): Elevated risk; SR 11-7 applies proportionally
- Establish basic output monitoring through supervisory review of Copilot-assisted activities
- Document Copilot's known limitations and communicate them to all users
- Include Copilot in the institution's vendor risk management program (see Control 1.10)
- Designate an internal model owner responsible for Copilot MRM alignment
Recommended
- Conduct use-case-specific output quality assessments quarterly
- Implement automated output monitoring for hallucination and accuracy indicators
- Establish fair lending testing protocols for Copilot-assisted lending and advisory activities
- Create Copilot-specific model risk documentation that follows the firm's approved structure, using OCC Bulletin 2011-12 as a historical reference where approved, including these example elements:
- AI inventory entry: Tool name, version, purpose, business owner, deployment date, risk classification
- Vendor due diligence: Microsoft service agreements, DPA (Data Processing Agreement), transparency documentation
- Use case risk assessment: Input data types, output use, whether outputs inform regulated decisions
- Control environment documentation: Data access controls, audit logging enablement, DLP policies, retention policies
- Ongoing monitoring plan: Frequency of control testing, escalation procedures
- Change management log: Track Microsoft Copilot updates via Message Center
- Implement periodic output quality monitoring to track accuracy and hallucination rates over time
- Leverage Microsoft tools to collect MRM-relevant data:
- Microsoft Purview Data Security Posture Management (including DSPM for AI/classic capabilities): data risk assessments for oversharing, AI app activity reports, sensitive-information findings in prompts/responses where supported, and recommendations/policies such as risky-AI-usage detection — feeds risk assessment
- Purview Audit (UAL): Interaction logs, accessed resources, sensitivity labels on accessed files
- Microsoft Defender for Cloud Apps: discover, monitor, and block generative AI apps, including app catalog/risk-score review and custom policies for Generative AI app usage
- Viva Insights Copilot Dashboard: Usage frequency, adoption metrics, active user counts
- Insider Risk Management (Risky AI usage): Alerts on risky Copilot interactions — document as control test results
- Review Microsoft's responsible AI reports and model updates annually
- Integrate Copilot MRM into the institution's model risk governance committee
- Track Copilot output quality metrics over time and report trends to the AI governance committee
- Document compensating controls for each identified model risk area
- Conduct vendor due diligence review of Microsoft Copilot documentation (SOC 2, AI Impact Assessment, data processing terms)
Regulated
Firm-approved tier guidance for institutions deploying Copilot in client-facing, lending, or complex financial workflows. Note: For Copilot used solely as a productivity tool with no automated decision-making, annual comprehensive validation is not assumed solely from OCC Bulletin 2025-26; firms should confirm with legal/MRM owners when the regulated tier applies because Copilot outputs materially affect bank decisions, customer communications, or lending activities:
- Conduct annual comprehensive MRM assessment for Copilot aligned with SR 11-7 / OCC Bulletin 2011-12 expectations, including validation report focused on usage controls and output quality (not internal model architecture, which is Microsoft's responsibility as vendor)
- Implement ongoing fair lending monitoring for Copilot-assisted activities with statistical testing for disparate impact
- Commission independent third-party assessment of Copilot governance framework effectiveness
- Maintain model risk quantification metrics (e.g., output error rates, hallucination frequency, bias detection rates)
- Establish model risk appetite limits for Copilot and trigger enhanced controls when limits are approached
- Prepare examination-ready MRM documentation package for OCC, Federal Reserve, or other banking regulators, organized to include: AI inventory, vendor due diligence, use case risk assessments, control environment documentation, monitoring plan, and change management log
- Implement challenger or benchmark testing where Copilot outputs for specific use cases are compared against human or alternative system outputs
- Conduct stress testing of Copilot governance controls (e.g., what happens when Copilot output quality degrades)
Setup & Configuration
Step 1: Register Copilot in Model Inventory
- Open the institution's model inventory system (GRC platform, spreadsheet, or MRM tool)
- Create a new model entry using the Model Inventory Entry template in this control
- Classify Copilot at the appropriate risk tier based on actual usage scope and the institution's MRM policy — applying OCC Bulletin 2025-26 proportionality where appropriate:
- Tier 1 (High): If Copilot is used in client-facing activities, lending workflows, or financial reporting — full MRM lifecycle applies under the firm's approved MRM framework
- Tier 2 (Medium): If Copilot is used only for internal productivity without direct client impact — output monitoring and periodic vendor review
- Tier 3 (Low / Limited-scope): If Copilot usage is limited to non-regulated administrative tasks — model inventory entry with usage scope documentation; community banks with primarily internal Copilot use may apply this tier as firm policy using OCC Bulletin 2025-26 proportionality context
- Assign an internal model owner and document the governance chain
- Document the proportionality rationale if applying a simplified MRM approach (cite OCC Bulletin 2025-26 and describe how Copilot usage scope and institution size support the tier selection)
Step 2: Document Use-Case Scope
- Catalog all approved Copilot use cases within the institution:
| Use Case | Business Unit | Risk Level | Approval Status |
|---|---|---|---|
| Client email drafting | Wealth management | High | Approved with supervisory review |
| Financial analysis assistance | Corporate finance | High | Approved with output verification |
| Meeting summarization | All departments | Low | Approved |
| Research and information gathering | Compliance | Medium | Approved |
| Lending communication drafting | Consumer lending | High | Approved with fair lending monitoring |
| Marketing content generation | Marketing | High | Approved with FINRA 2210 review |
- Document prohibited use cases and the rationale for each prohibition
- Establish a process for requesting approval of new Copilot use cases
Step 3: Establish Output Monitoring
- Define output quality metrics for each high-risk use case:
- Accuracy: Percentage of Copilot outputs containing factual errors (target: < 5%)
- Hallucination rate: Percentage of Copilot outputs containing fabricated information (target: < 2%)
- Bias indicators: Number of Copilot outputs flagged for potential bias (target: declining trend)
- Compliance alignment: Percentage of Copilot-drafted communications passing regulatory review (target: > 95%)
- Implement monitoring through:
- Communication Compliance policy results (see Control 3.4)
- Supervisory review sampling results (see Control 3.6)
- User-reported output errors
- Periodic quality audits of Copilot outputs
Step 4: Implement Fair Lending Monitoring
- Identify Copilot-assisted activities that intersect with fair lending obligations:
- Loan application correspondence
- Credit decision support
- Customer communication for loan products
- Marketing for lending products
- Establish testing methodology:
- Sample Copilot-drafted lending communications across demographic segments
- Compare language, tone, helpfulness, and accuracy across segments
- Test for disparate impact using paired testing scenarios
- Document findings and remediation actions
- Report fair lending monitoring results to the fair lending officer and compliance committee
Step 5: Prepare MRM Documentation Package
Create a Copilot MRM documentation package containing:
- Model overview: Capabilities, limitations, vendor information, and tier classification with proportionality rationale (if applicable)
- Use-case register: Approved and prohibited uses
- Validation approach: Output monitoring, use-case testing, vendor attestation
- Monitoring results: Quarterly output quality metrics and trends
- Fair lending assessment: Testing methodology and results
- Compensating controls: Human review requirements, DLP, Communication Compliance
- Vendor due diligence: Microsoft responsible AI documentation review
- Risk assessment: Residual risk after compensating controls
- Governance: Committee oversight, review cadence, escalation procedures
Financial Sector Considerations
OCC and Federal Reserve Examination Focus
Banking regulators increasingly ask about AI and LLM governance during examinations. Institutions should prepare for potential questions about:
- How Copilot is classified in the model inventory and whether the proportionality determination is documented
- What validation has been performed on Copilot outputs (recognizing the vendor-model limitation)
- How fair lending risks from Copilot are monitored
- What compensating controls exist for model risk areas that cannot be directly validated
- How the institution assesses vendor (Microsoft) model governance practices
Proportionality Principle (OCC Bulletin 2025-26)
MRM program depth should scale with usage scope, institutional size, and risk. OCC Bulletin 2025-26 provides community-bank proportionality context; firms should confirm with legal/MRM owners how that context applies to Copilot and whether a community bank using Copilot only for internal meeting summaries and document drafting has different MRM obligations than a large complex banking organization using Copilot to draft lending communications or assist with investment recommendations.
For institutions applying the proportionality principle, the documentation approach should record the usage scope, institution characteristics, and citation (OCC Bulletin 2025-26) supporting the simplified MRM approach. This documentation provides evidence for legal/MRM owner review of the proportionality determination — not an informal decision to skip the MRM framework.
Vendor Model Risk vs. In-House Model Risk
Traditional MRM frameworks assume the institution has visibility into model internals. For vendor-provided LLMs like Copilot, the MRM focus shifts to:
- Input controls: What data Copilot can access (permissions, DLP, information barriers)
- Output controls: How Copilot outputs are reviewed, verified, and approved
- Usage controls: Which use cases are approved and which are prohibited
- Monitoring controls: How output quality and bias are tracked over time
- Vendor governance: How Microsoft governs the underlying model
Generative-AI Supervisory Source Monitoring
No specific 2023 interagency AI guidance source is cited here. Firms should not treat Copilot as exempt from governance simply because it is a vendor-provided general-purpose tool rather than a purpose-built financial model, and should confirm the applicable MRM framework with legal and MRM owners.
Verification Criteria
| # | Verification Step | Expected Outcome | Governance Level |
|---|---|---|---|
| 1 | Verify Copilot is registered in the model inventory | Model entry exists with complete fields including risk tier, model owner, and proportionality rationale (if applicable) | Baseline |
| 2 | Review use-case documentation | Approved and prohibited uses are documented and communicated | Baseline |
| 3 | Verify known limitations are documented and communicated | Limitation documentation is available to all Copilot users | Baseline |
| 4 | Verify proportionality determination is documented | OCC Bulletin 2025-26 cited with usage scope and institution characteristics supporting tier selection as a firm policy rationale | Baseline (community banks) |
| 5 | Review quarterly output quality metrics | Metrics are tracked and reported for high-risk use cases | Recommended |
| 6 | Verify periodic output quality monitoring is implemented | Output monitoring covers accuracy, hallucination rate, and bias indicators | Recommended |
| 7 | Verify fair lending testing is conducted | Testing methodology and results are documented | Recommended |
| 8 | Review AI governance committee minutes for Copilot discussion | Copilot MRM is a regular agenda item | Recommended |
| 9 | Verify annual comprehensive MRM assessment is completed | Assessment follows the firm-approved structure; SR 11-7 / OCC Bulletin 2011-12 may be used as a historical internal-policy reference where approved | Regulated |
| 10 | Review third-party assessment results | Independent assessment validates governance framework effectiveness | Regulated |
| 11 | Verify examination-ready MRM documentation package | Complete package is assembled and current | Regulated |
| 12 | Review fair lending statistical testing results | Disparate impact testing shows no statistically significant bias in Copilot-assisted lending activities | Regulated |
Additional Resources
- OCC Bulletin 2011-12 rescission status — replaced by OCC Bulletin 2026-13
- Historical SR 11-7 / OCC 2011-12 model risk management guidance attachment
- OCC Bulletin 2026-13 (Model Risk Management: Revised Guidance, April 2026 — supersedes 2011-12; excludes generative/agentic AI)
- OCC Bulletin 2025-26 (Model Risk Management — Community Bank Proportionality)
- Federal Reserve SR 26-2 (Revised Guidance on Model Risk Management, April 17, 2026 — supersedes SR 11-7)
- Equal Credit Opportunity Act (ECOA)
- Fair Housing Act
- Microsoft Responsible AI principles
- Microsoft 365 Copilot data, privacy, and security
- Control 1.10 -- Vendor Risk Management
-
Control 3.9 -- AI Disclosure, Transparency, and SEC Marketing Rule
-
Related Controls: 3.8a Generative AI Model Governance, 3.7 Regulatory Reporting, 1.10 Vendor Risk Management, 3.9 AI Disclosure and Transparency
FSI Copilot Governance Framework v1.8.0 - July 2026