#100Guide3 min
Prepare a security audit before a certification
Use a technical pre-audit to expose gaps and organize evidence for the independent assessment.
Hackaiz team · updated 21/11/2026

01Agree the assessment boundary with your reviewer
Before ordering technical checks, ask the person leading the certification effort which systems, environments and requirements are in scope. An application analysis may contribute evidence for a specific control, while the assessment may also concern governance, personnel, suppliers or incident handling. Write down the boundary and the expected deliverables in your own preparation plan. Do not assume that a vulnerability report is the complete set of material an assessor will request.
Hackaiz provides technical evidence only and never certifies. Its role here is to help document observable weaknesses, examination limits and corrective work before your formal assessment. A report without findings is not a readiness certificate. The applicable scheme and the assessor determine what is sufficient; Hackaiz does not promise acceptance of an export or a successful certification outcome.
03Use control states to build the gap list
In the result, look for the Technical pre-audit alignment report when available. “Issue detected: see evidence” directs attention to a problem; “Partly examined” calls for a narrower conclusion; “Not examined by this analysis” identifies missing technical examination. Keep these distinctions in the gap list you maintain for the audit. “Examined, nothing found” is evidence of an examination result, not an assertion that the organization meets the corresponding requirement.
Treat “Declared by you: in place (not proven)” as a statement awaiting support, not a passed test. Controls marked “Must be proven by a person” should be assigned to an appropriate colleague for documentary or other review. The Download (JSON) button preserves control identifiers, states and finding references for your working file. The export explicitly says it is not certification and does not calculate a compliance percentage; do not add such a percentage to your presentation.
04Verify changes and hand over an honest evidence pack
Prioritize findings by Danger, To fix and To watch, then consider the affected data and business operation with the responsible owner. For a supported code correction, Hackaiz prepares a draft GitHub pull request. A human reviews and approves the proposed change, and merging is never automatic. Your team should also test the change before applying it. A proposed patch alone does not show that the deployed system has changed.
After remediation, run a relevant new analysis and retain both results with a note of the change and the remaining gaps. In Shareable report, select Security lead and PDF for a readable handover, alongside the technical alignment JSON where useful. The PDF uses the browser’s print window. Explain to the assessor which version and environment each attachment concerns, which work was not performed and which declarations still need support. This makes the pack reviewable without presenting technical preparation as an independent certification decision.
Frequently asked questions
Take the next step
Was this article helpful?