> ## Documentation Index
> Fetch the complete documentation index at: https://standard.aiuc-1.com/llms.txt
> Use this file to discover all available pages before exploring further.

# AIUC-1 changelog

export const InlineClock = ({city, timeZone}) => {
  const [time, setTime] = useState('--:--:--');
  useEffect(() => {
    const update = () => setTime(new Intl.DateTimeFormat('en-US', {
      hour: '2-digit',
      minute: '2-digit',
      second: '2-digit',
      hour12: false,
      timeZone
    }).format(new Date()));
    update();
    const id = setInterval(update, 1000);
    return () => clearInterval(id);
  }, [timeZone]);
  return <div className="aiuc-footer-clock">
      <span className="aiuc-footer-clock-city">{city}</span>
      <span className="aiuc-footer-clock-time">{time}</span>
    </div>;
};

AIUC-1 is updated formally each quarter to ensure that the standard evolves as technology, risk, and regulation evolves.

The most recent version of AIUC-1 was released on July 15, 2026.

The next version of AIUC-1 will be released on October 15, 2026.

## July 15, 2026 release

This update focused on expanding coding agent requirements, developing public-facing guidance for auditors and organizations pursuing AIUC-1, and further clarifications to existing requirements. This quarter's refresh updated 8 requirements and 41 controls.

### Overview of key updates

* **AIUC-1 for coding agents:** Secrets management, secure defaults in code, and execution-level safeguards broadened to coding agents.
* **Technical guidance for auditors:** Public documentation on AIUC-1 audit scoping and annual re-certification.
* **Clarifications to existing requirements:** Clearer rules for which controls apply to which agent types, and removal of duplicative controls.

### Detailed changelog

<div className="aiuc-changelog-table" />

| Date    | AIUC-1 requirement and control                                             | Category      | Change notes                                                                                                                                                                                                                                               |
| ------- | -------------------------------------------------------------------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Q3 2026 | A008: Prevent leakage of credentials and secrets                           | New addition  | Added new mandatory requirement for code-generating agents covering detection and prevention of secrets leakage in AI system inputs, outputs, logs, and credential storage, with five new controls (A008.1-A008.5)                                         |
| Q3 2026 | B010: Promote secure patterns in generated code                            | New addition  | Added new mandatory requirement for code-generating agents to promote secure patterns and prevent known vulnerabilities in generated code, with six new controls (B010.1-B010.6)                                                                           |
| Q3 2026 | A003: Limit AI agent data access                                           | Revision      | Retired the supplemental control on alerting for auth failures; agent identity management and agent access and permissions management renumbered to A003.2 and A003.3                                                                                      |
| Q3 2026 | A003.1 Config: Data access scoping                                         | Clarification | Clarified the control to cover data access rather than data collection                                                                                                                                                                                     |
| Q3 2026 | A004.1 Documentation: User guidance on confidential information            | Clarification | Recategorized the evidence from Technical Implementation to Operational Practices                                                                                                                                                                          |
| Q3 2026 | A005: Prevent cross-customer data exposure                                 | Revision      | Broadened the requirement to cover cross-customer data exposure generally, not only when combining customer data from multiple sources                                                                                                                     |
| Q3 2026 | A005.2 Config: Customer data isolation controls                            | Clarification | Generalized typical evidence to logical isolation appropriate to the architecture rather than specific app-ID patterns                                                                                                                                     |
| Q3 2026 | A006: Prevent PII leakage                                                  | Revision      | Retired the core control requiring authentication and authorization for PII access; DLP system integration renumbered to A006.2 as a supplemental control                                                                                                  |
| Q3 2026 | A007: Prevent IP violations                                                | Revision      | Retagged capability scoping from generation modalities to externally facing agents                                                                                                                                                                         |
| Q3 2026 | B006.3 Config: Execution-level safeguards                                  | Revision      | Extended sandboxed execution safeguards to cover agent-executed code alongside first-party MCP servers                                                                                                                                                     |
| Q3 2026 | B008: Protect AI system deployment environment                             | Revision      | Retired the core control on model access controls; remaining controls renumbered B008.1-B008.5 with agentic interface data integrity retagged as supplemental                                                                                              |
| Q3 2026 | B009: Limit output over-exposure                                           | Revision      | Extended capability scoping to cover image generation alongside text and voice generation                                                                                                                                                                  |
| Q3 2026 | C005: Prevent agent-specific high risk outputs                             | Clarification | Renamed from customer-defined to agent-specific high-risk outputs to reflect that the risk taxonomy is defined per agent                                                                                                                                   |
| Q3 2026 | C006.2 Demonstration: Content handling and labelling for untrusted content | Clarification | Relabelled from warning labels to content handling and labelling for untrusted content                                                                                                                                                                     |
| Q3 2026 | C008.3 Config: Security tooling                                            | Clarification | Renumbered from C008.4 to C008.3 to close a numbering gap                                                                                                                                                                                                  |
| Q3 2026 | E002: AI failure plan for harmful outputs                                  | Revision      | Retagged capability scoping from generation modalities to externally facing agents                                                                                                                                                                         |
| Q3 2026 | E003: AI failure plan for hallucinations                                   | Revision      | Retagged capability scoping from generation modalities to externally facing agents                                                                                                                                                                         |
| Q3 2026 | E003.1 Documentation: AI failure plan for hallucinations                   | Revision      | Refocused the control on customer communication protocols and immediate mitigation steps with designated staff responsibilities                                                                                                                            |
| Q3 2026 | E005.1 Documentation: Data storage security practices                      | Revision      | Simplified the control to focus on documenting data storage security practices such as cloud vs. on-premises assessments                                                                                                                                   |
| Q3 2026 | E009: Monitor third-party access                                           | Revision      | Expanded the requirement to cover monitoring and logging of third-party API connections, sessions, and data access                                                                                                                                         |
| Q3 2026 | E009.2 Config: Anomalous third-party access alerting                       | Addition      | Added new supplemental control for alerting on anomalous third-party access                                                                                                                                                                                |
| Q3 2026 | E017: Document system transparency policy                                  | Revision      | Restructured controls: transparency documentation is now the core control E017.1, transparency report sharing policy retagged supplemental as E017.2, and a new supplemental control E017.3 added covering platform and deployer security responsibilities |

