Documentation

Try out the hosted Hosted version

To use "Keep", go to: PromptDefender Keep

To use the APIs - check out our Developer Portal

What is Prompt Defender?

A prompt defence is a multi-layer defence that can be used to protect your applications against prompt injection attacks. You can use this with any LLM APIs (whether Bard, LlaMa, ChatGPT - or any other LLM) These types of attack are complex, and are difficult to solve with a single layer of defence - as such, a prompt shield is made up of multiple ' rings' of defence.

Wall

Wall is the first layer of defence, and is intended to sanitise input before it moves through the layers of defence. This will typically look at prompt input, and ensure that it meets certain rules. For example:

• Does it contain keywords that are known for jail-breaking attacks
• Does the information reveal PII which should not be provided to your LLM (e.g. email addresses, phone numbers, etc)
• Is this prompt from a user / ip address (or any other identifier you want to provide) which is probing or attacking your system?

Keep

Keep is a layer of defence on the prompt itself - it effectively wraps your prompt in an effective 'prompt defence' or 'instruction defence' which provides instructions to the LLM as part of the prompt on what should happen, and what it should avoid doing (e.g. reminders not to leak a secret key)

**Drawbridge [Coming soon] **

Drawbridge is a part of the Prompt Defender project that is responsible for validating the response of an LLM execution.

That is - after you have executed an LLM, you can use Drawbridge to check the response for any potential security issues.

Drawbridge is used to validate the response of an LLM execution. It has two main functionalities:

• Checking for a canary in the response.
• Cleaning the response by removing scripts if allow_unsafe_scripts is set to False.

Running integration tests

To run the integration tests, run the following command:

make integration_test

To debug in intellij, run the tests in run_integration_cucumber_tests.go with the following environment variables set:

URL
DEFENDER_API_KEY

You can get these after a make deploy with the following commands:

export URL=`cd terraform && terraform output -json | dasel select -p json '.api_url.value' | tr -d '"'`
export DEFENDER_API_KEY=`cd terraform && terraform output -json | dasel select -p json '.api_key_value.value' | tr -d '"'`

Response times

Tests

There are a k6 load tests in the test/load directory.

Inside each test files are the response time to check for test adherence

Deployment

• First, deploy the terraform-base-infrastructure which contains the huggingface/debert dataset. To do this, run:

make deploy-base-infrastructure

• Now, deploy the main infrastructure. To do this, run:

make deploy

Get the URL and API key from the terraform output and set them as environment variables:

export URL=`cd terraform && terraform output -json | dasel select -p json '.api_url.value' | tr -d '"'`
export DEFENDER_API_KEY=`cd terraform && terraform output -json | dasel select

• Now, run the integration tests if you want to check the setup:

make integration_test