Gary Richardson | SMF24 | Harpenden Building Society
Hiding in plain sight
Hiding in plain sight, their sheer scale can paradoxically obscure their true impact. When everything is interconnected, it becomes difficult to see the full picture. Welcome to technology, third‑party, and cyber risk - where countless dependencies, hidden pathways, and operational weak points sit quietly across your entire technology stack and supporting operations.
In short, these functional areas include ineffective architecture, technical debt, capacity issues, tech obsolesce, emerging tech disruption (including AI), cyber security, third party failures, data corruption, human capital shortages, and failure to deliver business requirements. The result is an untenable mix of gaps, duplication and missed opportunities - leading inevitably to greater exposure overall.
Financial services firms must navigate overlapping tech regulations. UK banks and building societies comply with GDPR / data protection rules and PRA / FCA operational resilience rules, including senior management systems and controls (SYSC) for IT risk management.
Regulators increasingly use enforcement tools for digital failings - such as Section 166 reviews for poor data governance and fines for weak cyber security under Principle 2. Global institutions also face cross-border challenges, e.g. ensuring trading apps meet the EU Digital Services Act and FCA conduct standards.
Approach
Where do you start? Before you can identify and assess the many risks in your organisation, you need to catalogue your capabilities. Understanding all that your organisation does with technology can help uncover where the risks lie. This requires having a governance framework in place that accounts for all technology, cyber and third party capabilities across the enterprise. The point is to forge a consensus on a working taxonomy that will serve as a foundation for identifying, assessing and managing related risk across the enterprise.
Reputable frameworks such as COBIT, ITIL, TOGAF, NIST and CQUEST can serve as a starting point, but it shouldn’t be a lift-and-shift and will require customisation and phased implementation. The goal is to implement a widely accepted mechanism for governing technology capabilities and aligning them to business priorities, processes, functions and infrastructure.
Once you’ve done this foundational work, you’ll be well-positioned to take meaningful action. But first things first. Understand the risk and its many forms, know where it lives and align on terminology for describing and categorising it.
Keep the framework current as it does little good if it hasn’t kept pace with the evolving technology and capabilities.
Why choose Green Dolphin
Please let us put you in touch with your peers at other building societies and banks so you can hear first hand how we've helped them assess and manage their technology risks.
Typical Green Dolphin Effort:
Design: 2 to 4 days
Implementation support: 8 to 10 days
Challenge
An SME bank was preparing to migrate its on‑premise infrastructure, systems, and APIs to a combination of Cloud Service Providers and new third‑party partners.
Recognising the scale and risk of the transformation, the Chief Operating Officer (COO) asked us to provide independent first line assurance to support the Technology and Change Team and the Head of Operational Resilience.
The bank needed confidence that the change was controlled, pitfalls avoided, and residual risk understood throughout the journey - particularly given ongoing regulatory scrutiny following several problematic change initiatives.
Approach
We worked alongside Technology, Operational Resilience, and Supplier Management teams as a critical friend, providing constructive challenge, proportionate support, and evidence‑led assurance.
Our work focused on:
We also used the proprietary Green Dolphin contract database to provide a commercial review of third‑party contracts and schedules. This complemented (but did not replace) legal review, focusing on areas such as payment milestones, remedies for under‑performance, change control, exit planning, and transparency of costs.
Throughout, our role was to challenge constructively while enabling safe, confident delivery.
Outcome
The bank gained a clear, independent view of the risks, controls, and supplier responsibilities underpinning its cloud transformation, giving the COO the confidence to demonstrate to the Board and Regulator that the migration was being governed and delivered safely.
Key outcomes included:
The COO was able to present a confident, defensible assurance position, showing that the transformation was well‑controlled and progressing with the right level of oversight.


Subscribe For Early Access👇🏼