### Detailed side-by-side comparison

Detailed comparisons of current and previous AIUC-1 standards are available on [GitHub](https://github.com/aiunderwriting/AIUC-1-Changelog).

### Standard history

<div className="aiuc-changelog-history-table" />

| Version          | Link to changelog                         |
| ---------------- | ----------------------------------------- |
| April 15, 2026   | [See changes here](/changelog/2026-04-15) |
| January 15, 2026 | [See changes here](/changelog/2026-01-15) |
| October 1, 2025  | [See changes here](/changelog/2025-10-01) |
| July 22, 2025    | First launch of the standard              |

### Tenets that guide the standard update

* **Customer-focused.** We prioritize requirements that enterprise customers demand and vendors can pragmatically meet, increasing confidence without adding unnecessary compliance.
* **AI-focused.** We do not cover non-AI risks that are addressed in frameworks or regulations like SOC 2, ISO 27001, or GDPR.
* **Insurance-enabling.** We prioritize risks that lead to direct harms and financial losses.
* **Adapts to regulation.** We update AIUC-1 to make it easier to comply with new regulations.
* **Adapts to AI progress.** We update AIUC-1 to keep up with new capabilities, like reasoning capabilities and new modalities.
* **Adapts to the threat landscape.** We update AIUC-1 in response to real-world incidents.
* **Continuous improvement.** We regularly update the standard based on real-world deployment experience and stakeholder feedback.
* **Predictability.** We review the standard and push updates quarterly, on January 15, April 15, July 15, and October 15 of each year.
* **Transparency.** We keep a public changelog and share our lessons.
* **Backward compatibility.** Existing certifications remain valid during transition periods.

### Provide input on AIUC-1

We welcome feedback, ideas, suggestions, and criticism. [Provide input on AIUC-1](/learn/contribute).

<div className="aiuc-footer">
  <span className="aiuc-footer-corner aiuc-footer-corner-tl">
    <svg fill="none" stroke="currentColor" strokeWidth="1" viewBox="0 0 12 12" width="12" height="12">
      <line x1="0" x2="12" y1="6" y2="6" />

      <line x1="6" x2="6" y1="0" y2="12" />
    </svg>
  </span>

  <span className="aiuc-footer-corner aiuc-footer-corner-tr">
    <svg fill="none" stroke="currentColor" strokeWidth="1" viewBox="0 0 12 12" width="12" height="12">
      <line x1="0" x2="12" y1="6" y2="6" />

      <line x1="6" x2="6" y1="0" y2="12" />
    </svg>
  </span>

  <div className="aiuc-footer-strip">
    <span className="aiuc-footer-mono">37.782274° N -122.392147° W</span>
    <span className="aiuc-footer-strip-center">FIG. A (SITE INDEX)</span>

    <span />
  </div>

  <div className="aiuc-footer-row-main">
    <div className="aiuc-footer-wireframe-cell">
      <svg className="aiuc-footer-wireframe" fill="none" stroke="currentColor" strokeWidth="0.4" viewBox="0 0 200 150">
        <rect height="130" width="180" x="10" y="10" />

        <rect height="40" width="60" x="20" y="20" />

        <rect height="40" width="40" x="90" y="20" />

        <rect height="40" width="40" x="140" y="20" />

        <rect height="60" width="60" x="20" y="70" />

        <rect height="60" width="90" x="90" y="70" />

        <line strokeDasharray="2,2" x1="20" x2="180" y1="65" y2="65" />

        <line strokeDasharray="2,2" x1="85" x2="85" y1="20" y2="60" />

        <circle cx="50" cy="40" r="6" />

        <circle cx="110" cy="40" r="6" />

        <circle cx="160" cy="40" r="6" />
      </svg>
    </div>

    <div className="aiuc-footer-wordmark-cell">
      <div className="aiuc-footer-wordmark">Artificial Intelligence Underwriting Company</div>
    </div>

    <div className="aiuc-footer-clocks">
      <InlineClock city="SFO" timeZone="America/Los_Angeles" />

      <InlineClock city="NYC" timeZone="America/New_York" />

      <InlineClock city="LON" timeZone="Europe/London" />
    </div>
  </div>

  <div className="aiuc-footer-row-sub">
    <div className="aiuc-footer-codeblock-cell">
      <div className="aiuc-footer-codeblock">
        <span className="aiuc-footer-codeblock-header">Code</span>
        <span className="aiuc-footer-codeblock-header">Structural unit</span>
        <span className="aiuc-footer-codeblock-code">a.</span>
        <span className="aiuc-footer-codeblock-text">AIUC-1 requirements for agent data, privacy, security, safety, reliability, accountability, and societal risk.</span>
        <span className="aiuc-footer-codeblock-code">b.</span>
        <span className="aiuc-footer-codeblock-text">Evidence templates for technical implementation, legal policy, operational practice, and third-party evaluation.</span>
        <span className="aiuc-footer-codeblock-code">c.</span>
        <span className="aiuc-footer-codeblock-text">Crosswalks to AI regulations, standards, and security frameworks.</span>
        <span className="aiuc-footer-codeblock-code">d.</span>
        <span className="aiuc-footer-codeblock-text">Quarterly updates shaped by enterprise adoption, risk, regulation, and community input.</span>
      </div>
    </div>

    <div className="aiuc-footer-columns-cell">
      <div className="aiuc-footer-columns">
        <div>
          <div className="aiuc-footer-column-header">I. Standard</div>

          <ul className="aiuc-footer-column-list">
            <li><a className="aiuc-footer-column-link" href="/">Overview</a></li>
            <li><a className="aiuc-footer-column-link" href="/crosswalks">Crosswalks</a></li>
            <li><a className="aiuc-footer-column-link" href="/evidence">Evidence</a></li>
            <li><a className="aiuc-footer-column-link" href="/changelog">Changelog</a></li>
          </ul>
        </div>

        <div>
          <div className="aiuc-footer-column-header">II. Learn</div>

          <ul className="aiuc-footer-column-list">
            <li><a className="aiuc-footer-column-link" href="/learn/about">About AIUC-1</a></li>
            <li><a className="aiuc-footer-column-link" href="/learn/contribute">Contribute</a></li>
            <li><a className="aiuc-footer-column-link" href="/scoping">Scoping</a></li>
            <li><a className="aiuc-footer-column-link" href="/faq">FAQ</a></li>
          </ul>
        </div>

        <div>
          <div className="aiuc-footer-column-header">III. Office</div>

          <ul className="aiuc-footer-column-list">
            <li><a className="aiuc-footer-column-link" href="/consortium">Consortium</a></li>
            <li><a className="aiuc-footer-column-link" href="/contact">Contact</a></li>
            <li><a className="aiuc-footer-column-link" href="/legal/privacy">Privacy policy</a></li>
            <li><a className="aiuc-footer-column-link" href="/legal/terms">Terms of use</a></li>
          </ul>
        </div>
      </div>
    </div>
  </div>

  <div className="aiuc-footer-strip-bottom">
    <span className="aiuc-footer-mono">100</span>
    <span>© AIUC — ALL RIGHTS RESERVED</span>
  </div>

  <span className="aiuc-footer-corner aiuc-footer-corner-bl">
    <svg fill="none" stroke="currentColor" strokeWidth="1" viewBox="0 0 12 12" width="12" height="12">
      <line x1="0" x2="12" y1="6" y2="6" />

      <line x1="6" x2="6" y1="0" y2="12" />
    </svg>
  </span>

  <span className="aiuc-footer-corner aiuc-footer-corner-br">
    <svg fill="none" stroke="currentColor" strokeWidth="1" viewBox="0 0 12 12" width="12" height="12">
      <line x1="0" x2="12" y1="6" y2="6" />

      <line x1="6" x2="6" y1="0" y2="12" />
    </svg>
  </span>
</div>