#033Technical1 min

Read the technical evidence of a vulnerability

Request, response, file, line: how evidence is built and why it stays untranslated.

Hackaiz team · updated 18/11/2026

Illustration: a team reads a security report and marks priorities.
Illustration: a team reads a security report and marks priorities. Illustrative photo, not a screenshot.

01What evidence is

Evidence is the technical element behind a finding: a captured server response, a file and line of code, a database rule, a missing header. It is kept in its original form, untranslated, so any developer can verify it.

Sensitive values such as passwords, cookies or keys are masked before storage.

02Kinds of evidence

The form depends on the source.

  1. 1Live observation: the read request sent and the structured response received from the proven host.
  2. 2Code: the file path, line and excerpt, on a specific repository version.
  3. 3Configuration: the rule or setting read, such as a table access rule.
  4. 4External component: the pattern found in the manifest or code examined in a sandbox.

03What does not count as evidence

Text displayed on a page does not prove a flaw on its own. A redirect is not attributed to the requested address. An error or incomplete response makes the result “inconclusive”, never “protected” or “vulnerable”.

04Verify it yourself

Open the cited file or rule, replay the described scenario in your head, then compare it with your intent. If in doubt, flag the finding: your feedback is recorded and can lower the rule’s confidence.

Tip: Copy the rule identifier as-is when talking to support: it points to the exact logic.

Frequently asked questions

Take the next step

Was this article helpful?

Related articles