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.
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.
Who approved it.
The named approver, approved scope, identities, allowed actions, and limits in force when the run started.
What ran.
Every executed step in order, with the agent and identity that performed it.
What came back.
Requests, responses, and artifacts, with sensitive values redacted before storage.
What your controls saw.
Detections, blocks, and logs from connected controls, captured during each step.
What it proves.
The finding, its evidence state, and the specific steps that support it.
Whether the fix held.
Each retest under the original approval, appended to the same record.
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.
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.
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.
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.
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.
Writes the record as it validates.
Each step Nectar plans and executes is recorded with its reasoning, identity, and outcome.
Explore Nectar →HIVEGoverns who sees and replays it.
Approvals, roles, and replay permissions are set in Hive, the governed workspace for validation.
Explore Hive →VALIDATIONSSame record for every validation type.
Web application, API, and identity validations all produce records with the same anatomy.
Web application exposure validation →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.