At a glance

  • An AI governance policy is the organization-level policy for AI systems, from inventory and risk tiering through approval, monitoring, board reporting, and retirement. Staff rules for using AI tools belong in the separate acceptable use policy.
  • As of November 15, 2026, we found no US federal or state statute that requires every company to adopt an AI governance policy. EU AI Act Article 17 requires providers of high-risk AI systems to document a quality management system in written policies, procedures and instructions, including an accountability framework for management and other staff, from December 2, 2027 (Annex III) or August 2, 2028 (Annex I Section A). Insurance regulators expect a written AI program or written AI policies under board or senior management oversight from the insurers their rules cover. In Colorado, Regulation 10-1-1 sets a governance framework, including board oversight, for the insurers it covers.
  • OMB Memorandum M-25-21 requires federal agencies, not private companies, to retain or designate a Chief AI Officer and, for CFO Act agencies, to convene an AI governance board chaired at the Deputy Secretary level or equivalent.
  • Colorado SB 26-189, which applies to consequential decisions made on or after January 1, 2027, contains no risk management program or impact assessment duty, though the 2024 law it replaced required both. As of November 3, 2026, a federal court order limited Attorney General enforcement of the new law. In Texas, the framework clause in Sec. 552.105(e) of HB 149 attaches to the internal review route, so a company that adopts a recognized AI risk management framework but never runs the internal review gets nothing from the framework alone.

What is an AI governance policy?

An AI governance policy is the document in which an organization sets how it approves, owns, assesses, tests, monitors, and retires AI systems. It covers scope and definitions, the AI inventory, risk tiering, roles and an AI governance committee, approval gates before deployment, impact or risk assessment, vendor review, testing and monitoring, incidents, records, board reporting, and a review cycle. No statute covered in this guide requires a document by that name, but several rules require or expect the program it describes.

Its readers are the people who build, buy, and oversee AI: system owners, risk, legal, compliance, privacy, security, procurement, and the board. The AI acceptable use policy guide covers the staff-facing policy: approved tools, data rules, prohibited uses, human review, and disclosure. Some companies combine the two. A combined policy should keep the governance sections whole, because those are the sections an examiner or auditor walks through.

Which rules require or expect an AI governance program?

As of November 15, 2026, the binding requirements reach defined groups: providers and deployers within the EU AI Act’s reach, insurers covered by Colorado’s Regulation 10-1-1, and federal agencies. Colorado SB 26-189 and Texas HB 149 set no policy mandate, but their duties and defenses need an owner and a process. The NAIC bulletin, Circular Letter No. 7, and the bank model risk material are guidance. The broker-dealer and adviser material applies existing rules, and the frameworks are voluntary.

  • EU AI Act. Under Article 17(1), from December 2, 2027 (Annex III) or August 2, 2028 (Annex I Section A), providers of high-risk AI systems must put a quality management system in place that ensures compliance with the Regulation, documented in a systematic and orderly manner in the form of written policies, procedures and instructions, and including at least the aspects it lists, among them a strategy for regulatory compliance, the Article 9 risk management system, post-market monitoring, serious incident reporting procedures, record-keeping, and an accountability framework setting out the responsibilities of the management and other staff. Under Article 17(2), as amended in 2026, implementation must be proportionate to the size of the provider’s organisation, in particular for an SME, including a start-up, or an SMC, but providers must in any event respect the degree of rigour and the level of protection required for their high-risk systems to comply. A provider that is a financial institution subject to internal governance requirements under Union financial services law meets the duty by complying with those rules, except points (g), (h), and (i) (Article 17(4)). As of November 15, 2026, EN 18286:2026 was the harmonised standard cited for Article 17. Deployers of high-risk systems carry the Article 26 operating duties on the same dates and, for the deployers Article 27 lists, a fundamental rights impact assessment. Article 4 has applied to providers and deployers since February 2, 2025 and, as amended in 2026, requires measures to support AI literacy without guaranteeing a level for any individual.
  • Insurers. The NAIC Model Bulletin, adopted December 4, 2023, expects a written AI Systems Program with senior management accountable to the board or a board committee, in the states that have adopted it. Circular Letter No. 7 says insurers authorized in New York that use AI systems or external consumer data in underwriting or pricing “should formalize their development and management of ECDIS and AIS in written policies and procedures.” Colorado’s Regulation 10-1-1 (3 CCR 702-10) sets a governance framework that includes board oversight, a cross-functional governance group, an inventory, ongoing monitoring that accounts for model drift, an annual review, and annual reporting for life insurers that use external consumer data and, since October 15, 2025, private passenger auto and health benefit plan insurers. The framework must be designed to determine whether the insurer’s use of that data and of algorithms and predictive models using it potentially results in unfair discrimination with respect to race; its quantitative testing piece follows testing requirements the Division establishes, and the insurance guide tracks their status.
  • Banks, broker-dealers, and advisers. SR 26-2, OCC Bulletin 2026-13, and FDIC FIL-15-2026 cover governance and controls for the models within their scope. The agencies say the guidance is expected to be most relevant to banking organizations with more than $30 billion in total assets, footnote 3 states that generative and agentic AI models are not within its scope, and non-compliance with the guidance will not by itself result in supervisory criticism. FINRA Regulatory Notice 24-09 says the securities rules, including Rule 3110 on supervision, apply to generative AI, and creates no new requirements. In its fiscal year 2026 priorities, the SEC Division of Examinations said it would assess policies and procedures to monitor or supervise AI use. See the financial services guide.
  • Federal agencies. M-25-21, issued April 3, 2025, governs only agencies’ own use of AI and states that it does not create rights or obligations for the public. Its Chief AI Officer and governance board requirements are in the committee section below.

