SSQ.AISSQ.AI

Red Teaming
& Resilience Testing

Red teaming, and testing detection and response

We find out how your defences work under a realistic attack.

Against agreed objectives and scenarios, we attempt the attack and test how your organisation prevents, detects, reports and responds to it. We review the results with the teams involved and turn them into the improvements and re-checks that are needed.

How does the organisation prevent, detect and respond under a realistic attack?

We assess whether attack objectives were reached, together with the evidence of response.

Reviewed

ATTACK Attacker role Agreed objective RESPONSE Your response Prevent Detect Report Respond time to detect
As the attack moves on, we see when the organisation notices and how it responds.

Three ways to test

Choose by the question you want answered. Every service can be contracted on its own or combined with others.

Red Team Assessment

Objective-based red team exercise

Would the organisation notice and stop an attacker going after an agreed objective?

We act as a real attacker going for an agreed objective, and record and assess, stage by stage, when your organisation notices and how it stops and responds.

Starting point
An objective you want to protect, and the agreed conditions
The defence team
Announced, limited or unannounced; the response is observed as it happens
What you get
Attack paths and timeline, and an assessment of the response at each stage

Threat-Led Penetration Testing (TLPT)

Red team testing led by threat intelligence

If the attackers relevant to us came for real, how would the organisation respond?

We build the scenario from threat intelligence relevant to you, to see whether you are ready for the attacks you could realistically face.

Starting point
The threat actors and methods relevant to your organisation and industry
The defence team
Run under agreed controls and stop criteria; where a framework applies, its roles are followed
What you get
The threat basis for the scenarios, a record of detection and response, and improvements

Purple Teaming & Detection Validation

Attack and defence test detection together

Does our detection really catch the attacks we believe we are ready for?

Attack and defence work openly together, check technique by technique whether detection catches it, and fix what is missed on the spot.

Starting point
A list of techniques to check, chosen from threat intelligence or red team results
The defence team
Openly involved from the start, adjusting on the spot
What you get
Detection by technique, rules and settings changed, gaps that remain

When it fits

  • You don't know whether you'd notice a real attack

    You have tools and procedures, and need evidence that you would notice and stop an attack before it reaches its objective. A Red Team Assessment fits.

  • You want to know if you're ready for the threats aimed at your sector

    You want to test against the threat actors and methods relevant to your organisation and industry, or a supervisor or parent company has asked for testing under a set framework. TLPT fits.

  • You don't know whether your tools and monitoring catch real attacks

    Monitoring reports say ‘nothing unusual’, or new detection rules have gone in, and you want attack and defence to check together, technique by technique. Purple Teaming & Detection Validation fits.

Keeping it safe

For all three, these are settled with an authorised approver before we start.

  • Objective, scope and what is off limits

    The objective, the systems and people in scope, the methods used, and what we will not do.

  • Safety and stop criteria

    Anything that could affect operations happens only with an agreed immediate-stop procedure in place.

  • Who knows in advance

    Announced, limited or unannounced. Whichever you choose, an authorised approver is always aware and there is a contact line throughout. Purple teaming is open from the start.

  • Results reviewed together

    Afterwards the records are reviewed with the teams involved and turned into improvements and re-checks.

What you receive

Evidence on whether the objectives were reached, a record of prevention, detection and response, and the improvements to make next. Purple teaming leaves detection results by technique and the rules that were tuned.

Evidence on the objectives

Under which conditions the agreed objectives were reached, or where the attempt was stopped.

Record of the response

What was blocked, detected and reported at each stage, and how the organisation responded.

Improvements and follow-up checks

Improvements agreed with the teams involved, and the items to check again afterwards.

Resilience here means prevention, detection and response in agreed cyber-attack scenarios, not company-wide business continuity.

Related research: Offensive Engineering (EXPLOIT) — We research ways to analyse and verify vulnerabilities and their impact from an attacker's perspective.