Why zkao
Built by auditors.
Improved by real audits.
Attackers run AI against your code around the clock. zkao is the red team that answers in kind, bringing specialist investigations and the lessons of our human audits to the code your team is building.
Sign in to request access. We review each team before enabling scans.
A published discovery
Who could decrypt a message in Cloudflare’s CIRCL?
zkao found a flaw in Cloudflare’s open-source CIRCL cryptography library. A key could decrypt a message even when it failed the sender’s access policy. zkSecurity’s auditors validated the finding. The CIRCL maintainers fixed it and added regression tests.
Audit experience, put to work.
zkSecurity builds zkao alongside its manual audit practice. Every bug our experts find in a private audit becomes a lesson zkao learns.
Beyond One Codebase
Learns From Every Audit
Patterns from zkSecurity’s cryptography audits inform new investigations. We turn lessons from different protocols into techniques that can apply to your code.
Every Audit Is a Lesson
Taught by Our Auditors
We are an audit firm first. Our experts keep finding bugs in private audits that no model finds on its own. Each one, and the reasoning behind it, is worked into zkao as a technique. That expert knowledge exists nowhere public, and it flows into zkao with every engagement.
Our Full-Time Job
Always Improving
New models, agent harnesses, techniques, and analysis tools appear every week. We try them on real cryptography code as they land. The ones that find bugs become part of zkao.
Where zkao fits in your team
Red team and blue team are different jobs. Your developers, your security team, and your internal harness defend the system they know. zkao attacks it, all the time.
Your engineers and coding agents
Bring product context, implement changes, and review what is intended behavior. Give zkao that context through guidance, reference documents, and threat-model answers.
zkao
Your standing red team. Attacks the code the way an adversary would, challenges candidate findings, and returns evidence and recommended fixes. Continuous Security keeps the attack going as the code changes.
Your human auditors
Challenge the design and security assumptions in depth. Use automated findings to focus the discussion, while leaving room for issues the agents missed.
Our auditors still find cryptography bugs that zkao misses. Automated analysis can make a review more useful; it does not establish that a system is secure.
How zkao compares to other security toolsEvidence your team can question.
A finding should help you make a decision. Inspect the affected code, the attack path, how the issue was confirmed, and the recommended fix. Then bring your own context to the review.
A product by zkSecurity
Add an auditor’s perspective.
Request access for your team, or ask us for a demo of the workflow on cryptographic code.