What should each section of the policy say?

Write each section to the strictest rule that reaches you. A row marked voluntary or guidance still shows what an examiner, auditor, or customer will look for.

AI governance policy sections and the rules that require or expect them, as of November 15, 2026
Policy sectionWhat it should sayRule that requires or expects itBinding or voluntary
Scope and definitionsWhich systems the policy covers and which role the organization holds for each: provider, deployer, developerEU AI Act role definitions; Colorado SB 26-189 definition of covered ADMT and its exclusions (C.R.S. 6-1-1701); M-25-21: no system should be considered too simple to qualify as covered AI due to a lack of technical complexityBinding (EU; Colorado from January 1, 2027); M-25-21 binds agencies only
AI inventoryEvery system in use, under development, or recently retired, with owner, vendor, purpose, and the decision it touchesCircular Letter No. 7 documentation; Colorado Regulation 10-1-1 inventory; M-25-21 annual AI use case inventory; NIST GOVERN 1.6Guidance (NYDFS); binding regulation (Colorado insurers); agencies only (OMB); voluntary (NIST)
Risk tieringCriteria that sort each system into a tier, with the legal triggers namedEU high-risk classification (Article 6 and Annex III); Colorado consequential decisions; M-25-21 process for determining and documenting high-impact use cases; NIST GOVERN 1.3Binding (EU from the high-risk dates; Colorado from 2027); agencies only (OMB); voluntary (NIST)
Roles and accountabilityA named accountable executive, owners for each system, and who may accept riskEU Article 17(1)(m) accountability framework (high-risk providers); NAIC senior management accountability to the board; Circular Letter No. 7 clearly defined roles and responsibilities; M-25-21 Chief AI Officer; NIST GOVERN 2Binding (EU from the high-risk dates); guidance (NAIC, NYDFS); agencies only (OMB); voluntary (NIST)
AI governance committeeCharter, members, quorum, and the decisions reserved to itColorado Regulation 10-1-1 cross-functional governance group (Colorado insurers); NAIC governance committees; M-25-21 agency AI governance board (CFO Act agencies)Binding regulation (Colorado insurers); guidance (NAIC); agencies only (OMB)
Approval gates before deploymentWhat each tier must complete before go-live, and who signsEU Article 9 risk management system and Article 17(1)(d) examination, test and validation procedures; M-25-21 independent review of high-impact use cases before risk acceptance; Colorado notice before useBinding (EU from the high-risk dates; Colorado from 2027); agencies only (OMB)
Impact or risk assessmentWhich tiers need an assessment, what it contains, and when it is repeatedEU Article 27 fundamental rights impact assessment for listed deployers; M-25-21 impact assessment before deploying high-impact AI; Colorado SB 26-189: none (the 2024 duty was repealed)Binding (EU from December 2, 2027); agencies only (OMB)
Vendor reviewDue diligence before purchase and oversight afterColorado Regulation 10-1-1 documented process for selecting and overseeing vendors (the insurer stays responsible); NAIC processes for acquiring and overseeing third-party AI systems and data; Circular Letter No. 7 (responsibility stays with the insurer); SR 26-2 vendor and third-party models; NIST GOVERN 6Binding regulation (Colorado insurers); guidance (NAIC, NYDFS, banking agencies); voluntary (NIST)
Testing and monitoringPre-deployment testing, ongoing performance and drift monitoring, and who reviews resultsEU Article 26(5) deployer monitoring; Article 17(1)(h) post-market monitoring (providers); Circular Letter No. 7 testing for unfair discrimination; Colorado Regulation 10-1-1 documented testing and drift monitoring, with quantitative testing under Division requirements; SR 26-2 validation and monitoring; M-25-21 ongoing monitoring of high-impact AIBinding (EU from the high-risk dates; Colorado insurers); guidance (NYDFS, banking agencies); agencies only (OMB)
IncidentsWhat counts as an incident, who is told, how fast, and when use is suspendedEU Article 26(5) and Article 17(1)(i); NIST GOVERN 4.3; Texas 60-day cure process (Sec. 552.104)Binding (EU from the high-risk dates; Texas); voluntary (NIST)
Records and retentionWhat is kept, by whom, and for how longColorado: at least 3 years (C.R.S. 6-1-1702(4) and 6-1-1703); EU Article 18: provider documentation for 10 years; EU Article 26(6): deployer logs at least six monthsBinding (Colorado from 2027; EU from the high-risk dates)
Board reporting and review cycleWhat the board receives, how often, and when the policy is reviewedNAIC board or board committee oversight; Circular Letter No. 7 review and approval at least annually; Colorado Regulation 10-1-1 board oversight and annual reporting; NIST GOVERN 1.5 and 2.3Guidance (NAIC, NYDFS); binding regulation (Colorado insurers); voluntary (NIST)

