What Coriqo doesn't do yet.
Examiners, boards and vendor-risk teams rely on our record. They should hear what we can't do yet from us, before they find it themselves, because a vendor that hides its gaps gives them no reason to believe the rest. Below are the certifications and features we have not shipped yet. Deployment guidance is in the security pack, available under NDA.
Last verified 15 September 2026
Certifications and independent review
Your vendor-risk team will look for outside audits first. We don't have them yet.
SOC 2
SOC 2 is in progress. We do not hold a SOC 2 report today, or any other third-party security certification.
Independent cryptographic review
The signing and sealing core has not had an independent cryptographic review.
Platform features
The first gap below limits how much independent proof stands behind the record today. The others affect how you install Coriqo and feed it data.
External witness cosigning
Witness cosigning is built, and our verification tool checks witness signatures. No outside witness has signed up yet, so today only Coriqo signs each checkpoint.
Kubernetes packaging
The container runs on Kubernetes, but we don't ship manifests or a Helm chart yet.
Live system connectors
Coriqo does not yet pull continuously from your model registries and cloud accounts. Your cloud accounts can be read by an on-demand, read-only scan, and your model inventory comes in by CSV or Excel file, with a review step before anything is applied. Jira, GitHub and SharePoint are the exception: Evidence Connect syncs them daily or when you ask.
Email from your own Gmail or Outlook
This covers the emails to your committee and your examiners. Staff alerts, sign-in links and billing emails still come from Coriqo. Gmail and Outlook don't tell us when a message is delivered or opened, so an examiner package sent from your mailbox shows that your mailbox sent it, and nothing more. Yes, No and Maybe buttons on committee invitations appear only when the invitation comes from your connected mailbox.
Two things can slow you down at the start. Google has not yet approved our app, so for now Gmail connections are limited to people we have added as testers. And if your Microsoft 365 administrator has locked down who can approve apps, they will need to approve Coriqo once before you can connect Outlook. We have tested the Outlook connection with automated checks, but not yet with a live Microsoft 365 account.
Agent discovery from logs
Log import reads five formats: Azure OpenAI diagnostic logs, Azure API Management gateway logs, AWS Bedrock model invocation logs, AWS CloudTrail Bedrock events, and OpenTelemetry GenAI traces. We built the Azure and AWS readers from Microsoft's and AWS's published documentation and from public or synthetic sample events. None of them has been checked on a production export from a customer. What each one can tell you differs. Azure OpenAI's own logs do not name the calling application, so from those alone Coriqo lists the AI callers and deployments it sees, not confirmed agents. API Management gateway logs, Bedrock invocation logs and CloudTrail do name the caller, and Bedrock lets a team tag its calls with an application name. Traces that carry agent and tool spans give the firmest answer. Coriqo never reads prompt or response content, and it deletes the uploaded file when the import ends unless an admin chooses to keep it. Every import ends Partial until a cloud account is connected to compare against. Verified 9 October 2026.
Operations and alerting
When an AI system goes wrong out of hours, the right person has to hear about it. This is what our alerting does not do yet.
Native on-call routing
We don't send SMS, offer a PagerDuty or Opsgenie app, or run on-call rotations. Alerts reach PagerDuty and Opsgenie through their events APIs: an alert opens the incident, and acknowledging or resolving it in Coriqo acknowledges or closes it there. The other direction is not built in: acknowledging inside PagerDuty reaches Coriqo only if your own automation calls our acknowledgement API with a service account. Alerts by webhook (an automatic message to another system), Slack, email and Teams work too, and every one records acknowledgement and escalation.
Slack confirms delivery, not acknowledgement
Slack tells us a message arrived. It cannot tell us that anyone read it, so the furthest a Slack delivery can get is "delivered". The message has an "Acknowledge in Coriqo" button that opens Coriqo, and the acknowledgement is recorded there, not in Slack.
Escalation runs once a minute
The job that escalates unacknowledged alerts runs on a one-minute schedule, so a step can happen up to a minute after its deadline.
No policy, no escalation
An alert category with no escalation policy does not escalate. Its alerts are still recorded, but they have no acknowledgement deadline and no next level. The same is true of an alert your policy sends same day, to the weekly digest or to the record only: only paged alerts escalate.
Report a vulnerability
If you've found a security issue rather than a missing feature, please don't post it here. Email security@coriqo.io or see /.well-known/security.txt. We investigate every report, fix confirmed issues, and credit the reporter privately unless asked to do otherwise.
Ask us about anything on this page.
An engineer who works on the code will answer. If something you need isn't listed, tell us.