Run Evidence

Run evidence should not require screenshot archaeology

Zerocheck turns executed browser runs into timestamped, commit-bound JSON evidence with screenshots, recordings, and step traces.

Who this is for

Role
Compliance officer or CTO
Company
B2B SaaS (50–500 engineers) going through SOC 2 Type II
Trigger
Audit window opens, enterprise deal blocked pending certification, or compliance officer sends the evidence request email

This is for you if:

  • Screenshots and ad-hoc explanations carry less weight than system-generated logs - auditors are raising the bar on what counts as evidence
  • SOC 2 Type II certification or renewal in the next 6 months
  • Currently assembling application testing evidence manually (screenshots, spreadsheets, Confluence)

The pain is real

“The guts of a SOC2 audit are a giant spreadsheet questionnaire and a battery of screenshots serving as evidence for the answers in the questionnaire.”

Thomas Ptacek, Fly.iosource

“Evidence collection becomes a quarterly scavenger hunt - a tax on engineering velocity that produces almost no security value.”

Ederasource

“If your evidence collection process is ‘take a screenshot on Tuesday,’ your evidence is already stale by Wednesday.”

Ederasource

“Organizations often find they are already doing 80% of what they should be doing but have only documented 20% of it.”

HiComplysource

SOC 2 requires documenting 200+ controls with evidence per audit cycle

Vanta and Drata leave a “20% manual gap” - application-level testing evidence is untouched

Fintech and healthtech testing markets growing at 26.4% and 13.6% CAGR

Why nobody else solves this

Compliance platforms like Vanta and Drata automate infrastructure evidence - they can confirm MFA is enabled or access reviews happened. But they cannot see inside your application. They can’t prove “we tested the checkout flow and it passed on this commit.”

Momentic has SOC 2 Type II, SAML/SCIM, and immutable audit logs - all for their own platform’s compliance. They don’t generate evidence for the customer’s audit. Bug0 is SOC 2 certified themselves but likewise produces nothing your auditor can use. TesterArmy doesn’t mention compliance at all.

No E2E testing tool generates audit-ready artifacts. CI logs expire. Test dashboards aren’t formatted for auditors. The bridge between “test passed” and “auditable proof of control effectiveness” is entirely manual - screenshots pasted into Confluence.

The workflow today vs. with Zerocheck

Without Zerocheck

SOC 2 Type II audit is scheduled. Compliance officer requests evidence of change management controls (CC7.2, CC8.1). QA has CI logs - but they’re not linked to controls, not timestamped in auditor-friendly format, and half have already expired. A 2-week sprint begins: 2 engineers manually map Jira tickets → test runs → screenshots → Confluence pages. 200 pages assembled. The auditor flags gaps. Repeat every year.

With Zerocheck

Approved tests run on PRs and production monitors. Every executed run generates JSON evidence with commit, timestamp, result, screenshots, recording, and step trace. Compliance still owns audit mapping, but the raw proof no longer depends on screenshots pasted into documents.

How it works

1

Mark critical tests and keep JSON run evidence tied to commits

2

Executed PR and monitor runs generate timestamped, commit-bound JSON evidence

3

One-click JSON export of run evidence with screenshots, recordings, and step traces

4

Searchable evidence history with retention policies

FAQ

Will my auditor accept evidence from AI-authored tests?

The evidence is factual: timestamped pass/fail, screenshots, step traces, and commit SHA. If a test was suggested by AI, a human approves it before it becomes run evidence. The proof is the output of real test execution.

We already use Vanta. Why do we need Zerocheck?

Vanta automates infrastructure evidence. Zerocheck produces JSON evidence from real application test runs: which approved test ran, the commit, result, screenshots, recording, and step trace. Your compliance team can map that proof to controls as needed.

How do you map tests to SOC 2 controls?

Zerocheck does not currently map tests to SOC 2 controls. It exports timestamped JSON run evidence with test name, result, commit, timestamp, screenshots, recordings, and step traces for your compliance team to map as needed.

We have zero tests. Can we still use this?

Yes. Start by discovering the critical flows, review the suggested tests, and approve the ones that should run. Evidence starts accumulating once those approved tests execute on PRs or production monitors.

Run evidence should not require screenshot archaeology

Other tools prove their own platform is secure. Zerocheck produces JSON evidence from your executed application tests.

Get a demo