01
Evidence Room
See completed work by actual Git repository, URL, upload, or path and export the latest report for selected assets.
Security evidence and reporting
Make security work provable when someone asks.
Package current evidence by asset, export reviewed reports, share only the findings a recipient needs, and retain the decision history behind remediation, retest, and accepted risk.
Asset-level Evidence RoomPentest-style PDF exportsExpiring finding shares
evidence://current-stateprocessing
ASSESSMENTrelease 1.14
DECISIONaccepted and owned
RETESTfix verified
ZEROQUARRYEvidence room assemblyBuild the answer from the live product historyactive
REPORTcustomer-ready PDF
SHAREpassword + expiry
ANSWERcurrent control story
the evidence comes from operating work, not a last-minute document hunt
Capabilities
Evidence should be a by-product of the operating process.
Reconstructing security history from tickets and chat during a customer review is expensive. The resulting story is usually incomplete.
02
Report and finding exports
Create Markdown, single-file HTML, or pentest-style PDF outputs with confidence and review filters.
03
Controlled secure shares
Give a named recipient read-only access to selected findings through a password-protected, expiring, revocable link.
04
Disclosure tracking
Preserve reported, acknowledged, fixed, advisory, bounty, credit, and closure milestones for external issues.
05
Audit history
Show investigation stages, model resolution, human actors, outcomes, lifecycle changes, and reasons.
06
Branding and disclaimers
Apply account and tier settings to customer-facing reports without rewriting historical evidence.
How it runs
A concrete path through the work.
ZeroQuarry automates investigation and coordination. Your team keeps control of authorization, risk ownership, and production changes.
Build
Create evidence continuously through projects, scan versions, finding states, tickets, and retests.
Select
Choose the exact assets, reports, sections, findings, and confidence boundary relevant to the request.
Review
Remove irrelevant or sensitive context and confirm important findings have current decisions.
Deliver
Export a static pack or use a time-bounded share, then revoke access when the review ends.
Operational result
What the team gets back.
Useful coverage should lead to faster decisions, cleaner remediation, and evidence that holds up when someone asks for it later.
Faster assurance responses
Answer customer, audit, investor, insurance, and internal governance requests from current product history.
Smaller disclosure surface
Share selected findings instead of granting access to the workspace or sending the full internal report.
Defensible risk narratives
Connect the technical issue to validation, ownership, mitigation, and retest rather than presenting a static scan snapshot.
Details
Questions that come up in evaluation.
These are the product boundaries, controls, and operating details teams usually want to understand first.
Does the Evidence Room prove compliance?
No. It packages assessment evidence and history. Your organization still determines control scope, test frequency, reviewer requirements, and framework assertions.
Can a recipient see the rest of our scan?
A secure share exposes only the selected findings. It does not grant the recipient access to the rest of the report, project, or account.
What is included in a PDF report?
The pentest-style layout can include target context, executive summary, finding overview, per-finding evidence, and configured report definitions, branding, and disclaimers.
Related workflows
Continue through the operating loop.
Start with one real security boundary.
Use the free trial on your own product, then decide whether the resulting security work is useful enough to keep.