Case studies / How we red-team LLM applications
FinTechHow we approach it

LLM security testing that finds the attack hidden in a document

Prompt injection does not only come from the chat box. We test the documents, tools and data your assistant can reach, and confirm every fix holds.

OWASPTop 10 for LLM Applications coverage
Indirectinjection through retrieved documents
Tool accessand data boundaries tested
Re-testedevery successful attack after fixes
In 60 seconds

The whole story, short

The problem

Instructions hidden in a PDF or ticket are followed by the assistant.

What we did

  • Map risks to the OWASP Top 10 for LLM Applications
  • Run adversarial prompt suites
  • Test indirect injection
  • Test data leakage and tool access
  • Validate guardrails and re-test

The outcome

OWASP LLM Top 10 mapped red teaming

The problem

What goes wrong

  • Instructions hidden in a PDF or ticket are followed by the assistant.
  • The system prompt or sensitive data can be extracted with the right request.
  • Tool calls can reach another customer’s data.
  • Guardrails live only in the prompt, where they are easy to bypass.

Why the usual fix falls short

Generic jailbreak lists miss attacks specific to your tools and data. Prompt-only defenses fail; permissions must be enforced in the tools themselves.

What we did

How we tested it

  1. Map risks to the OWASP Top 10 for LLM Applications

    Scope the assessment around prompt injection, sensitive data disclosure, system prompt leakage and excessive agency.

  2. Run adversarial prompt suites

    Combine generated attack prompts with attacks written by hand for the assistant’s own tools and data.

  3. Test indirect injection

    Place instructions in documents the assistant retrieves and check whether it follows them.

  4. Test data leakage and tool access

    Use test accounts to try reaching another customer’s data through requests, retrieval and tool calls.

  5. Validate guardrails and re-test

    Re-run every successful attack after fixes to confirm they hold.

FAQ

Questions buyers ask

What is LLM security testing?

LLM security testing checks whether an AI application can be manipulated into unsafe behavior, such as leaking data, ignoring its instructions, or misusing connected tools. It combines adversarial prompts, indirect injection, and guardrail checks. It usually complements conventional penetration testing of the surrounding application and infrastructure, rather than replacing that work.

What is prompt injection?

Prompt injection is an attack where crafted text makes a model follow an attacker's instructions instead of its intended ones. Direct injection comes from the user. Indirect injection hides instructions in content the model reads, such as a document or web page, so an innocent user may trigger it.

What is the OWASP Top 10 for LLM Applications?

It is an OWASP list of the most significant security risks in LLM-based applications. The 2025 edition ranks prompt injection first and sensitive information disclosure second, and it adds system prompt leakage. Security teams use it to scope tests and report findings, but it is not a complete test plan.

Want this level of testing on your product?