#130Case study3 min
Discovering a vulnerability with Hackaiz
Follow an illustrative access-control finding from authorized analysis to a reviewed and verified response.
Hackaiz team · updated 21/11/2026

01Understand what a discovery would mean
This walkthrough uses an illustrative situation, not a customer story or a claim about a particular analysis. Imagine a project that stores private records and exposes an operation intended only for their owner. The security question is whether a different authenticated user could reach the same records. A functioning sign-in page does not establish that every operation checks ownership correctly.
Hackaiz findings should be read as evidence about the examined system. A plausible concern, an observed weakness and proof of a past intrusion are different things. If a finding suggests unauthorized access could occur, do not announce that an attacker has already used it. Keep the technical evidence and ask the system owner to inspect logs when investigating actual misuse. Avoid testing the idea against another person’s data or a system outside your authorization.
03Read the evidence before accepting the conclusion
Begin with “Executive summary”, then open the finding details. The customer-facing categories are Danger, To fix and To watch. Read the affected component, the supporting observation, why it matters and the proposed response together. In our illustrative situation, the useful question is not simply whether authentication exists, but where the application checks that the requesting user owns the record being requested.
Have a maintainer compare the finding with the actual implementation and intended permissions. A restriction may be enforced in another layer, or the submitted material may not show the whole path. Conversely, hiding an interface element does not enforce a server permission. Record what additional evidence resolves the question in your own investigation notes. Use controlled test accounts and non-sensitive data for authorized validation rather than trying to extract real customer records.
04Treat a proposed fix as the start of remediation
For eligible code fixes, Hackaiz can prepare a draft GitHub pull request, which is a proposed code change for human review. A human approves publication and reviews the proposal; it is never merged automatically. Check that the change enforces the intended boundary without breaking legitimate access. In this example, the owner should retain access while a different user should not gain it merely by changing a record identifier.
Your team decides when to test, merge and deploy. After deployment, run the relevant verification again and read its coverage, not just its headline. Keep a record of the original evidence, the reviewed change and the later result in your own delivery documentation. Further analysis and correction work uses credits. Optional monitoring is available only for eligible connected systems and does not block attacks or replace an incident-response process. Discovery becomes useful when a responsible person carries the evidence through to a verified outcome.
Frequently asked questions
Take the next step
Was this article helpful?