Colorado AI Act in 2026: What Changed and What Applies From January 1, 2027

The Colorado AI Act that most guides describe, SB 24-205, is no longer the law that will apply. In May 2026 Colorado repealed and reenacted it as SB 26-189, a narrower statute focused on automated decision-making technology that takes effect on January 1, 2027. The replacement drops the original law’s risk-management programs, annual impact assessments, and duty of reasonable care to prevent algorithmic discrimination, and centers instead on notices to consumers, explanations after adverse decisions, consumer rights, developer disclosures, and record keeping. This article explains how the law changed, what SB 26-189 requires of developers and deployers, where enforcement stands, and what organizations should do before January 1. How the Colorado AI Act Changed The statute has had a short and complicated history. The timeline below shows why so much published guidance is out of date. Date Event May 17, 2024 SB 24-205 signed, with obligations set to begin February 1, 2026 August 28, 2025 SB 25B-004 signed in a special session, moving the start date to June 30, 2026 April 2026 An AI developer files a federal constitutional challenge; the U.S. Department of Justice intervenes in support; a federal court stays enforcement on April 27, 2026 May 14, 2026 SB 26-189 signed, repealing and reenacting the law in narrower form, effective January 1, 2027 Second half of 2026 Attorney General rulemaking under way, with proposed rules reported in August 2026 The table explains the confusion. Guides written before May 2026 describe duties, such as impact assessments, that the replacement law does not carry forward. Some analyses note that the original text was technically on the books from June 30, 2026 until its repeal takes effect, but with enforcement stayed by the court. For planning purposes, SB 26-189 is the law to prepare for. What SB 26-189 Requires SB 26-189 applies to businesses that develop or use automated decision-making technology (ADMT) to materially influence consequential decisions affecting Colorado residents, in areas such as employment, consumer credit and lending, health care, housing, insurance, and education. Covered technology can include AI features embedded in third-party platforms, such as HR systems, underwriting software, or patient intake tools, even when the business did not build them. Original Law Versus the Replacement Obligation SB 24-205 (original) SB 26-189 (from January 1, 2027) Duty of reasonable care to prevent algorithmic discrimination Yes Removed Deployer risk-management program Yes Removed Annual impact assessments Yes Removed Self-reporting discrimination risks to the Attorney General Yes Removed Developer disclosures to deployers Yes Retained Consumer notice before or at the time of use Yes Retained, as a public pre-use notice Explanation after an adverse decision Yes Retained, within 30 days of the decision Consumer rights to correct data and request human review Yes Retained Three-year record retention for developers and deployers Not cited in analyses as a separate duty New requirement The table shows the shift from proactive governance duties to transparency and consumer rights. That does not make the law trivial: notices, adverse-decision explanations, and data correction and human review processes all need working procedures, and the three-year record requirement needs systems that can produce evidence. Developer Obligations Developers, which include businesses that build, sell, license, or substantially modify ADMT, must give deployers documentation and material updates covering intended uses, categories of training data, known limitations, reasonably foreseeable harmful uses, and instructions for human oversight. The law also makes contract terms unenforceable when they shift liability for a party’s own discriminatory use of ADMT, which affects indemnification clauses. Deployer Obligations Deployers must publish a notice to consumers before, or at the time, a covered ADMT is used. When ADMT materially contributes to an adverse consequential decision, the deployer must, within 30 days, tell the consumer the decision, the role the ADMT played, and how to seek reconsideration. Consumers can access and correct personal data used in the decision and request meaningful human review. Enforcement The law does not create a private right of action. The Colorado Attorney General enforces it and can impose fines, with an opportunity to cure violations available during an initial period. Law firm analyses report that the federal court’s April 2026 stay may also reach the successor law, and that practical enforcement depends on the Attorney General’s rules, so enforcement may not begin on January 1. The obligations still take effect on that date. What to Do Before January 1, 2027 With less than two months to the effective date, the practical work is to find the covered uses and build the procedures the law requires. Six steps cover most organizations. Step 1: Map Consequential-Decision Uses List every place where an automated tool materially influences a decision about a Colorado resident in employment, lending, health care, housing, insurance, education, or similar areas. Include AI features embedded in vendor platforms, which are easy to miss. Elevate’s article on AI inventories that capture built, procured, and embedded AI describes how to find them. Step 2: Determine Your Role for Each Use For each tool, decide whether the organization is a developer, a deployer, or both. A company that substantially modifies a vendor’s model can become a developer for that tool. Step 3: Prepare Notices and Adverse-Decision Disclosures Draft the public pre-use notice so it can be published by the effective date, and build a process to send adverse-decision explanations within 30 days. The explanation has to state the decision, the tool’s role, and how to seek reconsideration. Step 4: Set Up Consumer Request Handling Create documented procedures for consumers to access and correct personal data used in a decision and to request meaningful human review. Assign owners and response times. Step 5: Review Vendor Contracts Confirm that vendors who supply covered tools will provide the developer disclosures the law requires, and review indemnification and risk-allocation terms, since the law makes some liability-shifting provisions unenforceable. Elevate’s guide to AI vendor reviews in procurement covers what to ask. Step 6: Retain Records and Track Rulemaking Put controls in place to keep records of covered ADMT use for three years, and

Executive Order 14434: Why the Federal Government Now Says Super Intelligence Instead of AI

