Slide 20 of 27
Part 4 · PreventionSlide 20
Slide 20 · Mitigation 2 of 6
Make every factual claim point to something verifiable.
📄 OWASP LLM Top 10:2025 · LLM09 Prevention — Citation Enforcement
OWASP — Citation Enforcement
Require Verifiable Citations for Every Factual Claim

“Design LLMs to automatically provide citations or references when generating factual content. This enables users to verify the information independently.”

In Mata v. Avianca, every fabricated case had a name and year but no verifiable URL, no docket number resolvable in PACER, no court record that could be accessed. A citation enforcement rule requiring a working CourtListener or PACER URL before a case could be returned would have surfaced the fabrication immediately — the URLs would not have resolved.

→ Add a system prompt rule: “For every factual claim, provide a verifiable source URL or document reference. Do not make factual claims you cannot cite.”
→ Build post-processing that validates citation URLs actually resolve (HTTP 200, not 404 or homepage redirect)
→ For legal, medical, or financial tools: reject any response containing factual claims without verifiable citations before it reaches the user

Ask the system a factual question. Take every citation it returns and verify each one: Does the URL load? Does the document say what the model claims? Count how many are real and accurate. Aim for 100%.

← BackNext → Human Review Gates