SSQ.AISSQ.AI

Purple Teaming & Detection Validation

Attack and defence test detection together

Attack and defence work side by side: we check whether your detection catches real attack techniques, and fix it on the spot.

This is collaboration, not an assessment. With your monitoring, detection and response staff, looking at the same records at the same time, we reproduce attack techniques in a controlled way and see how detection, alerts and logs respond. Where something is missed, we adjust detection rules, alert thresholds and protections together, and check again.

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

We set out, technique by technique, what was detected, what we changed, and the gaps that remain.

Reviewed

Detection ATTACK Reproduce a technique DEFENCE Check detection TOGETHER Tune together RETEST Check again
Reproduce a technique, check detection, tune it together, and check again, for each technique in scope.

When it fits

  • Detection has been built or changed

    You want to know whether new detection rules, security tools or a new monitoring setup catch real attack techniques.

  • A red team assessment left gaps

    You want to fix what a red team assessment found was missed, together with your defence team, and check it again.

  • You need to show what you can detect

    You want to set out, technique by technique, what you detect and what you do not yet.

What we look at together

We lay the attack side and the defence side over the same events, and adjust from what was missed.

the same events, reviewed together ATTACK Attack team what was done DEFENCE Defence team what was seen missed events Adjust detection run again to confirm update rules Detected Partly detected Missed
Attack records and defence records laid over the same events; adjustment starts from what was missed.
  • Detection rules and alerts

    Whether an alert fires for each technique, and whether its threshold is right.

  • Logs and records

    Whether the records needed for detection and investigation are kept, with no gaps in what is collected.

  • Security tool settings

    Whether tools such as EDR, NDR and SIEM are set up as intended.

  • Alert quality

    Misses and false alarms, and places where too many alerts bury the ones that matter.

  • The first step of response

    What the person who receives an alert checks, and to whom they pass it.

How it runs

  1. Agree techniques and scope

    We agree the techniques to check, the target systems, who takes part and the safety conditions. Techniques can come from threat intelligence or from red team assessment results.

  2. Prepare together

    With the defence team we check logs, alerts and detection tools, and agree how things will be recorded.

  3. Reproduce and check

    The attack side reproduces a technique in a controlled way; the defence side checks detection, alerts and records on the spot.

  4. Tune and check again

    Where something is missed, we adjust detection rules, alert thresholds and protections together, and run the same technique again.

  5. Write it up

    Results by technique, what was changed, and the gaps and next steps that remain.

When it runs on live systems, the scope, methods and stop conditions are agreed first so that operations are not affected.

What you receive

Detection by technique

Detected, partly detected or missed, for each technique checked.

Rules and settings changed

What was changed during the work, and why.

Remaining gaps and priorities

What still cannot be detected, and what to address first.

What to check again

Techniques and criteria to check again after changes, so the next round starts from here.