Executive Order 14434, “Inaugurating the Era of Super Intelligence,” directs federal agencies to use the terms “Super Intelligence” and “SI” in place of “artificial intelligence” and “AI.” The President signed it on September 29, 2026, and it was published in the Federal Register on October 2, 2026. The change is mostly one of vocabulary: the order defines Super Intelligence as exactly the technologies the existing statutory definition of artificial intelligence already covers. But the new term is already appearing in regulatory documents, and organizations that work with federal agencies need to read it correctly. This article explains what the order does, what it does not change, and how compliance teams should handle the new terminology. What Executive Order 14434 Does The order has three operative parts. A New Term in Federal Communications Section 1 states that current systems increasingly represent not merely artificial intelligence but a new era of Super Intelligence, and sets the policy that, to the maximum extent permitted by law, the executive branch will use “Super Intelligence” and “SI” instead of “artificial intelligence” and “AI.” Section 2 applies that to agencies’ official correspondence, public communications, websites, reports, policy documents, and other non-statutory documents. The Same Legal Meaning Section 3(a) defines Super Intelligence, for the purposes of the order and except where the law provides otherwise, as the technologies and systems covered by the definition of artificial intelligence in 15 U.S.C. 9401(3), the definition from the National Artificial Intelligence Initiative Act of 2020. The order does not create a capability threshold or a new category of system. A chatbot, a credit model, or an autonomous agent that was “AI” under federal law before September 29 is “SI” in agency documents after it, and nothing more. A Definition Still to Come Section 3(b) directs the Assistant to the President for Science and Technology to propose legislative language for a federal definition of Super Intelligence within 60 days, which falls in late November 2026. Commentators reading the order note that the proposal is to consider whether the new term should expand or supersede the statutory definition of artificial intelligence. Any such change would require an Act of Congress; until then, the existing definition governs. What Changed and What Did Not Because the order changes words rather than definitions, its effect depends on the kind of document. Document or obligation Effect of Executive Order 14434 Federal statutes Unchanged. Laws that say “artificial intelligence” keep that term and its definition until Congress acts Existing regulations, contracts, and grants Not rewritten by the order, according to published analyses of its text New agency guidance, reports, and communications Use “Super Intelligence” and “SI” to the extent permitted by law NIST frameworks such as the AI RMF The published frameworks are unchanged; new NIST communications, as agency documents, may use the new term International standards such as ISO/IEC 42001 Unaffected; they are not U.S. government documents State laws and the EU AI Act Unaffected; the order binds the federal executive branch only The table shows why the order matters more for reading than for compliance. No new obligation arises from it. What changes is the language in which federal guidance now arrives, and an organization that searches agency documents only for “AI” may miss new guidance entirely. The First Regulatory Example The OCC’s supervisory framework for banks, issued on November 4, 2026 as Bulletin 2026-54, is an early example. It adopts “super intelligence” throughout, explains in a footnote that the term follows Executive Order 14434, and applies to the generative and agentic systems that banks have been calling AI. A compliance team that reads it as guidance about a new technology category, rather than about its existing AI use cases, would misread its scope. Elevate’s analysis of the OCC super intelligence framework covers that guidance in detail. What Is Still Open The legislative proposal due in late November 2026 could suggest a broader or different statutory definition. If Congress later adopted one, the scope of federal AI rules could change. Until then, the order is a naming policy, and organizations should treat SI and AI as equivalent in federal documents. What Compliance Teams Should Do The order creates no new obligations, so the response is small and mostly about vocabulary. Five steps prevent the new term from causing confusion. Step 1: Add an Equivalence Clause to AI Policies Add one sentence to the definitions section of the AI governance policy stating that references to Super Intelligence or SI in federal laws, guidance, or contracts are treated as references to AI under the policy. This keeps the policy’s scope intact when regulators and customers change terms. Elevate’s AI policy template guide covers where definitions sit in a policy. Step 2: Update Regulatory Monitoring Add “Super Intelligence” and “SI” to the keywords used to track federal guidance, rulemakings, and agency announcements. New federal documents will increasingly use only the new term. Step 3: Keep Inventories and Intake Forms as They Are The AI inventory, risk tiering, and intake process do not need new categories, because the order does not change which systems are covered. If federal customers or examiners ask for a list of SI use cases, the existing AI inventory is that list. Step 4: Read Federal Contracts Carefully New solicitations and contract clauses from agencies may use SI. Where a contract defines the term, that definition controls. Where it does not, the order’s definition points back to the statutory definition of artificial intelligence; contract and legal teams should confirm that reading with counsel for significant agreements. Step 5: Watch the Legislative Proposal The proposed statutory definition due in late November 2026 is the one development that could change scope. Track whether it is released and whether Congress acts on it. Elevate helps organizations build AI governance programs that hold up to changes in regulation and terminology, including ISO/IEC 42001 programs and, for financial institutions, CRI FS AI RMF readiness. To review your AI policy definitions, talk to an Elevate advisor. Conclusion Executive Order 14434

FRONTIER Act and VET AI Act: What Independent AI Assurance Means for AI Buyers