AI governance committee: who sits on it and what it decides

For insurers, two rules covered in this guide describe the committee. Colorado’s Regulation 10-1-1 requires the insurers it covers to keep a documented cross-functional governance group with representatives from key functional areas, including legal, compliance, risk management, product development, underwriting, actuarial, data science, marketing, and customer service, as applicable. The NAIC bulletin, in adopting states, gives as an example committees of representatives from appropriate disciplines and units within the insurer, such as business units, product specialists, actuarial, data science and analytics, underwriting, claims, compliance, and legal. Outside insurance, the closest public model is M-25-21, which binds federal agencies only. Within 60 days of the memo, each agency head had to retain or designate a Chief AI Officer with the necessary authority, positioned highly enough to engage regularly with other agency leadership, including the Deputy Secretary or equivalent. Within 90 days, each CFO Act agency had to convene its relevant officials to coordinate and govern issues related to the use of AI within the Executive Branch, and may rely on an existing governance body to do so. The board must have a chair at the Deputy Secretary level or equivalent and the Chief AI Officer as vice-chair, include representation from offices responsible for IT, cybersecurity, data, budget, statistics, legal counsel, privacy, civil rights, and civil liberties, add agency management, human capital, procurement, customer experience, program evaluation, and program office officials when relevant, and consult external experts as needed and appropriate.

For a company, the same structure translates into a chair who is the senior executive accountable for AI risk, consistent with NIST GOVERN 2.3, under which executive leadership takes responsibility for decisions about risks associated with AI system development and deployment. Members usually come from legal, compliance, privacy, security, data, model risk, procurement, and the business lines that own the systems, with human resources added where AI touches hiring or discipline. The charter should reserve these decisions to the committee:

  • Approve the tiering criteria and the risk tolerance behind them
  • Approve, condition, or reject deployment of systems in the highest tiers
  • Accept residual risk in writing, or name the official who may
  • Decide when an incident requires suspension and regulator notice
  • Grant, time-limit, and log exceptions to the policy
  • Approve the annual review and the report to the board

