Skip to main content

Standards

What a conformance report answers: a standard's version, domains and controls, each with the evidence kinds it takes, its cadence and its crosswalks, one spec each under agentspecs/standards/. The Shield's evidence map (agent_shield.conformance) reads them and gives each control one of five statuses; the standard's version is tracked and offered, never applied silently.

StandardIdVersionReleasedNext releaseRead onControlsMandatoryRetired
AIUC-1aiuc-12026.42026-10-152027-01-152026-10-1555425
ISO/IEC 42001:2023iso-4200120232023-12-18not scheduled2026-10-1570700

AIUC-1 (aiuc-1)โ€‹

The AI agent standard of the Artificial Intelligence Underwriting Company: six principles โ€” data and privacy, security, safety, reliability, accountability, society โ€” each a set of requirements with core and supplemental controls, mandatory or optional, updated each quarter and certified against a version locked for the certification's year.

  • Published by AIUC (Artificial Intelligence Underwriting Company); a certification holds 12 months.
  • Evidence kinds: documentation (Policies, contracts, plans and procedures a person wrote and signed.), config (Code and settings that implement a control, as they run.), logs (Audit trails and monitoring: what the system recorded as it ran.), evals (A third party's evaluation report, on the standard's cadence.), report (A report the organization publishes or records.), demonstration (A screen, a notice, a walkthrough: the control seen working.).
  • Crosswalks to: EU AI Act, NIST AI RMF, ISO/IEC 42001, MITRE ATLAS, OWASP Top 10 for LLM Applications, OWASP Top 10 for Agentic Applications, OWASP AIVSS, CSA AICM, SOC 2, IBM AI Risk Atlas, Cisco AI Security & Safety Framework, Colorado AI Act, California SB 53, NYC Local Law 144.

A. Data & Privacyโ€‹

ControlTitleApplicationCadenceEvidence
A001Establish input data policymandatoryevery 12 monthsA001.1 (documentation), A001.2 (config), A001.3 (documentation)
A002Establish output data policymandatoryevery 12 monthsA002.1 (documentation), A002.2 (config)
A003Limit AI agent data accessmandatoryevery 12 monthsA003.1 (config), A003.2 (config), A003.3 (config)
A004Protect IP & trade secretsmandatoryevery 12 monthsA004.1 (documentation), A004.2 (documentation), A004.3 (config), A004.4 (config)
A005Prevent cross-customer data exposuremandatoryevery 12 monthsA005.1 (documentation), A005.2 (config), A005.3 (config)
A006Prevent PII leakagemandatoryevery 12 monthsA006.1 (config), A006.2 (config)
A007Prevent IP violationsmandatoryevery 12 monthsA007.1 (documentation), A007.2 (config), A007.3 (logs)
A008Prevent leakage of credentials and secretsmandatoryevery 12 monthsA008.1 (config), A008.2 (config), A008.3 (config), A008.4 (documentation), A008.5 (config)
A009Third-party testing for data & privacy riskmandatoryevery 3 monthsA009.1 (evals)

B. Securityโ€‹

ControlTitleApplicationCadenceEvidence
B001Third-party testing for security riskmandatoryevery 3 monthsB001.1 (evals), B001.2 (documentation)
B002Detect adversarial inputoptionalevery 3 monthsB002.1 (config), B002.2 (logs), B002.3 (documentation), B002.4 (config), B002.5 (config)
B003Manage public release of technical detailsoptionalevery 12 monthsB003.1 (documentation), B003.2 (documentation)
B004Prevent AI endpoint scrapingmandatoryevery 12 monthsB004.1 (config), B004.2 (config), B004.3 (report), B004.4 (documentation)
B005Implement real-time input filteringoptionalevery 12 monthsB005.1 (config), B005.2 (documentation), B005.3 (demonstration), B005.4 (logs), B005.5 (documentation)
B006Prevent unauthorized AI agent actionsmandatoryevery 12 monthsB006.1 (config), B006.2 (config), B006.3 (config)
B007Enforce user access privileges to AI systemsmandatoryevery 3 monthsB007.1 (config), B007.2 (documentation)
B008Protect AI system deployment environmentmandatoryevery 12 monthsB008.1 (config), B008.2 (config), B008.5 (config), B008.3 (config), B008.4 (config)
B009Limit output over-exposuremandatoryevery 12 monthsB009.1 (config), B009.2 (demonstration), B009.3 (config)
B010Promote secure patterns in generated codemandatoryevery 12 monthsB010.1 (config), B010.2 (config), B010.3 (config), B010.4 (config), B010.5 (config), B010.6 (config)

C. Safetyโ€‹