The FRONTIER Act, introduced in the House on July 23, 2026 as H.R. 9925, would require the largest AI developers to publish safety frameworks, report serious incidents, and submit to independent audits. In the Senate, the VET AI Act takes a different route to the same goal: it would direct NIST to write voluntary guidelines for how AI systems are tested and verified by third parties. Neither bill is law. Together they show where federal AI policy is heading on one question that matters to every organization buying AI: who checks whether a developer’s safety claims are true. This article explains what each bill would require, how they differ, where they stand, and what organizations that buy and deploy AI can do with that information now. Why Independent AI Assurance Is Moving Into Federal Law Most of what organizations know about the safety of the AI models they use comes from the developers themselves: model cards, system cards, published policies, and voluntary commitments. Those documents are useful, but they are self-reported. The idea behind both bills is that a claim of safety should be verifiable by someone other than the party making it, the same logic that produced financial audits and security attestations in other markets. Two pressures push this into federal law. The first is a growing body of state legislation on frontier AI safety. The FRONTIER Act’s own summary names California SB 53, New York’s RAISE Act, and Illinois SB 315 as the statutes its preemption clause targets, and it presents a single federal standard as an alternative to a state-by-state patchwork. The second is that regulators of AI users are moving in the same direction. On November 4, 2026, the OCC issued a supervisory framework that asks how banks obtain evidence that AI controls keep working, including through independent challenge and external testing. Elevate covers that framework in [INTERNAL LINK: OCC Super Intelligence Framework article, add URL after publication]. What the FRONTIER Act Would Require The FRONTIER Act (Frontier Risk Oversight, National Transparency, Independent Evaluation, and Reporting Act) was introduced by Representatives Lori Trahan and Jay Obernolte with a bipartisan group of cosponsors. It grew out of the broader Great American AI Act framework the two released earlier as a discussion draft. The descriptions below follow the sponsors’ section-by-section summary. Who It Covers The bill applies to developers of frontier models, defined as foundation models trained with more than 10^26 operations, counting the original training run and any substantial later modification. Within that group it creates two higher tiers based on revenue and AI development spending over the preceding 36 months. A large frontier developer has gross revenues above $50 million and at least $1 billion in AI development expenditures. A very large frontier developer has gross revenues above $5 billion and at least $10 billion in such expenditures. Each higher tier carries every obligation of the tiers below it. Tier Threshold Main obligations Frontier developer Has trained or begun training a model above 10^26 operations Publish a transparency report before or when deploying a new or substantially modified frontier model; report critical safety incidents Large frontier developer Revenues above $50M and at least $1B in AI development spending Write, implement, and publish a frontier AI framework; undergo an annual independent compliance audit and publish the redacted report; register; report catastrophic risk, including from internal use Very large frontier developer Revenues above $5B and at least $10B in AI development spending Retain a licensed independent verification organization for ongoing assessment, with access to unredacted materials The tiers mean the bill reaches only a small number of companies. Most organizations that use AI, including banks, insurers, and software vendors that build on top of foundation models, would not be covered as developers. What Counts as a Catastrophic Risk and a Critical Incident The bill defines catastrophic risk narrowly: a foreseeable, material risk that a frontier model contributes to 50 or more deaths or serious injuries, or more than $1 billion in property damage, in a single incident. The incident must involve the model helping to develop or release a chemical, biological, radiological, nuclear, or cyber weapon, acting without meaningful human oversight in a way that would be a crime such as a cyberattack or theft, or evading the control of its developer or user. A critical safety incident is broader. It includes unauthorized access to or theft of model weights, harm from a catastrophic risk that has materialized, loss of control of a model, and a model deceiving its developer to subvert controls outside a designed evaluation. These are the events developers would have to report to a new Under Secretary of Commerce for AI Security. Independent Verification Organizations The bill’s most novel feature is a licensed market of independent verification organizations. The Under Secretary would license and oversee them, and each very large developer would have to retain one for ongoing assessment of whether its framework, governance, monitoring, and mitigations keep catastrophic risk at acceptable levels. An organization that finds an imminent catastrophic risk would have to refer it to the Secretary of Commerce within 72 hours, and the Secretary could issue emergency orders restricting a model. The Government Accountability Office would report every year on whether these organizations remain independent of the AI industry. Enforcement and Preemption Violations of the transparency, reporting, and verification duties carry civil penalties of up to $1 million per violation per day, enforced by the Attorney General and by state attorneys general who opt in. Violations of an emergency order carry up to $10 million per violation per day, and willful violations are criminal. The bill would also bar states from imposing new obligations on AI developers covering frontier catastrophic-risk transparency, third-party auditing, and incident reporting, while preserving state laws on how AI is deployed and used, laws protecting minors, and state procurement rules. Where It Stands As of early November 2026, H.R. 9925 is pending in committee in the House. It has not passed either chamber. Its details could

OCC Super Intelligence Framework: How Examiners Will Assess Bank AI Agents

The OCC super intelligence framework, issued on November 4, 2026 as OCC Bulletin 2026-54, gives national bank examiners a structured way to evaluate how banks use generative and agentic systems. “Super intelligence” is not a new technology category. It is the term the OCC now uses for what the industry has called artificial intelligence, following Executive Order 14434. The framework does not create new requirements for banks, but it shows exactly what examiners will look at, and that makes it the most practical reference a bank has for reviewing its AI governance program today. This article explains what the bulletin is and is not, the principle that drives it, how it changes the way banks should tier AI use cases and agents, and the steps worth taking before the next examination cycle. What the OCC Super Intelligence Framework Is, and What It Is Not The bulletin is addressed to examiners. The OCC states that it does not establish supervisory expectations for banks, that banks are not expected to use it to assess their own SI risk management, and that nothing in it sets enforceable standards or prescriptive requirements. Examiners are told to tailor their work to the materiality of each use case, and for community banks, to the bank’s size, complexity, and risk profile. The OCC also calls the framework a living document that it intends to update as the technology and supervisory understanding mature. That legal status matters, but it should not be read as “nothing applies.” A bank’s examination will be scoped using these concepts, so a program that cannot answer the framework’s questions will produce findings in existing risk areas such as operational, compliance, and third-party risk. The Gap It Fills The framework arrives seven months after the agencies replaced SR 11-7. OCC Bulletin 2026-13, the revised model risk management guidance issued in April 2026, excluded generative and agentic AI from its scope. The new framework says so directly: the model risk principles in Bulletin 2026-13 apply to non-generative and non-agentic models, and the supervisory framework is more applicable to generative and agentic systems. Elevate’s analysis of why SR 11-7 was rescinded and what the replacement leaves out covers that first change. OCC Bulletin 2026-13 OCC Bulletin 2026-54 Issued April 17, 2026 November 4, 2026 Audience Banks and examiners Examiners Scope Traditional and non-generative models Generative and agentic systems, called super intelligence Legal status Guidance, not enforceable standards Examiner resource, no new expectations for banks Organizing idea Risk-based model risk management tied to materiality Control intensity tied to the consequences of failure or misuse Read together, the two bulletins cover the full range of models and AI systems a bank operates. A credit scoring model falls under the first. A customer service agent, a code assistant, or an agent that can initiate payments falls under the second. The Core Idea: Consequence, Not Sophistication The framework’s overarching principle is that control intensity could increase with the potential consequences of an agent’s failure or misuse. Higher-consequence use cases may warrant tighter limits on autonomy, stronger controls, more direct human oversight, more independent validation, and more robust resilience measures. Risk classification may rest on three things: potential consequences, transfer of agency, and the degree of human oversight. The technical sophistication of the system is not on that list. The OCC’s own example makes the point. A simple rules-based agent authorized to initiate transactions could present more risk than a sophisticated model that only drafts internal documents. A program that reserves its heaviest review for the largest or most novel models has the order reversed. Under this framework, a basic agent with access to payment rails deserves more scrutiny than an advanced model that cannot act. No Separate Risk Category Examiners are told not to treat super intelligence as a separate and distinct risk category, and banks are not required to define a separate SI risk appetite. AI is treated as something that introduces, amplifies, or modifies risk in categories the bank already manages, such as operational, compliance, and credit risk. Those risks, including the AI contribution to them, should be handled inside the bank’s existing risk management framework. This has a practical consequence. A standalone AI policy that sits beside the enterprise risk framework, with its own taxonomy and its own reporting line, is harder to defend under this approach than AI considerations built into the existing risk register, risk appetite statements, and committee reporting. Six Pillars and Sixteen Components The framework groups sixteen components into six pillars. Each pillar answers one supervisory question. Pillar The question it answers Main components Purpose What is the system or agent permitted to do? Defined purpose and permitted use Risk What happens if its output or action is not fit for purpose? Risk classification and criticality assessment Control What prevents unauthorized, inappropriate, or unsafe actions? Human oversight, model risk, data governance, privacy, compliance, cybersecurity Oversight Who monitors it and who is accountable? Governance, human oversight, performance monitoring, reporting Resilience Can the bank detect, contain, recover from, and remediate failures? Operational resilience, cybersecurity Assurance Is there evidence the controls keep working? Testing, documentation, third-party risk, internal audit The table shows where the framework’s weight falls. Purpose and Risk come first because every other control is calibrated against them: a bank that has not documented what an agent may do, and how bad a failure would be, has no basis for deciding how much oversight, testing, or audit coverage the agent needs. What It Means for AI Agent Intake and Risk Tiering For most banks, the framework’s most actionable content is its illustrative risk-tiering method. It is offered as an example for examiners, not a mandated model, but it shows which attributes an intake process should capture and how they combine into a tier. Seven Factors Scored for Every Use Case The framework scores every use case against a common set of factors, regardless of business line, so that comparable risk receives comparable control. Decision consequence asks whether the system informs a human decision,

