One goal, and whether you notice.
A red team picks an objective, such as reaching your payment system or your source code, and pursues it across every route: the internet, your people and your premises. The question is not only whether we get there, but whether your team sees us and responds.
- Price
- Set in your written proposal
- You receive
- The attack narrative step by step, mapped to MITRE ATT&CK, with what was detected, what was missed and what to improve.
Scope, timeline and price in writing before any work starts.
How an exercise runs. Controlled throughout.
- 01
Objectives
One or two goals agreed with a small control group on your side.
- 02
Campaign
Weeks of quiet work across external, phishing and, where agreed, physical routes.
- 03
Detection review
For each step, whether your tools alerted and your team responded.
- 04
Debrief
A joint session with your defenders that replays the attack and tunes detection.
Questions, answered.
01Red team or penetration test?
A penetration test finds as many weaknesses as possible within a scope. A red team tests whether your people and tools notice a real attack. Most companies need regular penetration tests first.
02Who knows the exercise is happening?
A small control group on your side, which keeps the exercise realistic and can stop it at any time.
Know where you stand before an attacker does.
Tell us what you want tested. We will come back with a scope, a timeline and a price.