Appendix K provides a complete control-by-instrument cross-tab, an explanation and evidence table, and a current regulatory source register. It covers the 45 handbook practices, 12 implementation specifications and 112 reference controls. Use the source-specific status and applicability limits before treating a mapping as relevant to your deployment.
This chapter distinguishes regulatory text, official implementation information, supervisory guidance, draft rules, and voluntary technical documentation. Applicability still depends on the entity, jurisdiction, role, decision, and data. This chapter supplies an implementation crosswalk rather than a comprehensive legal opinion.
The 17 selected instruments at a glance. These are the instruments in the Appendix K cross-tab and the searchable regulatory map, with the same reference numbers, status and applicability. Appendix K adds the version, timing, interpretation limits and the dated status source for each.
| Reference | Instrument | Jurisdiction | Legal status | When it matters |
|---|---|---|---|---|
| R01 · EU | EU AI Act: Regulation (EU) 2024/1689 | EU | Binding law | EU-market providers, deployers and other covered operators; classify intended use and role first. |
| R02 · GD | GDPR: Regulation (EU) 2016/679 | EU | Binding law | Personal-data processing within Articles 2/3; controller and processor duties differ. |
| R03 · DO | DORA: Regulation (EU) 2022/2554 | EU | Binding law | Financial entities listed in Article 2; check exclusions, proportionality and the simplified framework. |
| R04 · FC | FCA Consumer Duty: PRIN 2A | UK | Binding rules and guidance | FCA firms and retail business in the Duty’s scope; account for position in the distribution chain. |
| R05 · PR | PRA model risk management: SS1/23 | UK | Supervisory expectations | UK-incorporated banks, building societies and PRA-designated investment firms with internal-model capital approval; model definition and materiality still matter. |
| R06 · RB | ECOA / Regulation B | US | Binding regulation | Creditors and covered credit decisions; notification procedures and exceptions vary by application and applicant. |
| R07 · CA | California CCPA: ADMT and risk assessments | US | Binding regulation | CCPA businesses and covered processing; ADMT significant-decision definition, exemptions and opt-out exceptions are specific. |
| R08 · CO | Colorado SB26-189: covered ADMT | US | Enacted law; future duties | Developers/deployers of ADMT materially influencing specified consequential decisions; statutory exemptions require review. |
| R09 · SR | US interagency model risk guidance: SR 26-2 | US | Supervisory guidance | Banking organizations supervised by the Federal Reserve, OCC or FDIC. The Federal Reserve cover letter says it is expected to be most relevant to banking organizations with over $30 billion in total assets regulated by the Federal Reserve. Scope: traditional statistical/quantitative and non-generative, non-agentic AI models. |
| R10 · IM | IMDA Model AI Governance Framework for Agentic AI | Singapore | Voluntary guidance | Organisations deploying agents; practical cross-sector design guidance. |
| R11 · SF | MAS / industry SAFR | Singapore | Voluntary industry white paper | Agentic financial workflows; runtime authorisation and review design. |
| R12 · HK | PCPD guidance on agentic AI and personal data | Hong Kong | Regulator guidance | Data users processing personal data with agents; underlying PDPO duties remain binding. |
| R13 · NI | NIST AI Risk Management Framework | Global | Voluntary framework | Organisations managing AI risk across the lifecycle. |
| R14 · NG | NIST Generative AI Profile | Global | Voluntary framework | Generative AI uses, components and supply chains; contextualise the profile to the complete agent workflow. |
| R15 · IS | ISO/IEC 42001 | Global | Voluntary standard | Organisational AI management systems; contract or policy may make adoption an organisational obligation. |
| R16 · IR | ISO/IEC 23894 | Global | Voluntary guidance standard | AI risk-management processes appropriate to organisational context. |
| R17 · FS | FSB sound practices for responsible AI adoption | Global | Consultation draft | Financial institutions; organisation-wide governance and AI lifecycle practices. |
Status points that change enterprise action. The following verified points change how an enterprise should act now. The relationship types in Appendix K still apply; none is a compliance verdict.
| Instrument or source | Status and verified point | Enterprise action | Related practices |
|---|---|---|---|
| US bank model-risk guidance (R09) | SR 26-2, issued 17 April 2026, supersedes and replaces SR 11-7 and SR 21-8. The Federal Reserve cover letter says it is expected to be most relevant to banking organizations with over $30 billion in total assets regulated by the Federal Reserve. Its attachment excludes generative and agentic AI models from scope. [S31, S32] | Treat the guidance as a domain analogy for agent governance, not as an agent-specific requirement. Document the institution's agent governance standard separately and explain which model-risk disciplines it elects to reuse. Assess any conventional quantitative models inside the workflow on their own terms. | H-GOV-02, H-ASR-02, H-ASR-03 |
| EU AI Act / AI Omnibus (R01) | The Commission reports entry into force on 27 July 2026 and application of Annex III high-risk rules from 2 December 2027, with high-risk AI embedded in Annex I products from 2 August 2028. [S33] | Maintain an obligation-specific calendar. Distinguish those dates from other already applicable provisions and role-specific duties. Obtain the controlling consolidated text before issuing an article-level compliance determination. | H-GOV-02, H-ASR-01 |
| Colorado ADMT (R08) | The official bill page identifies SB26-189 as enacted. The Attorney General states the new provisions take effect 1 January 2027. [S34, S35] | Classify consequential-decision influence and the developer/deployer role. Implement the relevant notice, review, correction, and evidence workflows after legal applicability review. | H-GOV-02, H-FCO-03, H-FCO-04, H-FCO-05 |
| Colorado implementing rules | The Attorney General identifies the 11 August 2026 ADMT and chatbot rules as proposed drafts, with comments through 26 October 2026. [S35] | Track the final rule. Do not represent a draft-specific requirement as enacted law. | H-GOV-02, H-ASR-01 |
| California CCPA ADMT (R07) | Final regulations section 7200 sets compliance for covered significant-decision ADMT from 1 January 2027. [S36, S41] | Assess covered business status, the ADMT use, and applicable exemptions. Review sector/data exemptions individually; avoid assuming all financial-sector processing is exempt. | H-GOV-02, H-FCO-01, H-DES-03 |
| US credit adverse-action notices (R06) | Regulation B section 1002.9 supplies the governing notification and reasons provisions. [S37] | Preserve actual reasons and verify agent-assisted notices against them. | H-FCO-03 |
| NIST agent identity work | September project outputs and public-comment summaries support implementation development. They are not a completed certification standard and are not among the 17 mapped instruments. [S25, S26] | Track the DevSecOps demonstration and validate the local identity/delegation design now. | H-DES-02, H-MAS-02 |
Technical specifications and voluntary technical frameworks. These documents define implementation behavior or security references. They are not legislation or supervisory guidance, and they are not part of the regulatory cross-tab.
| Specification or framework | Status and inspected version | Enterprise action | Related practices |
|---|---|---|---|
| MCP 2026-07-28 | Released protocol and authorization documentation; protocol requirements apply to implementations claiming conformance. [S27, S28] | Pin deployed versions and test migration, audience/issuer checks, explicit state, and authorization boundaries. | H-RUN-01, H-DES-02, H-TPR-01 |
| OWASP Agent Control Standard (ACS) | Voluntary runtime-control interface; inspected repository version 0.1.0. [S29, S30] | Establish per-framework hook coverage and bypass tests before claiming enforcement. | H-RUN-01, H-TPR-01, H-MON-01 |
| OpenTelemetry GenAI attributes | The inspected registry marks relevant agent/tool operation attributes as Development. [S42] | Version the telemetry mapping; supplement it with institution-specific control and effect fields. | H-MON-01, H-DES-01 |
| OWASP Top 10 for Agentic Applications | Voluntary security framework, 2026 edition published 9 December 2025. [S46] | Use it as a reference when building the threat model in chapter 4. The handbook's threat analysis is original and does not claim conformance to its categories. | H-EVL-03 |
The EU legislative links returned an access/anti-bot limitation during this review. The timeline above is attributed to the Commission's official implementation page; this report does not claim a completed review of the amending or consolidated regulation. Colorado and California draft/final status and dates are stated at the inspected source level. Avoid placing one jurisdiction's record-retention or incident-reporting clock on every enterprise agent.
16.1 Foundational voluntary references
NIST AI RMF 1.0, its Generative AI Profile, the OECD AI Principles, and OWASP agent security guidance supply different forms of context. They are voluntary references; this handbook does not assert certification, complete clause coverage, or legal compliance from using its practices. Record which version and scope the enterprise adopts, and distinguish its internal policy commitments from external duties. [S43, S44, S45, S46, S47]