Exceptions need limits. M-25-21 lets a Chief AI Officer waive one or more minimum practices for a specific covered AI application or component only after a written determination, based on a system-specific and context-specific risk assessment, that fulfilling the requirement would increase risks to safety or rights overall or would create an unacceptable impediment to critical agency operations. Each waiver must be recertified annually, and the agency must publicly release a summary of it to the extent consistent with law. A company policy can copy that discipline: written grounds, a named approver, and an expiry.

What should happen before an AI system goes live?

Each tier should have a gate, and the gate should list the evidence that must exist before the system is used on real people or real decisions.

  1. Classify. Record the role and the legal triggers: EU high-risk classification, a Colorado consequential decision that covered ADMT materially influences, or, for agencies, a high-impact determination. The EU high-risk AI systems guide covers Article 6 and Annex III.
  2. Assess. From December 2, 2027, under Article 27(1), before deploying a high-risk system referred to in Article 6(2), other than one intended to be used in the area listed in point 2 of Annex III, deployers that are bodies governed by public law or private entities providing public services, and deployers of systems referred to in points 5(b) and (c) of Annex III, must assess the impact on fundamental rights that the use of the system may produce. The assessment covers six listed elements, the last of which is the measures to be taken in the case of the materialisation of the identified risks, including the arrangements for internal governance and complaint mechanisms. Under Article 27(3), the deployer then notifies the market surveillance authority of the results, except where Article 46(1) exempts it. M-25-21 requires agencies to complete an AI impact assessment before deploying any high-impact AI use case. Colorado SB 26-189 requires no impact assessment. The AI impact assessment guide gives each law’s contents.
  3. Test. Article 9(2) describes the risk management system as a continuous iterative process planned and run throughout the entire lifecycle of a high-risk system, requiring regular systematic review and updating, and Article 17(1)(d) requires a provider’s quality management system to include examination, test and validation procedures before, during and after development, with their frequency.
  4. Review the vendor. Bought systems go through the same gate. The AI vendor risk assessment guide lists the questions by law, and the model cards guide covers the documentation a developer owes.
  5. Prepare notices and human review. For decisions made on or after January 1, 2027, Colorado requires notice before covered ADMT is used to materially influence a consequential decision, and its definition of meaningful human review starts with a reviewer the deployer designates who has authority to approve, modify, or override the decision and is trained to conduct the review. C.R.S. 6-1-1701(15) lists the other conditions, and the policy should meet all of them. Under Article 26(7), once the high-risk duties apply, a deployer that is an employer must inform workers’ representatives and the affected workers before putting a high-risk system into use at a workplace.
  6. Sign off. Record who approved, on what evidence, with what conditions, and when the system will be reassessed.

What should the policy say about monitoring, incidents, and records?

Under Article 26(5), once the high-risk duties apply, a deployer monitors operation on the basis of the instructions for use; where it has reason to consider that use in accordance with the instructions may result in the system presenting a risk, it informs the provider or distributor and the market surveillance authority without undue delay and suspends use, and where it identifies a serious incident it immediately informs the provider, then the importer or distributor and the market surveillance authorities. If the deployer cannot reach the provider, Article 73 on serious incident reporting applies to the deployer mutatis mutandis. A deployer that is a financial institution subject to internal governance requirements under EU financial services law meets the monitoring duty by complying with those rules. NIST GOVERN 4.3 calls for organizational practices that enable AI testing, identification of incidents, and information sharing.

