#132Case study3 min
Can the wrong person reach your data?
Check who can read or change information, not just who can open your app.
Hackaiz team · updated 21/11/2026

01A hidden page is not an access rule
A sign-in screen can look convincing while the service behind it still returns private information. Imagine an invoices page that disappears when you sign out, but whose data address still answers a request without a session. This is an example to investigate, not a report of an actual customer incident. The important question is whether the server checks permission before returning each protected resource.
Authentication establishes who a person is. Authorization decides what that person may do. A signed-in customer should not automatically be able to read another customer’s invoices. Before reviewing findings, write down your intended boundaries: which information is public, which belongs to one person, and which is reserved for an administrator. Those expectations help distinguish a deliberate public feature from an unwanted disclosure.
02Give Hackaiz the right source of evidence
On “Scan your platform”, choose the target you own or are authorized to assess. A website or API cannot be analyzed until domain ownership proof is validated. Use the DNS TXT record _hackaiz, the HTTPS file /.well-known/hackaiz-verification.txt, or the instruction for your project’s AI to create that file. Permission in a sentence does not replace this technical proof.
A deployed website and a GitHub repository answer different questions. The website can reveal responses available from the deployed service; repository access lets Hackaiz examine the implementation and exposed secrets in the code it receives. Do not interpret one as complete coverage of the other. In particular, seeing a login component in the repository does not establish that the production database rejects anonymous requests.
- 1Open “Scan your platform” and identify the exact environment containing the data you want to check.
- 2Complete ownership verification before launching a website or API analysis.
- 3Use “Connect GitHub” if you also need the repository examined; select the authorized repository rather than a similarly named demo.
03Read the evidence before deciding the impact
Hackaiz includes checks for routes answering without a session, anonymous Supabase queries, access rules and public storage. A finding about a public image folder does not have the same meaning as an anonymous response containing private messages. Read the reported resource and response evidence, then compare them with your intended access rules. Do not copy personal information or secrets into a public issue to explain the problem.
Customer-facing severity groups are Danger, To fix and To watch. Use them to organize review, then consider the specific information involved and whether an unauthorized person can read or change it. An exposed public Supabase key alone is not proof that private records are accessible: public client keys are meant to appear in client applications. The permissions available with that key are the important part of the investigation.
04Repair the boundary, not only the screen
If an unauthorized response is demonstrated, ask the developer to correct the server or database access rule that allowed it. Removing a button or hiding a table in the interface does not itself change the permission. Use synthetic records and separate test accounts to check your intended access matrix without exposing real customer data. These are review practices, not a claim that Hackaiz automatically tests every possible user role.
Where a GitHub fix is proposed, it is a draft pull request for human review and approval; Hackaiz never merges it automatically. After an approved change is deployed, run a relevant new analysis and check that the original resource is no longer exposed. Analysis and follow-up work consume credits. Checks you leave unticked are neither run nor billed; an omitted access check must not be treated as a successful one.
Frequently asked questions
Take the next step
Was this article helpful?