zkao for Enterprise

What changed since your last audit?

Put zkSecurity’s cryptography audit experience to work on your next release. Review changes as they land, give engineers evidence they can act on, and keep testing between manual audits.

Open-source research

A key that could read too much.

What zkao found
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.
What happened next
zkSecurity’s auditors validated the finding. The CIRCL maintainers fixed it and added regression tests.

Evaluate zkao on a release you know.

Start with one repository

Pick a release candidate and the code you care about. Review the changes since the last audited commit, or widen the scope to include the protocol they depend on.

Give engineers the evidence

Each finding points to the affected code and explains the potential impact. Engineers can inspect the evidence, see whether zkao confirmed the issue, and decide what to fix before release.

Check the fix at the next revision

Run a Regression Check after the patch lands. Between releases, Continuous Security can follow up on open questions and build on what earlier scans learned.

Where will our code run?

Hosted by zkSecurity

Choose which GitHub repositories the zkao app can access. The hosted service uses commercial model APIs, AWS Bedrock, and local models. Our privacy policy explains how we handle code sent for analysis.

In your cloud or on premises

We can set up and operate a dedicated zkao instance with your team. Code, scan artifacts, and findings stay in your environment. Model requests can go through your own provider agreements.

On the hosted service, raw scan logs and code snapshots expire after 90 days. Storage cleanup can take longer. Saved findings, reports, and current analysis memory persist and can contain code excerpts.

Read the data handling policy

Roll it out on your terms.

Access for each team

Group repositories into projects and invite the engineers who review them. Give CI or a coding agent a project token scoped to the repositories and actions it needs.

A budget you control

Set a hard cap for each scan and monthly spending limits for projects. Teams share prepaid organization credits. If you plan to scan at high volume or need invoiced billing, talk to us.

A human review when you need one

Bring zkSecurity’s auditors into a release for a separately scoped manual audit. Give them the design questions, findings, and fixes that need a closer look.