A cyber insurance policy is often bought on the strength of a headline limit and a premium. Rarely is it read against the obligations a breach would actually trigger. For organisations in the Kingdom, those obligations include the Personal Data Protection Law (PDPL), overseen by SDAIA, with its notification duties and its timelines. A cyber insurance policy review for PDPL asks a plain question: when notification, investigation and recovery costs arrive on the schedule the law sets, does the policy respond, and on what terms?
This article describes how we run that review in four phases, who takes part on your side, and what you hold at the end of each. It is written for CFOs, risk managers and board members who need to decide whether the policy they hold is the policy they need.
What the review is, and what it is not
Our Cyber Insurance Coverage Review is a broker-neutral review of your cyber policy against your actual risks: limits, sub-limits, retentions, waiting periods, exclusions and conditions. The assessment takes 2–3 weeks.
It is not legal advice. It is a technical and risk review, and your legal and broker advisers remain responsible for policy interpretation. We read the wording as risk practitioners and flag where it needs their attention.
The review follows four steps: collect, model, compare and advise. We organise them here into four phases that suit a PDPL-focused engagement, each ending in a gate where you receive something concrete.
Phase 1: The PDPL breach-notification clause audit
What happens. We collect the policy wording, the schedule and every endorsement. Then we read the notification-related provisions against what the PDPL expects when personal data is breached: notice to the regulator, notice to affected individuals where required, and the timelines that apply. We look at how the policy defines a covered event, when it requires you to notify the insurer, whether it expects insurer consent before you spend, and whether any panel or vendor requirements could slow your response.
The question at this phase is whether the policy's own clock and conditions fit the legal clock. A policy that demands prior approval for forensic work, for example, can sit awkwardly beside a short regulatory deadline.
Who takes part on your side. The risk manager or insurance owner supplies the documents. Someone from legal or the data protection function joins a working session to confirm how your organisation interprets its notification duties. Your broker may attend to clarify wording intent.
What you hold at the end. A clause-by-clause audit of the notification and claims-conditions wording, with each point marked as aligned, unclear or in conflict with your PDPL obligations. Points that need legal interpretation are marked for your advisers rather than resolved by us.
Phase 2: Sub-limit reconciliation
What happens. A large aggregate limit can hide small sub-limits. We extract every sub-limit, retention and waiting period, then set them beside the cost lines a breach produces: forensic investigation, notification and call-handling, legal support, regulatory response and business interruption. We model your top cyber loss scenarios so the comparison rests on your situation rather than generic assumptions.
Where you already hold quantified estimates, we use them. Where you do not, our Cyber Risk Quantification for Insurance service estimates the financial impact of your most likely and most severe scenarios, so limits and retentions rest on numbers the board can trust.
Who takes part on your side. The CFO or finance lead, who knows what a retention means for cash and the balance sheet, and the risk manager. The CISO or security lead helps describe how each scenario would unfold.
What you hold at the end. A reconciliation showing, per scenario, which cost lines are covered, which are capped by a sub-limit, and where the retention or waiting period would leave you carrying the early cost. This is the first view of the scenario-to-coverage map.
Phase 3: The exclusion scenario test
What happens. Exclusions decide claims. We take the scenarios from Phase 2 and test them against the exclusions and conditions in the policy, using your architecture as the reference. If a scenario involves a third-party processor, a legacy system, or a delayed patch, we check whether an exclusion or a condition could apply. We pay particular attention to conditions that could void a claim, such as security-control warranties that your environment might not meet in practice.
For each scenario we compare coverage, limits and exclusions, and record the outcome in plain language.
Who takes part on your side. The CISO or head of IT, who can confirm how systems and controls are really configured, and the risk manager. We ask for a technical walk-through, not a policy attestation.
What you hold at the end. The completed scenario-to-coverage map, showing for each top scenario what responds, what is limited, and what is excluded or conditional. You also have a list of conditions that could put a claim at risk.
Phase 4: The board-ready gap summary
What happens. We turn the findings into advice: the gaps, and the points to raise at renewal. The summary is written for directors, not for underwriters. It states what the policy covers, what it does not, and what the organisation would bear on its own in each scenario. It also carries the questions to put to your broker and insurer.
Because the review also draws on the SAMA Cyber Security Framework, financial-sector clients can see how coverage conditions sit alongside their supervisory obligations. If you are comparing quotes, we can compare them side by side against the same scenarios.
Who takes part on your side. The CFO and risk lead review the draft first. The summary then goes to the board or its risk committee, with the CISO and your legal and broker advisers available for questions.
What you hold at the end. A coverage gap report and a set of renewal negotiation points, ready for a board paper and for the renewal conversation.
What you hold at the end of week three
The assessment runs 2–3 weeks. At the close you hold:
- A coverage gap report covering limits, sub-limits, retentions, waiting periods, exclusions and conditions.
- A scenario-to-coverage map for your top cyber loss scenarios.
- The PDPL notification-clause audit, with items marked for legal review.
- A list of conditions that could void a claim.
- Renewal negotiation points and questions to raise with your broker and insurer.
Where to go next
If you are approaching renewal, or have never mapped your policy to the PDPL obligations a breach would trigger, the Cyber Insurance Coverage Review is the place to start. Where the question is how to present your risk to underwriters, our Cyber Insurance Readiness Assessment covers that separately. Contact us to scope a review against your policy and your top scenarios.