Background: Your firm has been engaged by Northgate Financial Group, a banking group headquartered in the UK with a regulated banking subsidiary in Australia and a smaller wealth management subsidiary in Singapore. The UK entity has been selected for CBEST. Separately, and coincidentally in the same year, the Australian subsidiary's regulators have indicated interest in the bank participating in a CORIE-aligned exercise, and the Singapore subsidiary - while not currently mandated for any specific named scheme - has asked whether an AASE-aligned voluntary exercise would be sensible given its size and risk profile.
Northgate's newly appointed Group Head of Cyber Resilience, who has significant experience with CBEST from a previous UK-only role but no prior exposure to CORIE or AASE, asks you: "Since we're already doing CBEST properly in the UK, can we just apply the exact same scope document, RoE template, and Control Group structure to the Australian and Singapore entities, just with the names changed? It would save a huge amount of time and I already know CBEST works well." Question: Explain how you would respond to this request, addressing what can legitimately be reused across the three engagements and what must be handled separately for each, with reference to the relevant frameworks and jurisdictions involved.

See The answer in Explanation part below.
Explanation:
Step 1 - Acknowledge the genuine, legitimate efficiency instinct while correcting the flawed assumption.
The Group Head's instinct to seek efficiency across a multi-jurisdictional group is reasonable and reflects good practice management thinking, but the specific proposal - reusing the exact CBEST scope, RoE, and governance structure with only the names changed - is not appropriate, because it assumes CBEST, CORIE, and AASE are interchangeable, when in fact, as covered in the syllabus, they are conceptually related but administered by different authorities, under different legal frameworks, with different specific procedural, documentation, and governance requirements.
Step 2 - Explain what must NOT be reused unchanged. The formal scope specification, authorisation/legal documentation, and specific governance terminology and process must each be developed to genuinely meet the requirements of the applicable local scheme and legal jurisdiction: CBEST (UK, Bank of England-owned, governed by UK law including the Computer Misuse Act and UK GDPR) for the UK entity; the CORIE- aligned framework (Australia, developed with Australian regulatory involvement, governed by Australian law) for the Australian subsidiary; and, for Singapore, since the wealth management subsidiary is not currently mandated but considering a voluntary AASE-aligned exercise, the relevant Monetary Authority of Singapore-associated expectations and Singapore law, governed as a voluntary but still rigorous exercise.
Applying a UK-templated document with only the entity name changed for the Australian or Singapore engagements would repeat exactly the "assume it's the same everywhere" mistake highlighted elsewhere in this syllabus, creating real legal and governance risk in each local jurisdiction.
Step 3 - Explain what CAN legitimately be shared or coordinated at group level. Consistent with the syllabus's discussion of building a strong core methodology adaptable across the "family" of related frameworks, your firm can legitimately reuse: the underlying core delivery methodology and quality standards (structured scoping process, threat-intelligence-led scenario design principles, reporting quality standards, professional conduct expectations); internal knowledge management and staff expertise built through CBEST experience, appropriately supplemented with genuine CORIE- and AASE-specific expertise for those engagements; and sensible group-level coordination - such as a group-level oversight function that receives appropriately summarised, high-level risk reporting across all three engagements to support board-level group risk oversight - provided this coordination does not blur or replace each entity's own distinct, locally- appropriate governance structure and formal authorisation.
Step 4 - Address governance structure specifically. Each entity needs its own properly constituted local governance body (a UK Control Group for the CBEST engagement, and an equivalent, appropriately named and locally appropriate governance structure for the Australian and Singapore engagements, reflecting each local scheme's own terminology and requirements) - reusing the "CBEST Control Group" label and structure wholesale for Australia and Singapore, as though it automatically satisfied their different local expectations, would not be appropriate, mirroring the syllabus's point about not assuming schemes are legally interchangeable.
Step 5 - Recommend a practical way forward. You should propose to the Group Head a practical plan: use the firm's proven core methodology and quality standards as the consistent foundation across all three engagements (genuine efficiency gain), while commissioning or applying genuine local expertise (including local legal input where needed, consistent with the legal considerations domain) to properly adapt scope, authorisation/RoE documentation, and governance structure for each jurisdiction's actual applicable scheme and law - explaining that this hybrid approach captures real, legitimate efficiency without the serious legal and governance risk of the fully "copy-paste" approach originally proposed.
Step 6 - Note the additional nuance for the voluntary Singapore engagement. For Singapore, since no scheme is currently mandated, you should also clarify with the Group Head that proceeding with a voluntary AASE-aligned exercise is a legitimate and sensible option (echoing the syllabus's point that intelligence-led testing can be conducted on a voluntary, best-practice basis even absent a specific mandate), but that
"voluntary" does not mean "low rigor" - the same careful, locally-appropriate scoping, legal, and governance discipline should apply as for the mandated UK and Australian engagements.
Conclusion: The three engagements share a valuable common methodological foundation that can and should be leveraged for efficiency, but the specific scope, authorisation/RoE documentation, and governance structure must each be properly and separately developed to reflect CBEST, the CORIE-aligned framework, and the Singapore context respectively, given their distinct legal bases, owning authorities, and jurisdictional requirements - the "just change the names" approach originally proposed should be clearly and constructively declined.
---

Background: You are the Test Manager (the independent quality assurance role) overseeing a TIBER-EU
/DORA TLPT engagement for Veltane Asset Management, an EU-domiciled entity designated as significant by its national competent authority. The Control Team Lead (CTL) is under considerable internal pressure:
the firm's CFO has publicly committed, in an earnings call, to "having our resilience testing fully wrapped up" before the next quarterly results announcement - a date that falls just 9 weeks after the Red Team testing phase is due to begin, even though TIBER-EU guidance calls for a minimum of 12 weeks of active Red Team testing.
The CTL approaches you, as Test Manager, and asks whether you would be willing to "just sign off that the
12-week guidance was substantially met" if the team compresses testing into 9 weeks but works longer hours each week to "cover the same amount of ground." Separately, you learn that the Red Team provider has privately told the CTL they are confident they can still achieve the agreed objectives in 9 weeks, though they acknowledge to you privately that a compressed timeline will require a noticeably faster, more front-loaded testing tempo than they would normally use.
Question: As the independent Test Manager, how should you respond to the CTL's request, and what considerations should inform your assessment of whether the 9-week compressed timeline is acceptable?

Explain the governance principles at stake.
See The answer in Explanation part below.
Explanation:
Step 1 - Recognise the core tension the scenario presents. This scenario tests understanding of the Test Manager's independence and the substantive (not merely formal) purpose of TIBER-EU's minimum testing duration guidance. The CFO's external commercial commitment is a genuine business pressure, but it is not a valid basis for retroactively certifying that a shortened engagement "substantially met" a minimum duration requirement that exists for a specific methodological reason: realistic, patient, low-and-slow adversary emulation that a compressed, front-loaded tempo cannot fully replicate, however many hours are worked.
Step 2 - Decline to pre-commit to a favourable sign-off. As independent Test Manager, you should not agree in advance to characterise a 9-week engagement as substantially meeting a 12-week guideline; doing so before the work has even happened would compromise your independence and pre-judge an assessment that must actually be based on how the engagement is genuinely delivered and what it actually achieves. Your role, as established in the syllabus, is to provide independent, credible quality assurance - agreeing to a favourable conclusion in advance, to accommodate commercial pressure, would fundamentally undermine that role's entire purpose and credibility.
Step 3 - Assess the underlying methodological substance, not just the headline duration. Working "longer hours" does not equate to more weeks of realistic, patient adversary emulation - genuine advanced threat actors typically do not operate in short, intense bursts; the extended timeframe exists specifically to test whether an organisation can detect low-and-slow activity that unfolds gradually over a period comparable to genuine sophisticated campaigns. A compressed, front-loaded tempo risks producing a fundamentally different (and less realistic) kind of test, regardless of the total hours logged, and this distinction should be explained clearly to the CTL and, if necessary, the national TIBER Cyber Team.
Step 4 - Escalate the timeline conflict rather than resolving it unilaterally. This is a significant issue that should be raised transparently with the Control Team (and, given its significance, likely the national TIBER Cyber Team, consistent with the syllabus principle that material deviations from framework guidance should be discussed with the overseeing authority rather than decided informally between the CTL and Test Manager). The commercial pressure driving the compressed timeline is a legitimate business reality, but the solution should be sought through proper channels - for example, exploring whether the CFO's public statement can be clarified or whether the quarterly announcement can reference the testing being "in progress with results to follow," rather than by quietly compromising the assessment's evidential basis.
Step 5 - Consider genuinely legitimate alternative solutions. Rather than simply refusing to engage constructively, you should help the Control Team explore options that preserve both the framework's integrity and, where reasonably possible, some accommodation of the business context - for example, an earlier start date if the Preparation phase can be safely and properly accelerated without compromising its own requirements, a clear, honest internal/external communication adjustment about timing, or, if a shortened engagement is ultimately what the entity chooses to proceed with despite your advice, ensuring this is a fully informed, properly escalated and documented decision by the Control Team and national authority - not a decision effectively made by the Test Manager pre-agreeing to a favourable characterisation.
Step 6 - Document your professional position clearly regardless of outcome. Whatever the Control Team and authority ultimately decide, you should ensure your own professional assessment and reasoning are clearly documented and communicated, so your position as an independent, evidence-based assessor is preserved and defensible, and so the actual attestation decision-maker (the authority, informed by your assessment) has an accurate, unvarnished picture on which to decide, rather than a conclusion shaped in advance by commercial pressure.
Conclusion: The Test Manager must decline to pre-commit to a favourable characterisation of a compressed timeline, explain clearly why duration compression risks the exercise's methodological validity regardless of hours worked, escalate the underlying conflict to the Control Team and national authority rather than resolving it informally, and preserve independent, honestly documented professional judgement throughout
- protecting the integrity of the eventual attestation decision.
---