ControlTitleApplicationCadenceEvidence
C001Define AI risk taxonomymandatoryevery 12 monthsC001.1 (documentation), C001.2 (documentation)
C002Conduct pre-deployment testingmandatoryevery 12 monthsC002.1 (documentation), C002.2 (config), C002.3 (documentation), C002.4 (documentation)
C003Prevent harmful outputsmandatoryevery 12 monthsC003.1 (config), C003.2 (config), C003.3 (config), C003.4 (documentation)
C004Prevent out-of-scope outputsmandatoryevery 12 monthsC004.1 (config), C004.2 (logs), C004.3 (demonstration)
C005Prevent agent-specific high risk outputsmandatoryevery 12 monthsC005.1 (config), C005.2 (documentation), C005.3 (config)
C006Prevent output vulnerabilitiesmandatoryevery 3 monthsC006.1 (config), C006.2 (demonstration), C006.3 (config)
C007Flag high risk outputs for human reviewoptionalevery 12 monthsC007.1 (documentation), C007.2 (config), C007.3 (documentation)
C008Monitor AI risk categoriesoptionalevery 12 monthsC008.1 (logs), C008.2 (documentation), C008.3 (config)
C009Enable real-time feedback and interventionoptionalevery 3 monthsC009.1 (demonstration), C009.2 (documentation)
C010Third-party testing for safety riskmandatoryevery 3 monthsC010.1 (evals)
C011Third-party testing for out-of-scope outputsretiredโ€”โ€”
C012Third-party testing for customer-defined riskretiredโ€”โ€”

D. Reliabilityโ€‹

ControlTitleApplicationCadenceEvidence
D001Prevent hallucinated outputsmandatoryevery 12 monthsD001.1 (config), D001.2 (demonstration), D001.3 (demonstration)
D002Third-party testing for hallucinationsretiredโ€”โ€”
D003Restrict unsafe tool callsmandatoryevery 12 monthsD003.1 (config), D003.2 (config), D003.3 (config), D003.4 (config), D003.5 (documentation)
D004Third-party testing for reliability riskmandatoryevery 3 monthsD004.1 (evals)

E. Accountabilityโ€‹

ControlTitleApplicationCadenceEvidence
E001AI failure plan for security breachesmandatoryevery 12 monthsE001.1 (documentation)
E002AI failure plan for harmful outputsmandatoryevery 12 monthsE002.1 (documentation), E002.2 (documentation)
E003AI failure plan for hallucinationsmandatoryevery 12 monthsE003.1 (documentation), E003.2 (documentation)
E004Assign accountabilitymandatoryevery 12 monthsE004.1 (documentation), E004.2 (config)
E005Document data storage securitymandatoryevery 12 monthsE005.1 (documentation)
E006Conduct vendor and model due diligencemandatoryevery 12 monthsE006.1 (documentation), E006.2 (documentation)
E007Document system change approvalsretiredโ€”โ€”
E008Review internal processesmandatoryevery 12 monthsE008.1 (documentation), E008.2 (documentation)
E009Monitor third-party accessmandatoryevery 12 monthsE009.1 (config), E009.2 (config)
E010Establish AI acceptable use policymandatoryevery 12 monthsE010.1 (documentation), E010.2 (config), E010.3 (demonstration), E010.4 (documentation)
E011Record processing locationsmandatoryevery 12 monthsE011.1 (documentation), E011.2 (documentation)
E012Document regulatory compliancemandatoryevery 6 monthsE012.1 (documentation)
E013Implement quality management systemoptionalevery 12 monthsE013.1 (documentation), E013.2 (documentation), E013.3 (config), E013.4 (documentation), E013.5 (documentation)
E014Share transparency reportsretiredโ€”โ€”
E015Log AI system activitymandatoryevery 12 monthsE015.1 (config), E015.3 (config), E015.4 (config), E015.2 (config)
E016Implement AI disclosure mechanismsmandatoryevery 12 monthsE016.1 (demonstration)
E017Document system transparency policyoptionalevery 12 monthsE017.1 (documentation), E017.2 (documentation), E017.3 (documentation)
E018Third-party testing for accountability riskmandatoryevery 3 monthsE018.1 (evals)

F. Societyโ€‹

ControlTitleApplicationCadenceEvidence
F001Prevent AI cyber misusemandatoryevery 12 monthsF001.1 (documentation), F001.2 (config), F001.3 (documentation)
F002Prevent catastrophic misusemandatoryevery 12 monthsF002.1 (documentation), F002.2 (config)

ISO/IEC 42001:2023 (iso-42001)โ€‹

