Why TLPT scopes stall
A TLPT notification starts a regulatory clock, and the scope specification has to be approved by your management body inside it. Most delays come from treating scoping as an IT asset export rather than a map of what an adversary would target.
- Asset lists instead of function lineageScopes built backwards from a CMDB do not show how a critical or important function (DORA Article 3(22)) depends on systems, suppliers and people. Authorities expect the trace to run top-down.
- Weak exclusion rationaleWhat you leave out is scrutinised as hard as what you put in. Thin justifications, or gaps against your Register of Information, lead to pushback and lost weeks.
- Payment rails and insiders left untestedGeneric scopes stop at perimeter infrastructure. Payment messaging, cloud dependencies and coerced or collusive insider routes go unexamined.
The scoping pack
A fixed-price, four to six week sprint. Each module drops straight into your scope specification and business case.
| Module | What we produce with your control team | Why it matters |
|---|---|---|
| Critical function register and exclusions | Every critical or important function catalogued, scored for materiality, with a clear rationale for each inclusion and exclusion. | Gives your management body and authority a scope they can approve without a round of questions. |
| Function-to-system lineage map | A trace from each in-scope function to its production systems, ICT third-party providers (reconciled to your Register of Information), locations and privileged roles. | Closes the gaps in third-party dependencies and gives the intelligence phase real supply-chain and insider context. |
| Payment and fraud pathway overlay | High-value transaction flows, maker-checker controls and payment messaging gateways mapped beneath each function. | Lets scenarios test fraud and financial crime controls, not only SOC detection. |
| Preliminary flags | Concrete confidentiality, integrity, availability and authenticity objectives for each in-scope system. | The threat intelligence provider and red team know what success looks like from day one. |
You also receive the assembled scope specification document, a board briefing deck and a handover pack for your threat intelligence provider.
How we work
- Week 1: Alignment and secrecyAgree secure channels with your control team lead and take in your Register of Information, architecture and existing function documentation. No one outside the control team is told.
- Weeks 2–4: Function-to-flag workshopsWorking sessions with business owners, payment leads and risk stakeholders to build the lineage, the third-party map and the preliminary flags.
- Weeks 5–6: Scope specification and board packThe complete scope specification, a briefing for your management body and a clean handover to the threat intelligence phase.
Independence, by design. A threat-led test is only credible if no one involved has an interest in the outcome. We do not sell architecture, configuration or remediation work, so nothing we scope is something we built or will be paid to fix.
Scoping questions
What is a TLPT scope specification?
The document that fixes what a threat-led penetration test will cover: the critical or important functions in scope, the ICT systems, third parties and people behind them, any exclusions with their rationale, and the flags the red team must reach. Under DORA it follows the content set out in the RTS on TLPT, Delegated Regulation (EU) 2025/1190, and is agreed with the TLPT authority before testing starts.
Who is responsible for the scope?
The financial entity. The control team lead owns it and the management body signs it off. We work alongside the control team to build the evidence and the document. We do not take ownership of decisions that belong to you or your authority.
Can you scope the test and also provide the threat intelligence?
Yes, and the handover is seamless if you do. The pack is equally usable by any threat intelligence provider you appoint. What we never do is design or fix the controls being tested.
How long does a scoping sprint take?
Four to six weeks on a fixed price, depending on the number of functions in scope and how much of your Register of Information and architecture documentation already exists.
Does the work alert our SOC or blue team?
No. We work only through the control team on a strict need-to-know basis, using channels agreed in week one. Workshops are run with business and risk owners, never with defenders who will be tested.