Sample Tender Response Extract

Risk Management

Contracting Authority NorthBridge Building Society (UK)
Service Cloud cybersecurity monitoring service (24/7 SOC, SIEM, EDR integration, threat detection and response)
Question

Identify the key risks to delivering and operating the cloud cybersecurity monitoring service and explain how they will be managed and mitigated, including ownership and escalation.

Word Limit: 700 words
Response 700 words

1. Understanding of the risk context

For a regulated financial services environment, the main risk is not "an alert being missed"; it is a security event becoming a customer-impacting incident because detection, triage, or containment is delayed or inconsistent. The service must therefore control operational risks (process, coverage, skills, handover) as tightly as technical risks (telemetry, configuration, access, tooling). We also recognise the dependency risk: our monitoring is only as good as the data sources and the authority we have to act when something is found.

We manage risk through a live risk register, reviewed weekly during mobilisation and monthly thereafter, with clear owners and evidence-based mitigations. High and critical risks are escalated through a defined governance framework to the Authority's Security Lead and our SOC Service Manager.

2. Key risks and mitigations (with ownership)

Risk 1: Incomplete telemetry and log coverage
Description If cloud audit logs, identity logs, endpoint telemetry, and key SaaS logs are not ingested (or are sampled inconsistently), detections will be blind to material activity.
Mitigation We run a "minimum viable visibility" checklist during mobilisation covering cloud control plane logs, IAM events, endpoint events, network telemetry (where available), and critical SaaS (e.g., email/collaboration). We validate ingestion by replay testing and coverage dashboards, with priority sources visible in the SIEM within 5 minutes for ≥95% of events.
Owner Our Technical Lead (delivery); Authority Cloud Platform Lead (access and enabling)
Risk 2: Poor detection fidelity causing alert fatigue
Description Excessive false positives lead to missed true positives and slow response.
Mitigation We tune detections in stages: baseline (week 1–2), targeted tuning (weeks 3–6), then monthly optimisation. We set severity definitions with the Authority and enforce suppression rules only with documented rationale. We measure alert quality (validated true positives/triaged), mean time to triage and triage volume per analyst-hour.
Owner Our SOC Lead
Risk 3: Unclear incident authority and slow containment
Description If it is not agreed who can isolate devices, disable accounts, or block tokens, containment will be delayed.
Mitigation We agree an incident playbook and RACI for each incident type (identity compromise, ransomware indicators, data exfiltration, privileged access misuse). We pre-authorise containment actions for high-severity scenarios, including out-of-hours contacts and on-call escalation.
Owner Authority CISO (decisions) and our Incident Manager (execution coordination)
Risk 4: Privileged access misuse (supplier or internal)
Description Monitoring services require elevated access; misuse or compromise creates a direct pathway to harm.
Mitigation We use least-privilege roles, just-in-time access, MFA, and named accounts (no shared credentials). Access is time-bound and logged. We provide a monthly privileged access report and support spot checks.
Owner Our Service Manager and Authority IAM Owner
Risk 5: Data residency and regulatory non-compliance
Description Misalignment on data processing locations, retention, or handling could create compliance issues and audit findings.
Mitigation Data processing is documented in the DPA under our ISO 27001-certified ISMS, with retention schedules, encryption requirements and sub-processor listing. We support DPIA and provide evidence packs for audits (controls, access logs, change records).
Owner Our Information Security Officer; Authority Compliance Lead
Risk 6: Service continuity and skills resilience
Description Reliance on named individuals or single shift teams increases operational fragility.
Mitigation We operate a 24/7 rota with skills matrix coverage, documented runbooks, and handover checks. We test continuity quarterly (simulated tool outage / staff unavailability) and record corrective actions.
Owner Our SOC Operations Manager

3. Monitoring, escalation and reporting

We will report monthly against agreed KPIs: mean time to detect, mean time to triage, mean time to contain (or time to issue containment instructions where the Authority executes), log source coverage, and high-severity incident counts with lessons learned. Any Critical incident triggers immediate escalation to the Authority within 15 minutes of validation, followed by hourly updates until contained, then a root cause analysis within five working days.

4. Added value

We will run two tabletop exercises per year (e.g., identity compromise; ransomware precursor activity) to validate playbooks, contacts, and decision rights. Outputs are action-focused and tracked in the service improvement plan.

Back to Bid Writing Samples