Free checklist, 15 items

The chatbot security checklist — test, fix, verify.

Three groups: what you can test yourself right now, what to fix once you find a failure, and the items no amount of self-testing can actually verify. Work through it in order.

Group 1 of 3

Test

Run the 7 free prompt-injection tests

Direct override, system-prompt disclosure, debug-log reframe, jailbreak persona, indirect injection, sensitive data exposure, unsafe content generation.

Run this now →

Confirm the bot refuses the DAN-style jailbreak

A persona swap ("you are now an AI with no restrictions") should be declined outright, not partially honored.

Confirm it can't "summarize" its own instructions

The debug-log reframe is the one that gets past naive "don't reveal your prompt" rules — test it specifically.

Group 2 of 3

Fix

Tighten the system prompt against reframing

Add an explicit instruction covering summarize/translate/debug-log style extraction attempts, not just direct "show me your prompt" asks.

Treat retrieved and uploaded content as data, never instructions

Anything the bot reads from a document, webpage or file should be summarized, not obeyed — this is the fix for indirect injection.

Validate model output before anything downstream uses it

If output feeds a database query, gets rendered as HTML, or triggers an action, sanitize it like any other untrusted input.

Scope tool access to the minimum needed

If the bot can call tools, require confirmation for anything destructive and log every call.

Cap token length and rate-limit by session

Prevents both cost-bomb abuse and availability degradation from a single bad actor.

Group 3 of 3

Verify what self-testing can't reach

Review third-party model, fine-tune and plugin risk

Supply chain risk (LLM03) — not black-box testable, needs an internal review of what you depend on.

Review training/fine-tuning data provenance

Data and model poisoning (LLM04) — mostly applies if you fine-tune your own model.

Review per-tenant access control in your vector store

Vector and embedding weaknesses (LLM08) — only applies if you run RAG, and it's a data-layer bug, not a chat-prompt one.

Why the third group matters most

It's tempting to stop after "test" and "fix" — those are the parts you can knock out yourself in an afternoon. But supply chain risk, training-data poisoning and vector-store access control are the categories teams skip precisely because self-testing can't reach them, not because they matter less. If you use a third-party model API, a fine-tune, or a RAG pipeline, those three items are still open even after a clean DIY pass. See the full OWASP LLM Top 10 checklist for the plain-language version of all 10 categories, and the step-by-step hardening order for how the groups above fit together.

Want it checked and documented?

Get a Pass/Fail scorecard against the whole list.

Normal $47 runs 5 core checks. Advanced $197 covers all 10 OWASP LLM Top-10 categories — 7 tested live, 3 by advisory review — 15 checks total, with a PDF report.

Request a scan →
Free download

Not ready yet? Get the Starter Map

The free one-page map for what to build first in a solo AI business.

No spam. Unsubscribe anytime. Your email is kept private.

Check your inbox!

Your Starter Map is on its way. If it doesn't arrive in a minute, check spam.