Correct Answer:

See The answer in Explanation part below.
Explanation:
Step 1 - Recognise the QA reviewer has identified a genuine reporting quality gap. Consistent with the reporting domain's principle that risk ratings should reflect genuine business impact and full context (not technical severity considered in isolation), the original draft's rating based purely on technical severity - while not factually inaccurate about the vulnerability itself - provides an incomplete picture by omitting the fact that Ellerslie's own detection and partial containment capability actually worked reasonably quickly. This omission risks either overstating the organisation's real residual risk (if containment was genuinely effective) or, just as importantly, failing to give Ellerslie credit for a detection/response capability that did function, which is itself valuable, actionable information about what is working, not just what is broken.
Step 2 - Revise the finding to reflect the full, accurate picture. The finding should be revised to include the complete, accurate narrative: the technical vulnerability and successful initial lateral movement (which remains a genuine, valid, significant finding warranting a high rating, since real access was achieved), alongside the factual detail that detection occurred within eleven minutes and partial containment within twenty-five minutes - and, critically, the further fact that the Red Team was able to continue limited activity afterward via a separate, undetected foothold, which is itself an important, distinct sub-finding about the limits of the partial containment action (it addressed one avenue but not a parallel one). This is not a case of softening the finding to protect the client's feelings (which would breach the objectivity principle discussed elsewhere in this practice set) - it is a case of correcting an incomplete draft to reflect the full, accurate, evidence-based picture, which happens to include both a genuine weakness (initial compromise, and a containment gap regarding the parallel foothold) and a genuine strength (reasonably fast detection and partial response) side by side.
Step 3 - Reassess the risk rating based on the complete picture, not simply lower it by default. The revised rating should be reached through fresh, honest analysis of the complete picture, not by mechanically downgrading the finding just because some detection occurred - the continued, undetected activity via the separate foothold means genuine residual risk remains significant, and the rating should reflect that reality accurately, whatever specific level that turns out to be, rather than either the original technical-severity-only inflation or an inappropriate deflation now that partial detection is known.
Step 4 - Thank and act on the QA reviewer's input as the system working as intended. This is a good, concrete illustration of why independent internal quality assurance review matters, as discussed in the governance domain: it caught a genuine, material gap in reporting completeness before the report reached the client, which is exactly its purpose - and you should treat this constructively as the QA process succeeding, not as criticism to be defensive about.
Step 5 - Address the Head of Finance's premature, informal awareness directly and promptly. The fact that partial, informal, and (per the scenario) somewhat alarming information ("the finance domain was compromised") has already begun circulating internally ahead of the planned closure briefing is a live communication risk that should not simply be left until the scheduled briefing date. Consistent with the syllabus principle on proactive, transparent client communication, you should raise this promptly with the Control Group: informing them that this partial information appears to have leaked informally and is causing some internal anxiety, and discussing whether an earlier, appropriately scoped, accurate communication to relevant stakeholders (potentially including a brief, factual clarification to the Head of Finance specifically, coordinated through the Control Group rather than delivered unilaterally by you) would help correct any premature or exaggerated impression before the full closure briefing, rather than allowing an inaccurate or incomplete picture to circulate and harden in the meantime.
Step 6 - Ensure any early clarification is accurate and consistent with the eventual full report, without pre- empting the formal briefing inappropriately. Any interim communication should be carefully calibrated:
accurate and reassuring where the facts genuinely support reassurance (e.g., confirming detection did occur reasonably quickly), while not overstating containment given the continued undetected activity finding, and should be coordinated with and approved by the Control Group rather than improvised informally, so that the eventual formal closure briefing remains consistent with, and simply elaborates on, what has already been accurately communicated.
Step 7 - Draw the broader lesson. This scenario illustrates two connected principles central to this domain:
that accurate, complete, properly-contextualised risk reporting (neither inflated nor artificially softened) depends on genuine independent quality assurance review catching gaps before delivery, and that proactive, honest, appropriately governed communication is essential not only in the formal report itself but throughout the closure period, especially once informal, partial information has begun to circulate and create anxiety that inaccurate rumour could otherwise make worse.
Conclusion: The finding should be revised to include the full, accurate context (both the genuine initial compromise and continued undetected activity, and the genuinely fast detection and partial containment), with the risk rating reassessed honestly on that complete picture rather than adjusted in either direction for the wrong reasons; and the Head of Finance's premature, informal awareness should be addressed promptly and transparently through the Control Group with an accurate, appropriately scoped interim clarification, rather than left unaddressed until the originally scheduled closure briefing.