For records, Colorado requires deployers to keep records reasonably necessary to demonstrate compliance for at least 3 years after the decision, and developers to keep compliance records for at least three years after a record is created. Once the high-risk duties apply, Article 18 requires a high-risk provider to keep documentation including its technical documentation and quality management system documentation for 10 years after the system is placed on the market or put into service, and Article 26(6) requires deployers to keep the logs under their control for at least six months, unless other Union or national law provides otherwise. NIST GOVERN 1.7 calls for processes and procedures for decommissioning and phasing out AI systems safely and in a manner that does not increase risks or decrease the organization’s trustworthiness, so retirement belongs in the policy too.

What should the board see, and how often?

The board, or a board committee, should receive a report at least once a year and after any material incident or law change, and should approve the policy.

Circular Letter No. 7 says an insurer’s board of directors or other governing body, one of its committees, or senior management acting under delegated authority should review and approve the insurer’s policies and procedures for AI systems and external consumer data at least annually, and that policies and procedures should include clearly defined roles and responsibilities, as well as monitoring and reporting requirements to senior management. A useful board report covers inventory changes, systems approved or rejected in the highest tiers, incidents and suspensions, testing results that crossed a threshold, open exceptions, and law changes that affect the policy.

Where do the NIST AI RMF and ISO/IEC 42001 fit?

The two frameworks are voluntary, and neither makes a company compliant with any law by itself. They give the policy a structure and, in Texas, a route to a defense.

GOVERN 1 of the NIST AI RMF reads: “Policies, processes, procedures, and practices across the organization related to the mapping, measuring, and managing of AI risks are in place, transparent, and implemented effectively.” GOVERN 2 calls for accountability structures so that the appropriate teams and individuals are empowered, responsible, and trained for mapping, measuring, and managing AI risks.

ISO/IEC 42001:2023 is a certifiable AI management system standard. The NIST AI RMF to ISO/IEC 42001 crosswalk listed on NIST’s AI Resource Center, contributed by Microsoft and drawn against the final draft (FDIS) text of the standard, maps GOVERN 1.2 to clauses including 5.2 (AI policy), GOVERN 2.1 to clauses including 5.3 (roles, responsibilities and authorities), and GOVERN 2.3 to clauses including 5.1 (leadership and commitment) and 9.3.1 to 9.3.3 (management review: general, inputs, and results). A crosswalk shows where topics meet; it does not make one document satisfy the other. The NIST AI RMF guide and the AI governance frameworks guide compare the two.

In Texas, under Sec. 552.105(e) of HB 149, a defendant may not be found liable for a violation it discovers through an internal review process if it substantially complies with the most recent version of the NIST Generative AI Profile or another nationally or internationally recognized AI risk management framework; feedback, testing, and following state agency guidelines are separate discovery routes that need no framework. Colorado’s 2024 law gave a framework-based defense. SB 26-189 contains no framework safe harbor, and a federal court order in X.AI LLC v. Weiser bars Colorado’s Attorney General from enforcing SB 26-189, including by investigation, for violations occurring on or before 14 days after the court rules on xAI’s preliminary injunction motion; xAI had not filed that motion as of November 3, 2026. The Colorado SB 26-189 guide covers the law and the litigation.

AI governance policy template: which sections map to which rule?

