AIUC-1
E015

Log model activity

Maintain logs of AI system processes, actions, and model outputs where permitted to support incident investigation, auditing, and explanation of AI system behavior

Keywords
Explainability
Logs
Application
Mandatory
Frequency
Every 12 months
Type
Detective
Crosswalks
AML-M0024: AI Telemetry Logging
Article 12: Record-Keeping
Article 19: Automatically Generated Logs
A.6.2.8: AI system recording of event logs
MEASURE 2.4: Production monitoring
MEASURE 2.8: Transparency and accountability
LLM10:25 - Unbounded Consumption
LOG-01: Logging and Monitoring Policy and Procedures
LOG-03: Security Monitoring and Alerting
LOG-07: Logging Scope
LOG-08: Log Records
LOG-09: Log Protection
LOG-10: Encryption Monitoring and Reporting
LOG-11: Transaction / Activity Logging
LOG-13: Failures and Anomalies Reporting
LOG-14: Input Monitoring
LOG-15: Output Monitoring
MDS-10: Model Continuous Monitoring
LOG-04: Audit Logs Access and Accountability
LOG-05: Audit Logs Monitoring and Response
LOG-06: Clock Synchronization
LOG-12: Access Control Logs
SEF-05: Incident Response Metrics
SEF-07: Security Breach Notification
Capturing system activity details to support incident investigation and behavior explanation. For example, logging inputs, processing steps, outputs, and metadata for AI systems.
E015.1 Config: Logging implementation

Screenshot of logging code or configuration showing what system activity is captured - may include code logging inputs and outputs, logging configuration file specifying what to log, or example log entries showing captured information (timestamps, inputs, outputs, user actions).

Logs
Universal
Implementing log storage with appropriate retention periods, access controls, and data sanitation to support auditing and incident response.
E015.2 Config: Log storage

Screenshot of log storage system showing retention policies, access controls and sanitation practices - may include log management platform (Datadog, Splunk, CloudWatch) with retention period settings and PII-masking, access control configuration showing who can view logs, or storage settings with automatic deletion rules.

LogsEngineering Tooling
Universal
Implementing technical controls to ensure logs are tamper-evident and independently verifiable. For example, ensuring that captured records cannot be modified or deleted after creation, ensuring sequence integrity so that gaps, omissions, and reordering are detectable during incident investigation or audit.
E015.3 Config: Log integrity protection

Screenshot or documentation of log immutability controls - for example, write-once-read-many (WORM) storage configuration, cryptographic hashing of log entries, append-only database settings, or third-party log management platform features.

LogsEngineering Code
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-1 standardizes how AI is adopted. That's powerful."

Orrick
John Bautista
Partner at Orrick
Lena Smart

"An AIUC-1 certificate 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