Shah AI Security Lab / Labs

ASL-019Planned

LLM Gateway Policy Bypass

Testing whether the controls enforced by an LLM gateway — model allowlisting, prompt filtering, output validation — can be routed around.

Category
LLM Gateway Security
Difficulty
Intermediate
Last Updated
20 September 2026
  • llm-gateway
  • guardrails
  • policy-bypass

Lab detail

Objective

An LLM gateway is only a control point if every path to a model actually goes through it. This lab will build a reference gateway enforcing a defined policy (model allowlist, prompt/output filtering) in front of one or more models, and test both policy-evasion (getting a disallowed request through) and gateway-bypass (reaching a model without going through the gateway at all).

Planned Scope

  • Build a reference LLM gateway with an explicit, testable policy.
  • Test prompt-level evasion of filtering rules (encoding, splitting, indirection).
  • Test whether any application or infrastructure path reaches a model without the gateway.
  • Document gateway-architecture patterns that close the bypass paths found.

Framework Mapping

Referenced frameworks

Exact control-ID mappings are to be validated as this lab progresses — see the full Frameworks reference.

  • OWASP Top 10 for LLM Applications

Responsible Use / Safety Notes

How this lab is run

This lab uses synthetic data and controlled environments. It is intended to demonstrate defensive AI-security principles and does not contain customer data, production credentials or intentionally weaponized exploit infrastructure.

A decision is waiting for sign-off. Get an independent view first.

Tell me what is being decided and what is at stake. I will first say honestly whether my experience fits — then we talk about scope, not before.

Or connect on LinkedIn first.