#141Case study3 min

Why an agency should audit before delivery

Turn a pre-delivery security review into a clear record of scope, evidence, decisions and remaining work.

Hackaiz team · updated 21/11/2026

Illustration: a creator films a short video on a phone.
Illustration: a creator films a short video on a phone. Illustrative photo, not a screenshot.

01Make the review part of the delivery decision

A working demonstration does not answer every security question. Before handing over an application, an agency needs to distinguish what was built, what was examined and what still needs a decision. A pre-delivery Hackaiz analysis can provide technical findings with evidence for the inspected scope. It is not a security certification, a compliance guarantee or a substitute for the agency’s own acceptance tests and professional judgement.

Use a practical delivery question to frame the review: does the inspected version correspond to the version the client will receive? A repository can contain a prepared fix while the published site still uses older code. Establish the intended release, the authorized targets and the person who will review the results. This is recommended handover practice, not a claim that Hackaiz supplies a contractual acceptance workflow or signs off the project for the client.

02Obtain authorization before scanning a client system

Client work does not remove the ownership requirement. Before analyzing a website or API, prove control of its domain through the DNS TXT record _hackaiz or the HTTPS file /.well-known/hackaiz-verification.txt. The project’s AI can also be asked to create the required file. The Connect flow provides the value to publish. If the client controls DNS or deployment, arrange that step with the authorized person instead of treating a publicly accessible address as consent.

Open Connect, prepare the relevant system connection and complete the proof before launching the website or API analysis. On the project page, Run security scan starts the selected analysis. Review the checked controls with the client’s delivery scope in mind: unticked checks are not executed and are not billed. Analysis work consumes credits. A check omitted from this engagement must remain an explicit limit in the handover, not be silently described as passed.

03Convert findings into reviewable delivery work

Read Danger, To fix and To watch as prioritization groups, then inspect the evidence behind each finding. For an agency, a useful handover item identifies the affected part of the application, the observed issue, the proposed response and the person responsible for deciding. These are suggested contents for your own delivery notes, not an assertion that every field is automatically generated in a client acceptance document.

For code corrections supported by Hackaiz, open the prepared proposal on Fixes. Review Files concerned, What the change does, Validation performed and Known limitations before approving delivery as a draft GitHub pull request. Human approval is required, and Hackaiz never merges automatically. Retain time for the developer’s review, tests and deployment. External configuration changes that cannot be automated need guidance and targeted retesting rather than a promise of direct database modification.

04Deliver a dated record, not a permanent assurance

After changes are deployed, verify the relevant target again and compare the available evidence. The project page exposes Scan history and comparison with the previous analysis. In your handover notes, identify the relevant analysis, the inspected version, unresolved findings and untested areas. An unfinished check is not a successful check, and a finding that no longer appears should still be interpreted in light of the new analysis scope.

Agree who owns subsequent changes and who will respond if the application evolves. Hackaiz offers optional monitoring for connected systems, with credits consumed by monitoring and analyses; it is not automatic for every delivered site. The agency can use technical evidence to explain its decisions without promising that an application is permanently safe. A clear delivery record is valuable precisely because it distinguishes completed work from residual risk and future responsibility.

Frequently asked questions

Was this article helpful?

Related articles