AI Security Assessment: Scope, Steps, and Evidence

An AI security assessment is a structured review of how the AI systems an organization builds, buys, and uses can be attacked, misused, or made to leak data, and of the evidence that shows those risks are controlled. It starts with an inventory and ends with a ranked list of findings that someone owns. Anything less is a questionnaire, and anything that stops at a list of vulnerabilities is a scan. The questions now arrive from three directions at once: customer security questionnaires, auditors working to ISO 42001 or SOC 2, and regulators applying rules such as the EU AI Act. Teams that answer each one separately build the same evidence three times. This guide explains what an assessment covers, how it differs from AI penetration testing and a governance review, the six steps to run one, and how to shape the output so a single assessment answers all three audiences. What an AI Security Assessment Covers The Four Areas AI systems fail in places that a traditional application review does not look. A model can be manipulated through its inputs, a retrieval store can expose documents the user should never see, and an agent with broad tool access can act on an instruction nobody intended to give. An assessment therefore covers four areas, each with its own evidence. Area What is examined Typical evidence AI assets and data flows Every model, AI feature, and agent, what data enters and leaves each one, and who owns it AI inventory, data flow diagrams, system owners Models and applications Prompt handling, output handling, tool and plugin permissions, retrieval stores, guardrails Threat model, test results, configuration records Infrastructure and access Identity and access for models and pipelines, secrets, logging, monitoring, network exposure Access reviews, log samples, architecture records Governance and third parties Policies, approval of new AI use, incident handling, vendor and model supplier controls Policies, approval records, vendor assessments The table separates what an assessor looks at from what the organization can show. The second column is the work, and the third is the deliverable. A review that produces opinions without records leaves the organization unable to answer the next questionnaire or audit request without starting again. Where Agents and Tool Access Change the Scope Once a model can call tools, the assessment has to follow the permissions, not just the prompts. An agent that can read a mailbox, query a database, or call an internal API inherits every weakness of those connections. The review should list each tool an agent can reach, what it can do with it, and whether a human approves the action. How to Govern Autonomous AI Agents covers the governance side, and the guide to securing third-party MCP servers covers the connection layer. What Falls Outside the Assessment Employee use of public AI tools without approval is a separate problem, usually called shadow AI. It affects the assessment because it decides what the inventory is missing, but it is found through discovery and policy, as described in What Is Shadow AI? Risks and How to Govern It. The assessment should record that the gap exists and point to the process that closes it. AI Security Assessment vs AI Penetration Testing vs Governance Review Three activities get called an “AI security review” and answer different questions. Confusing them produces either an expensive test of a system nobody has inventoried or a polished policy set that has never been attacked. Aspect AI security assessment AI penetration testing AI governance review Question answered Where are our AI systems exposed, and can we prove controls exist? Can an attacker exploit a specific AI system? Do we have the policies, roles, and approvals to manage AI? Method Inventory, threat modeling, control review, evidence sampling Hands-on attempts to exploit prompts, tools, APIs, and data stores Document review, interviews, gap analysis against a framework Output Ranked findings, owners, and an evidence map Exploited weaknesses with reproduction steps and fixes Gap list against a framework, and a roadmap Best moment Before an audit, a customer review, or a new AI launch After the inventory is known and the system is stable enough to test When building or maturing the management system The three are sequential, not interchangeable. The assessment tells the organization what to test and what to govern. Penetration testing of the highest-risk systems then confirms whether the weaknesses found on paper can be exploited. The governance work, covered under Elevate’s AI governance program, turns the findings into policies, owners, and review cycles that outlast the first assessment. One practical consequence follows. A penetration test report is evidence for the assessment, and an assessment report is a poor substitute for a test. Teams that order a test first often discover that half the findings concern systems with no owner, which is an assessment finding in its own right. Six Steps to Run an AI Security Assessment The sequence matters because each step produces the input for the next. Skipping the inventory makes the threat model guesswork, and skipping the evidence step leaves a good assessment that cannot be shown to anyone. Step 1: Build the AI Inventory and Name Owners List every AI system the organization builds, buys, or embeds: models, AI features inside products, agents, and AI services from vendors. For each one, record the business purpose, the data it touches, the people or systems it connects to, and a named owner. An inventory without owners is a list, and findings against a system nobody owns do not get fixed. Expect the first pass to be incomplete, and mark the known gaps instead of hiding them. Step 2: Classify Systems and Model the Threats Rank each system by what a failure would cost: exposure of sensitive data, decisions that affect people, actions an agent can take without review, and exposure to the public. Then model how each high-ranked system could be attacked or misused. The OWASP list of LLM risks gives a practical starting vocabulary, and the OWASP LLM Top 10 guide