The international standard for an AI management system: clauses 4 to 10 of the management system and the Annex A controls. Read here through AIUC-1's crosswalk: each clause names the AIUC-1 controls that cover it and how far; what no AIUC-1 control covers is the organization's.

  • Published by ISO/IEC; a certification holds 36 months.
  • Evidence kinds: documentation (Policies, contracts, plans and procedures a person wrote and signed.), config (Code and settings that implement a control, as they run.), logs (Audit trails and monitoring: what the system recorded as it ran.), evals (A third party's evaluation report, on the standard's cadence.), report (A report the organization publishes or records.), demonstration (A screen, a notice, a walkthrough: the control seen working.).
  • Crosswalks to: AIUC-1.
  • Each control names the aiuc-1 controls that cover it, and how far.

4. Context of the organizationโ€‹

ClauseTitleCovered byCoverage
4.1Understanding the organization and its contextC001, E010partial: AIUC-1 is focused on defining acceptable use and assessing risk of the AI system
4.2Understanding the needs and expectations of interested partiesโ€”none: Outside the scope of AIUC-1
4.3Determining the scope of the AI management systemE017, E010full
4.4AI management systemE013full: Met by organizations that opt-in to the optional quality management system requirement

5. Leadershipโ€‹

ClauseTitleCovered byCoverage
5.1Leadership and commitmentE004full
5.2AI policyE010, E017full: AI Acceptable Use Policy and Transparency Policy collectively fulfil the ISO control. Organizations may develop a standalone AI policy
5.3Roles, responsibilities and authoritiesE004full

6. Planningโ€‹

ClauseTitleCovered byCoverage
6.1.1Actions to address risks and opportunities โ€” GeneralC001, C008full
6.1.2AI risk assessmentC001, C008full
6.1.3AI risk treatmentC001, C008full
6.1.4AI system impact assessmentE013, C001partial: AIUC-1 requires risk assessment and organizations can opt-in to the optional quality management system requirement, but does not require impact assessment specifically
6.2AI objectives and planning to achieve themโ€”none: Requiring high-level AI objectives is outside the scope of AIUC-1
6.3Planning of changesE007, E008full: AIUC-1 requires that both system changes and process changes are reviewed

7. Supportโ€‹

ClauseTitleCovered byCoverage
7.1ResourcesE013partial: Organizations opting-in to the optional quality management system requirement will be required to documenting resource management, including security-of-supply related measures
7.2CompetenceE004partial: AIUC-1 requires that accountability is clearly assigned, but does not require competence assessment specifically
7.3Awarenessโ€”none: Internal training processes are outside the scope of AIUC-1
7.4CommunicationE014partial: AIUC-1 does not specify internal communication requirements
7.5.1Documented information โ€” GeneralE013full: Organizations opting-in to the optional quality management system requirement will meet this control
7.5.2Creating and updating documented informationE008full: The combination of quarterly internal reviews and annual recertification requirements fulfils this control
7.5.3Control of documented informationโ€”full: Required as part of AIUC-1 certification process

8. Operationโ€‹

ClauseTitleCovered byCoverage
8.1Operational planning and controlE013full: Organizations opting-in to the optional quality management system requirement will meet this control
8.2AI risk assessmentC001, C008full
8.3AI risk treatmentC001, C008full
8.4AI system impact assessmentE013, C001partial: AIUC-1 requires risk assessment and organizations can opt-in to the optional quality management system requirement, but does not require impact assessment specifically

9. Performance evaluationโ€‹

ClauseTitleCovered byCoverage
9.1Monitoring, measurement, analysis and evaluationE013, C008full: Organizations opting-in to the optional quality management system requirement will meet this control
9.2.1Internal audit - GeneralE008full
9.2.2Internal audit programmeE008full
9.3.1Management review - GeneralE008full
9.3.2Management review inputsE008partial: AIUC-1 internal review requirement is smaller in scope, so fulfilment of 9.3.2 depends on organizational implementation
9.3.3Management review resultsE008partial: AIUC-1 internal review requirement is smaller in scope, so fulfilment of 9.3.2 depends on organizational implementation

10. Improvementโ€‹

ClauseTitleCovered byCoverage
10.1Continual improvementE013full: Organizations opting-in to the optional quality management system requirement will meet this control
10.2Nonconformity and corrective actionE012, E013full: Organizations opting-in to the optional quality management system requirement will meet this control

A. Annex A controlsโ€‹

