Wir hoffen, dass sich alle Ihrer in der CREST CCRTM-SC Prüfungssoftware gesetzten Erwartungen erfüllen können. Die Vollständigkeit und Autorität der Test-Bank, Vielfältigkeit der Versionen von Unterlagen---- Es gibt 3 Versionen, nämlich PDF, Online Test Engine und Practice Testing Engine, und auch die kostenlose Demo und einjährige Aktualisierung der CREST CCRTM-SC Software, alles enthält unsere herzlichste Anstrengungen!
| Section | Objectives |
|---|---|
| Red Team Engagement Management | - Threat Intelligence Interpretation & Application
|
>> CCRTM-SC Zertifikatsdemo <<
Die CREST CCRTM-SC Zertifizierungsprüfung ist eine sehr populäre Prüfung. Obwohl es sehr schwierig zu bestehen ist, können Sie diese Prüfung leichter bestehen, wenn Sie die richtige Methode finden. Und Wir ZertPruefung sind Ihre beste Wahl. Mit der 100%-Hitrate Prüfungsunterlagen von ZertPruefung können Sie alle Probleme in der CREST CCRTM-SC Zertifizierungsprüfung auslösen. Wenn Sie die Prüfungsfragen und Testantworten ernst lernen, gibt es keine Probleme für Sie. Und nach dem Kauf können Sie einjährigen kostlosen Aktualisierungsservice bekommen. (innerhalb einem Jahr) Sie können über die gewünschten CREST CCRTM-SC Schulungsunterlagen beherrschen, wenn Sie auf jeden Fall die neueste Version bekommen. Probieren Sie sofort, bitte.
17. Frage
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.
Antwort:
Begründung:
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.
---
18. Frage
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.
Antwort:
Begründung:
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.
---
19. Frage
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.
Antwort:
Begründung:
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.
---
20. Frage
Background: You manage an engagement for Copperfield Manufacturing Group. The signed RoE contains a standard clause prohibiting "destructive attacks or any activity likely to cause denial of service to production systems," and separately lists specific named systems explicitly excluded from all testing, including a legacy order-processing system described in the exclusion list as "critical, fragile, do not interact with under any circumstances." During reconnaissance, your team discovers that a separate, in-scope customer-facing web application shares a backend database server with the excluded legacy order-processing system - a fact not previously known to either your team or, it emerges when you raise it, to Copperfield's own IT team, who believed the two systems had been fully separated during a migration project two years earlier that was, in fact, only partially completed.
Exploiting a vulnerability in the in-scope web application would very likely provide database-level access that could technically reach the excluded legacy system's data, even though the web application itself is legitimately in scope.
Question: Explain how you should handle this discovery, addressing both the immediate technical/operational decision and the broader governance implications, including what this reveals about the client's own understanding of its environment.
Antwort:
Begründung:
See The answer in Explanation part below.
Explanation:
Step 1 - Recognise this as a direct, high-stakes scope-boundary and safety issue. This is a serious situation: a legitimately in-scope system provides a technical path that could reach an explicitly, emphatically excluded system ("do not interact with under any circumstances") that the client itself believed was already isolated.
Proceeding with full exploitation of the in-scope web application without addressing this discovery first would create a genuine, material risk of inadvertently affecting the excluded fragile legacy system - precisely the outcome the exclusion was designed to prevent.
Step 2 - Pause before proceeding further on this specific path. Consistent with the syllabus principle on discovering unplanned pivot paths toward out-of-scope systems, your team should pause any further exploitation activity on the in-scope web application that could plausibly reach the shared backend database, rather than proceeding on the basis that the web application itself is technically in scope - the relevant risk here is the downstream reachability of the excluded system, not merely the starting point's scope status.
Step 3 - Escalate immediately and clearly to the Control Group. This discovery must be escalated promptly and clearly to the Control Group, explaining precisely what has been found: that the excluded legacy system is not, in fact, isolated as previously believed, and that a legitimately in-scope system provides a plausible technical path to it. This is exactly the kind of significant, safety-relevant scope discovery that requires an explicit Control Group risk decision before any further related activity proceeds, consistent with the syllabus's repeated emphasis on escalating rather than unilaterally resolving scope-boundary ambiguities, especially ones with genuine safety/fragility implications.
Step 4 - Present the Control Group with realistic options, not just a problem. You should help the Control Group understand the realistic options: (a) proceeding with carefully scoped, closely controlled activity that demonstrates the reachability risk without actually interacting with the excluded system's own data or functionality (e.g., demonstrating database-level access is achievable in principle, using a proof-of-concept approach analogous to the "create and remove a labelled test artefact" principle discussed elsewhere in this practice set, without ever querying or touching the legacy system's actual tables/data) - an approach that could deliver highly valuable risk insight while respecting the spirit of the exclusion; (b) excluding further technical demonstration of this specific path altogether and instead documenting the newly discovered reachability as a critical, urgent finding in its own right, given its significance; or (c) if the Control Group wishes to genuinely understand the full extent of exposure, formally and explicitly amending the exclusion (with appropriate additional risk controls and stakeholder sign-off, given the legacy system's described fragility) to permit carefully controlled, limited investigation - a significant decision that should not be made lightly or without input from whoever owns/understands the fragile legacy system best.
Step 5 - Treat the discovery itself as an urgent, high-value finding regardless of what testing path is chosen.
Independently of how (or whether) further technical demonstration proceeds, the fact that the client's own assumption about system isolation was incorrect is itself an extremely significant finding that should be communicated to the Control Group with urgency, given its potential relevance well beyond this engagement (e.g., to the client's own ongoing operational risk management, patching, and architecture decisions) - this is exactly the kind of urgent, severe finding that, per the reporting domain, should be escalated promptly rather than held until the final report.
Step 6 - Reflect on what this reveals about the client's own environment understanding, and note it explicitly. This discovery reveals a genuine, material gap between the client's assumed architecture (systems fully separated) and its actual, current-state architecture (a partially completed migration leaving a shared backend) - a gap the client's own IT team was unaware of until your team's reconnaissance surfaced it. This is valuable, standalone insight for the client about the reliability of its own architecture documentation and change-management assurance processes, and should be explicitly reflected in your reporting/closure commentary as a broader lesson, not just narrowly treated as a scoping technicality to be resolved and then forgotten.
Step 7 - Document the whole episode thoroughly. The discovery, the escalation, the Control Group's decision, and the rationale should all be clearly and contemporaneously documented, both to protect the integrity of the engagement's record and because this kind of significant, safety-relevant scope discovery is precisely the sort of event most likely to be scrutinised later if any question about the engagement's conduct ever arose.
Conclusion: Further exploitation activity on the path toward the excluded legacy system should pause immediately upon discovery, with prompt escalation to the Control Group presenting realistic options ranging from carefully controlled, non-intrusive demonstration to full exclusion of further technical activity on that path; the discovery itself should be treated and escalated as an urgent, high-value finding in its own right; and the episode should be explicitly used to highlight, in reporting, the client's own gap between assumed and actual system architecture as a valuable standalone lesson.
---
21. Frage
Background: You are the Red Team Manager on a CBEST-style engagement for Rowanmere Building Society. The Control Group consists of the CISO (chair), the Head of Operational Resilience, and the General Counsel. In week 3 of an 8-week Red Team testing phase, you receive an unusual, unscheduled email from the Head of IT Operations (not a Control Group member) stating: "I heard through a colleague that there's some kind of security exercise happening - is this you? If so, please stop targeting the payments infrastructure team specifically, they're stretched thin this month with a system migration." The email is polite but clearly indicates the Blue Team, or at least part of it, may have become aware of the exercise.
You also separately learn, through your own team's monitoring of the engagement's dedicated inbox, that the CISO forwarded a summary of "upcoming testing activity, including likely timing" to the Head of IT Operations two weeks earlier "so he wouldn't panic if he noticed anything odd," without informing the rest of the Control Group of this decision.
Question: Assess the significance of these two developments for the integrity of the engagement, and set out the steps you should take as Red Team Manager, including how you would engage the Control Group.
Antwort:
Begründung:
See The answer in Explanation part below.
Explanation:
Step 1 - Correctly diagnose the core problem. The central issue is that the Blue Team's blindness - the foundational methodological control that makes an intelligence-led exercise like this a genuine, valid test of detection and response - has been compromised, apparently by the CISO's own unilateral, undocumented decision to pre-warn the Head of IT Operations. This is not a minor administrative slip; it strikes at the exercise's core validity, since the very rationale for keeping the Blue Team unaware (discussed extensively in the syllabus) is to obtain an honest, unprimed measurement of real detection and response capability.
Step 2 - Assess the scope of the compromise. You need to establish, as precisely as possible, what the Head of IT Operations was actually told (timing, targeting detail, or just "something is happening"), how widely that information may have already spread within his team or beyond (the second email - asking you to avoid a specific team - suggests some further, second-hand awareness may already exist), and whether any observed Blue Team behaviour so far in the engagement may already have been influenced by this foreknowledge, which would need to be factored into how you interpret results to date.
Step 3 - Do not respond directly to the Head of IT Operations substantively. While a brief, non-committal acknowledgement may be unavoidable, you should not confirm engagement details, adjust targeting, or engage in further substantive discussion with him directly - doing so would compound the breach and further blur the Control Group/Blue Team segregation this entire framework depends on. Any response should be deferred to, and coordinated through, the Control Group.
Step 4 - Escalate promptly and transparently to the full Control Group. This is precisely the kind of significant governance issue that must be raised with the full Control Group without delay, including the General Counsel and Head of Operational Resilience, not resolved unilaterally between you and the CISO alone (especially since the CISO is implicated in the breach). The conversation should cover: what actually happened, the assessed extent of compromise, and - critically - an honest, non-defensive discussion of why the normal escalation/decision process was bypassed, since preventing recurrence requires understanding why it happened.
Step 5 - Jointly assess options for the path forward. Depending on the assessed extent of compromise, the Control Group (informed by your professional advice) will need to decide among options such as: continuing testing with a documented caveat about potential Blue Team awareness affecting result interpretation from a certain point onward; formally accepting the Head of IT Operations (and possibly his direct team) into a limited "informed" status for the remainder of the engagement, adjusting objectives accordingly (e.g., shifting remaining focus toward areas of the estate genuinely unaffected by the leak); or, in a more severe case, considering whether elements of the test need to be repeated later, once the Control Group is confident blindness can be properly re-established elsewhere in the environment. There is no single universally
"correct" choice - the right answer depends on the assessed severity, and the model answer should demonstrate that the candidate understands this is a risk-based Control Group decision, not a unilateral technical one.
Step 6 - Address the process failure itself. Beyond fixing the immediate compromise, the Control Group needs to address the underlying governance failure: an individual Control Group member unilaterally sharing sensitive engagement information outside the group, without documentation or collective decision-making.
This should be discussed directly and professionally (not punitively) with the CISO, and the Control Group's own operating norms (e.g., explicit agreement that no member shares engagement information externally without collective sign-off) should be reinforced and, ideally, documented for the remainder of this and future engagements.
Step 7 - Document everything. The incident, the Control Group's discussion, the options considered, and the final decision should all be clearly documented, both to preserve a clean audit trail for any eventual reporting
/attestation and to support honest lessons-learned review at closure.
Conclusion: This scenario centres on a serious, self-inflicted breach of Blue Team blindness by a Control Group member; the correct response is prompt, full, transparent escalation to the whole Control Group (not unilateral action or side-conversation with the individuals involved), a risk-based joint decision on how to adapt the remaining engagement, and a deliberate fix to the Control Group's own internal information-sharing discipline.
---
22. Frage
......
Vielleicht können Sie auch die relevanten CREST CCRTM-SC Schulungsunterlagen in anderen Büchern oder auf anderen Websites finden. Aber wenn Sie die Produkte von ZertPruefung mit ihnen vergleichen, würden Sie herausfinden, dass unsere Produkte mehr Wissensgebiete umfassen. Sie können auch im Internet teilweise die Fragen und Antworten zur CREST CCRTM-SC Zertifizierungsprüfung kostenlos herunterladen, so dass Sie die Qualität unserer Produkte testen können. Die Gründe, dass ZertPruefung exklusiv umfassende Materialien von guter Qualität bieten können, liegt darin, dass wir ein exzellentes Expertenteam hat. Sie bearbeiten die neuesten Fragen und Antworten zur CREST CCRTM-SC Zertifizierungsprüfung nach ihren IT-Kenntnissen und Erfahrungen. Deshalb sind die Fragen und Antworten zur CREST CCRTM-SC Zertifizierungsprüfung von ZertPruefung bei den Kandidaten ganz beliebt.
CCRTM-SC Prüfungsfragen: https://www.zertpruefung.ch/CCRTM-SC_exam.html