#111Guide1 min
Use Hackaiz as a security consultant
What the tool speeds up, what stays your expertise, and how to say it to the client.
Hackaiz team · updated 18/11/2026

01Keep responsibility for the advice
Hackaiz helps you examine authorized systems and organize technical results. It does not replace your professional judgment, contract or understanding of your client’s business. Before starting, specify the applications, permitted access, exclusions and people allowed to receive results. An analysis is not certification and does not, by itself, demonstrate an organization’s compliance.
02Prepare access with your client
For a website, establish the required control proof and consent before any read. For a repository, use an authorized GitHub installation on the selected repositories. For a supported database, prepare limited read-only access. A client space is an organizational tool: it grants no rights over a system and does not create a delegated account for your client.
- 1Agree on the systems in scope with your client.
- 2Check authorizations and current access.
- 3Run only the agreed and selected checks.
03Separate observation from interpretation
Open the recorded report from Projects. For each finding, examine evidence, confidence and unperformed checks. Then explain potential business impact without turning a hypothesis into a fact. A result without findings does not guarantee that no vulnerabilities exist. Keep technical evidence in its original form and share only necessary information with authorized recipients.
04Follow decisions and verification
Agree on an owner for each action and separately document the proposal, application and verification. Preparing a fix remains billed; a GitHub write requires human approval and never triggers automatic merging. Include limitations and partial results in your delivery. Your fees, contractual follow-up and any professional qualification remain independent of Hackaiz.
Frequently asked questions
Take the next step
Was this article helpful?