Design Partner Program
EVIDENCE FABRIC · SECURITY VALIDATION EVIDENCE

Replayable evidence for every finding and every fix.

Evidence Fabric keeps the full record behind each validation result: who approved it, what ran, what came back, what your controls saw, and whether the fix held. Engineering, security, and audit read the same record.

EVR-0418 Cross-user order access · orders-api · staging
ILLUSTRATIVE DATA In progress
OBJECTIVE1 / 7
Determine whether one buyer can read another buyer’s orders.
Defined
target orders-api · staging
requested by AppSec lead
question Cross-user order access
The objective is written before anything runs, so the result can be judged against what was asked.
↑ ↓ to step through
01 · WHAT A RECORD HOLDS

Security Validation Evidence: Six Parts, One Record per Conclusion

A finding without its evidence is an opinion. Every Hayrok conclusion carries the authority, actions, and observations that produced it, so anyone reviewing it can see exactly how it was reached.

AUTHORITY01

Who approved it.

The named approver, approved scope, identities, allowed actions, and limits in force when the run started.

ACTIONS02

What ran.

Every executed step in order, with the agent and identity that performed it.

OBSERVATIONS03

What came back.

Requests, responses, and artifacts, with sensitive values redacted before storage.

CONTROL TELEMETRY04

What your controls saw.

Detections, blocks, and logs from connected controls, captured during each step.

CONCLUSION05

What it proves.

The finding, its evidence state, and the specific steps that support it.

RETEST HISTORY06

Whether the fix held.

Each retest under the original approval, appended to the same record.

02 · EVIDENCE STATES

Confidence Levels: Say Exactly How Sure You Are

Each conclusion is labelled by the strength of its evidence. The label travels with the finding into tickets, reports, and reviews, so no one has to guess whether a result was proven or inferred.

Reproduced The condition was demonstrated.An approved step produced the outcome under the stated identity. The strongest evidence state.
Observed The behavior was seen directly.A response, log, or control signal was captured, without a full end-to-end demonstration.
Assessed Reasoned from evidence.The conclusion follows from recorded evidence but was not executed. Marked so no one mistakes it for proof.
Not confirmed Not established.The scenario ran and the condition did not occur, or could not be tested within scope.
03 · REMEDIATION VERIFICATION

Fix Verification: Prove It With the Test That Found the Flaw

Retest from the original record after a fix ships. The same scenario runs under the same identities and approvals, and the result joins the record, so "fixed" means proven, not closed.

ORIGINAL RUN · 2026-10-28Reproduced
requestGET /api/orders/{order_id}
identitybuyer_b
response200 OK
databuyer_a order fields
RETEST · pendingPending
requestGET /api/orders/{order_id}
identitybuyer_b
responsenot yet run
data—
Same scenario, same approval
04 · AUDIT-READY SECURITY EVIDENCE

Control Assurance Evidence: Traceable for Your Auditors

Security control testing produces evidence as a by-product, not a separate project. Each record links the approval, the test, the control observation, and the retest, in the order they happened.

01

Ordered and attributable

Each entry carries a timestamp, actor, and the approval it ran under, so the sequence can be reconstructed without interviews.

02

Redacted by default

Sensitive values are masked before storage. Reviewers see that data was exposed without the record becoming a second copy of it.

03

Access-controlled

Who can view, replay, or export a record follows the roles your team sets in Hive.

04

Exportable as an evidence pack

Share a record or a set of records with auditors, customers, or leadership in a single package.

05 · REPORT VS RECORD

Replayable Records: A Report Describes, a Record Replays

Scanner output and penetration test reports are snapshots. Security validation evidence stays connected to the scope, actions, and retests behind it.

Scanner output
Penetration test report
Evidence Fabric record
WHAT IT SHOWS
Patterns that might be exploitable.
What a tester found during the engagement.
What ran, what came back, and the evidence state of each conclusion.
AUTHORITY
Rarely recorded.
Statement of work and rules of engagement, kept separately.
Approver, scope, identities, and limits stored with every result.
CONTROL VIEW
Not included.
Sometimes noted by the tester.
Control telemetry captured at each executed step.
AFTER A FIX
The next scan.
A separately scheduled retest.
Retest from the record; the result joins the same history.
FOR AUDIT
Exported findings list.
Static PDF.
Ordered, attributable record, exportable as an evidence pack.
06 · ACROSS THE PLATFORM

How Evidence Is Made: Produced by Nectar, Kept by Evidence Fabric

Evidence is not an export step at the end. It is written as each validation runs, under the same approvals, and read wherever your team works.

07 · FAQ

Security Validation Evidence FAQ: What Reviewers Ask

The record behind a validation result: the approval it ran under, the steps executed, the responses and control observations captured, and the conclusion those steps support.

See an Evidence Record: From Approval to Verified Fix

Walk through a sample record with your security and audit leads, then discuss the evidence your program needs to keep.

✓A sample record from approval to verified fix✓Evidence states and redaction✓Exporting an evidence pack for audit
Book a Demo