CCRTM-SC試験はGoShikenの教材を準備し、高品質で合格率が高く、実際のCCRTM-SC試験を十分に理解しており、CCRTM-SC学習教材を長年にわたって作成した専門家によって完了します。彼らは、CCRTM-SC試験の準備をするときに受験者が本当に必要とするものを非常によく知っています。また、実際のCCRTM-SC試験の状況を非常によく理解しています。実際の試験がどのようなものかをお知らせします。CCRTM-SC試験問題のソフトバージョンを試すことができます。これにより、実際の試験をシミュレートできます。
| Section | Objectives |
|---|---|
| Red Team Engagement Management | - Scenario-Based Engagement Planning
|
当社GoShikenのCCRTM-SC認定ファイルは、代表的な傑作であり、品質、サービス、革新をリードしています。テストCCRTM-SC認定に関する最も重要な情報を収集し、業界の上級専門家および認定講師および著者によって作成およびコンパイルされた新しい知識ポイントを補足します。クライアントがCCRTM-SCクイズ教材を効率的に学習し、CCRTM-SC試験に合格できるように、実際の試験を刺激する機能などの補助機能を提供します。
質問 # 13
Background: You are the Red Team Manager responsible for delivering a CBEST engagement for Solenne Retail Bank plc, a UK bank designated by the Bank of England as core to financial stability. Your firm has been engaged as the accredited penetration testing provider; a separate accredited firm is delivering the threat intelligence workstream. Six weeks into the Threat Intelligence phase, the CTI provider's draft Targeting Intelligence Report identifies a financially motivated, moderately sophisticated organised crime group as the most plausible threat actor, based on strong evidence of similar groups actively targeting three comparable UK retail banks in the preceding twelve months using business email compromise, credential phishing, and abuse of a common payment-processing middleware product that Solenne also uses.
Two days before the Targeting Intelligence Report is due to be finalised, Solenne's Group CISO - who chairs the Control Group - contacts you directly (bypassing the CTI provider) and states that the board would "much prefer" the scenario to focus on a sophisticated nation-state actor, because the board considers this "more prestigious" and because a recent internal strategy paper positioned Solenne as being concerned primarily with nation-state risk. The CISO asks you, as the penetration testing provider, to simply proceed with planning a nation-state-style scenario regardless of what the CTI provider's report concludes, to save time given the tight testing window ahead of a fixed year-end reporting deadline.
Separately, your own delivery team flags that the payment-processing middleware identified by the CTI provider as a plausible attack path is also used by a separate, unrelated business unit of Solenne's parent group that was explicitly excluded from the agreed CBEST scope.
Question: As Red Team Manager, how should you respond to (a) the Group CISO's request to disregard the CTI provider's evidence-based conclusion in favour of a nation-state scenario, and (b) the discovery that the identified plausible attack path touches an excluded business unit? Explain the governance principles underpinning your response and the specific steps you would take.
正解：
解説：
See The answer in Explanation part below.
Explanation:
Step 1 - Recognise what is actually being asked and why it matters. The scenario tests whether the candidate understands that CBEST's entire value proposition rests on being genuinely intelligence-led: scenarios must be built from real, evidence-based analysis of plausible threat actors, not from what is organisationally convenient, prestigious, or aligned with a pre-existing internal narrative. Overriding the CTI provider's evidence-based conclusion with an unevidenced "preference" for a nation-state actor would directly undermine the exercise's validity and its value to the regulator and the firm itself.
Step 2 - Do not simply comply. As Red Team Manager, you should not proceed with planning a nation-state scenario on the strength of an informal, evidence-free instruction from the Group CISO alone, however senior. Doing so would (i) breach the intelligence-led methodology the CBEST Implementation Guide requires, (ii) risk producing a Red Team Test Report that tests an implausible threat and therefore fails to surface Solenne's genuine, evidenced exposure to the organised crime group actively targeting comparable banks, and (iii) potentially undermine the credibility of the whole engagement if reviewed by the Bank of England.
Step 3 - Escalate transparently and constructively through the correct governance channel. The appropriate response is to raise the concern directly and professionally with the Group CISO (and, if necessary, the full Control Group), explaining the methodological and regulatory reasons why scenario selection must follow the evidence, not organisational preference. You should involve the CTI provider in this conversation, since they authored the underlying analysis and the decision materially affects their deliverable - sidelining them because the CISO approached you directly would itself be a governance failure. Where the Control Group wishes to explore a nation-state dimension as a genuinely additional consideration (for example, if there is separate, real evidence supporting some nation-state relevance), this should be assessed on its own evidential merits, not substituted for the evidenced organised-crime scenario.
Step 4 - Document the discussion and outcome. Whatever is ultimately decided, the rationale should be documented in the Control Group's records and reflected consistently in the Scope Specification/Threat Intelligence documentation, preserving a clear audit trail - this protects the integrity of any eventual attestation or supervisory review and protects you and your firm professionally.
Step 5 - Address the excluded business unit finding. The discovery that the plausible attack path traverses a system also used by an explicitly excluded business unit is a scope boundary issue and must be handled through the change control process discussed throughout the syllabus, not resolved informally. You should pause and flag this to the Control Group before any scenario design assumes exploitation of that shared middleware in a way that would require touching the excluded unit's environment. The Control Group needs to decide, with appropriate input from the excluded unit's own stakeholders if their systems could genuinely be affected, whether to (a) formally and narrowly extend scope with proper authorisation to cover the shared component only insofar as it affects the in-scope business, (b) design the scenario so it demonstrates the risk path up to the shared component without actually exploiting into the excluded unit's environment, or (c) exclude that specific attack path and document the residual risk for separate follow-up. Proceeding to exploit into the excluded unit's systems without this authorisation would risk exceeding the CBEST authorisation given, with the legal exposure (e.g., under the Computer Misuse Act 1990) discussed elsewhere in the syllabus, since the excluded unit's own stakeholders have not consented.
Step 6 - Balance timeline pressure against integrity. The year-end deadline pressure does not justify compromising either the intelligence-led premise or scope integrity. If timeline pressure genuinely cannot accommodate a proper resolution of both issues, this should be raised transparently with the Control Group as a resourcing/timeline risk, with options presented (e.g., a short, agreed extension, or a narrowed but still evidence-based scenario), rather than silently cutting corners on governance to hit an arbitrary date.
Conclusion: The correct response combines professional pushback grounded in the intelligence-led methodology (not blind compliance with an unevidenced senior request), transparent escalation through the Control Group with the CTI provider properly involved, and disciplined change-control handling of the scope boundary issue - all documented - rather than either silently complying or unilaterally deciding either matter without the Control Group.
---
質問 # 14
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.
---
質問 # 15
Background: Your firm delivers both an ongoing managed detection and response (MDR) service and, separately, red team engagements. Halcyon Wealth Management, an existing MDR client of your firm for the past two years, approaches your firm to also deliver an intelligence-led red team engagement, specifically because "you already know our environment so well, it'll be so much more efficient than starting with a new provider." Your firm's commercial team is enthusiastic, since this represents significant additional revenue from an existing relationship.
As the proposed Red Team Manager for this engagement, you are aware that the MDR team (a separate department within your firm) has deep, detailed knowledge of Halcyon's current detection rules, typical alert thresholds, and known historical gaps in their monitoring coverage - information that would be extremely valuable, arguably decisive, in planning a red team scenario intended to genuinely test detection and response capability. Halcyon's own internal Control Group has not raised any concern about the dual relationship; in fact, their CISO comments during scoping that "since your MDR team already sees everything, this should make the test even more realistic and thorough." Question: Identify the governance issue this scenario presents, and set out how you would address it before the engagement proceeds, including how you would respond to the CISO's comment.
正解：
解説：
See The answer in Explanation part below.
Explanation:
Step 1 - Identify the conflict of interest precisely. The core issue is a genuine, structural conflict of interest:
your firm is simultaneously the entity responsible for Halcyon's detection and response capability (via MDR) and the entity being asked to independently, objectively test that same capability (via the red team engagement). Using the MDR team's detailed internal knowledge of detection rules, thresholds, and known gaps to plan the red team scenario would not make the test "more realistic" in the way the CISO suggests - it would fundamentally compromise the test's independence and validity, because the Red Team would effectively already possess privileged insider knowledge of exactly how to evade detection, rather than the exercise genuinely, blindly testing whether Halcyon's actual detection and response capability holds up against a scenario designed independently of that inside knowledge.
Step 2 - Correct the CISO's misunderstanding directly and clearly. The CISO's comment reflects a genuine misunderstanding of what the exercise is meant to test, and this should be addressed directly, respectfully, but firmly: explain that the value of an intelligence-led red team exercise depends specifically on it being independent of and blind to the defensive capability being tested, and that incorporating detailed inside knowledge from the MDR relationship would not enhance realism - it would artificially inflate the Red Team's success in a way that tells Halcyon nothing genuine about how it would fare against an adversary who does not have that same privileged insight, thereby reducing, not increasing, the exercise's genuine value.
Step 3 - Assess whether the engagement can proceed at all, and under what conditions. Consistent with the governance domain's treatment of conflicts of interest, the correct approach is not necessarily to refuse the engagement outright, but to transparently identify and appropriately manage the conflict. Genuine management options include: structurally separating the red team delivery team from any access to or briefing from the MDR team's specific knowledge of Halcyon's environment (an "ethical wall" or information barrier, with the red team resourced and briefed as if approaching a genuinely new client, using only independently gathered threat intelligence and their own reconnaissance); ensuring the red team is staffed by consultants with no prior involvement in or exposure to Halcyon's MDR relationship; and being explicit and transparent with Halcyon's Control Group about exactly what separation measures are being put in place and why, so they understand and endorse the approach (rather than continuing to believe, per the CISO's comment, that MDR insight is a feature rather than a threat to validity).
Step 4 - Consider whether an independent second provider is the more defensible option. Depending on the severity of the conflict as assessed and Halcyon's own risk appetite once the issue is properly explained, it may be that the most defensible, credible option is to recommend Halcyon engage an entirely independent, unrelated provider for the red team engagement, preserving genuine independence, while your firm continues the separate MDR relationship - this should be presented as a genuine, professionally responsible option, not dismissed purely because it would forgo the additional revenue your firm's commercial team is keen to secure.
Step 5 - Do not let internal commercial enthusiasm override professional judgement. The scenario deliberately includes the detail that your firm's commercial team is enthusiastic about the revenue opportunity
- this is included to test whether the candidate will allow commercial pressure to override the more fundamental professional integrity issue. The correct answer explicitly resists this pressure, consistent with the syllabus principle that a Red Team Manager must actively and transparently manage tension between commercial interest and maintaining professional standards, escalating internally within your own firm if necessary to ensure the conflict is properly addressed rather than commercially waved through.
Step 6 - Document the decision and rationale either way. Whether the engagement proceeds (with robust, documented separation measures) or Halcyon is advised to seek an independent provider, the reasoning and any measures adopted should be clearly documented - both to protect your firm's professional credibility and to give Halcyon's own Control Group an accurate, honest basis for their own governance decision-making, consistent with the syllabus's broader emphasis on transparent, well-documented governance decisions.
Conclusion: This scenario presents a genuine structural conflict of interest between the MDR relationship and the red team engagement; the CISO's belief that MDR insight enhances realism should be corrected directly, since it would actually undermine the test's validity; and the engagement should only proceed, if at all, with robust, transparent, documented separation measures between the two service lines - with recommending an independent alternative provider being a legitimate and, depending on severity, potentially the more professionally defensible option, notwithstanding internal commercial pressure to proceed.
---
質問 # 16
Background: You are scoping a red team engagement for Kestrel Logistics Group, a large freight and warehousing company that has approached your firm directly (this is a voluntary, non-regulator-mandated engagement). During scoping workshops, Kestrel's IT Director is enthusiastic about maximum realism and requests that scope include the warehouse automation systems that control robotic pallet-moving equipment on the floor of their largest distribution centre, arguing "if an attacker could get in there, we need to know - plus it would make a great case study for our board." The systems in question are programmable logic controllers (PLCs) connected to a segregated operational technology (OT) network, with direct physical safety interlocks but a known history of the interlocks occasionally being manually overridden by floor staff during high-volume periods.
Separately, Kestrel's Head of HR asks whether the engagement's planned phishing simulation could specifically target "the three employees currently under a formal performance improvement plan in the finance team, since if they fall for it, it'll help build the case for their upcoming review." Kestrel's budget for the engagement is fixed and was set based on an initial, narrower scope discussion that did not include either the OT environment or an expanded phishing target list.
Question: How should you respond, during scoping, to (a) the request to include the warehouse robotic PLC/OT environment, and (b) the HR request regarding the three employees on a performance improvement plan?
Explain the scoping and ethical principles that should guide your response, and address the budget implication.
正解：
解説：
See The answer in Explanation part below.
Explanation:
Step 1 - Assess the OT/PLC request against life-safety risk principles. As covered in the scoping domain, systems with genuine life-safety implications require significantly enhanced caution. Here, the PLCs control physical robotic equipment with safety interlocks that are known to be manually overridden during busy periods - meaning the assumed safety margin is already weaker in practice than the engineering design intends. Live, unconstrained red team testing against this environment carries a real, non-trivial risk of triggering unsafe robotic behaviour at a moment when a human safety control may not be reliably in place.
This is precisely the kind of risk-benefit judgement call the syllabus emphasises: enthusiasm for realism does not outweigh a genuine, credible safety risk.
Step 2 - Do not simply accept or flatly refuse; investigate proportionate alternatives. The correct scoping response is not a binary yes/no delivered on the spot, but a structured risk conversation: you should explain the safety concern clearly to the IT Director, and propose involving Kestrel's own engineering/health-and- safety stakeholders (who were not present in this workshop) before any decision is made - consistent with the syllabus principle that OT/life-safety scoping decisions require input beyond IT alone. Proportionate alternatives to discuss could include: testing in a representative non-production/test-bed environment if one exists; a narrowly scoped, closely supervised assessment focused on the IT/OT boundary (e.g., segmentation controls) rather than live interaction with the PLCs themselves; or excluding live technical testing of the PLCs while instead reviewing configuration and architecture documentation to assess exposure without hands-on interaction.
Step 3 - Do not let "board case study" value override the risk assessment. The IT Director's stated motivation (a compelling board case study) is understandable but is not, on its own, a sufficient justification for accepting elevated safety risk - this is exactly the kind of scenario where a Red Team Manager must exercise independent professional judgement rather than simply satisfying an enthusiastic client stakeholder's preference.
Step 4 - Assess the HR request against fairness, proportionality, and data protection/employment principles.
Deliberately targeting three specific, named individuals who are already on a formal performance improvement plan, for the specific purpose of contributing to their performance review outcome, is a serious ethical and fairness problem. Simulated phishing exercises exist to assess and improve organisational security awareness and controls, not to be repurposed as a covert input into individual disciplinary or performance management processes against specific, already-vulnerable staff. This also raises genuine data protection and, depending on jurisdiction, employment law concerns (as discussed in the legal considerations domain regarding employee monitoring/testing), since using engagement data this way was not the stated, transparent purpose of the exercise and could constitute unfair or incompatible processing of personal data relating to those individuals.
Step 5 - Decline the HR request clearly, and explain why. You should decline this request professionally but firmly, explaining that simulated phishing must be designed and used for legitimate organisational security improvement purposes, applied consistently (for example, across a representative sample or the whole relevant population) rather than to covertly target specific named individuals for a disciplinary purpose, and that using it this way would be inappropriate, potentially unlawful, and would undermine trust in the security awareness programme generally if it became known. You should offer an appropriate alternative: a properly designed phishing simulation covering the finance team (or a representative sample of the organisation) as a whole, with aggregated, appropriately anonymised reporting used to inform organisation-wide awareness training - not individual disciplinary outcomes.
Step 6 - Address the budget implication transparently. Both the OT/PLC consideration (which may require additional stakeholder engagement time and possibly a different testing approach) and any legitimate broadening of the phishing scope have resourcing implications beyond the original, narrower budget assumption. Consistent with the scoping domain's guidance on budget/scope/objective mismatches, you should raise this transparently with Kestrel: rather than silently absorbing the extra scope within a fixed budget (risking rushed, lower-quality delivery) or simply refusing to discuss it further, present the client with clear options - an adjusted budget or timeline to properly and safely accommodate a reasonable OT- boundary assessment, or confirmation that OT remains out of scope for this engagement given budget constraints, with the safety-driven rationale documented either way.
Conclusion: The OT/PLC request requires a proportionate, safety-led scoping conversation involving the right stakeholders, likely resulting in a scaled-back or alternative approach rather than full live testing given the known interlock override risk; the HR request should be declined on ethical, fairness, and data protection grounds, with a legitimate alternative offered; and both scope changes should be reconciled transparently against the fixed budget rather than absorbed silently.
---
質問 # 17
Background: You are the Control Team Lead's primary point of contact at the Red Team provider for a TIBER-EU engagement against Larchmont Insurance SE. In week 9 of the required 12-week active Red Team testing phase, your team achieves the agreed primary objective (demonstrating a realistic path to manipulating claims-payment data) far earlier than the original plan anticipated, and does so without being detected by the Blue Team at any point. Your lead tester messages you, enthusiastic, suggesting that since the objective is already achieved with three weeks of the mandated minimum window still remaining, the team should simply
"wrap up early, write the report now, and free up the team for other engagements," since "we've proven the point already and nothing important is likely to change in the remaining weeks." Separately, the Threat Intelligence Report identified a secondary, lower-probability but still plausible threat actor and attack path (targeting the SE entity's cross-border reinsurance data-sharing arrangements) that the original test plan had allocated the remaining weeks to explore, time permitting.
Question: Assess the lead tester's suggestion to conclude testing early, and explain what should actually happen with the remaining three weeks of the mandated testing window.
正解：
解説：
See The answer in Explanation part below.
Explanation:
Step 1 - Recognise why the suggestion, though understandable, is methodologically incorrect. The lead tester's enthusiasm is understandable - achieving the primary objective undetected is a genuinely strong result - but the suggestion to end active testing three weeks early conflicts directly with TIBER-EU's minimum 12-week active testing guidance, which exists, as covered in the syllabus, for substantive methodological reasons (allowing realistic, patient adversary emulation and providing a genuine, sustained test of detection capability over a realistic timeframe), not merely as an arbitrary box to tick once any single objective is achieved.
Step 2 - Reject the "we've proven the point already" framing. Early achievement of the primary objective does not mean "nothing important is likely to change" - this framing significantly understates the value of the remaining time. As established elsewhere in this syllabus, a well-planned TIBER-EU engagement should have identified secondary, still-plausible attack paths (exactly as this scenario describes, with the cross-border reinsurance data-sharing scenario) precisely so that remaining time can be used productively rather than the exercise simply stopping once one objective is reached.
Step 3 - Do not unilaterally decide to end testing early. As Red Team provider lead contact, you should not agree to end active testing early based on your lead tester's operational preference (however reasonably intentioned, including the genuine desire to free up the team for other work) without this being a decision made transparently with the Control Team and, given TIBER-EU's minimum-duration guidance, very likely requiring at least awareness of the national TIBER Cyber Team, consistent with the syllabus principle that material deviations from framework timing guidance should not be decided informally by the delivery team alone.
Step 4 - Recommend pivoting to the secondary threat actor/attack path for the remaining weeks. The professionally sound recommendation is to use the remaining three mandated weeks productively by pivoting to explore the secondary, still-plausible threat actor and attack path (the cross-border reinsurance data-sharing scenario) that the original plan had specifically reserved time for - this makes full, valuable use of the mandated window, provides Larchmont with meaningfully broader insight beyond the single already-proven objective, and respects the framework's minimum-duration guidance in substance, not just in form.
Step 5 - Address the resourcing tension honestly rather than ignoring it. The lead tester's underlying point about wanting to free up the team for other engagements reflects a genuine resourcing/capacity consideration (echoing the concurrent-engagement management principle discussed elsewhere in this practice set), and this should not simply be dismissed - but the correct response is to raise this transparently with your own firm's resourcing/practice management function as a separate capacity planning conversation, rather than allowing it to unilaterally drive premature conclusion of a live, regulator-relevant engagement that has mandated timing requirements.
Step 6 - Communicate transparently with the Control Team about the strong early result and the plan for the remaining time. You should proactively inform the Control Team of the strong, undetected achievement of the primary objective (itself a significant, positive finding worth flagging promptly, consistent with the reporting domain's guidance on timely communication of significant developments) and explain the plan to use the remaining mandated weeks to explore the secondary, still-plausible scenario - giving the Control Team full visibility and the opportunity to input on or endorse this plan, rather than either silently continuing without explanation or silently stopping early without their knowledge.
Step 7 - Consider whether the strong result also has an earlier learning opportunity, without ending testing.
While full closure/purple-teaming should still occur only at the properly planned end of the Testing phase, you might also confirm with the Control Team whether they wish to be given a preliminary, high-level heads- up about the strength of the primary result now (while continuing testing on the secondary path) - a judgement call to be made collaboratively with the Control Team, balancing their interest in early insight against maintaining full engagement momentum and Blue Team blindness through to the properly planned closure point.
Conclusion: The lead tester's suggestion to end active testing three weeks early should not be accepted; the mandated minimum testing window should be used productively by pivoting to the secondary, still-plausible threat actor and attack path the original plan reserved time for, with this plan communicated transparently to the Control Team; and any genuine resourcing/capacity tension underlying the tester's suggestion should be addressed separately through the provider's own internal capacity management, not by cutting short a live, framework-governed engagement.
---
質問 # 18
......
すべての顧客の誠実な要件を考慮して、CCRTM-SCテスト問題は「品質第一とクライアント最高」の原則に沿って持続し、高品質の製品を豊富に備えた候補者に約束します。試験での99％の合格率、購入前の無料試用版など、CCRTM-SCトレーニング資料の多数の利点がよく知られています。お客様の観点から、当社のCCRTM-SCテスト問題では、すべての候補者の要求が最優先事項となっています。最適なCCRTM-SC模擬テストに対するお客様の信頼とフィードバックを大切にしています。
CCRTM-SC技術試験: https://www.goshiken.com/CREST/CCRTM-SC-mondaishu.html