Custom app development for the blue team during a TLPT
In a threat-led penetration test under DORA, the blue team doesn't know that testing is under way. That is by design: the defence has to respond as it would to a real attack. Only afterwards does the team find out what was going on, and it then has to show, for each attack step, what it noticed and when.
What is asked of you afterwards
The regulatory technical standard under DORA, Delegated Regulation (EU) 2025/1190, describes the blue team as the people who defend the systems and who are not aware of the TLPT. They carry out their normal work: the security operations centre, the helpdesk, incident management. The control team lead informs them only after the active red team testing phase has ended, and that phase lasts at least twelve weeks.
Then comes the report. Within four weeks of that end date, the testers deliver their red team test report, and no later than ten weeks after the same date the blue team delivers its own. Annex VI prescribes what it must contain: for each attack step, the detected attack actions with their log entries, an assessment of the testers' findings, the evidence gathered, a root cause analysis, the lessons learned and topics for purple teaming.
This report can't be put together after the fact. The detections took place weeks ago, spread across services and systems, and the question isn't only whether something was noticed but when, by whom and what happened next. What wasn't recorded at the time can't be recovered later. The process and the file around it are described on our page about software for the TLPT process.
How we build this
The app has to be in use before anyone knows a test is running. Something rolled out only after the test has been designated gives the test away and starts with no history.
Observations, triage and escalation are part of the security centre's normal work, and the app is no exception to that.
When a signal came in, when an analyst picked it up and when it was escalated. Those three moments carry the reconstruction.
Annex VI asks for the log entries for each detection. A reference to a system that has since been cleaned up is not evidence.
Afterwards, you lay your timeline alongside the testers' attack paths. We build that comparison rather than leaving it to a spreadsheet.
What the app actually does
The observation with its timestamp carries the whole. What else you record depends on how your detection is set up and who owns it.
Observation in the moment
What was seen, in which system and what made it stand out. Recorded during the shift, not from memory weeks later.
The timeline from signal to response
Receipt, pick-up, assessment, escalation and closure, with time and person. The blue team's report rests on that sequence.
Keeping the log entry with it
From your SIEM or detection platform, linked to the observation and kept with the case file. Annex VI asks for this in so many words.
Handover between shifts
A signal that comes up at night and is handled during the day keeps its history. Otherwise the response time you need to demonstrate is lost.
The analyst's judgement alongside it
Why something was dismissed as noise or escalated instead. In the replay, that judgement is more interesting than the outcome.
Shielding what is sensitive
The test managers can ask for a report without sensitive information. That only works if what is sensitive is already marked at the source.
Who we build for
Where detection sits differs per institution. Four situations.
An in-house security centre
Analysts on shift rosters, with existing tooling and procedures. Here the point is recording alongside those systems, not instead of them. See also software for the financial sector.
Detection at an external party
Your detection is outsourced and the provider reports in its own way. For Annex VI you need to get those observations into your own timeline, with its timestamps.
Groups sharing ICT systems
In a joint test, the indicator reaches several entities that use the same intragroup provider. Observations must then remain separable per entity.
Processes that must not stop
If the test is discovered, the control team must be able to contain the escalation. That is only possible if it is visible where a report stands.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
What you measure and what you call it differs per detection platform. The content of Annex VI is fixed, the route to it is not, so it should be configurable.
Why Appfront
A timestamp cannot be rebuilt
We record the moment something was noticed, not the moment someone remembers it. In the replay with the testers, the conversation is about that difference.
The report grows out of the shift
We build the recording so that Annex VI becomes an export of what is already there. Anyone who only starts collecting after the reveal ends up with a reconstruction.
The app doesn't give the test away
The blue team must not know a TLPT is running. We therefore build no test mode and show no marker in the app; the control team works in a separate section.
We don't test and we don't defend
You hire the red team separately and the defence is your job. We build the recording that lets you show afterwards what was noticed.
Security and privacy
Observations from your defence show what you do and don't see. That is as useful to an attacker as it is to you, and the RTS counts this as sensitive information: the test managers can ask for a report from which it is absent. We place that marking at the source, per observation, so that such a version doesn't become cut-and-paste work afterwards.
The reliability of the timeline is the whole point here. A timestamp that can be adjusted afterwards makes any comparison with the testers' attack paths worthless. We record observations immutably, with a timestamp and the person responsible, and show a correction alongside the original entry. Where that record runs is a separate consideration; for this sector we also build on a sovereign cloud. How we handle security ourselves is set out in our information security policy; reports from outside go through our coordinated vulnerability disclosure policy.
Frequently asked questions about the blue team in a TLPT
Yes, that is how the RTS has it. Information about the test stays with the control team, the management body, the testers, the threat intelligence provider and the authority. The blue team only hears about it after the active phase.
For each attack step in the red team test report, Annex VI asks for the detected attack actions and their log entries, plus an assessment of the testers' findings, the evidence gathered, a root cause analysis and topics for the purple teaming.
At least twelve weeks, according to the RTS, and beyond that proportionate to the scope and the complexity of the parties involved. The control team, the testers and the test managers agree when that phase ends.
A joint exercise between the testers and the blue team. No later than ten weeks after the end of the active phase, a replay of the offensive and defensive actions follows, with purple teaming on what each side saw. Since the update of TIBER-EU, this step is mandatory.
The RTS covers this: the control team is informed of every discovery and, where necessary, contains the escalation. It then proposes measures to the test managers that allow the test to continue and remain confidential. Your records must show where a report stopped. Staff recognition belongs on an awareness platform.
Because the observation arises on the shop floor of the service, not in a case file. A ticket records that something has been handled; Annex VI asks what was detected, when and by what. We build that layer alongside your existing systems.
That is about a product you have examined; this is about a regulated testing regime with a supervisor involved. For the former there is app security testing and the ICT security assessment; for DORA as a whole there is DORA compliance software.
That depends on the number of teams, where detection takes place and which integrations you want. The recording function is usually the first to become useful and starts building history straight away. We give a well-founded estimate after the discovery phase.
Can you demonstrate what you saw at the time?
Take an incident from last quarter and look up when the first signal came in and who picked it up. If you can't do that now, you won't be able to after a TLPT either. We build this as a standalone solution or as part of a broader app development project.