teach your team to find it themselves
We already do this on every engagement — the replay week of a red team, the working sessions in a retainer. These are those sessions unbundled and run on their own, by the same people, against labs built from real work.
- courses
- 6
- total material
- 20 days
- cohort size
- 8–16
three ways to run it
Most training happens as a private cohort, because a lab shaped like your architecture teaches more in two days than a generic one does in four.
private cohort
Your team only, on your estate or ours.
The lab is rebuilt to resemble your stack, and the case studies are chosen to match what you run. This is how most training happens, because generic examples teach generic lessons.
- Content tuned to your architecture
- On site or remote
- Runs from 6 people
open cohort
Scheduled dates in Abuja and London.
Mixed rooms with people from different organisations, which changes the conversation for the better — nobody is protecting a decision their colleague made.
- Published dates each quarter
- Individual seats
- Small by design
attached to an engagement
The teaching we already do, made explicit.
Added to a red team or a retainer, so your team learns against their own estate with findings that are theirs. The replay week of a red team is already this; this makes it longer and deliberate.
- Runs alongside the engagement
- Your systems, your findings
- Priced with the engagement
taught by people still doing the work
Every course is written and delivered by the principal named against it, who is running engagements the rest of the quarter. We employ no full-time trainers, which limits how often we can run a course and is the price of the material staying true.
the lab is a real system, redacted
Deliberately vulnerable applications teach people to find bugs that were left out for them. Our labs are rebuilt from real engagements, so the bugs sit where they actually occur — surrounded by code that is mostly fine, which is the hard part.
no certificate, on purpose
We issue a record of what was covered and nothing about competence. Two days in a room does not establish competence, and a certificate implying otherwise would be the first dishonest thing we sold you.
small rooms, or it is a talk
Cohorts cap between eight and sixteen depending on the course. Past that, the hands-on half stops working and you have paid for a conference session.
training is not a substitute for testing
A well-trained team finds more of its own problems, earlier and more cheaply than we ever could. It does not find the ones that come from knowing the system too well — the assumption everyone in the room shares, which is usually the one worth attacking.
So the honest version is that these run alongside the engagements, not instead of them. If you only have budget for one this year, buy the test — and ask us to teach during it.
questions
If yours is not here, ask it. A principal answers these, not a sales team.
No. We issue a record of attendance that says what was covered and nothing about competence, because two days in a room does not establish competence and a certificate implying otherwise would be dishonest. If you need a certification for a framework, buy one from a body that awards them.
tell us who you are trying to train
Team size, what they already do, and what you want them able to do afterwards. We will tell you which course fits — including when the answer is that a shorter one would do.