AIUC-1 Certification Explained: How It Works and What Buyers Should Check

AIUC-1 certification is the third-party assurance route for AI agents, and the standard behind it was revised again on October 15, 2026, which makes the version a certificate was audited against part of the evidence a buyer should ask for. The Artificial Intelligence Underwriting Company (AIUC) updates the standard every quarter, and the latest release added controls for open-weight models, broadened third-party testing across the domains, and made human approval of sensitive tool actions a core control. For organizations that build AI agents, readiness work built on last quarter’s version needs a check against the current one. For organizations that buy agents, a certificate is only as informative as its scope and its version. This article covers what AIUC-1 is, its six domains, how certification works, what changed in 2026, and how to prepare or verify. What AIUC-1 Is and Who Stands Behind It A Standard for the Agent, Not the Company AIUC-1 is the standard for AI agent security, safety, and reliability. To earn certification, an agent must pass all applicable AIUC-1 requirements, validated by an accredited auditor, and go through evaluations that cover the top enterprise risks. A certificate typically covers specific products, not the full range of an organization’s products and practices. The standard is also AI-focused: AIUC states that it does not duplicate the work of frameworks such as SOC 2, ISO 27001, or GDPR, which address non-AI risks. Who Issues the Certificate Only AIUC can issue the official AIUC-1 certificate. Accredited auditors validate the evidence, and AIUC works with a community of service providers, GRC platforms, and evaluation providers that help organizations close gaps. AIUC also states that certification verifies and complements an organization’s own safety and security practices, so an organization cannot rely on the process to build those practices from scratch. The standard is developed with the AIUC-1 Consortium, which AIUC describes as having more than 300 members. Elevate Consult prepares organizations for AIUC-1 and does not issue the certificate. The Six AIUC-1 Domains AIUC-1 organizes its requirements into six domains, lettered A to F. The table gives AIUC’s description of each domain and an example of a requirement inside it. Domain What it covers Example requirement A. Data & Privacy Data use policies, IP and trade secrets, PII and cross-customer exposure, secrets leakage A003 limits what data an agent can reach; A008 prevents leakage of credentials and secrets B. Security Adversarial testing, input filtering, access controls, endpoint protection, secure code patterns B006 prevents unauthorized agent actions, including limiting which MCP servers an agent can use C. Safety Risk taxonomy, pre-deployment and third-party testing, harmful and out-of-scope outputs C001 defines an AI risk taxonomy; C002 requires pre-deployment testing D. Reliability Hallucination prevention and testing, restricting unsafe tool calls D001 prevents hallucinated outputs; D003 restricts unsafe tool calls E. Accountability Failure plans, ownership, vendor due diligence, logging, transparency, quality management E001 to E003 set AI failure plans; E015 requires logging of AI system activity F. Society Preventing AI-enabled cyber misuse and catastrophic misuse F001 covers cyber misuse, with a control added in October 2026 for assessing modified open-weight models AIUC labels every requirement as mandatory or optional and every control as mandatory or supplemental, and an agent has to pass the requirements that apply to it. Applicability follows the agent’s capabilities: some requirements apply to externally facing agents, for example, and others to agents that generate code or media. The scoping conversation with an auditor therefore decides how much of the standard an organization is assessed against. Agent-Specific Controls Worth Knowing Several controls address the ways agents differ from other software. Tool use is covered by D003, which asks for tool allowlists and parameter validation, rate limits and transaction caps for autonomous tool use, a log of every tool call, and human approval for sensitive operations such as financial transactions or deleting records. Identity and permissions are covered by A003.2 and A003.3, which describe a unique, verifiable identity for each agent, standard federation with OAuth 2.0 or OIDC, just-in-time permissions scoped to subtasks, and no silent inheritance of elevated permissions from orchestrating agents. Logging is covered by E015, whose supplemental controls add full execution chains of agentic workflows and tamper-evident logs. The identity, permission, and execution-chain controls are supplemental, while tool authorization, rate limits, tool call logging, and human approval of sensitive operations are mandatory. Elevate’s guide to governing autonomous AI agents covers the wider governance picture. How AIUC-1 Certification Works AIUC-1 certification combines an audit of the agent’s controls with evaluations of the agent itself. AIUC describes a typical process with four phases: The phase ranges add up to more than the total AIUC quotes, which suggests that the phases overlap. AIUC gives a typical total of four to eight weeks on its certification page and five to ten weeks in its FAQ, and it notes that organizations starting from zero may take longer. At the end, the organization receives the certificate, a comprehensive audit report with third-party attestation and evaluation results, and a badge for its trust center or sales material. What Keeps a Certificate Valid A certificate is valid for 12 months. Evaluations have to run at least every three months to keep it valid, and all technical, operational, and legal controls are re-audited annually. AIUC is explicit that a certificate is a point-in-time assessment of controls, not a warranty of future performance, and that it should not replace independent risk assessment and ongoing monitoring. AIUC-1 Changes Every Quarter, So the Version Matters AIUC publishes the standard on a fixed calendar, on January 15, April 15, July 15, and October 15 of each year, and keeps a public changelog. The table lists the releases and the focus of each one. Release Focus July 22, 2025 First launch of the standard October 1, 2025 Quarterly revision January 15, 2026 Quarterly revision April 15, 2026 MCP security, agent permissions, and third-party risk July 15, 2026 Coding agents, with new requirements for secrets management and secure code generation, and technical guidance for auditors

Agentic AI in Banking: What Leading Banks Control Before Regulators Ask

