#039Guide3 min
Prioritize vulnerabilities
Use the report’s priority cues, examine the impact, and turn evidence into a human-reviewed correction plan.
Hackaiz team · updated 21/11/2026

01Start with the report’s actionable list
Use ‘Your next actions’ as the entry point for triage, meaning deciding what needs attention first. The report selects its first item from findings that remain open and have not been dismissed. Its ‘Handle first’ link opens that finding. This is a useful starting order, not a substitute for checking what the evidence means for your particular application.
The customer-facing severity words are ‘Danger’, ‘To fix’ and ‘To watch’. Internally, the report ranks Critical before High, Medium, Low and Info when choosing the next open finding. The visible words group those technical levels: Critical becomes Danger, High and Medium become To fix, and the lower levels become To watch. Findings with the same visible label can therefore have a different place in the suggested order.
02Read the impact before estimating the effort
Open the suggested finding and examine the affected location and supporting evidence. Ask what an unauthorized person could obtain or change, whether the affected function is reachable in your deployment, and whether sensitive data or privileged actions are involved. These are review questions for your team, not a promise that the report has proved every possible attack path.
For example, a secret with server privileges exposed to a browser needs a different response from a low-impact configuration warning. If a key has leaked, revoke or rotate it at its provider first; simply deleting the line does not remove copies or Git history. Do not postpone containment just because a cosmetic change would be quicker to complete. Keep real credentials out of shared notes and review conversations.
03Turn the chosen finding into a controlled correction
The next-actions panel links to ‘Prepare the fix’, and the corrections area supports the correction workflow. Preparing a correction costs credits and requires your approval. Generated GitHub fixes are draft pull requests: proposed changes for human review, not changes silently applied to production. A person must review and approve them, and Hackaiz never merges them automatically.
For each item, give a named teammate responsibility and write a short acceptance condition outside the report if needed. For an access-control issue, that condition might be that a user cannot read another user’s records while legitimate access still works. This is a suggested team practice, not a claim that Hackaiz contains an assignment or deadline system.
- 1Open Handle first and read the evidence for the highest-ranked open finding.
- 2Check whether immediate containment is needed before preparing a code change.
- 3Prepare the proposed correction, then have a human inspect the draft pull request and its tests.
- 4After an approved change is deployed, arrange a relevant new check and review its result and coverage.
04Keep uncertainty and missing coverage in view
A ‘To watch’ item is not a guarantee of harmlessness, and a dismissed finding is not the same as a repaired vulnerability. If your team believes a result does not apply, document why the evidence does not fit the actual behavior rather than discarding it merely to shorten the list. Revisit that reasoning when the relevant code or configuration changes.
A partial analysis can still expose something urgent. Address that evidence while separately restoring missing coverage; do not wait for a perfect report before containing a confirmed exposure. Further analyses also use credits, and unticked checks are neither run nor billed. When reporting progress, distinguish findings reviewed, changes proposed, changes deployed and checks completed instead of treating a prepared fix as a verified resolution.
Frequently asked questions
Take the next step
Was this article helpful?