You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AI-CAIQ question LOG-15.1 (Logging and Monitoring, control LOG-15), answered NO in the CloudLab Works AI-CAIQ (CSA AI-CAIQ v1.1.0).
Are all input events (content and metadata) logged and monitored to enable auditing and reporting on the usage of AI models?
Gap and corrective plan
Gap: Image inputs to the detector are deliberately never logged (privacy design); model metadata (model, device, det_fps) is logged in camera and alive events; MCP tool calls from agents (inputs to the AI-facing interface) are not logged. Corrective plan: Optional MCP access log; document that image content is excluded by design [Code change in oak-events (described per row), with tests and a CHANGELOG entry]. Owner: Alex Alvord. Milestones: draft by 2027-02-07; in place by 2027-02-28. Due: 2027-02-28.
Owner
Alex Alvord
Due
2027-02-28
SSRM ownership
Shared AP-AIC
Customer responsibility
Log agent tool calls in your MCP client if needed.
Activity
cloudlabworks commentedon Nov 3, 2026
Progress 2026-11-02 (after the text above was written):
oak-events mcp --access-log FILErecords every agent tool call (time, tool, argument names and value sizes, result count, outcome, client process id), never values, results or image content. See https://github.com/cloudlabworks/oak-events/blob/v0.1.2/README.md anddocs/HARDENING.md.Open: the remaining gap is by design; Alex decides at the next AI-CAIQ review whether this issue stays open as the record of that decision.