This outline is a starting point and is not complete for any one law or sector. Each section is tagged with the rules it helps satisfy; a tag does not mean the rule reaches your organization, and several tagged rules reach only insurers, banks, or federal agencies. Check each applicable provision in full.

  1. Purpose, scope, and definitions, including the roles the organization holds. (EU role definitions; Colorado 6-1-1701; M-25-21 covered AI)
  2. Relationship to other policies: acceptable use, privacy, security, model risk, procurement. (NYDFS Part 500 letter; SR 26-2; FINRA Rule 3110 supervisory procedures)
  3. Roles and accountability: accountable executive, system owners, risk acceptance authority. (EU 17(1)(m); NAIC; Circular Letter No. 7; NIST GOVERN 2; ISO/IEC 42001 clause 5.3 per crosswalk)
  4. AI governance committee charter. (Colorado Regulation 10-1-1 governance group; NAIC; M-25-21 governance board for agencies; NIST GOVERN 2.3; ISO/IEC 42001 clause 5.1 per crosswalk)
  5. AI inventory: fields, owner, update trigger. (Circular Letter No. 7; Colorado Regulation 10-1-1; M-25-21; NIST GOVERN 1.6)
  6. Risk tiering criteria and risk tolerance. (EU Article 6 and Annex III; Colorado consequential decisions; M-25-21 high-impact determination; NIST GOVERN 1.3)
  7. Approval gates by tier. (EU 9 and 17(1)(d); M-25-21 independent review before risk acceptance)
  8. Impact and risk assessment. (EU 27; M-25-21 impact assessment; NIST MAP)
  9. Vendor and third-party AI. (Colorado Regulation 10-1-1; NAIC; Circular Letter No. 7; SR 26-2; NIST GOVERN 6)
  10. Testing, validation, and monitoring. (EU 17(1)(d) and (h), 26(5); Circular Letter No. 7; Colorado Regulation 10-1-1; SR 26-2)
  11. Human oversight and review: who may override, their training and authority. (EU 26(2); Colorado 6-1-1701(15) and 6-1-1705)
  12. Incident management and regulator notice. (EU 17(1)(i) and 26(5); Texas 552.104; NIST GOVERN 4.3)
  13. Records, retention, and decommissioning. (Colorado 6-1-1702(4) and 6-1-1703; EU 18 and 26(6); NIST GOVERN 1.7)
  14. Training and AI literacy for the people who run the program. (EU 4; Circular Letter No. 7; NIST GOVERN 2.2)
  15. Framework alignment and internal review. (Texas 552.105(e); NIST AI RMF; ISO/IEC 42001 clause 5.2 per crosswalk)
  16. Board reporting, exceptions, and annual review. (Circular Letter No. 7; NAIC; Colorado Regulation 10-1-1; NIST GOVERN 1.5; ISO/IEC 42001 clauses 9.3.1 to 9.3.3 per crosswalk)

How do you put an AI governance policy in place?

  • Build the AI inventory before writing the policy, including vendor systems and systems under development, and record your role for each system and the jurisdictions where its output is used and where the people it affects live
  • Charter the committee with members, quorum, reserved decisions, and written risk acceptance
  • Write tiering criteria that name the legal triggers that apply to you, and have the committee approve them
  • Set a gate for each tier, and do not let a system in the highest tier go live without its assessment, test results, notices, and sign-off on file
  • Name a monitoring owner for each system, with suspension triggers and incident routes that meet Article 26(5) where it applies
  • Set retention to the longest rule that applies to each record
  • If you rely on Texas Sec. 552.105(e), adopt the framework, run the internal review under it on a schedule, and log what it finds and when
  • Report to the board at least annually, and review the policy after each material incident or law change

For the EU duties behind several sections, see the EU AI Act compliance guide.

This guide is general information as of November 15, 2026, not legal advice. Confirm current requirements with the primary source, your regulator, or counsel before adopting a policy.

Common questions

Is an AI governance policy legally required?

As of November 15, 2026, we found no US federal or state statute that requires every company to adopt one. EU AI Act Article 17 requires providers of high-risk AI systems to document a quality management system in the form of written policies, procedures and instructions, including an accountability framework for management and other staff, from December 2, 2027 (Annex III) or August 2, 2028 (Annex I Section A). The NAIC model bulletin, in adopting states, expects insurers to keep a written AI Systems Program with senior management accountable to the board or a board committee, Colorado's Regulation 10-1-1 sets a governance framework for the insurers it covers, and OMB M-25-21 sets governance requirements for federal agencies only.

How is an AI governance policy different from an AI acceptable use policy?

A governance policy sets how the organization approves, owns, assesses, tests, monitors, and retires AI systems: the inventory, risk tiering, the committee, approval gates, vendor review, incidents, records, and board reporting. An acceptable use policy tells staff which AI tools they may use, with which data, and for what. Some companies combine the two in one document.

Who should sit on an AI governance committee?

