#106Tutorial3 min

Audit your clients’ applications with Hackaiz

Prepare the client mandate, prove control of each target and keep analysis and corrective work within the agreed scope.

Hackaiz team · updated 21/11/2026

Illustration: an agency discusses several client projects.
Illustration: an agency discusses several client projects. Illustrative photo, not a screenshot.

01Start with an exact client inventory

Before connecting anything, ask the client which application and environment you are reviewing. Write down the deployed host, the GitHub repository if code review is included, the client signatory and the dates of the engagement. Treat app.example.com and api.example.com as separate hosts. A client’s permission for its own application does not automatically authorize examination of a payment provider or another third party linked from it.

Use this inventory to avoid a common mismatch: reviewing the repository for a staging application while presenting conclusions about production. Record the environment in your engagement notes and compare it with the target displayed in Hackaiz. If you use Client spaces to group this work, remember that client spaces and white-label reports require Agency or Business. Grouping a project does not grant access to its systems.

02File the mandate before client-host analysis

Open Agency mandates and use New record to identify the Client legal name, Client signatory and Signatory e-mail. List Exact hosts (one per line, no *) and GitHub repositories (owner/name), select only the actions the client has authorized, and enter Start and End. The form limits the period to 366 days. The declaration confirms that you hold a written, signed mandate for that exact scope and period.

Keep the signed document yourself; the page asks you not to upload it. Select File record and follow the dossier in My records. Submission leaves it awaiting review. An approved mandate is an operational authorization record, not a legal opinion. For third-party client hosts, a current, unrevoked approval with the required review evidence must match both the exact host and requested action. A pending or expired dossier is not enough.

  1. 1Check the host list against the client’s actual deployment addresses, without wildcard entries.
  2. 2Make sure the requested actions and dates match the signed agreement before filing.
  3. 3If the engagement ends or consent is withdrawn, use Revoke rather than continuing under the old dossier.

03Prove ownership and select the work

The mandate is additional to technical verification. No website or API is analyzed before domain ownership proof: use a DNS TXT record named _hackaiz, publish the supplied value at /.well-known/hackaiz-verification.txt over HTTPS, or ask the project’s AI to create that file. Coordinate with the client’s domain or deployment administrator. A signed agreement alone cannot unlock the analysis, even when your agency built the site.

Open Connect for the authorized target and follow the displayed proof instructions. For repository work, connect the appropriate GitHub access and check the selected owner and repository name against the mandate. Review the analysis selection before launch. Unticked checks are neither run nor billed; selected actions consume credits. Do not silently expand the engagement because another linked domain or repository becomes visible.

04Separate findings, proposals and verified outcomes

Read each finding before presenting it to the client. Danger, To fix and To watch are customer-facing priorities, not a statement that every item is proven exploitable in that client’s business context. Explain the evidence and any missing coverage. For instance, a suspected missing access check in an invoice endpoint needs to be understood in relation to the actual server-side permissions; do not demonstrate it using another person’s data without a properly authorized procedure.

When a supported correction is proposed, a draft GitHub pull request is a reviewable code change, not a deployed fix. A human reviews and approves it, the team tests it and decides whether to merge and deploy; Hackaiz never merges automatically. Arrange a new authorized check after deployment and distinguish accepted code from a verified live outcome. If the client requests follow-up monitoring, enable it only as an optional service on connected systems within the agreed authorization, with credits for the actions performed.

Frequently asked questions

Was this article helpful?

Related articles