Correct Answer:

See The answer in Explanation part below.
Explanation:
Step 1 - Analyse the authorisation's actual scope. The written authorisation covers systems "owned and operated by Corvane Insurance Group plc and its wholly owned UK subsidiaries." TrueClaim Systems Ltd is a separate legal entity that owns and operates the underlying claims portal infrastructure; Corvane merely licenses and customises the front end. On the facts given, TrueClaim's backend does not fall within the literal or reasonable interpretation of the authorised scope, because Corvane does not own or operate it and therefore has no authority to consent to its testing.
Step 2 - Apply the authorisation-boundary principle. As established throughout the syllabus, a client can only validly authorise testing of systems it owns or controls. Corvane's authorisation letter, however broadly worded, cannot extend legal cover to TrueClaim's infrastructure, because Corvane is not the party with authority to grant that permission. Testing TrueClaim's backend without TrueClaim's own separate, specific consent would risk unauthorised access under legislation such as the Computer Misuse Act 1990, exposing both the individual testers and the firm to potential criminal and civil liability, regardless of Corvane's own instructions.
Step 3 - Assess the IT manager's email. This email does not cure the authorisation gap, for two independent reasons: first, the IT manager is not shown to be a Control Group member or otherwise a person with the requisite authority to expand scope (the earlier syllabus material on authorisation specifically emphasises that authorisation must come from someone genuinely entitled to grant it); second, even full authority within Corvane could not authorise testing of infrastructure Corvane itself does not own, per Step 2. The informal, single-recipient nature of the email (no Control Group visibility) is itself a governance red flag consistent with the change-control principles covered elsewhere in the syllabus.
Step 4 - Correct action on TrueClaim. The team should not test TrueClaim's backend. The correct professional response is to decline politely, explain the authorisation-boundary issue to the IT manager, and escalate the request to the Control Group so it can decide, with TrueClaim's own consent obtainable and documented if genuinely desired, whether and how to pursue an amended, properly authorised scope covering that platform's backend (likely requiring TrueClaim's own testing policy or explicit sign-off).
Step 5 - Handle the personal Gmail discovery. The underwriter's personal Gmail account is not Corvane's system, and Corvane cannot authorise its testing or access - the earlier syllabus material on this exact issue (an employer cannot authorise access to accounts it does not own or control) applies directly. Your team must not attempt to access, further investigate, or exploit that Gmail account. However, the fact that a policy violation is occurring (sensitive client data being routed through an unauthorised personal account) is a genuine, relevant finding about Corvane's data handling practices and control environment. The proportionate, correct action is to report the existence and nature of this control weakness (a policy compliance/data handling gap) to the Control Group through the normal escalation and reporting channel - without extracting, reviewing, or retaining the content of the account itself - so Corvane can address the underlying process failure. This also touches data protection considerations: any personal data about the underwriter or their account incidentally learned should be handled under data minimisation principles and not gratuitously retained or elaborated upon beyond what substantiates the finding.
Step 6 - Address the IT manager's direct-contact governance issue. Beyond declining the specific request, this incident should itself be flagged to the Control Group as a governance/communication issue: it suggests scope and authorisation boundaries may not be well understood by staff outside the Control Group, and it indicates a channel-control gap (a non-Control Group individual attempting to informally direct testing activity). Best practice is to remind the Control Group of the importance of channelling all scope-related requests through the agreed escalation path, and to consider whether wider internal communication about the engagement's boundaries (calibrated so as not to compromise Blue Team blindness) is warranted.
Conclusion: Neither the written authorisation nor the IT manager's informal email extends legal cover to TrueClaim's infrastructure; the Gmail discovery must be reported as a control weakness without accessing the account itself; and both issues should be escalated transparently to the Control Group, with the direct-contact incident treated as a standalone governance concern.
---