Outside insurance, no private-sector rule covered in this guide sets the membership. Colorado's Regulation 10-1-1 requires the insurers it covers to keep a documented cross-functional governance group with representatives from key functional areas, including legal, compliance, risk management, underwriting, actuarial, and data science, as applicable. OMB M-25-21, which binds federal agencies only, requires each CFO Act agency's AI governance board to have a chair at the Deputy Secretary level or equivalent and the Chief AI Officer as vice-chair, with representation from offices responsible for IT, cybersecurity, data, budget, statistics, legal counsel, privacy, civil rights, and civil liberties, and other disciplines when relevant. A company committee usually draws on legal, compliance, privacy, security, data, model risk, procurement, and the business lines that own the systems, chaired by the senior executive accountable for AI risk.

By industry: all 8 industry pages

Sources

  1. Regulation (EU) 2024/1689 (Artificial Intelligence Act), consolidated text as of July 27, 2026, as amended by Regulation (EU) 2026/1744, EUR-Lex, Articles 4, 9, 17, 18, 26, 27, and 113, accessed November 15, 2026.
  2. Regulation (EU) 2026/1744 (Digital Omnibus on AI), EUR-Lex, July 24, 2026.
  3. Commission Implementing Decision (EU) 2026/2274 of 12 October 2026 on the harmonised standards for high-risk AI systems drafted in support of Regulation (EU) 2024/1689 of the European Parliament and of the Council, Official Journal of the European Union, L series, October 14, 2026.
  4. NAIC Model Bulletin: Use of Artificial Intelligence Systems by Insurers, National Association of Insurance Commissioners, December 4, 2023.
  5. Implementation of NAIC Model Bulletin: Use of Artificial Intelligence Systems by Insurers (status as of November 3, 2026), National Association of Insurance Commissioners, November 2026.
  6. Insurance Circular Letter No. 7 (2024): Use of Artificial Intelligence Systems and External Consumer Data and Information Sources in Insurance Underwriting and Pricing, New York State Department of Financial Services, July 11, 2024.
  7. Cybersecurity Risks Arising from Artificial Intelligence and Strategies to Combat Related Risks, New York State Department of Financial Services, October 16, 2024.
  8. Amended Regulation 10-1-1 (3 CCR 702-10), Governance and Risk Management Framework Requirements for Life Insurers’, Private Passenger Automobile Insurers’, and Health Benefit Plan Insurers’ Use of External Consumer Data and Information Sources, Algorithms, and Predictive Models, Colorado Division of Insurance, effective October 15, 2025, linked from the Division’s notice of adoption of August 20, 2025.
  9. SR 26-2: Revised Guidance on Model Risk Management, Federal Reserve Board, April 17, 2026.
  10. OCC Bulletin 2026-13, Model Risk Management: Revised Guidance, Office of the Comptroller of the Currency, April 17, 2026.
  11. FIL-15-2026, Agencies Revise Interagency Model Risk Management Guidance, FDIC, April 17, 2026.
  12. Regulatory Notice 24-09, FINRA, June 27, 2024.
  13. Fiscal Year 2026 Examination Priorities, SEC Division of Examinations, November 17, 2025.
  14. OMB Memorandum M-25-21, Accelerating Federal Use of AI through Innovation, Governance, and Public Trust, Office of Management and Budget, April 3, 2025.
  15. SB 26-189, Session Laws 2026, Chapter 131 (enrolled act), Colorado General Assembly, approved May 14, 2026.
  16. Docket, X.AI LLC v. Weiser, No. 1:26-cv-01515 (D. Colo.), Minute Order, ECF No. 24 (April 27, 2026), CourtListener RECAP, accessed November 3, 2026.
  17. H.B. No. 149 (enrolled), Texas Responsible Artificial Intelligence Governance Act, Texas Legislature, 2025.
  18. Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1 (PDF), National Institute of Standards and Technology, January 26, 2023.
  19. AI RMF Playbook: Govern, NIST AI Resource Center, accessed November 15, 2026.
  20. NIST AI Risk Management Framework to ISO/IEC 42001 Crosswalk (PDF), contributed by Microsoft, listed on the NIST AI Resource Center crosswalks page, accessed November 15, 2026.
  21. ISO/IEC 42001:2023, Information technology, Artificial intelligence, Management system, International Organization for Standardization, December 2023.