
Adam Wenham | Founder & Managing Director, Garrison · 8 October 2026
The Bermuda Monetary Authority is no longer asking carriers about their cyber risk management. It is looking for itself.
The BMA's 2025 Operational Cyber Risk Management Report confirmed what the supervisory community has been signalling for two years: cyber risk is a "key supervisory priority" for 2026 and beyond. Filing return analysis is being used to profile individual insurers' cyber risk. And the BMA has said its cyber supervision in 2026 runs through filing return analysis and supervisory cyber risk on-site reviews.
Adding inspection to self-reporting changes the conversation entirely.
I spent four years at the Bank of England leading technology transformation and operational resilience, including DMZ architecture and cyber infrastructure remediation, and seventeen years at Credit Suisse delivering technology transformation across regulated environments. What follows is what I've learned about the gap between what boards report about cyber governance and what supervisors actually find.
The BMA's reports are not opinion pieces. They are drawn from filing return data submitted by every commercial insurer, insurance manager, and insurance agent and broker operating in Bermuda. The numbers paint a specific picture.
Ninety-seven per cent of entities report having a board-approved cyber risk policy. Ninety-nine per cent say they regularly communicate cyber risk updates to senior management and boards. Those headlines sound reassuring. The detail is less comfortable.
Twenty-one per cent of entities — roughly one in five — have not completed the classification of their data. Data classification is not an advanced capability. It is a foundational control: knowing what data you hold, how sensitive it is, and how it should be protected. Section 5.9 of the code requires information to be classified by value, legal requirements, sensitivity and criticality. A carrier that had not completed this three years after compliance was due, at the end of 2021, cannot meaningfully claim to be managing its cyber risk, regardless of what its board-approved policy says.
Third-party cyber risk management declined slightly in 2024. Eighty-six per cent of entities reported reviewing the cyber risks associated with outsourced IT providers in the past twelve months, down from eighty-seven per cent a year earlier. Among commercial insurers specifically, that figure dropped from ninety per cent to eighty-five per cent. In a market where outsourcing is the operational model, a decline in third-party cyber oversight is a decline in operational security.
Eighteen per cent of insurance agents and brokers did not test their business continuity and disaster recovery plans during the year. Section 7.1 of the code requires every registrant to test its business continuity and disaster recovery plans at least annually.
These numbers reveal a pattern I saw repeatedly inside the Bank of England and across large financial institutions: the governance layer is in place, but the operational substance behind it is thin.
A board-approved cyber risk policy is necessary but not sufficient. The policy is a document. What matters is whether the organisation has actually implemented the controls the policy describes.
The BMA's shift to on-site reviews will expose this gap. When a supervisor visits a carrier's office, they do not read the policy document and leave. They ask to see the evidence: the data classification register, the third-party risk assessment results, the BCP test report, the incident response exercise log, the board reporting pack that shows what was escalated and what was decided. The carriers that can produce this evidence will pass. The carriers that have policies without evidence will not.
Cyber risk does not exist in isolation. This is the point most carriers miss and most consultants fail to address.
The BMA's own regulatory structure makes the intersection explicit. Section 6.10 of the Insurance Sector Operational Cyber Risk Management Code of Conduct requires that personally identifiable information be handled in accordance with applicable privacy laws. A cyber breach is therefore simultaneously a potential PIPA violation — with fines of up to $250,000 for a company and a duty to notify the Privacy Commissioner without undue delay. A carrier that treats its cyber incident response and its PIPA breach response as separate processes will find itself managing two regulatory crises instead of one, with conflicting timelines and different reporting obligations.
The new Operational Resilience and Outsourcing Code adds a third dimension. A cyber event that disrupts an important business service is an operational resilience event. The carrier must demonstrate that it remained within its impact tolerances during the disruption, that it communicated appropriately with the BMA, and that its outsourced providers maintained their own resilience. Three regulatory instruments. One incident. Three different compliance obligations triggered simultaneously.
And as carriers adopt AI-powered tools for underwriting, claims processing, and risk assessment — as the BMA's August 2026 AI governance consultation anticipates — a fourth dimension emerges. A cyber compromise of an AI system is a cyber event, a potential PIPA breach (if the AI processes personal data), an operational resilience event (if the AI supports an important business service), and a potential AI governance failure (if the AI's outputs can no longer be trusted). Four regulatory domains, one incident.
The carriers that manage these domains in separate spreadsheets with separate teams will discover, during an actual incident, that their compliance frameworks are as siloed as their technology. The BMA's regulatory architecture is integrated. The carrier's response must be equally integrated.
The code is organised in three sections: identification of assets and risks, detect and protect controls, and response and recovery. Mapping the BMA's own data against five of its requirements shows where the sector stands.
Strong on paper. Ninety-seven per cent have approved policies. But board reporting quality is untested — the BMA's on-site reviews will assess whether boards receive actionable intelligence or generic assurance.
Most entities have one. Whether it is proportionate to their actual risk profile — rather than copied from a group parent or downloaded from a consultancy — is the question the BMA will ask.
This is where data classification sits. At twenty-one per cent non-compliance, the sector has a foundational gap that undermines everything above it. Without knowing what data you hold and how sensitive it is, you cannot meaningfully assess your cyber risk.
Declining. In a market built on outsourcing, this trend moves in the wrong direction. The new OpRes Code will amplify this requirement — carriers must now assess not just their third parties' cyber controls but their third parties' operational resilience under stress.
Untested at eighteen per cent of agents and brokers. For carriers, the question is not whether a plan exists but whether it has been exercised against a realistic scenario — and whether that exercise included the PIPA notification process, the BMA communication protocol, and the assessment of impact tolerance breach under the OpRes Code.
The BMA's supervisory focus on cyber risk will continue through 2026 and beyond. On-site reviews are happening now. Filing return analysis will identify carriers whose self-reported data reveals compliance gaps. The window for quiet remediation is closing.
Four actions boards should prioritise:
This is the single most visible compliance gap in the BMA's report. Every piece of data the carrier holds — policyholder information, claims data, underwriting models, financial records, employee records — should be classified by sensitivity and criticality, with controls commensurate to that classification. If this exercise is not complete, it should be the board's first directive.
Not a procurement review. An assessment of whether each critical third party — insurance managers, IT outsourcers, cloud providers, TPAs — has adequate cyber controls, tested incident response capabilities, and contractual obligations around breach notification. The OpRes Code now requires this assessment to extend to operational resilience, not just cyber hygiene.
Design a scenario that triggers all four regulatory domains simultaneously: a cyber breach that compromises personal data (PIPA), disrupts an important business service (OpRes), and affects an AI-enabled process (AI governance). Test whether the carrier's response framework handles all four obligations coherently, with consistent communication to the BMA. If it doesn't, that is the remediation priority.
The board should be receiving specific, evidenced reporting: what data has been classified and what remains outstanding, which third parties have been assessed and which have not, what scenarios have been tested and what the results showed. A board that receives only 'we are compliant with the code' is a board that will be surprised by the BMA's on-site findings.
As Appleby's cyber and IT security guide for Bermuda and EY's work on Bermuda cyber and privacy risk management both illustrate, the regulatory framework is maturing rapidly. The BMA's increasing supervisory investment in cyber risk — from filing return analysis to on-site reviews to the integration of cyber with operational resilience and AI governance — reflects a regulator that is building toward continuous, evidence-based oversight.
Carriers that respond to this by treating cyber governance as a genuine operational capability — not a policy document that sits in a drawer — will find themselves better prepared for every regulatory requirement that follows. The OpRes Code, PIPA, the AI governance framework — all of them depend on the same foundational controls: know your data, know your third parties, test your response, and report honestly to your board.
The BMA is already inside the network. The question is whether what they find matches what the board has been told.
Garrison · Hamilton, Bermuda · adam@garrison.re
Practitioner analysis, not legal advice. More at garrison.re/analysis
About the author. Adam Wenham is the founder of Garrison, a Bermuda firm that provides senior technology leadership to Bermuda's regulated firms: covering technology seats, running programmes, bringing in specialists and getting firms ready for the BMA's technology codes. He led technology transformation and operational resilience at the Bank of England, held senior roles across operations, engineering, architecture, innovation and change during seventeen years at Credit Suisse, and led the technology modernisation function at StoneX. At both Credit Suisse and StoneX he led the technology side of mergers and acquisitions. He began his career at Barclays, where he ran the technology for the move of BZW's 3,500-strong investment bank and its 1,300-position dealing room to Canary Wharf. adam@garrison.re