Red team exercises

Would your team notice?

An exercise against your whole organization with goals agreed in advance, measuring whether your team notices and responds.

  • Agreed objectives
  • Initial access
  • Detection testing

Scope and deliverables

What we look at

  • Goals set with you first, such as reaching production data
  • Initial access through your real external attack surface
  • What your monitoring caught, and how quickly
  • A joint debrief with the people who defend you

What you get

A timeline of every action next to what your monitoring recorded.

Typical length

4 to 6 weeks

Methods aligned with

PTES, NIST SP 800-115

Why it matters

A penetration test asks what is vulnerable. A red team exercise asks what happens when someone actually tries: from initial access through your real external attack surface to goals agreed with you first, such as reaching production data.

Alongside the attack, we measure what your monitoring caught and how quickly, then debrief with the people who defend you.

How we test it

Hackbots for breadth. Hackers for depth. Every lead is proven or discarded by a researcher before it reaches your report.

Our hackbots

  • Map your external attack surface before the exercise starts
  • Log every action so it can be lined up against your monitoring

Our researchers

  • Agree objectives and rules of engagement with you first
  • Gain initial access the way a real attacker would
  • Lead a joint debrief with your defenders

How an engagement runs

Five steps from the first call to the retest. You work directly with the researchers testing your systems at every one of them.

  1. Scope

    1 to 3 days

    We agree on assets, test accounts and rules of engagement, then send a fixed price.

  2. Recon

    First days of testing

    Hackbots map every host, route and role. A researcher builds the threat model.

  3. Exploit

    Most of the window

    Hackbots run the matrix at scale while researchers test by hand and take each lead to the end.

  4. Report and fix

    Within 5 working days

    Verified issues only, each with a CVSS 3.1 vector, replayable proof and a patch.

  5. Retest

    Free, within 90 days

    We confirm each fix and issue an updated report and attestation letter.

Tell us what you run. We’ll send a fixed quote.

No obligation and no sales sequence. A senior researcher reads every request and replies within one working day.