AIUC-1
Context
IntroductionCertificate overview
Framework comparisons
ChangelogAIUC-1 ConsortiumProvide input on AIUC-1Contact
Standard
A. Data & Privacy
B. Security
C. Safety
Define AI risk taxonomyConduct pre-deployment testingPrevent harmful outputsPrevent out-of-scope outputsPrevent customer-defined high risk outputsPrevent output vulnerabilitiesFlag high risk outputs for human reviewMonitor AI risk categoriesEnable real-time feedback and interventionThird-party testing for harmful outputsThird-party testing for out-of-scope outputsThird-party testing for customer-defined risk
D. Reliability
E. Accountability
F. Society
Certification
AIUC-1 certification Scoping Accredited auditors FAQ
Evidence overview
AIUC-1

Share your details and let us know how you hope to use AIUC-1

I am interested in...

The Security, Safety, and Reliability standard for AI agents

Stay up to date with AIUC-1

AIUC-1
AIUC-1.COM

© 2026.AIUC

OverviewChangelogConsortium

LEGAL

Privacy PolicyTerms of Service
AIUC-1 Standard
→
C. Safety
→
C008. Monitor AI risk categories
C008

Monitor AI risk categories

Implement monitoring of AI systems across risk categories

Keywords

MonitoringHigh-Risk Outputs

Application

Optional

Frequency

Every 12 months

Type

Detective

Crosswalks

EU AI Act
Article 72: Post-Market Monitoring by Providers and Post-Market Monitoring Plan for High-Risk AI Systems
ISO 42001
A.5.4: Assessing AI system impact on individuals or groups of individuals
A.6.2.6: AI system operation and monitoring
A.9.4: Intended use of the AI system
6.1.1: Actions to address risks and opportunities — General
6.1.2: AI risk assessment
6.1.3: AI risk treatment
8.2: AI risk assessment
8.3: AI risk treatment
9.1: Monitoring, measurement, analysis and evaluation
A.9.2: Processes for responsible use of AI systems
NIST AI RMF
GOVERN 1.5: Risk monitoring and review
MANAGE 3.1: Third-party monitoring
MANAGE 4.1: Post-deployment monitoring
MEASURE 2.4: Production monitoring
MEASURE 4.3: Performance tracking
CSA AICM
GRC-02: Risk Management Program
MDS-11: Model Failure
TVM-03: Vulnerability Remediation Schedule
MDS-12: Open Model Risk Assessment
TVM-07: Vulnerability Remediation Schedule
OWASP AIVSS
Agent Untraceability
IBM AI Risk Atlas
IBM 85: Non-Technical - Incorrect risk testing
CO AI Act
6-1-1702: Developer Duties
6-1-1703: Deployer Duties

Control activities

Typical evidence

Establishing ongoing monitoring of AI outputs across risk categories. For example, conducting regular evaluations prioritized by risk severity, sampling outputs for review, and tracking system behavior patterns.
C008.1 Logs: AI risk monitoring

Monitoring dashboard, logging system, or evaluation reports showing ongoing AI output tracking - may include output sampling logs with review results, behavior trace logs showing system patterns, prompt-response logging configuration, evaluation schedules prioritized by risk severity, or monitoring metrics dashboard tracking trends over time.

Category

Technical Implementation
Engineering Tooling
Universal
Maintaining documentation. For example, recording identified scenarios with clear examples, updating risk taxonomy based on monitoring findings and incidents.
C008.2 Documentation: Monitoring findings

Document or change log showing identified risk scenarios with examples - may include incident reports triggering taxonomy changes, risk scenario database with concrete examples, or version history of risk taxonomy showing updates with rationale linked to monitoring findings.

Category

Technical Implementation
Engineering Practice
Universal
Integrating AI output monitoring with existing security tools. For example, forwarding alerts and flagged outputs to SIEM platforms, applying standard logging formats (e.g. JSON, syslog) to support automated threat detection workflows.
C008.4 Config: Security tooling

Monitoring dashboard, logging system, or evaluation reports showing ongoing AI output tracking - may include output sampling logs with review results, behavior trace logs showing system patterns, prompt-response logging configuration, evaluation schedules prioritized by risk severity, or monitoring metrics dashboard tracking trends over time.

Category

Technical Implementation
Engineering Tooling
Universal

Organizations can submit alternative evidence demonstrating how they meet the requirement.

AIUC-1 is built with industry leaders

Phil Venables

"We need a SOC 2 for AI agents— a familiar, actionable standard for security and trust."

Google Cloud
Phil Venables
Former CISO of Google Cloud
Dr. Christina Liaghati

"Integrating MITRE ATLAS ensures AI security risk management tools are informed by the latest AI threat patterns and leverage state of the art defensive strategies."

MITRE
Dr. Christina Liaghati
MITRE ATLAS lead
Hyrum Anderson

"Today, enterprises can't reliably assess the security of their AI vendors— we need a standard to address this gap."

Cisco
Hyrum Anderson
Senior Director, Security & AI
Prof. Sanmi Koyejo

"Built on the latest advances in AI research, AIUC-1 empowers organizations to identify, assess, and mitigate AI risks with confidence."

Stanford
Prof. Sanmi Koyejo
Lead for Stanford Trustworthy AI Research
John Bautista

"AIUC-1standardizes how AI is adopted. That's powerful."

Orrick
John Bautista
Partner at Orrick
Lena Smart

"An AIUC-1certificate enables me to sign contracts much faster— it's a clear signal I can trust."

SecurityPal
Lena Smart
Head of Trust for SecurityPal and former CISO of MongoDB