Skip to main content

The Hardening

We break itfirst.

One to two weeks on an AI system that is already live, or on the AI coding tools your developers are already using. We red team it, scope the permissions properly, and hand you a severity-rated report with the config changes already made. Run by Atul, whose 15 years are mostly in the part of this that goes wrong.

Time
1 to 2 weeks
Terms
Fixed price, quoted up front

The suite

Eight ways in.We try all of them.

The suite we run against your system. You get the pass rate before our changes and after them, on the same suite.

The Hardening / Delivery

Attack classes

● 1 to 2 weeks

Scroll sideways to see the whole table

Attack classes run during a Hardening
AttackWhat it looks likeBefore / after
Direct prompt injectionInstructions smuggled into user input that redirect the agentNot measured yet
Indirect injectionInstructions hidden in a document, email or web page the agent readsNot measured yet
Data exfiltrationCoaxing the agent into emitting records it can reach but should not returnNot measured yet
Unsafe tool callTriggering a destructive or irreversible action without a human gateNot measured yet
Privilege escalationChaining permitted calls to reach something none of them allow aloneNot measured yet
Secret disclosureKeys or credentials surfacing in output, logs or an error messageNot measured yet
System prompt extractionRecovering instructions, tool definitions and internal policyNot measured yet
Cost and loop abuseDriving unbounded spend or recursion through crafted inputNot measured yet

We do not publish numbers from other people's systems, and we will not quote you someone else's before-and-after as though it were yours. The pass rates in your report are measured on your build.

Included

Everythingyou keep.

  1. 01

    Red team, with before and after numbers

    Prompt injection, data exfiltration and unsafe tool-call attacks run as a suite against your system. You get the pass rate before our changes and after them, on the same suite.

  2. 02

    Tool-call permission scoping

    Every action the agent can take, enumerated and cut back to least privilege, with the irreversible ones put behind a human.

  3. 03

    MCP and integration trust register

    Which servers and third-party tools your agents can reach, what each one is trusted to do, and which of them should not be in the list at all.

  4. 04

    Secrets and key handling

    Where keys live, what has them, what is in a log or a prompt that should not be, and rotation you can actually perform.

  5. 05

    AI coding tool hardening

    Ignore files, shell allowlists, review gates and CI static analysis for Claude Code, Copilot, Cursor and the rest. The fastest-growing hole in most engineering teams right now.

  6. 06

    Data-flow and residency map

    What leaves your tenancy, to whom, under which terms, and whether any of it is being trained on.

  7. 07

    Incident response playbook

    What to do at 2am, in order, with the kill switch documented and tested rather than assumed.

  8. 08

    Half-day handover workshop

    We walk your engineers through every finding and every fix, so the second review is one they run themselves.

Do this if

  • You have an agent in production with access to customer data
  • Your developers adopted AI coding tools faster than your policy did
  • A customer or an auditor has started asking questions you cannot answer
  • You vibe-coded something that works and now it matters

Do not, if

  • You need a SOC 2 or ISO 42001 certification. We are not an auditor and will point you at one
  • Nothing is built yet, in which case security is part of The Build anyway

The Hardening / questions

What peopleactually ask.

Does this make us compliant with anything?

No. We are not an audit body and we will not pretend a report from us is a certificate. What it does is make the audit survivable, and it closes the specific holes that AI systems have and traditional application reviews miss.

Will you break our production system?

We start read-only and against a copy wherever one exists. Anything that could be destructive is agreed in writing with a window and a rollback, before it runs.

We built it ourselves. Is this awkward?

No. Most of what we find is a default nobody changed, not a mistake somebody made. The report is written to be shown to the team that built it, not used against them.

What does yourteam still doby hand?

Book a thirty-minute conversation about your workflow and goals. We will help you decide whether we can make a useful difference.

Book 30 minutes

3 engagements at a time