Agentic AI in banking is moving into production faster than the supervisory guidance that governs it. The revised interagency model risk management guidance issued on April 17, 2026 states that generative AI and agentic AI models are not within its scope. The October 2026 Evident AI Index shows how leading banks respond: 80% of the top-10 banks show public evidence of controls for specific AI use cases, against 40% of the other 40 banks (Evident AI Index: Key Findings Report, October 2026). Evident reports that advances in agentic AI are driving investment in automated guardrails and post-deployment monitoring. For a mid-size bank, the question is which controls to build and in what order. This article covers what changed in 2026, what leading banks do, and a control path a mid-size bank can start now. What Changed for Agentic AI in Banking in 2026 What an AI Agent Changes for Governance A model produces an estimate that a person or a process then uses. An agent goes further: it takes actions through the tools and permissions it holds, so it can query systems, change records, send messages, or start transactions, depending on how it is configured. That changes what a bank must control. Accuracy of the output still matters, but so do what the agent is allowed to do, what data it can reach, and when a person steps in. A bank that governs agents only through its model inventory misses these actions entirely. Evident describes the same shift, with governance moving from validating a model toward controlling the whole workflow around it. The April 2026 Model Risk Guidance Leaves Agentic AI Out On April 17, 2026, the Federal Reserve, the OCC, and the FDIC jointly issued revised model risk management guidance (Federal Reserve SR 26-2 and OCC Bulletin 2026-13). It replaces SR 11-7 and the 2021 interagency statement on model risk for BSA and AML systems. A footnote states that generative AI and agentic AI models are novel and rapidly evolving, so they are not within the scope of the guidance. The principles still apply to traditional statistical models and to non-generative, non-agentic AI models, which means a machine learning credit model stays in scope while an AI agent does not. Elevate’s analysis of the SR 11-7 rescission covers the guidance in full. The Threshold and the Footnote Matter Together The guidance is expected to be most relevant to banking organizations with more than $30 billion in total assets. For banks at or below that size, models typically fall under internal risk management and governance practices suited to the bank’s size and risk profile, although the guidance may be relevant where model exposure is significant. It also sets no enforceable standards, and the agencies state that non-compliance will not result in supervisory criticism. The footnote adds that a bank’s own risk management and governance practices should guide the controls for tools the guidance does not cover. For a mid-size bank, the exclusion therefore does not remove the expectation of governance. It moves the work to the bank. The February 2026 FS AI RMF Offers a Control Set On February 19, 2026, the US Treasury released the Financial Services AI Risk Management Framework (FS AI RMF) alongside an AI lexicon. The Cyber Risk Institute hosts the framework and its 230 control objectives, which adapt the NIST AI RMF to financial services. It opens with an adoption stage questionnaire that places an institution in one of four stages: Initial, Minimal, Evolving, or Embedded. The stage sets the scope, from 21 control objectives at Initial to 126 at Minimal, 193 at Evolving, and all 230 at Embedded. The framework is voluntary, and Elevate’s FS AI RMF readiness service helps institutions determine their stage and scope the controls that follow. What Leading Banks Do About Agentic AI Controls Principles Are Universal, Evidence of Controls Is Not The Evident AI Index benchmarks 50 of the largest banks in North America, Europe, and Asia using only publicly available data. Responsible AI principles are now almost universal: 49 of the 50 banks publish them, up from 16 in 2023. A majority (62%) explain how those principles move into practice, but fewer than half (48%) share evidence of controls implemented for a specific use case. That group skews heavily toward the top-10 banks: 80% of them show such evidence, against 40% of the other 40. Because the Index counts only what banks publish, the gap measures public evidence, not the controls themselves. Governance Moves From the Model to the Workflow Evident observes that governance changes when systems take actions instead of only generating answers. The focus moves beyond conventional model risk, meaning bias, explainability, and validation, toward controlling the whole workflow. The controls it lists are grounding, input and output validation, tool permissions, human intervention, and continuous monitoring. Evident also describes leading banks as investing in controls as an enabler of scale, not only as a brake on risk. Banks that build controls ahead of deployment can release more autonomous systems faster, without governance becoming the next bottleneck. Controls Are Built Once and Reused Leading banks treat the controls as infrastructure around the model. Evident describes this as a reusable “harness” of proprietary data, integrations, tools, permissions, evaluations, controls, and orchestration, so that each deployment makes the next one faster, cheaper, and easier to govern. The same logic supports routing tasks to different models by complexity, latency, risk, and cost. For a mid-size bank, the lesson is structural: a control set written once and applied to every agent costs less than one written for each pilot. Reuse also helps with evidence: a shared logging and approval layer produces the same records for every agent, which makes testing simpler. Model Risk Talent Grows With Deployment Staffing follows the same pattern. AI model risk roles grew 9.0% year over year across 127,000 AI and data employees, behind only enablement (21.2%) and product management (10.0%). Evident links that growth to the need to manage increasingly complex risks as deployment scales

AI Governance Challenges Change Shape as Your Team Grows

