#098Guide3 min

Understand how Hackaiz relates to OWASP

Use OWASP references to interpret findings without treating a category label as a complete assessment.

Hackaiz team · updated 21/11/2026

Illustration: a professional files evidence folders.
Illustration: a professional files evidence folders. Illustrative photo, not a screenshot.

01Treat OWASP as a classification reference

OWASP references help place a technical finding in a recognized family of application risks. In Hackaiz, the reference accompanies an observation; it is not a badge proving that your application passed an entire standard. Start with what the finding actually says happened, the evidence it provides and the action it recommends. Only then use the reference to explain the wider type of weakness to a developer or reviewer.

The code supports references from several families, including web application, API and language-model security. Their identifiers retain edition information, such as A01:2021 or API1:2023. Preserve that identifier in your notes so that two similarly named categories from different editions are not silently treated as interchangeable. Do not describe a report as covering the latest edition of every OWASP publication.

02Understand what the mapping does and does not mean

The fallback mapping associates selected rule patterns with reference identifiers. For example, the rule pattern admin-client-unscoped-id maps to A01:2021 and API1:2023, alongside CWE-639. This is useful vocabulary for discussing an access-control observation: can an identifier select an object without a suitable ownership check? The mapping supplies context; it does not prove that every API authorization path was exercised.

Another mapping associates frontend-dep-cve with A06:2021 and A08:2021. A dependency finding can therefore inform a discussion about vulnerable components and software integrity, but one package observation is not a full review of your delivery chain. CWE is a separate weakness classification, not an additional OWASP pass result. When a rule has no supported fallback match, the mapping can return no references rather than inventing a category.

03Keep category references separate from examination coverage

Open the relevant result from Projects and inspect the technical pre-audit alignment panel when it is present. The states “Issue detected: see evidence”, “Partly examined” and “Not examined by this analysis” answer different questions from a category identifier. A reference says where a finding belongs; a control state explains what evidence is available for that point in this analysis. Neither is a promise that the whole category has been tested.

Use Download (JSON) to retain the control states and finding references for a technical review. In particular, preserve “Examined, nothing found” as written rather than replacing it with “OWASP compliant”. Declarations are marked as not proven, and some controls must be proven by a person. Hackaiz provides technical evidence, not certification or legal advice, and the alignment export deliberately avoids a compliance percentage.

04Use the reference to organize a practical review

For an AI-related finding, distinguish the family involved. Hackaiz maps prompt-injection rule patterns to LLM01 Prompt Injection, and tool-related patterns to LLM06 Excessive Agency. Those labels help a team ask whether untrusted instructions can influence a model or whether its tools have excessive authority. They do not establish that every prompt, tool response or future model behavior has been tested. Read the specific evidence before choosing a remedy.

In your own review notes, record the finding, its reference, the affected code or component and the question still requiring a human check. Apply the customer priorities Danger, To fix and To watch rather than assuming an OWASP category itself sets urgency. A requested supported code fix becomes a draft GitHub pull request for human review and approval, never an automatic merge. Follow changes with a relevant new analysis, which uses credits; unchecked checks do not run and are not billed.

Frequently asked questions

Was this article helpful?

Related articles