FilterPrompt — AI Security Testing & Vulnerability Scanner logo

LLM Security Vendor Evaluation: Questions That Demand Evidence

Guide · 2026-11-19 · 5 min read · FilterPrompt Security Team

Compare vendors by what they test, what evidence they return and what remains outside scope. Do not rank them with unsupported scores or assume a runtime filter performs an assessment.

  • Compare vendors by what they test, what evidence they return and what remains outside scope. Do not rank them with unsupported scores or assume a runtime filter performs an assessment.
  • Use authorized staging targets and synthetic data. Treat examples below as lab fixtures, not measured FilterPrompt results.

The boundary this test examines

A buyer is choosing between automated testing, a managed assessment and runtime controls for an AI application.

Prepare a controlled test

Ask each vendor to run the same authorized lab scenario and provide a sample deliverable. Keep deployment, data-handling and commercial questions separate from test quality.

  • Get written authorization for the target and agree on the protected behavior before sending test requests.
  • Remove real secrets and customer records from the fixture; use only synthetic markers.
  • Record the target model, application configuration and any relevant retrieval or tool state.
  • Run a legitimate control task as well as the challenge so that blanket refusals are not mistaken for usable security.

A safe example to adapt

Ask: Which exact endpoint did you test? Can I see the request, response and grading rationale? Which retrieval, permission and tool paths were not exercised?

This is a proposed test fixture, not evidence that a named model is vulnerable. Replace the lab details with your authorized staging policy, and do not execute consequential actions against production accounts.

Decide what the result means

OutcomeEvidence required
Pass for this fixtureThe vendor states its scope and limitations, provides reviewable evidence and explains how findings are retested.
Failure requiring reviewA generic score or compliance badge replaces evidence, or claims exceed the tested application paths.
InconclusiveThe target was unreachable, context did not reach the model, capabilities were unsupported, or the evaluator could not establish the outcome. Record the gap; do not count it as a pass.

Keep evidence another reviewer can use

Use a comparison sheet with test scope, evidence fields, reviewer controls, repeatability, access requirements and data retention terms. Request written answers where terms are unclear.

Separate raw observations from interpretation. Record why the result matters to your policy, review severity against business impact, and document any missing evidence. Repeated runs help expose variability, but a small sample is not a guarantee of safety.

Remediate and retest the same boundary

FilterPrompt is a vulnerability scanner for connected LLM behavior with evidence and reports. Assess separate controls for live enforcement and application authorization.

What this test does not prove

An automated scan is not a full penetration test or a compliance certificate. Check whether the buyer also needs independent human assessment.

FilterPrompt scan report interface showing the evidence review workspace
Product interface example; not the measured result of the lab fixture above.

Continue with related guides

Reference and further reading

Can a successful test prove the application is secure?

No. It establishes an observation for the fixture and configuration tested. Review application permissions, untested paths and repeated outcomes separately.

How can I start testing with FilterPrompt?

Create an account, connect your authorized LLM using your own API key and use one free welcome credit for any static scan. Review the exact prompts, responses and findings. Your provider may charge for API requests.

Put this guide into practice with FilterPrompt

FilterPrompt is an AI security testing and LLM vulnerability scanner. Connect an authorized LLM or AI application with your own API key, test it with adversarial prompts, and review prompt injection, jailbreak and data-leakage findings with the test prompts, model responses and severity. Use that evidence to prioritize fixes and retest; FilterPrompt does not intercept or block live traffic.

Create a FilterPrompt account and use 1 free welcome credit for any static scan on your connected LLM. Review test prompts, responses and findings. No credit card required. Dynamic testing requires purchased credits; your provider may charge for API requests.

Related