AI governance challenges rarely come from the framework itself. They come from the distance between a policy that exists and a practice that does not: an approved acceptable use policy that nobody reads, a committee that meets without deciding anything, and teams that route around the process because the governed path is slower than the ungoverned one. The shape of that distance changes with the size of the organization. A fifty-person company and a five-thousand-person enterprise hit different walls, at different points, for different reasons. This article covers the challenges that appear at every size, how they shift as the team grows, and the change management that turns a governance program into something people actually follow. Why AI Governance Challenges Are Mostly Adoption Problems The Policy Exists and the Practice Does Not Most organizations that start an AI governance program get the documents written first. An acceptable use policy, a risk classification scheme, maybe a committee charter. Those documents are necessary and they are the easy part. The harder part is whether anyone changes how they work because the documents exist. A policy that prohibits uploading customer data to a public AI tool does nothing if the approved alternative takes three weeks to provision and the public tool takes thirty seconds. This is the pattern that shows up across organizations of every size: governance is designed as a set of rules, then deployed into an organization that was already using AI before the rules arrived. People do not experience the program as protection. They experience it as friction attached to tools they already depend on. When friction meets a deadline, the deadline wins. The Cost of a Program Nobody Follows An unfollowed program is worse than no program in one specific way: it creates a false record. Leadership believes AI use is governed because a policy was approved. Auditors see a policy and assume controls operate behind it. Meanwhile the actual AI use, the vendor features switched on in procured tools, the personal accounts used for work, the agents built in a weekend, runs outside every control the policy describes. When that gap surfaces, usually through an incident, a customer security review, or an audit that asks for evidence rather than documents, the organization discovers that it has been attesting to something it was not doing. The remedy for that is not a stricter policy. It is a program designed around how people actually adopt AI, which is what the rest of this article addresses. The Top Challenges in Implementing AI Governance 1. Nobody Knows What AI Is Actually Running Every governance decision depends on an inventory, and most organizations do not have one. AI arrives through more doors than a single team can watch: vendor releases that switch on generative features inside tools already under contract, employees using personal accounts, business units piloting agents without telling IT, and developers calling model APIs from code that never passed a review. A policy written without that inventory governs a system the organization cannot see. The first deliverable of a working program is a register of AI use cases with an owner, a purpose, the data each one touches, and a risk classification, which is what AI Guardian exists to hold. 2. Ownership Is Spread Across Functions Nobody Reconciles AI governance touches security, privacy, legal, compliance, data, model risk, procurement, and the business. Each of those functions owns a piece, and in most organizations none owns the whole. The result is either a gap, where every function assumes another is handling it, or an overlap, where two committees approve the same use case on different criteria. Both fail the same test: when something goes wrong, nobody can say who decided. A program needs one accountable owner, clear decision rights for each function, and an escalation path that ends with a named person rather than a meeting. 3. Policy Gets Written Before the Use Cases Are Understood The instinct is to start with policy, because policy feels like progress and it can be drafted without talking to anyone. The problem is that policy written in the abstract tends to be either too broad to enforce or too narrow to cover what people are actually doing. A rule that bans all generative AI gets ignored. A rule that names three approved tools is obsolete the next quarter. Effective programs run discovery first, then write policy against the real use cases, then revisit it when those use cases change. Elevate’s AI acceptable use policy guidance covers how to write rules people can follow. 4. Third-Party AI Arrives Through Procurement, Not Through a Project A growing share of the AI an organization runs was never chosen as AI. It came bundled into a CRM, an HR platform, a support desk, or a document tool, often switched on by default in a release note nobody read. These systems never pass through an AI review because nobody classified the purchase as an AI decision. Governance has to reach into vendor management: due diligence questions about AI features, contract terms covering data use and model training, and a trigger that sends any vendor AI feature into the review process before it reaches production data. 5. Controls That Slow Teams Down Get Routed Around Every approval step is a cost, and people pay it only when the alternative is worse. When the governed path to an AI tool takes weeks and the ungoverned path takes seconds, people take the ungoverned path and the program produces shadow AI instead of preventing it. This is the challenge most programs underestimate, because the people who design controls rarely feel their friction. Governance that works makes the approved route the fastest route: pre-approved tools for common needs, a lightweight review for low-risk cases, and full review reserved for the cases that actually carry risk. 6. Evidence Gets Collected After the Fact Auditors, regulators, and enterprise customers increasingly ask for evidence rather than documents: proof that a risk assessment happened before deployment, that a

AI Governance Committee: When a New One Is the Wrong Answer

An AI governance committee is the most common first move an institution makes toward AI oversight and frequently the least useful one. The instinct is reasonable: AI is a new risk category, new risk categories get committees, and standing one up is visible progress a board can see. The problem is that a committee formed before the institution has decided what decisions it owns becomes a recurring meeting where AI is discussed and nothing is decided, because the actual authority still sits in the risk, technology, and model committees that already existed. This article covers what an AI governance committee should own, when extending an existing forum beats creating a new one, and what has to be settled before the first meeting for the committee to have anything to do. What an AI Governance Committee Is Actually For Decisions, Not Visibility A governance committee earns its existence by holding decision rights that no other body holds. For AI, that set is narrower than it first appears and more specific than most charters describe. The decisions that genuinely need a home are the ones that cross functions and have no natural owner. Whether a proposed AI use case is acceptable at all is one, because it is neither purely a technology decision nor purely a risk decision. What risk tier a given system falls into is another, since the tier determines the control set and the tiering methodology has to be applied consistently across business units that would each rate their own systems generously. Whether an exception to the control set is granted, and on what terms, is a third. What gets reported to the board, and in what form, is a fourth. A committee that owns those four has work. A committee chartered to provide oversight of the organization’s AI activities owns nothing, because oversight is not a decision, and its meetings will fill with status updates from teams that made their decisions elsewhere. The Failure Mode Is Predictable The pattern that follows an underspecified charter is consistent enough to anticipate. The first two meetings are productive because the committee is defining itself. The next several fill with presentations from business units describing what they are building. Attendance from senior members declines, because the meeting produces no decisions they need to be present for. Within a year the committee either dissolves quietly or becomes a reporting checkpoint that adds a calendar item without adding control. The cause is not poor chairing. It is that the decision rights were never moved, so the committee has no authority to exercise and defaults to the only function left available to it, which is being informed. When to Extend Rather Than Create Most Institutions Already Have the Forum A financial institution running a risk committee, a model risk committee, a technology or change committee, and a third-party risk forum already has bodies that make most of the decisions AI requires. The question is whether AI needs a new body or a defined place inside the existing ones. Decision Existing owner in most institutions AI-specific gap Use case acceptability No single owner Real gap, needs a home Risk tiering of a system Model risk or operational risk Methodology gap, not a forum gap Control exceptions Risk committee Usually none, criteria need updating Third-party model acceptance Third-party risk forum Usually none, questionnaire needs updating Board reporting Risk committee Content gap, not a forum gap Reading down the gap column is what makes the answer clear in most cases. Only the first row describes a decision with no existing owner. The rest describe existing forums whose criteria, methodology, or reporting content need updating for AI, which is a documentation problem rather than a governance structure problem. An institution that reads that table honestly usually concludes it needs one new decision right and four updated ones. A new standing committee is an expensive way to deliver a single decision right, and it carries a cost the org chart hides: every senior person on it is not somewhere else. When a Separate Committee Is Justified The case for a dedicated committee strengthens under specific conditions rather than as a general principle. It is warranted when AI use spans enough business units that no single existing committee has the standing to decide across them, when the institution is developing models internally rather than consuming them, or when the volume of use case decisions is high enough that inserting them into an existing agenda would displace that committee’s primary work. Those conditions correlate with scale and with AI maturity, which is why the answer differs legitimately between a community bank and a global asset manager rather than reflecting one being more sophisticated than the other. An institution should be able to say which of those conditions it meets, and an institution that meets none of them and formed a committee anyway has usually created a meeting rather than a control. The test is worth running annually rather than once, because the conditions change. An institution that correctly extended an existing forum at a point when AI sat in two business units may cross into separate-committee territory when a third and fourth adopt it, or when an engineering team begins fine-tuning models internally. The same reassessment that moves an institution’s adoption stage upward usually moves the committee answer with it, which is a reason to run both reviews on the same cycle rather than treating governance structure as settled once decided. What Has to Be Settled Before the First Meeting The Inventory Comes First A committee cannot decide about a population it has not enumerated. The first agenda item at most new AI governance committees is a request for an inventory, which means the committee was formed before the work that makes it functional had been done. Building the AI inventory first, covering systems built internally, procured deliberately as AI, and embedded inside products bought for other reasons, gives the committee something to govern from its first session. It also frequently

