#139Case study3 min
Read a Hackaiz security report in 60 seconds
A quick reading order for scope, evidence and next actions, not a promise of scan completion time.
Hackaiz team · updated 21/11/2026

01Use the minute to orient yourself
The sixty-second framing is a reading guide, not a claim that Hackaiz produces a complete report within a minute. Start by opening your project from Projects and locating its latest finished analysis. The project page distinguishes a finished scan from a project with no completed analysis. An analysis still in progress, or interrupted before all intended checks finished, should not be presented as a final assessment of the application.
Identify the target and the date before interpreting any result. A repository analysis concerns the inspected code; a deployed website may represent a different version. Read the report as evidence about the stated target at that moment. If you are making a release decision, note which version is actually going to production and whether it is the version examined. This avoids mistaking an older, reassuring result for a review of the change you are shipping today.
02Find the problems that deserve attention first
Customer-facing severity groups are Danger, To fix and To watch. Use them to choose a reading order rather than treating every finding as equally urgent. Start with Danger, then inspect the proposed action and evidence for each item. A severity label is a way to prioritize a detected issue; it is not a certificate, an exploit demonstration for every environment or a guarantee that nothing important exists outside the inspected scope.
For a concrete reading exercise, consider a report item about a secret in a source file. Ask which file and location are referenced, why that value is considered sensitive and what the finding recommends changing. Do not copy an actual credential into a team message to make the report easier to discuss. Keep the finding reference and the explanation together so that the developer can assess the issue without spreading the sensitive value.
03Read evidence and missing coverage together
Findings include the available evidence and confidence information. Read these alongside the checks performed and the coverage available. A control that was not run is not a successful control. For example, checks needing a reachable website cannot establish a live result if the required link is missing. Likewise, a control family left unselected in Choose mode was not tested. Unticked checks are neither run nor billed.
For websites and APIs, domain ownership must be proved before analysis. The supported methods are the _hackaiz DNS TXT record, the HTTPS file /.well-known/hackaiz-verification.txt, or asking the project’s AI to create that file. A blocked ownership step is a prerequisite to resolve, not a clean security result. If the analysis is partial, record the missing coverage explicitly instead of summarizing the report as “everything passed.”
04Finish with one concrete next action
After the first pass, choose an action you can assign: examine a finding with its evidence, complete a missing prerequisite or request a proposed fix. On the Fixes page, the review includes Files concerned, What the change does, Validation performed and Known limitations. These details are more useful for a handover than a headline alone because they explain both the intended change and what still needs testing.
Approval does not mean automatic deployment. Supported code fixes are delivered as draft GitHub pull requests after human review and approval; Hackaiz never merges them automatically. Retest after the relevant change reaches the system being examined. Analysis and correction work use credits, and optional monitoring is reserved for connected systems. If you need a release decision, allow time beyond this quick reading pass for review, tests and unresolved coverage.
Frequently asked questions
Take the next step
Was this article helpful?