Case 09

Risk Escalation Memo

Scenario

You lead third-party risk at Meridian Bank. A key payments vendor has missed two security patch deadlines and has not answered your letters. Policy says repeated breaches go to the Chief Risk Officer in writing.

Why this framework

Uses full PINPOINT because the consequence is higher: adds a professional stance, examples, self-checks, your own review before use, and a plan to tweak and test.

Example context

Invented example. All events are in 2026. Vendor: 'Harbourline Data Services' (classed as a critical vendor), hosting a customer records archive for a UK mid-sized insurer. Contract clause 12.3: vendor must notify of any security incident within 72 hours; clause 18.1: customer may terminate for repeated material breach after 30 days' written notice. Third-party risk policy section 4.2: any missed notification on a critical vendor must be escalated to the Chief Risk Officer within 5 working days; section 4.5: a time-limited exception of up to 90 days may be granted with a remediation plan. Email log: 3 Sep vendor emails that a misconfigured storage bucket was exposed 28 Aug to 1 Sep; 4 Sep our security team replies asking for detail; 5 Sep our security team chases for detail; 7 Sep vendor says analysis is under way; 9 Sep vendor confirms the bucket was secured on 1 Sep, which is when the exposure ended; 10 Sep vendor sends root-cause note; 12 Sep vendor apologises and offers a remediation plan. The vendor's root-cause note states it first became aware of the exposure on 29 Aug. This is the first notification failure by this vendor; the one earlier incident (March) was notified on time. The failure has not been escalated to the CRO before; this memo is the first escalation and is being written on 14 Sep 2026. No evidence in the emails that data was accessed externally.

Prompt

Purpose: Draft an escalation memo to the Chief Risk Officer so they can decide whether to trigger the vendor exit clause or grant a time-limited exception.

Context: Use the attached vendor contract, our third-party risk policy and the email log. The policy is the final word on what must be escalated and when. Do not describe the vendor's intentions beyond what the emails say.

Narrow the ask: One page. Sections: what happened, what the contract and policy say, the options with what each would involve, and the decision needed with a date. Neutral tone. Stop and ask me if the email log has gaps in dates.

Persona and role: Write as a careful second line risk professional. Fair to the vendor, clear about our obligations, no alarmism.

Check your work: For each material claim, label it as [Verified Source], [Inference], [Assumption], or [Unverified]. Cite the source where available. If an unverified or assumed point could materially change the conclusion, flag it for review rather than guessing. Quote the exact contract and policy clauses you rely on.

Before I use it: I will confirm the clause references and dates against the originals and have Legal read the options before sending.

If the first draft misses the mark, I will change one thing at a time, starting with the options section.

Materials (pasted here in place of the attachments):
Invented example. All events are in 2026. Vendor: 'Harbourline Data Services' (classed as a critical vendor), hosting a customer records archive for a UK mid-sized insurer. Contract clause 12.3: vendor must notify of any security incident within 72 hours; clause 18.1: customer may terminate for repeated material breach after 30 days' written notice. Third-party risk policy section 4.2: any missed notification on a critical vendor must be escalated to the Chief Risk Officer within 5 working days; section 4.5: a time-limited exception of up to 90 days may be granted with a remediation plan. Email log: 3 Sep vendor emails that a misconfigured storage bucket was exposed 28 Aug to 1 Sep; 4 Sep our security team replies asking for detail; 5 Sep our security team chases for detail; 7 Sep vendor says analysis is under way; 9 Sep vendor confirms the bucket was secured on 1 Sep, which is when the exposure ended; 10 Sep vendor sends root-cause note; 12 Sep vendor apologises and offers a remediation plan. The vendor's root-cause note states it first became aware of the exposure on 29 Aug. This is the first notification failure by this vendor; the one earlier incident (March) was notified on time. The failure has not been escalated to the CRO before; this memo is the first escalation and is being written on 14 Sep 2026. No evidence in the emails that data was accessed externally.

Example output from ChatGPT

The email log contains no obvious gaps in the sequence of dated communications. However, the precise date on which the missed-notification breach was first recognised internally is not established. This could affect the policy escalation deadline, so I have flagged it rather than assumed it.

Writing Confidential - CRO Escalation Memo

To: Chief Risk Officer From: Second Line Risk Date: 14 September 2026 Subject: Harbourline Data Services - Security Incident Notification Breach Decision required: Vendor exit pathway or time-limited exception

  1. What happened

[Verified Source - Email log] Harbourline Data Services, a critical vendor hosting customer records, reported on 3 September that a storage bucket had been exposed from 28 August to 1 September 2026.

[Verified Source - Root-cause note, 10 September] The vendor became aware of the exposure on 29 August but did not notify the insurer until 3 September.

[Verified Source - Email log] Security requested further details on 4 and 5 September. The vendor provided an interim update on 7 September, confirmed containment on 9 September, supplied a root-cause note on 10 September, and apologised and offered remediation on 12 September.

[Verified Source - Supplied incident history] This is the first notification failure. The previous March incident was notified on time. No evidence of external data access is recorded in the emails; absence of access has not been established.

  1. Contract and policy requirements Provision Supplied clause wording and assessment Contract 12.3 [Verified Source - Supplied clause summary] "vendor must notify of any security incident within 72 hours". [Inference] Notification occurred approximately five days after awareness, exceeding 72 hours. Contract 18.1 [Verified Source - Supplied clause summary] "customer may terminate for repeated material breach after 30 days' written notice". [Inference] The available history does not establish repeated material breach. Policy 4.2 [Verified Source - Supplied policy summary] "any missed notification on a critical vendor must be escalated to the Chief Risk Officer within 5 working days". [Inference] If identified on 3 September, escalation was due by 10 September. This memo, dated 14 September, would be late. Policy 4.5 [Verified Source - Supplied policy summary] "a time-limited exception of up to 90 days may be granted with a remediation plan".
  2. Options for decision

Option A - Initiate contractual exit assessment

[Inference] Request Legal's assessment of whether clause 18.1 is exercisable, including the repeated-material-breach requirement.

If legally supported, issue the required written notice and coordinate archive migration, data protection and service continuity.

Risk: Contractual eligibility is not established; exit may introduce operational disruption.

Option B - Grant a time-limited exception

[Inference] Approve a conditional exception, not exceeding 90 days, subject to an accepted remediation plan, named owner, milestones and independent validation.

Require evidence of containment, investigation of possible data access, strengthened incident notification controls and regular reporting to Risk.

Risk: Continued vendor exposure and remediation failure; defined escalation triggers are needed.

  1. Decision required - 14 September 2026

[Inference - Proposed course] Seek CRO approval to pursue Option B, conditional on satisfactory remediation and monitoring, while Legal assesses whether an exit right is available.

Matters requiring confirmation before approval:

[Unverified] Internal identification date and whether policy 4.2's escalation deadline was breached.

[Unverified] Whether external access occurred and whether further security or regulatory obligations arise.

[Unverified] Material-breach classification, contractual termination eligibility and adequacy of the proposed remediation plan.

Decision requested by 14 September 2026, or the next available CRO decision point if same-day approval is impracticable.

Source limitation: The material provides clause summaries, not the full contractual or policy text. The quoted wording above reproduces the supplied summaries exactly, but cannot be certified as verbatim contractual language. Legal should confirm the original wording, the termination threshold, and the appropriate decision route before issue.

Key risk judgement: The strongest established finding is the late security-incident notification. The evidence does not yet establish a contractual right to terminate for repeated material breach. The escalation timing also requires verification, because the internal recognition date is not recorded.