#097Guide3 min

Prepare technical evidence for a compliance effort

Build a traceable evidence pack without confusing technical observations with proof of compliance.

Hackaiz team · updated 21/11/2026

Illustration: a professional files evidence folders.
Illustration: a professional files evidence folders. Illustrative photo, not a screenshot.

01Start with the question the evidence must answer

A useful compliance file starts with a narrow question: which application, environment and technical control are you documenting? Write down the target, the analysis date and the requirement your reviewer wants to examine. Keep this scope note alongside the Hackaiz output in your own evidence repository. This is a recommended working method, not a promise that Hackaiz maintains your entire compliance file.

For example, a finding about access to another user’s record can support a discussion about application access controls. It cannot by itself establish that every employee has appropriate permissions or that access reviews happen on schedule. Hackaiz provides technical evidence only; it does not certify an organization, issue a compliance decision or replace the person responsible for interpreting the requirement.

02Separate observations, declarations and missing proof

Open the relevant analysis from Projects. Where the report includes the Technical pre-audit alignment report, read each control state before selecting evidence. “Issue detected: see evidence” points to an observed problem. “Examined, nothing found” describes the result of an examination, not a compliant control. “Partly examined” and “Not examined by this analysis” must remain visible in the material you hand over.

The report also distinguishes “Declared by you: in place (not proven)” from evidence produced by an analysis. Do not turn a team member’s answer into an independently verified fact. A control marked “Must be proven by a person” needs additional work outside the automated observation. Ask the responsible colleague for an appropriate policy, review record or other supporting material, then let the reviewer assess its relevance.

03Export material that preserves context

Use Download (JSON) in the technical alignment panel to retain the analysis identifier, export date, control identifiers, states and linked finding references. Those references can include the rule, file and line when available. Store the original export rather than only copying a reassuring heading into a presentation. The JSON explicitly identifies the material as technical pre-audit alignment, not certification, and does not compute a compliance percentage.

For a readable companion, use Shareable report, choose Security lead under Recipient and select PDF under Format. The PDF flow uses a browser print window; allow that window if the browser blocks it. Review the resulting file before circulation because technical evidence may disclose implementation details. Keep exports in an access-controlled location, and explain which analysis each attachment belongs to instead of combining unrelated results without dates.

04Attach the corrective action and its verification

For each relevant finding, add a short entry in your own tracker: the observed condition, its effect on the requirement, a responsible person, the proposed action and the evidence still missing. Preserve the initial result. A later clean result is more useful when the reviewer can understand what changed and what scope was checked again. An unresolved limitation should remain an open question, not disappear from the final summary.

When a supported fix is requested, Hackaiz prepares a draft GitHub pull request, a proposed code change that a human reviews and approves. It never merges automatically. After your team applies a correction, run an appropriate new analysis and compare the relevant evidence. Analyses and correction requests use credits; checks left unticked are neither run nor billed. Budget the verification step without presenting a fixed cost estimate.

Frequently asked questions

Was this article helpful?

Related articles