ClauseTitleCovered byCoverage
A.2.2AI policyE010, E017full: AI Acceptable Use Policy and Transparency Policy collectively fulfil the ISO control. Organizations may develop a standalone AI policy
A.2.3Alignment with other organizational policiesE012, E008partial: AIUC-1 does not require review of internal policies specifically, but require regulatory compliance reviews and regular internal reviews
A.2.4Review of the AI policyE008, E017, E010full
A.3.2AI roles and responsibilitiesE004full
A.3.3Reporting of concernsE008partial: AIUC-1 does not require internal reporting processes specifically, but require regular internal reviews
A.4.2Resource documentationE017, E013partial: AIUC-1 does not require resource documentation specifically, but requires maintaining a centralized repository of system documentation and documenting resource management for organizations opting in to the optional quality management system requirement
A.4.3Data resourcesE017full: Fulfilled by organisations opting into the capability-specific requirement A103: Track training data lineage. In addition, E017: Document system transparency policy lists documenting datasheets in control activities
A.4.4Tooling resourcesE017full: Included in transparency policy control activities
A.4.5System and computing resourcesE017full: Included in transparency policy control activities
A.4.6Human resourcesE004partial: AIUC-1 is scoped to require documentation of clear accountability assigned for system changes
A.5.2AI system impact assessment processC001, E013partial: AIUC-1 requires risk assessment and organizations can opt-in to the optional quality management system requirement, but does not require impact assessment specifically
A.5.3Documentation of AI system impact assessmentsC001, E013partial: AIUC-1 requires risk assessment and organizations can opt-in to the optional quality management system requirement, but does not require impact assessment specifically
A.5.4Assessing AI system impact on individuals or groups of individualsC001, C008, E013partial: AIUC-1 requires risk assessment and organizations can opt-in to the optional quality management system requirement, but does not require impact assessment specifically
A.5.5Assessing societal impacts of AI systemsC001, F001, F002partial: AIUC-1 requires risk assessment, but does not require impact assessment specifically. Impact on society is scoped to cyber and catastrophic misuse prevention
A.6.1.2Objectives for responsible development of AI systemC007none: Organizations pursuing AIUC-1 are naturally aligned with responsible AI principles, but AIUC-1 does not require documentation of responsible AI objectives specifically
A.6.1.3Processes for responsible AI system design and developmentโ€”none: Organizations pursuing AIUC-1 are naturally aligned with responsible AI principles, but AIUC-1 does not require documentation of responsible AI processes specifically
A.6.2.2AI system requirements and specificationE004, E007full
A.6.2.3Documentation of AI system design and developmentE017, E013full
A.6.2.4AI system verification and validationE007, C002, C010, C011, C012, D002, D004full
A.6.2.5AI system deploymentC002full
A.6.2.6AI system operation and monitoringC008partial: AIUC-1 is focused on monitoring risk categories and does not have product performance monitoring/product quality metrics in scope
A.6.2.7AI system technical documentationE014, E013full
A.6.2.8AI system recording of event logsE015full
A.7.2Data for development and enhancement of AI systemA001full: Met by organizations who opt-in to the capability specific requirements on training data quality and lineage
A.7.3Acquisition of dataA001full: Met by organizations who opt-in to the capability specific requirement E103: Track training data lineage
A.7.4Quality of data for AI systemsโ€”full: Met by organizations who opt-in to the capability specific requirement on training data quality
A.7.5Data provenanceE011, A007full
A.7.6Data preparationโ€”partial: AIUC-1 does not require data preparation methods specifically, but covers training data quality more broadly
A.8.2System documentation and information for usersE014, E016full
A.8.3External reportingC009partial: AIUC-1 requirement focuses on AI system users and does not require reporting capabilities for external parties
A.8.4Communication of incidentsE001, E003, E002full
A.8.5Information for interested partiesE001, E012, E014full
A.9.2Processes for responsible use of AI systemsE010, C007, C008full: AIUC-1 requires an Acceptable Use policy which covers prohibited use cases to ensure responsible use of AI systems. In addition, AIUC-1 has a number of concrete requirements ensuring responsible use of the AI system including, e.g., flagging high risk recommendations for human review and monitoring AI risk categories
A.9.3Objectives for responsible use of AI systemE010, C007partial: Partially covered by Acceptable Use Policy, but AIUC-1 does not require documenting objectives specifically
A.9.4Intended use of the AI systemE010, C008full: Acceptable Use Policy control activities require implementing detection and monitoring tools to track policy violations
A.10.2Allocating responsibilitiesE004full
A.10.3SuppliersE006full
A.10.4Customersโ€”none: AIUC-1 does not have specific requirements concerning customer expectations and needs, but covers a broad range of safeguards required to protect users of AI systems including regular testing that safeguards work

The organization's controlsโ€‹

The controls a person writes and signs start from a template under standards/templates/, with what the catalogue knows filled in:

  • E001: e001-failure-plan-security-breaches.md
  • E002: e002-failure-plan-harmful-outputs.md
  • E003: e003-failure-plan-hallucinations.md
  • E010: e010-acceptable-use.md
  • E011: e011-processing-locations.md
  • E012: e012-regulatory-compliance.md
  • A001: a001-input-data-policy.md
  • A002: a002-output-data-policy.md
  • C001: c001-risk-taxonomy.md
  • E006: e006-vendor-due-diligence.md