AI Security & LLM Risk

Use AI with confidence, not with crossed fingers.

We test and secure copilots, RAG systems and AI agents against the ways they actually fail: prompt injection, data leaking between users and agents taking actions they should not. We build these systems ourselves, so we know where the weak points are and how to fix them without making the product useless.

The problem

Why GenAI creates new security risks.

01

Prompt injection is easy

A line of text hidden in an email, web page or document can make a model ignore its instructions and do something else.

02

Answers that leak data

A copilot connected to company documents can show one user what only another user is allowed to see.

03

Agents with too much access

An agent with broad API keys can send emails, change records or move money if it is tricked or simply wrong.

04

Rules arriving faster than controls

The EU AI Act, ISO 42001 and customer questionnaires now ask how AI risk is managed, and most teams have no clear answer.

What we deliver

Security for the AI you build and buy.

Our AI security work sits next to our GenAI practice, so the people testing your systems know how they are built.

01

LLM application red teaming

Hands-on testing of your copilots and agents for prompt injection, jailbreaks, data leakage and harmful output, mapped to the OWASP Top 10 for LLM applications.

  • Red teaming
  • Prompt injection
  • OWASP LLM Top 10
02

RAG access control and data protection

Retrieval that respects your existing permissions, sensitive data filtered before it reaches the model and logs that show who saw what.

  • RAG
  • Permissions
  • Data leakage
03

Agent and tool use controls

Least-privilege tool access for agents, approval steps for risky actions, rate limits and a full audit trail of every action taken.

  • Agents
  • Tool permissions
  • Approvals
04

Model and data supply chain

Checks on the models, datasets, plugins and libraries you depend on, including provenance, licences and known vulnerabilities.

  • Model provenance
  • Datasets
  • Dependencies
05

Guardrails and monitoring

Input and output filters, abuse detection and monitoring in production, tested on an evaluation set built from your real cases.

  • Guardrails
  • Monitoring
  • Evals
06

AI governance and risk alignment

An AI risk process aligned to the NIST AI RMF, EU AI Act obligations and ISO 42001, with an inventory of your AI systems and owners.

  • NIST AI RMF
  • EU AI Act
  • ISO 42001

How we deliver

From AI inventory to controls in production.

We test how your AI systems can be misused, then add controls that keep them useful.

Always included

  • A named senior lead who stays with you from scoping to retest
  • Every finding ranked by risk, with clear fix guidance and a retest once you have fixed it
  • Reports, configurations and runbooks documented and owned by you
  • A founder reviewing the work every week, and an NDA signed before we touch anything

Typical tools

  • OWASP Top 10 for LLM
  • NIST AI RMF
  • MITRE ATLAS
  • ISO 42001
  • EU AI Act
  • garak
  • PyRIT
  • NeMo Guardrails
01
Weeks 1 to 2

Inventory and threat model

We list the AI systems you run or buy and map what each can see and do.

  • Inventory of models, data sources and tools
  • Threat model for each priority system
  • Risk ranking by data and actions involved
02
Weeks 2 to 4

Red team and review

Hands-on testing of your highest-risk AI systems.

  • Prompt injection and jailbreak testing
  • Data leakage and access control checks
  • Review of agent permissions and tool calls
03
Weeks 4 to 8

Fix and add guardrails

Controls built with your engineers, measured against an evaluation set.

  • Permission-aware retrieval and data filtering
  • Guardrails and human approval for risky actions
  • Logging and tracing of prompts, outputs and actions
04
Ongoing

Govern and monitor

AI risk managed like any other risk, with monitoring in production.

  • Monitoring for abuse, leakage and drift
  • Regular red team retests as systems change
  • AI risk register and reporting for leadership

FAQ

Questions we hear a lot.

What is prompt injection and can it be fully prevented?
Prompt injection is when text the model reads, from a user or from a document, email or web page, makes it ignore its instructions. Today it cannot be fully prevented by filters alone. What works is limiting what the system can see and do, separating trusted instructions from untrusted content, requiring approval for risky actions and monitoring for misuse, so a successful injection does little harm.
How do you stop a copilot leaking data between users?
By making retrieval follow your existing permissions, so the system only fetches documents the current user is allowed to see. We also filter sensitive data before it reaches the model, test for leakage with real user roles and log what was retrieved for whom.
We use a third-party model provider. What is our responsibility?
The provider secures the model and its infrastructure. You are still responsible for what data you send, what the model can access through your systems, what actions it can take and how outputs are used. Most real risk sits in that application layer, which is where we focus.
How does this relate to the EU AI Act and ISO 42001?
The EU AI Act sets obligations based on how risky an AI use is, and ISO 42001 is a management system standard for AI. We help you build an inventory of AI systems, classify their risk, put controls and documentation in place and prepare for assessment. As with other standards, certification comes from an accredited body, not from us.
Can you test AI systems that we bought rather than built?
Yes, within the limits of the vendor's terms. We can test how the product behaves with your data and permissions, review its configuration and integrations, and assess what the vendor tells you about its own controls.
Do guardrails make the product worse?
Badly tuned ones do. We measure guardrails on an evaluation set built from your real use cases, so we can show how much risk they remove and how often they block legitimate requests, and tune them until the balance is right.

Talk to a founder about AI Security.

Tell us where you are. We will come back within one business day with a point of view, not a sales deck.