AI red teaming for banks and regulated enterprises

The red team that never leaves your perimeter.

Borzone continuously tests your applications, application programming interfaces (APIs), internal network and AI agents the way a motivated adversary would, on open-weight security models that run inside your own network. Nothing leaves. Every step is scoped, approved and evidenced.

Early access · taking a small number of design partners

Zero outbound traffic in air-gapped mode

sealed in, Borzone makes no outbound connections

Every step scoped in software

rules of engagement enforced by the harness, not the model

Evidence built for DORA & RBI programmes

Digital Operational Resilience Act (DORA) · Reserve Bank of India (RBI)

Built for
  • Banks
  • Non-banking financial companies
  • Payments
  • Insurance
  • Healthcare
  • Critical infrastructure
[ Why now ]

Testing from first principles, not once a year.

Three things changed at once. Together they ask for a different kind of security testing than a periodic engagement can give.

01

Attackers already automate

A capable adversary probes continuously and chains small weaknesses into a real path. Most testing is still a once-a-year engagement, so the window between tests is where the risk lives.

02

Your data can't leave

The most sensitive systems and the models that reason over them can't be handed to a rented, hosted model. Testing that depends on sending your traffic to someone else's cloud is a non-starter in a regulated environment.

03

Regulators want evidence

The Digital Operational Resilience Act (DORA) in the European Union sets out threat-led penetration testing (TLPT), and the Reserve Bank of India (RBI) requires regular vulnerability assessment and penetration testing (VAPT). Borzone is built to produce the evidence these programmes ask for.

[ The console ]

One engagement, scoped and watched end to end.

The Borzone engagement console shows what is in scope, what the agents are testing, what they have found, and what is waiting for a person to approve.

Illustrative — fictional organisation and data
borzone / engagement / nw-example-bank
Northwind Example Bank
scope: staging.examplebank.internal
Running in staging
Attack path · outer zone → corelive
SeverityFindingStatus
Critical Outdated Transport Layer Security (TLS) configuration Open
High Prompt injection reaches an internal support agent Open
High Admin console reachable from the internal network Retest
Medium Missing rate limit on a login API Fixed
Low Secrets left in a build artefact Fixed
Approval needed

Next test step needs approval

scope: staging only

An agent wants to take the next step on a finding. It waits here until a person decides.

Evidence

Evidence pack ready

  • 12 findings, prioritised by severity
  • Replayable steps for each one
  • Fix guidance written for your team
[ How it works ]

Five steps, each one accountable.

  1. 01

    Scope

    Rules of engagement are agreed up front and enforced in software. What is in scope, what is off limits, and what needs a person's sign-off are set before anything runs.

  2. 02

    Discover

    Borzone maps what is actually exposed across your applications, interfaces, internal network and AI agents, so testing works from the real surface rather than a stale diagram.

  3. 03

    Test

    Agents look for weaknesses and connect the ones that matter into a real path. Any step that could change data stops and waits for a person to approve it.

  4. 04

    Prove

    Every finding comes with replayable evidence and fix guidance, so your team can confirm it and act, not take a report on trust.

  5. 05

    Retest

    When a fix ships, Borzone retests it and closes the loop, so you know the weakness is gone and stays gone.

outer zones secured · one path to the core

[ Coverage ]

One perimeter, tested as a whole.

Real incidents cross boundaries. Borzone tests across them instead of treating each layer on its own.

Web applications and APIs

The surfaces your customers and partners reach, tested for the weaknesses that let an outsider in or let one account reach another.

Internal network

What an adversary can reach once they are past the edge: flat segments, exposed consoles and paths that should not connect but do.

Cloud configuration

The settings that quietly widen the blast radius: over-broad roles, open storage and services reachable from further than intended.

AI applications and agents

The newest surface: assistants and agents that read untrusted input and can act. Borzone tests whether they can be steered past their intended bounds.

Source code

Reads the code behind the surface to find what black-box testing alone would miss, and to point a fix at the right line.

[ Deployment ]

It runs where your data already lives.

Borzone is self-hosted by design. You choose how tightly it is sealed in.

Inside your network

Run Borzone air-gapped, with zero outbound connections. Nothing about your environment leaves the perimeter it is testing.

Your private cloud

Prefer a cloud account you control? Deploy Borzone into your own private cloud, under your own identity and network rules.

Models you own

The security models are open-weight, fine-tuned on your environment, and they stay yours. No rented model sees your traffic.

The controls live in the harness, not the model — scope, approvals and logging are enforced by the software around the model, not left to the model to honour.

[ From Velofy ]

From Velofy, an applied AI and security lab.

Borzone is built on work Velofy already does in the open and in production.

Dexter

Velofy's multi-agent harness, with sandboxing and approval gates built in. It is proprietary and available by invitation.

Proprietary · by invitation

curl_reap

A Python client for the web with its own TLS 1.3 stack, so traffic is shaped and controlled from the socket up.

Open source · Python

Maestro Flash

An open-weight security model Velofy is building to run inside the customer network. It is in development.

In development

velofy.co →

[ Accountability ]

Power on a short leash.

A tool that probes your own systems has to be safe to run. These are design principles, not boasts.

Every agent action is logged

Designed so that every step an agent takes is recorded and attributable, with nothing happening off the record.

A kill switch

Designed so that a person can stop everything at once, immediately, without waiting for a step to finish.

No outbound traffic in air-gapped mode

Designed so that, sealed in, Borzone makes no outbound connections and nothing about your environment can leave.

Scope is enforced in software

Designed so that the rules of engagement are enforced by the harness, not left to the agent to respect.

Bring Borzone inside your perimeter.

We are taking on a small number of design partners in early access. A briefing is the place to start.

Book a briefing