Penetration testing · Red team · Purple team
Test the defence,not only the defences.
An objective-led engagement that tests people, process and detection together. We agree what an attacker would want, try to reach it by the routes in scope, and then sit down with your defenders to go through what they saw.
CREST-certified testersObjective-ledMITRE ATT&CK mappedPurple-team debrief
A penetration test asks what is weak. A red team asks whether you would notice.
Red teaming suits organisations that have already tested their systems and fixed what was found. The engagement starts from an objective, such as reaching a particular set of data or gaining administrative control of the domain or the cloud tenant, and the team chooses its own route within the rules: a phishing email, an exposed service, a credential found in public sources. Only a small group on your side knows it is happening. Afterwards comes the part that makes it worth doing, a purple-team debrief in which attackers and defenders replay the engagement together and tune the detections that missed.
- Objective
- Agreed in advance: reach the data, gain domain or cloud admin, move from outside to inside
- Tests
- People, process and detection as well as technology
- Duration
- Longer than a penetration test, and set by the objective
- Price
- Quoted separately after a scoping call
- Ends with
- A purple-team debrief with your defenders
Coverage
What a red team engagement covers
Reconnaissance
What can be learned about your people, systems and suppliers from public sources before anything is touched.
Initial access
Phishing, exposed services and credentials found in public sources, within the agreed rules.
Movement and escalation
From the first foothold towards the objective, as quietly as a real intruder would try to be.
The objective
Proof that the agreed target was reached, without touching more data than is needed to show it.
A detection record
A timeline of what the team did and when, mapped to MITRE ATT&CK, to set beside what your monitoring saw.
Purple-team debrief
Attackers and defenders replaying the engagement together and tuning what missed.
Findings
When it is the right exercise, and when it is not
- _01You have tested and fixed the basicsPenetration tests have been run, their findings closed and retested.Ready
- _02You have a SOC and want to know what it seesYours or a provider's: a red team is the fairest examination it will get.Ready
- _03You have never had a penetration testStart there. A red team against untested systems reaches its objective quickly and teaches you less, at greater cost.Not yet
Questions
Questions about this test
How is a red team engagement priced?
Red team and scenario-based engagements are quoted separately after a call, because the days depend on the objective and on the routes in scope.
Who on our side needs to know?
A small group who can authorise the work and stop it if they need to. Everyone else should respond as they would to a real event, which is the point of the exercise.
What happens if you are detected?
Then your detection worked, and the engagement records what triggered it. We agree in advance whether to stop, to carry on from where we were, or to continue from an assumed foothold so that the later stages are still examined.
Does this satisfy CBEST, TIBER or DORA threat-led testing?
Those schemes set their own rules for who may deliver a test and how it is run. Tell us which one applies to you and we will say plainly whether what we offer meets it.
How does it relate to SOC365?
For SOC365 clients the debrief feeds straight into detections and watchlists. If another provider runs your SOC, the same record lets you ask them what they saw.
Start a conversation
Decide what you would least like an attacker to reach.
A scoping call agrees the objective and the rules, and whether a red team is the right exercise yet.