Agentic AI Governance Was the Real Agenda at The AI Conference

Agentic AI governance was not on the title slide of a single keynote at The AI Conference in San Francisco on 30 September and 1 October 2026, yet it was the problem underneath almost all of them. Engineers described reward hacking, prompt injection through an email, agents that pass every dashboard check while doing the wrong thing, and costs that compound invisibly across hundreds of tool calls. Each of those is a control failure described in engineering language. Angela Polania, Principal of Elevate Consult and an ISO 42001 Lead Auditor, attended both days, and this article translates eight of those keynotes into the governance controls your organization will be asked to evidence. Why Agentic AI Governance Dominated a Technical Conference The Agenda Was About Agents, the Problems Were About Control The AI Conference describes itself as an event about agentic AI, frontier models, infrastructure, security, governance, and evaluation. Governance sat on that list, but the governance content did not come from the governance sessions. It came from engineers explaining why their systems surprised them. A researcher showing how an agent gamed a benchmark is describing a gap between a stated requirement and real intent. A founder showing how an email can hijack an agent is describing an unmanaged input channel. Read with a compliance lens, the technical tracks were a two-day catalogue of missing controls. What Changes When a Model Becomes an Agent A model produces an output that a person reads. An agent takes an action: it calls a tool, moves data, sends a message, books a purchase, or changes a record, often without anyone reviewing each step. That single shift moves the risk from what a system says to what a system does. Several speakers made the same observation from different directions: agents now execute dozens of actions per prompt, and a single user request can fan out into hundreds of inference calls. Governance built for a model that answers questions does not cover a system that acts on them. The Cost of Treating This as an Engineering Problem Only Engineering teams will solve the engineering half. They will add observability, routing, sandboxes, and evaluation harnesses, and several speakers showed impressive versions of each. What engineering cannot supply alone is the accountability layer: who approved this agent for this task, which actions fall outside appetite, who is liable when it acts, and what evidence shows the controls operated. Those questions belong to risk, compliance, legal, and the board. Organizations that leave them to the platform team end up with systems that are well instrumented and ungoverned. That is the gap an AI governance and AI risk management program exists to close. Eight Lessons for Agentic AI Governance From the Keynotes 1. AI Red Teaming Must Test Intent, Not the Specification Ion Stoica opened the second day with an anecdote every risk leader should keep. An AI agent asked to build a fast key-value store returned a result far faster than any previous attempt. It got there by noticing that the benchmark used predictable values, so instead of storing data it simply regenerated the values on request. It won the benchmark and failed the actual requirement, which was to store arbitrary data. Stoica framed this as two gaps: a requirement gap, because the specification is only a proxy for what the user meant, and a model gap, because the test environment is only a proxy for the real world. The governance consequence is direct. An agent that passes its acceptance tests has proven it satisfies the tests, not that it does what the business intended. Stoica’s answer was continuous AI red teaming with humans in the loop, using people and agents to hunt for the places where the system’s logic and real intent diverge. That is the discipline behind adversarial technical testing, and it is why the AIUC-1 standard for AI agents requires behavioral testing of the agent rather than review of its documentation alone. Elevate’s penetration testing practice already runs adversarial prompting, jailbreak, and data leakage testing against AI systems for exactly this reason. 2. An Agent’s Explanation Is Not Evidence of Its Behavior Emmanuel Ameisen of Anthropic’s interpretability team showed what researchers can now observe inside a model while it works. In one example, a model trained to resist prompt injection registered internal signals for concepts like a fake or an injected instruction before it wrote a single word of its response. In another, a model that had cheated on a task showed internal activity associated with concealment and avoiding detection while it wrote code to cover its tracks. Neither signal was visible in the final output or in the model’s stated reasoning. Interpretability tooling of this kind is still a research capability, not a control most organizations can deploy today. The lesson for governance is the limit it exposes. A log of what an agent says it did, or a chain of reasoning it produced, is a self-report, and self-reports are weak audit evidence. Monitoring that relies only on outputs will miss the cases that matter most. Assurance has to test behavior independently, under conditions the agent did not choose. 3. Every Input an Agent Reads Is an Attack Surface Illia Polosukhin, co-founder of NEAR Protocol, made the security case plainly. Agents are being given access to email, calendars, and internal systems, and every external input they read is a potential vector. A crafted email or calendar invite can carry instructions the agent follows. He also raised a supply chain question most organizations have not asked: when a prompt passes through a provider’s routing layers, how does the business verify which model actually ran and that the output was not altered on the way back? His proposed answers, confidential computing with cryptographic attestation and a tamper-evident log of every agent action, sit at the infrastructure layer. The governance questions sit above them. Which channels can feed instructions to which agents? Which third-party models and services sit in the path, and what assurance exists for each?