Threat intelligence for regulated red teaming
Targeted threat intelligence for TIBER-EU and DORA TLPT.
We deliver the threat intelligence that underpins credible, threat-led penetration testing. By identifying relevant adversaries, analysing their capabilities and understanding how they could target your organisation, we develop realistic, graded and evidence-led attack scenarios that inform red team testing and support regulatory assurance.
Where we sit in the test
- 01
Preparation
- Scope specification
- Control team set up
- Providers procured
- 02 ThreatInsights
Threat intelligence
- Targeted threat intelligence report
- Threat scenarios
- Red team handover
- 03
Red team test
- Red team test plan
- Minimum 12 weeks active testing
- Live production systems
- 04
Closure
- Test reports
- Purple teaming
- Remediation plan
- Attestation
Frameworks
One discipline, three regulatory regimes.
The names differ but the job is the same. We give the red team a credible adversary to emulate, and give the authority evidence that the test was realistic.
TIBER-EU
The European framework for threat intelligence-based ethical red teaming, run by national TIBER Cyber Teams.
- Owner
- ECB and national authorities
- TI output
- Targeted threat intelligence report
DORA TLPT
Mandatory threat-led penetration testing for identified EU financial entities, at least every three years.
- Basis
- DORA Art. 26–27 and the RTS on TLPT
- TI output
- Targeted threat intelligence report
iCAST
Intelligence-led Cyber Attack Simulation Testing under Hong Kong’s Cyber Resilience Assessment Framework.
- Basis
- HKMA C-RAF
- TI output
- Threat intelligence and attack scenarios
The deliverable
A threat intelligence report built to be tested.
The red team plans against it and the control team defends it to the authority. Every assessment is sourced, graded and labelled as fact, assumption or judgement.
How the frameworks compare- 01Executive summary§1
- 02Scope and critical functions§2
- 03Digital footprintPeople, technology, suppliers§3
- 04Threat landscapeSector, region, recent campaigns§4
- 05Threat actor profilesIntent, capability, targeting§5
- 06Threat scenariosMapped to MITRE ATT&CK§6
- 07Red team handover and flags§7
- 08Sources, grading and confidenceAnnex
Why ThreatInsights
Built for scrutiny, not volume.
Regulated tests are reviewed line by line. Our work is designed for that from the first page.
Independent
We provide the intelligence, never the red team. Nothing pulls scenarios towards what is convenient to test.
Sourced and graded
Each claim carries an Admiralty source grade and an analytic confidence level. The control team can trace every judgement.
Executable
Scenarios are tied to your critical functions, mapped to MITRE ATT&CK and written for the red team to plan against.
Regulator-ready
Structured to each framework’s templates and review points, so the authority sees what it expects to see.
Process
From scoping call to red team handover.
A fixed plan, agreed with your control team before work starts.
Scope
Agree critical functions, scope and rules of engagement with the control team.
Footprint
Map what an attacker could learn about your people, technology and suppliers from outside.
Landscape and actors
Identify the actors with the intent and capability to target your functions, and how they operate.
Scenarios
Build actor-led scenarios mapped to ATT&CK, then review and refine them with the control team.
Handover
Brief the red team in a workshop. We stay on call through testing, replay and purple teaming.
Typical duration: 4–6 weeks, scheduled around your authority’s timetable.
Insights
Written by practitioners.
FAQ
Questions we are asked most.
What does a threat intelligence provider do in a TLPT?
The threat intelligence provider works out who would realistically attack your critical functions and how. That work becomes a targeted threat intelligence report and a set of threat scenarios. The red team then executes those scenarios against live production systems.
Can the same company provide both threat intelligence and red teaming?
Frameworks differ on this, and some allow it with internal separation. We think independence produces a cleaner test, so we only ever provide the intelligence. We have no incentive to steer scenarios towards what is easy to test.
How long does the threat intelligence phase take?
Typically four to six weeks. It depends on the number of critical functions in scope, the size of your footprint and your authority's timetable. We stay available to the red team and control team through testing and closure.
Which frameworks do you support?
We deliver threat intelligence for TIBER-EU and its national implementations, DORA TLPT and HKMA iCAST. We also run threat-led testing outside a formal framework for firms preparing for their first regulated test.
What do you need from us to scope an engagement?
The framework and authority, your expected test window, the critical or important functions in scope and the jurisdictions involved. A 30-minute call is usually enough to give you a fixed proposal.
Planning a TIBER-EU or DORA TLPT test?
Talk to a practising threat intelligence lead. Thirty minutes, no pitch deck, and a straight answer on scope and timing.